Ubuntu
linux package

BUG: unable to handle kernel paging request at ffffebe000000000

Bug #1503568 reported by Jack Byles
62
This bug affects 12 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

Not sure what happened.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-15-generic 4.2.0-15.17
ProcVersionSignature: Ubuntu 4.2.0-15.17-generic 4.2.3
Uname: Linux 4.2.0-15-generic x86_64
NonfreeKernelModules: nvidia wl
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Wed Oct 7 03:12:52 2015
DuplicateSignature: BUG: unable to handle kernel paging request at location RIP: 0010:location location kmem_cache_free+0x69/0x1e0
Failure: oops
HibernationDevice: RESUME=UUID=e92dd984-60bd-4066-9aa2-4fbb662fbe90
InstallationDate: Installed on 2015-09-23 (13 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: ASUSTeK Computer INC. CM1630
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-15-generic root=UUID=93a7ab21-b1ea-4d11-85c6-c273e718d08b ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
SourcePackage: linux
Title: BUG: unable to handle kernel paging request at ffffebe000000000
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0304
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: CM1630
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd05/20/2010:svnASUSTeKComputerINC.:pnCM1630:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCM1630:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: CM1630
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Jack Byles (bobmcbobertson) wrote :
Apport retracing service (apport)
tags: removed: need-duplicate-check
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
foulonarnaud (foulonarnaud) wrote :

also affects with an intel graphic card (lenovo thinkpad t510), it causes to system to stuck on welcome screen possibly due to linux kernel 4.2.0.15

Revision history for this message
mkatiyar (mkatiyar) wrote :

How do we get out of stuck welcome screen ? Is there a workaround to let us boot till the bug is fixed ?

Revision history for this message
foulonarnaud (foulonarnaud) wrote :

The workaround is to use the previous kernel with grub, today a new kernel was out so I think this bug is fixed, I don't have any crash on welcome screen

penalvch (penalvch)
tags: added: bios-outdated-0801
Revision history for this message
penalvch (penalvch) wrote :

Jack Byles, thank you for reporting this and helping make Ubuntu better. As per http://www.asus.com/Tower-PCs/Essentio_CM1630/HelpDesk_Download/ an update to your computer's buggy and outdated BIOS is available (0801). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Low
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.
Subscribing...

Other bug subscribers

Remote bug watches

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