Bug 424 - Crash with ATi Radeon Mobility 7500
Summary: Crash with ATi Radeon Mobility 7500
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: PowerPC Linux (All)
: high major
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-07 18:35 UTC by Nathan Robertson
Modified: 2004-04-07 19:47 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg log from the crash (15.99 KB, text/plain)
2004-04-07 18:37 UTC, Nathan Robertson
no flags Details
dmesg from box in question (6.69 KB, text/plain)
2004-04-07 18:37 UTC, Nathan Robertson
no flags Details

Description Nathan Robertson 2004-04-07 18:35:23 UTC
The following is from a bug I reported at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119020

---------------------------------

Using a known to be good XF86Config (taken off my Yellow Dog Linux
install, which has XFree86 4.3.0), xorg crashes with the following
message:

[...]
(II) Setting vga for screen 0.
(II) RADEON(0): MMIO registers at 0xb0000000
 
Fatal server error:
xf86MapVidMem: Could not mmap framebuffer (0xb0000000,0x80000) (Bad
address)

I'm running Arjan's latest ppc kernel (2.6.4-1.279), which has the new
Radeon framebuffer driver in it (which I'm using).


Version-Release number of selected component (if applicable):
xorg-x11-0.0.6.6-0.0.2004_03_11.6
Comment 1 Nathan Robertson 2004-04-07 18:37:13 UTC
Created attachment 179 [details]
xorg log from the crash
Comment 2 Nathan Robertson 2004-04-07 18:37:52 UTC
Created attachment 180 [details]
dmesg from box in question
Comment 3 Mike A. Harris 2004-04-08 12:47:35 UTC
Arjan van de Ven has tracked this down to being a kernel bug in his kernel,
and has fixed it.  Closing bug as FIXED as per the Red Hat bugzilla
report comment from Arjan.

Thanks for reporting the issue.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.