Fatal Server error - Active Ring Not Flushed.

[point]

Atleast once or twice a day my display will go all "rainbow like".. flicker a couple times then crash and my monitor turns off. This normally happens when browsing in Firefox, but not just firefox: It may happen when i move my mouse over something... it may happen when i view a text file.. it may happen when i launch an xterm, etc, etc.

I am new to reporting bugs. I know i should have reported this a long time ago, but i figured i wasn't the only one and it would pass. I've seen a bug report that looks like mine, but X wouldn't start in their case; mine does, but i can't 'trust' it.

Adding /var/log/Xorg.0.log.old, /etc/X11/xorg.conf and lspci -vv output.

[point (p01n7)]

/var/log/Xorg.0.log.old:

X Window System Version 6.8.2 (Ubuntu 6.8.2-77 20051010174523 <email address hidden>)
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.10 i686 [ELF]
Current Operating System: Linux cytrex 2.6.12-8-386 #1 Tue Aug 30 22:41:30 BST 2005 i686
Build Date: 10 October 2005
 Before reporting problems, check http://wiki.X.Org
 to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.12-8-386 (buildd@rothera) (gcc version 3.4.5 20050809 (prerelease) (Debian 3.4.4-6ubuntu6)) #1 Tue Aug 30 22:41:30 BST 2005
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr 11 02:09:03 2006
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "AOC A785"
(**) | |-->Device "Intel Corporation 82810E DC-133 CGC [Chipset Graphics Controller]"
(**) |-->Input Device "Generic Keyboard"
(**) |-->Input Device "Configured Mouse"
(WW) The directory "/usr/share/X11/fonts/cyrillic" does not exist.
 Entry deleted from font path.
(WW) The directory "/usr/share/X11/fonts/CID" does not exist.
 Entry deleted from font path.
(WW) `fonts.dir' not found (or not valid) in "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID".
 Entry deleted from font path.
 (Run 'mkfontdir' on "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID").
(**) FontPath set to "/usr/share/X11/fonts/misc,/usr/share/X11/fonts/100dpi/:unscaled,/usr/share/X11/fonts/75dpi/:unscaled,/usr/share/X11/fonts/Type1,/usr/share/X11/fonts/100dpi,/usr/share/X11/fonts/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
(==) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) Module ABI versions:
 X.Org ANSI C Emulation: 0.2
 X.Org Video Driver: 0.7
 X.Org XInput driver : 0.4
 X.Org Server Extension : 0.2
 X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="X.Org Foundation"
 compiled for 6.8.2, module version = 1.0.0
 Module class: X.Org Font Renderer
 ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="X.Org Foundation"
 compiled for 6.8.2, module version = 1.0.0
 ABI class: X.Org Video Driver, version 0.7
(++) using VT number 8

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,7124 card 0000,0000 rev 03 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,7125 card 0e11,b1c1 rev 03 class 03,00,00 hdr 00
(II) PCI: 00:1e:0: chip 8086,2418 card 0000,0000 rev 02 class 06,04,00 hdr 01
(II) PCI: 00:1f:0: chip 8086,2410 card 0000,0000 rev 02 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 hdr 0...

[point (p01n7)]

I'm sorry.. is this how i am supposed to post the log contents?

[point (p01n7)]

xorg.conf

[point (p01n7)]

Sorry, i failed to notice the link. Xorg log

[point (p01n7)]

lspci -vv output

[point (p01n7)]

See? i am new. Failed to mention this is Ubuntu Breezy now. This also happend in Dapper and Hoary. It was the worst in Dapper.. it got to the point one time that i couldn't launch firefox because X would crash! ...but only with firefox with Dapper. Please yell at me to give you more info if i left anything else obvious out.

[Henrik Nilsen Omma (henrik)]

Hello,

You seem to have included lots of useful output, thank you. I see from the log file that this is indeed from breezy, but I'm a bit confused about your mention of the versions. You say it 'was worst in dapper'. Do you actually mean warty (4.10), our first version?

Have you actually tested it with the latest development version, which we call Dapper Drake (will be 6.06)? If so, it would be great to get logs from those tests as well.

Thanks.

- Henrik

[point (p01n7)]

Henrik Nilsen Omma wrote:

>Hello,
>
>You seem to have included lots of useful output, thank you. I see from the log file that this is indeed from breezy, but I'm a bit confused about your mention of the versions. You say it 'was worst in dapper'. Do you actually mean warty (4.10), our first version?
>
>Have you actually tested it with the latest development version, which we call Dapper Drake (will be 6.06)? If so, it would be great to get logs from those tests as well.
>
>Thanks.
>
>- Henrik
>
>
I've already given Dapper(flight 5 I think) a run, and it was worse in
dapper then in previous versions. I've also ran Hoary and breezy. This
problem occured during use of all. Although, Kubuntu only did this once
i think, the farthest i've gone with Kubuntu is Breezy, however.
I am running Breezy now, however, i already had plans to re-install
Dapper.. should i do this then wait for another crash and post the logs?
I have a spare partition where i store all my data, so reinstalling is
just the time it takes for me.

Regards,
Paul.

[point (p01n7)]

Update:
It seems i _can_ reproduce the crash with Firefox and X. I was just
snooping around to make sure this wasn't a firefox related problem (this
has happend alot, and i do recall it happening a couple times at random
without firefox running) and i found the site i went to before the last
crash ( http://www.opera.com )... now if you notice the pretty little
grey tool-bar-like row of buttons along the top of that site.. as soon
as i place my mouse over one of those buttons X falls to it's knees.
Adding the new log.

Keep in mind that it was _not_ only this time X crashed.. this has
happend alot.. and i don't go to the site everyday.

Regards,
Paul.

[point (p01n7)]

log from the firefox test i just did

[point (p01n7)]

point wrote:

>Update:
>It seems i _can_ reproduce the crash with Firefox and X. I was just
>snooping around to make sure this wasn't a firefox related problem (this
>has happend alot, and i do recall it happening a couple times at random
>without firefox running) and i found the site i went to before the last
>crash ( http://www.opera.com )... now if you notice the pretty little
>grey tool-bar-like row of buttons along the top of that site.. as soon
>as i place my mouse over one of those buttons X falls to it's knees.
>Adding the new log.
>
>Keep in mind that it was _not_ only this time X crashed.. this has
>happend alot.. and i don't go to the site everyday.
>
>Regards,
>Paul.
>
>
Another update:
Sorry for writing alot, but i tried to reproduce it again.. doin the
same thing ( putting mouse over button ).. nothing happend.. so i went
to my home page, cleard firefoxs cache, closed firefox, restarted
firefox, went to opera.com again.. tried the button thing and nothing
happend.. but!.. with the page still opened.. i clicked on Gnome's
applications menu-bar to launch another instance of firefox ( i was
going to test wether it's a system memory problem by having alot of
things running ) but before i could do that.. the same X crash happend
as I highlighted a sub-section of the menu.

Hope this helps,
Regards,
Paul.

[Henrik Nilsen Omma (henrik)]

For issues like improved hardware support we will be focusing our efforts on the next release, so testing of that would be appreciated (for security related issues OTOH we would always backport the fixes to the supported releases).

If you'd rather not install dapper yet you can try testing with the live CD (which it sounds like you've used already).

The following procedure should let you gather the needed info from a Live CD: Run these two commands from the live CD:
wget http://www.ubuntulinux.nl/files/pastebin
python pastebin --debug-x

That will first download a debugging script from ubuntulinux.nl. Running it will in turn gather all the log files and output we should need and paste it to a URL at http://paste.ubuntu-nl.org

If you then just paste that URL into a new comment here we should have what we need. Thanks! You can see a sample of what is collected here: http://paste.ubuntu-nl.org/11955

- Henrik

[point (p01n7)]

Dapper is now freshly installed. The link in question is here
http://paste.ubuntu-nl.org/12036 . The python script was ran before any
crashes ( iw asn't sure if you wanted it to be done before or after... ).

Regards,
Paul.

[point (p01n7)]

I reproduced the crash using www.opera.com on Dapper. This time i just
messed around with the "buttons" and my mouse for a little bit... after
about 20 seconds of that i had the same crash. Don't know if it's
useful, but heres a new link to the script output after a crash:
http://paste.ubuntu-nl.org/12039 .

Again, this has happened without Firefox running.

Regards,
Paul.

[Matt Zimmerman (mdz)]

The symptoms here are very similar to bug #29014, of which it is perhaps a duplicate.