kernel: Bad page state in process 'Xgl'

This is the part I copied & pasted from the screen session

And here what I got from my /var/log/messages file

Just a moment ago:

Message from syslogd@NemesisP4HT at Mon Feb 12 13:11:02 2007 ...
NemesisP4HT kernel: [17185777.624000] Bad page state in process 'Xgl'

Message from syslogd@NemesisP4HT at Mon Feb 12 13:11:02 2007 ...
NemesisP4HT kernel: [17185777.624000] page:c1a9f120 flags:0xc0000000 mapping:00000000 mapcount:0 count:262144

Message from syslogd@NemesisP4HT at Mon Feb 12 13:11:02 2007 ...
NemesisP4HT kernel: [17185777.624000] Trying to fix it up, but a reboot is needed

Message from syslogd@NemesisP4HT at Mon Feb 12 13:11:02 2007 ...
NemesisP4HT kernel: [17185777.624000] Backtrace:

Feb 12 13:11:02 NemesisP4HT kernel: [17185777.624000] <c015067b> bad_page+0x6b/0xb0 <c01512fd> get_page_from_freelist+0x3bd/0x410
Feb 12 13:11:02 NemesisP4HT kernel: [17185777.624000] <c01513a6> __alloc_pages+0x56/0x330 <c015f07d> anon_vma_prepare+0x1d/0xe0
Feb 12 13:11:02 NemesisP4HT kernel: [17185777.624000] <c0153660> __pagevec_lru_add_active+0xa0/0xc0 <c01594ea> __handle_mm_fault+0x7ba/0x900
Feb 12 13:11:02 NemesisP4HT kernel: [17185777.624000] <c015be9f> vma_merge+0xdf/0x1d0 <c02dc2cb> do_page_fault+0x3db/0x6f0
Feb 12 13:11:02 NemesisP4HT kernel: [17185777.624000] <c02dbef0> do_page_fault+0x0/0x6f0 <c010420f> error_code+0x4f/0x60

Might this be a hardware error?

Hmm... funny what has happened next.
Writing some text with gedit I accidently hit the `-key twice, followed by a backspace. The enviroment froze and next I found myself logged off again, the Xgl-server seemed to have restartet.

Enclosed the last piece of my /var/log/messages file:

Feb 12 15:53:25 NemesisP4HT kernel: [17195523.928000] BUG: warning at kernel/exit.c:855/do_exit()
Feb 12 15:53:25 NemesisP4HT kernel: [17195523.928000] <c0125bb2> do_exit+0x6c2/0x840 <c0125d67> do_group_exit+0x37/0x80
Feb 12 15:53:25 NemesisP4HT kernel: [17195523.928000] <c012e751> get_signal_to_deliver+0x281/0x3f0 <c010266b> do_notify_resume+0x8b/0x6c0
Feb 12 15:53:25 NemesisP4HT kernel: [17195523.928000] <c011bde0> default_wake_function+0x0/0x10 <c013a738> sys_futex+0x88/0x100
Feb 12 15:53:25 NemesisP4HT kernel: [17195523.928000] <c01030be> work_notifysig+0x13/0x25
Feb 12 15:53:26 NemesisP4HT kernel: [17195525.232000] [fglrx] Internal AGP support requested, but kernel AGP support active.
Feb 12 15:53:26 NemesisP4HT kernel: [17195525.232000] [fglrx] Have to use kernel AGP support to avoid conflicts.
Feb 12 15:53:26 NemesisP4HT kernel: [17195525.232000] [fglrx] AGP detected, AgpState = 0x1f004a1b (hardware caps of chipset)
Feb 12 15:53:37 NemesisP4HT gconfd (krummen-5176): Die Adresse »xml:readwrite:/home/krummen/.gconf« wurde an der Position 0 zu einer schreibbaren Konfigurationsquelle aufgelöst
Feb 12 15:54:18 NemesisP4HT kernel: [17195577.320000] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 185
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.180000] [fglrx] Internal AGP support requested, but kernel AGP support active.
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.180000] [fglrx] Have to use kernel AGP support to avoid conflicts.
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.180000] [fglrx] AGP detected, AgpState = 0x1f004a1b (hardware caps of chipset)
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.180000] agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.180000] agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.180000] agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.180000] [fglrx] AGP enabled, AgpCommand = 0x1f004312 (selected caps)
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.192000] [fglrx] total GART = 134217728
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.192000] [fglrx] free GART = 118222848
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.192000] [fglrx] max single GART = 118222848
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.192000] [fglrx] total LFB = 128970752
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.192000] [fglrx] free LFB = 122679296
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.192000] [fglrx] max single LFB = 122679296
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.192000] [fglrx] total Inv = 134217728
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.192000] [fglrx] free Inv = 134217728
Feb 12 15:54:19 NemesisP4HT kernel: [17195578.192000] [fglrx] max single Inv = 134217728
Feb 12 15:54:19 NemesisP4HT kernel:...

After logging in again, the crash report tool gave me a Xgl report. This might all be in the same conext.

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.