On Thu, 7 Jan 2010 01:46:55 +0100 Friedrich Delgado Friedrichs wrote: > Michael Gilbert schrieb: > > On Thu, 7 Jan 2010 00:12:58 +0100, Friedrich Delgado Friedrichs wrote: > > Given the fact that the fglrx driver needs a working MTRR lead me to > > conclude that your crashing MTRR is the root cause of the problem. > > fglrx driver 9.8 works with that same crashing mtrr. > > > BTW, your logs say that your MTRR is crashing. The stuff following > > 'Call Trace' is a backtrace, which you get when something crashes. > > Well, the line > > mtrr: your BIOS has set up an incorrect mask, fixing it up. > > and the word 'WARNING' led me to believe that the linux kernel is > working around a problem in my bios. But you're probably right, the > kernel (package) maintainers should know exactly what that means. > > I'm still not sure a bug report against the kernel is appropriate > here, as I only have problems with specific versions of the fglrx > driver on one specific mainboard + bios.
If MTRR crashes without fglrx, then it is kernel problem. MTRR may have become more important since 9-9 (this is conjecture since I have no evidence to back this up), which would explain why older versions worked ok. You need to test without fglrx, and if MTRR still crashes, a bug report on the kernel is really your only option for getting the problem fixed. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
