kernel crashes and reports "Fixing recursive fault but reboot is needed"

[mp]

apport report attached.

Screen goes black, flickers and goes to a console with this output:

Nov 14 16:54:33 compu kernel: [ 112.831665] Call Trace:
Nov 14 16:54:33 compu kernel: [ 112.831712] [<c0147ef5>] ? do_exit+0x215/0x2e0
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c0144f8a>] ? print_oops_end_marker+0x2a/0x30
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c0571730>] ? oops_end+0x90/0xd0
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c0128ad4>] ? no_context+0xb4/0xd0
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c0128b2d>] ? __bad_area_nosemaphore+0x3d/0x1a0
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c05708b8>] ? _spin_lock+0x8/0x10
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c01b3c4d>] ? find_get_page+0x1d/0x90
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c031043f>] ? cpumask_any_but+0x1f/0x40
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c012c927>] ? flush_tlb_page+0x37/0x90
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c012c01e>] ? ptep_set_access_flags+0x3e/0x50
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c0128cea>] ? __bad_area+0x3a/0x50
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c0128d12>] ? bad_area+0x12/0x20
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c0572ef2>] ? do_page_fault+0x342/0x380
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c012d347>] ? kmap_atomic_prot+0x47/0xf0
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c0572bb0>] ? do_page_fault+0x0/0x380
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c0570be3>] ? error_code+0x73/0x80
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c01f02d6>] ? getname+0x86/0xf0
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c0101a11>] ? sys_execve+0x11/0x60
Nov 14 16:54:33 compu kernel: [ 112.831757] [<c010336c>] ? syscall_call+0x7/0xb
Nov 14 16:54:33 compu kernel: [ 112.831757] Code: 8d b4 26 00 00 00 00 55 89 e5 83 ec 08 89 1c 24 89 c3 89 74 24 04 8b b0 f0 03 00 00 85 f6 75 0b 8b 1c 24 8b 74 24 04 89 ec 5d c3 <83> 7e 04 00 c7 46 30 00 00 00 00 c7 46 34 00 00 00 00 74 1a 83
Nov 14 16:54:33 compu kernel: [ 112.831757] EIP: [<c018ba94>] audit_free+0x24/0xa0 SS:ESP 0068:de5f9dc4
Nov 14 16:54:33 compu kernel: [ 112.831757] CR2: 0000000080000004
Nov 14 16:54:33 compu kernel: [ 112.834978] ---[ end trace 943b2157089ecdac ]---
Nov 14 16:54:33 compu kernel: [ 112.835024] Fixing recursive fault but reboot is needed!

ProblemType: Bug
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: V8233A [VIA 8233A], device 0: VIA 8233A [VIA 8233A]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nina 1378 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'V8233A'/'VIA 8233A with ALC200,200P at 0xe000, irq 22'
   Mixer name : 'Realtek ALC200,200P rev 0'
   Components : 'AC97a:414c4710'
   Controls : 39
   Simple ctrls : 25
Card1.Amixer.info:
 Card hw:1 'UART'/'MPU-401 UART at 0x330, irq 10'
   Mixer name : ''
   Components : ''
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

Date: Sat Nov 14 17:54:07 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=133706c3-112c-4eb3-91ad-09043a05a7c6
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: TriGem Computer NETHERLANDS Advent Series
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=2e66bf03-a764-471b-a7f4-62dca6fa5e14 ro
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-14-generic i686
WifiSyslog:

dmi.bios.date: 04/29/2002
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: KM266-8233
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd04/29/2002:svnTriGemComputerNETHERLANDS:pnAdventSeries:pvr:rvn:rnKM266-8233:rvr:cvn:ct3:cvr:
dmi.product.name: Advent Series
dmi.sys.vendor: TriGem Computer NETHERLANDS

[mp (m-p)]

Forgot to mention that this happened just after booting and Gnome had fully loaded and no user apps were running.

[northrup (northrupthebandgeek)]

I'm having a similar issue, but at boot-time. I'm trying to guide my mom through booting off an Ubuntu 9.10 LiveCD to repair a Windows installation on her Gateway laptop (I don't have the specs, sorry), but she's getting the "fixing recursive fault but reboot is needed" error message right after she selects either the "Try Ubuntu without making any changes" or the "OEM Install" options. The install CD was shipped from Canonical, so I'd hope there aren't any disk errors.

I'll try to get the stop screen word-for-word next time I work with the computer, but for now, what generally causes this kind of error message? Is it a hardware issue, or did I get a defective disk after all? I told my mom to run the "Check disk for errors" option, but I think she got a similar screen...

[mp (m-p)]

I tried the disk in other machines and it worked fine. However, no one
seems to care about these things. Since Hardy the bugs have just kept
piling up and the focus seems to on shortening boot times - and leaving
behind those that cannot boot at all. I think we need a new term to
reflect the "Ubuntel" paradigm - similar to the Wintel paradigm I
thought I had left behind. If your latest Ubuntu doesn't work, just buy
a new machine. Repeat until it works.

It is a worrying trend.

northrup wrote:
> I'm having a similar issue, but at boot-time. I'm trying to guide my
> mom through booting off an Ubuntu 9.10 LiveCD to repair a Windows
> installation on her Gateway laptop (I don't have the specs, sorry), but
> she's getting the "fixing recursive fault but reboot is needed" error
> message right after she selects either the "Try Ubuntu without making
> any changes" or the "OEM Install" options. The install CD was shipped
> from Canonical, so I'd hope there aren't any disk errors.
>
> I'll try to get the stop screen word-for-word next time I work with the
> computer, but for now, what generally causes this kind of error message?
> Is it a hardware issue, or did I get a defective disk after all? I told
> my mom to run the "Check disk for errors" option, but I think she got a
> similar screen...
>

[Jeremy Foshee (jeremyfoshee)]

Hi mp,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 482735

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]