On Jan 4, 2008 12:56 PM, Brice Goglin <[EMAIL PROTECTED]> wrote: > reassign 458858 xserver-xorg-video-intel > retitle 458858 xserver-xorg-video-intel 2.2.0: PRB0_HEAD and PRB0_TAIL > indicate ring buffer not flushed > found 458858 2:2.2.0-1 > severity 458858 important > thank you > > > > Ondrej Certik wrote: > > I think the severity of this bug should be raised, what do you think? > > > > Maybe the problem is not in the xserver-xorg package, but clearly the > > bug renders the computer unusable, and clearly, there is a bug > > somewhere. > >
Hi Brice, thanks for the reply. > I am reassigning to xserver-xorg-video-intel and making the severity > important. > > Some things you should try: > * disabling EXA (Option "AccelMethod" "XAA" in the the Device section) I put Option "AccelMethod" "XAA" in there 3 hours ago and now it hung twice in a row. > * downgrade to xserver-xorg-video-intel 2:2.1.1-4 (use > snapshot.debian.net to get it) I am doing this now. > Also, note that the following warnings may be caused by the crash of the > *previous* session laeving the hardware in a bad state and thus breaking > the new session. Trying after a hard reboot might make these warnings go > away as explained for other "error in hardware state" in #452739. > > (WW) intel(0): PRB0_CTL (0x0001f801) indicates ring buffer enabled > (WW) intel(0): PRB0_HEAD (0x98407814) and PRB0_TAIL (0x0000a738) indicate > ring buffer not flushed > (WW) intel(0): Existing errors found in hardware state. > > > So, it could be interesting to reboot hard, look at the log of the very > first crash and see whether these warnings are there or not. I read that bug report but I am not sure I understand. When X server hangs (for whatever reason), the log can always be accessed in the Xorg.0.log.old and it can also possibly leave the hardware in a bad state, so that when I restart, the X server hangs because of this bad state, right? So you suggestion is to always to hard reboot (shutdown, wait, powerup), right? And then look into Xorg.0.log.old Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
