general protection fault: 0000 [#1] SMP; RIP: 0010:[<ffffffff8100a0eb>] [<ffffffff8100a0eb>] system_call_fastpath+0xf/0x1b

Bug #621457 reported by toobuntu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Happened in a virtualbox vm that had worked fine until 2.6.35-16 and works fine after I finally got it to load a desktop. Took several tried to load the desktop, though. Interesting to note, when the desktop loaded it was the first time I could actually have audio output (MBP OS X host with CoreAudio driver). I had previously only seem null audio device in the sound menu. Changed nothing on the host or in vbox. With respect to the audio issue, this was an upgrade from lucid and not a clean install of maverick. On clean maverick installations I have functioning audio.

ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-16-virtual 2.6.35-16.22
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-16.22-virtual 2.6.35.2
Uname: Linux 2.6.35-16-virtual x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 82801AA-ICH]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: toobuntu 1343 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with STAC9700,83,84 at irq 21'
   Mixer name : 'SigmaTel STAC9700,83,84'
   Components : 'AC97a:83847600'
   Controls : 34
   Simple ctrls : 24
Date: Thu Aug 19 23:30:33 2010
Failure: oops
Frequency: This has only happened once.
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-16-virtual root=/dev/mapper/hostname-root ro splash quiet
RelatedPackageVersions: linux-firmware 1.38
RfKill:

SourcePackage: linux
Title: general protection fault: 0000 [#1] SMP
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Revision history for this message
toobuntu (toobuntu) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

toobuntu, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, 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 in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

summary: - general protection fault: 0000 [#1] SMP
+ general protection fault: 0000 [#1] SMP; RIP: 0010:[<ffffffff8100a0eb>]
+ [<ffffffff8100a0eb>] system_call_fastpath+0xf/0x1b
tags: added: kernel-bug
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.