general protection fault: 0000 [#1] SMP

Bug #968906 reported by ar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Just starting the machine after updating.

ProblemType: KernelOops
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-20-generic
Uname: Linux 3.2.0-20-generic x86_64
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
Date: Fri Mar 30 08:31:42 2012
Failure: oops
SourcePackage: linux
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: arjenmeijer 2117 F.... pulseaudio
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=60e1d4ed-1c42-4267-b85e-e03a9bddf10d
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: LENOVO 254127G
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=0785a485-75e6-4238-bae8-49e05b8488f6 ro quiet splash pcie_aspm=force vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-20-generic x86_64
UpgradeStatus: Upgraded to precise on 2011-12-02 (118 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/08/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6KET58WW (1.28 )
dmi.board.name: 254127G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6KET58WW(1.28):bd12/08/2011:svnLENOVO:pn254127G:pvrThinkPadW701:rvnLENOVO:rn254127G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 254127G
dmi.product.version: ThinkPad W701
dmi.sys.vendor: LENOVO

Revision history for this message
ar (arjenmeijernl) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 968906

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Revision history for this message
ar (arjenmeijernl) wrote : AcpiTables.txt

apport information

tags: added: apport-collected staging
description: updated
Revision history for this message
ar (arjenmeijernl) wrote : AlsaDevices.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : AplayDevices.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : ArecordDevices.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : BootDmesg.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : CRDA.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : Card0.Amixer.info.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : Card29.Amixer.info.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : Card29.Amixer.values.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : CurrentDmesg.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : IwConfig.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : Lspci.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : Lsusb.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : PciMultimedia.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : ProcEnviron.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : ProcInterrupts.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : ProcModules.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : PulseList.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : RfKill.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : UdevDb.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : UdevLog.txt

apport information

Revision history for this message
ar (arjenmeijernl) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Do you have a way to reproduce the bug, or was this a one time event?

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: queue-work
Revision history for this message
ar (arjenmeijernl) wrote :

I will restart a few time to see what happens.

Revision history for this message
ar (arjenmeijernl) wrote :

Every time I get tree other errors:

- ColorD --> bug is confirmed
- two times Xorg crashed with SIGSEGV in <signal handler called>() --> flaged as nvidia-graphics-drivers bug.
Command ubuntu-bug nvidia-graphics-drivers gives a pop-up that nvidia-graphic-drivers does not exist.

So to answer your question: No, it is an one time event.

If it happens again, I will report it here.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this just start happening after your last update?

Since this bug does happen multiple times, would it be possible for you to test the previous kernel to see if it is a new regression?

Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-21.34)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-21.34
ar (arjenmeijernl)
Changed in linux (Ubuntu):
status: Incomplete → Fix Released
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.