Michel Dänzer <[EMAIL PROTECTED]> writes: > On Thu, 2006-10-19 at 21:41 +0200, [EMAIL PROTECTED] wrote: >> Michel Dänzer <[EMAIL PROTECTED]> writes: >> >> > And this doesn't happen with version 6.6.2? If so, it would be great if >> > you could try isolating the upstream change that causes it with >> > git-bisect. >> >> I'm afraid that's a bit too much as I don't know anything about git... > > But it doesn't happen with version 6.6.2?
I'm not sure exactly when it stops working... > >> > That's an odd place for the log to stop... Can you not even log in >> > remotely or ping the machine at this point? If so, can you try >> > re-mounting the filesystem that contains the log file with -o sync >> > before starting the X server and see if you get any more output then? >> >> True. Before submiting the bug, I read the logs after several crashes >> and saw it was not always at the same line. Here's the one with -o sync >> and latest version of everything (deb sid). > > Thanks. Does it always stop in the same place with -o sync? Also, is > there anything related in /var/log/kern.log? Yes it stops always at the same time. The kernel logs show something that may be interesting: Oct 25 22:53:26 arrakis kernel: [drm] Setting GART location based on new memory map Oct 25 22:53:26 arrakis kernel: [drm] Loading R200 Microcode Oct 25 22:53:26 arrakis kernel: [drm] writeback test failed The last line here is the last line in the log. Is it possible that my hardware is damaged ? I find it strange that the microcode fails to load :/ Marc
