Summary: | Sparc SIMBA VGA routing code kills system by disabling IDE controller | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | David S. Miller <davem> | ||||
Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> | ||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | major | ||||||
Priority: | high | CC: | elendil, mat | ||||
Version: | git | ||||||
Hardware: | SPARC | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
David S. Miller
2006-08-26 22:21:41 UTC
I can confirm this bug. I have also experienced severe data loss from this bug as on two separate occasions the partition table on a IDE harddisk (first time hda, second time hdc) had disappeared! After the first time I reinstalled the system on hda and the disk showed no problems during or after the install. I have yet to resurrect hdc. It would be great if this issue could be given a bit more attention than it seems to have been given so far. I have checked and my system (a Sparc Ultra 10) does have the SIMBA Advanced PCI Bridge. As David pointed out, the code in question is very problematic with practically no added benefit, and can occasionally lead to serious data loss. We have disabled this code in Debian's X.org packages by applying the patch which I will attach to the report; nobody has complained so far. I'm taking the liberty to bump the severity of this bug a notch, in the hope that somebody will care enough to apply it (or propose an alternative solution). -- Jurij Smakov Debian SPARC port maintainer Created attachment 7701 [details] [review] Patch to disable Simba PCI bridge routing code Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. Committed. git ebaa6c920c82401952a0ccc991b94574306449bd |
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.