Kernel Oops - BUG: unable to handle kernel paging request at 03802050; EIP is at eventpoll_release_file+0x33/0x80
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Failure to shutdown or restart. had to hard reset
ProblemType: KernelOops
DistroRelease: Ubuntu 12.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.2.0-22-
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.0-0ubuntu4
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Date: Tue Apr 10 23:14:04 2012
Failure: oops
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120327.1)
MachineType: TOSHIBA TOSHIBA NB505
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at 03802050
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/02/2011
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.90
dmi.board.name: PBU00
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: TOSHIBA NB505
dmi.product.
dmi.sys.vendor: TOSHIBA
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
justin parker, thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
* Is this reproducible? /wiki.ubuntu. com/KernelMainl ineBuilds . 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.
* If so, what specific steps should we take to recreate this bug?
* Could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https:/
Thanks in advance.