Bug 151636 - ATI ES1000, Radeon 7000 System Hang due to inproper memory access, SERR generated.
Summary: ATI ES1000, Radeon 7000 System Hang due to inproper memory access, SERR gener...
Status: RESOLVED DUPLICATE of bug 151631
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: X.Org (show other bugs)
Version: unspecified
Hardware: i386 SLES 10
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-16 22:10 UTC by Rod Macdonald
Modified: 2006-02-22 15:38 UTC (History)
5 users (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rod Macdonald 2006-02-16 22:10:00 UTC 
This bugzilla is opened on behalf of Dell.  This Sev 1 problem has been observed on RHEL 4 and should also affect SLES 10.  

Detailed description:  https://bugs.freedesktop.org/show_bug.cgi?id=3911

The fix described above might be replaced with a more comprehensive fix which also addresses the problem in SuSE Bug 151631.  More information:  https://bugs.freedesktop.org/show_bug.cgi?id=5916
Comment 1 Stefan Dirsch 2006-02-16 22:44:00 UTC 
I think this problem has already been adressed by the patch in Bug #150146, correct?
Comment 2 Egbert Eich 2006-02-17 09:21:22 UTC 
This looks more like Bug #127757. This one addresses the FB location.
Comment 3 Stefan Dirsch 2006-02-17 09:33:57 UTC 
Egbert, Bug #150146 is the "official" successor of Bug Bug #127757. :-)
Just check http://gate.crashing.org/~benh/radeon-memmap-7.0-3.diff.
Comment 4 Stefan Dirsch 2006-02-20 11:17:36 UTC 
Rod, any news on this one?
Comment 5 Michel Danzer 2006-02-22 15:18:27 UTC 
This should be fixed by the patches discussed in bug 151631.
Comment 6 Stefan Dirsch 2006-02-22 15:38:58 UTC 
Michel, thanks for verifying this!

*** This bug has been marked as a duplicate of 151631 ***