[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#355125: marked as done (i810 X server dies with "Active ring not flushed" error)

Your message dated Sat, 13 Jun 2009 13:35:52 +0200
with message-id <4A338F18.3030408@ens-lyon.org>
and subject line Re: Bug#355125: i810 X server dies with "Active ring not flushed" 	error
has caused the Debian Bug report #355125,
regarding i810 X server dies with "Active ring not flushed" error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
355125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355125
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xserver-xorg
Version: 6.9.0.dfsg.1-4

While working in KWrite, X died unexpectedly. It stopped responding;
then a few seconds later, the screen blanked out, and it would no
longer respond to keystrokes (e.g. Ctrl+Alt+F1).

I was able to ssh in and grab the Xorg.0.log file, which is attached here.

Attempts to restart X are not working. The server is dying with a
similar error, with a few numbers changed.

---------------

(II) I810(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
pgetbl_ctl: 0xd550001 pgetbl_err: 0x1fc22013
ipeir: 0 iphdr: 50c00004
LP ring tail: f808 head: ec28 len: f001 start 690000
eir: 0 esr: 10 emr: 3d
instdone: ff3a instpm: 0
memmode: 4 instps: 810
hwstam: 9ac7 ier: 0 imr: 9ac7 iir: 0

Fatal server error:
Active ring not flushed

---------------

It looks like I'll have to reboot the machine.

-- graham

Attachment: Xorg.0.log
Description: Binary data


--- End Message ---
--- Begin Message --- 
Graham wrote:
>> Does this still happen with latest intel driver in unstable
>> or experimental?
>>     
>
> As I mentioned previously...
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355125#27
>
> I no longer have this hardware in my possession, so I'm unable to
> re-test. Sorry.
>   

Oops sorry, I missed this.

Let's close this bug then, it's too old anyway. If somebody reproduces
something similar, please try with unstable and open a new bug.

Brice

--- End Message ---
Reply to: