Hi Brice, Thank you for your mail. Basically, it's really hard for me to save the logs in time, because when this problem occures the screen become black and there is no way to get even a virtual console by (Ctrl-)Alt-Fx. The hotkey Ctrl-Alt-Backspace does not work too. The only thing I can do at that time is to press Ctrl-Alt-Del to get the whole machine reboot. The logs are gotten just after the restarting of the system (including the GDM). And, it is also difficult to reproduce it as desire; I don't know at all when it will happen. But I notice that, it occures always when I am using mouse to click some buttons in firefox/iceweasel. That is, I have encountered this bug several times; for each time, I do click some buttons of firefox/iceweasel, such as the closing button or other buttons of webpages. This is the only clue I can find up to now. I hope this is helpful and not a misleading one.
Thank you very much. On Dec 22, 2007 3:50 PM, Brice Goglin <[EMAIL PROTECTED]> wrote: > reassign 457385 xserver-xorg-video-intel > retitle 457385 xserver-xorg-video-intel: Existing errors found in hardware > state > found 457385 2:2.2.0-1 > thank you > > > > Hongzheng Wang wrote: > > Recently, the X usually crashed for hardware failure since the last > > upgrade. After its crash, the screen become black and only > > Ctrl-Alt-Del can be used, although the keyboard is not locked. The > > detailed Xorg.0.log.old is following and the hardware failure is > > reported at the end of this file: > > > > (WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled > > (WW) intel(0): PRB0_HEAD (0xd200100c) and PRB0_TAIL (0x00001070) indicate > > ring buffer not flushed > > (WW) intel(0): Existing errors found in hardware state. > > > > I am wondering whether this could be caused by the previous X session > crashing and letting the hardware in a bad state, and then the new > session failing with this message. > > Did you get this message right after the startup of the X server of > later? What happened before this? Did X fail in the same way? Did it > crash differently? Have you ever seen this problem after a hard reboot > of the machine? > > Every time you get a problem with X, you should save its log (either > Xorg.0.log or Xorg.0.log.old if X already restarted) and see whether you > get something strange in the log before the session where you get this > "errors found in hardware state". > > Do you have a way to reproduce the problem easily? > > Brice > > -- HZ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
