14.04 BUG: unable to handle kernel paging request at ...

[Daniel Hollocher]

hey guys. So I have been getting this kernel oops on an old laptop on 14.04. It is a laptop new to my posession, so I don't have a lot of experience with it. I believe it was running mainly windows xp before, and had an old but unused Ubuntu install on it as well. I first encountered it when trying to wipe the machine and install 14.04 xubuntu from scratch.

I assumed that maybe it is because the laptop is old, maybe the memory was bad, I dunno. I replaced the memory, same error.

I installed the server edition of ubuntu, and the install actually worked. This current bug is being filed from that install, where I installed xubuntu-desktop^ from the command line. I installed google-chrome, and then tried to open chrome, then the oops again.

I have also installed 10.04 and 12.04, and both installs went fine. Since the 14.04 kernel oops happened early in the install process, I'm inclined to believe that those earlier versions are working, and that this is a regression from 12.04->14.04.

I will attach a copy of dmesg which shows the oops, in case it isn't already included.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-35-generic 3.13.0-35.62
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic i686
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dan 1913 F.... pulseaudio
                      dan 2660 F.... pulseaudio
CurrentDesktop: XFCE
Date: Wed Sep 10 12:20:33 2014
HibernationDevice: RESUME=UUID=038cb881-a4ff-4ef6-b49e-bbe6a8610377
InstallationDate: Installed on 2014-09-07 (2 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.3)
MachineType: ASUSTeK Computer INC. 1101HA
ProcFB: 0 psbdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=4f6267be-c36c-4151-bfab-89d4e8897baf ro text
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-35-generic N/A
 linux-backports-modules-3.13.0-35-generic N/A
 linux-firmware 1.127.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0323
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1101HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0323:bd12/01/2009:svnASUSTeKComputerINC.:pn1101HA:pvrx.x:rvnASUSTeKComputerINC.:rn1101HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 1101HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Daniel Hollocher (chogydan)]

Here is a dmesg output, showing the kernel oops.

[Daniel Hollocher (chogydan)]

I forgot to mention, that while my system doesn't freeze, things start to stop working. It is hard to describe, programs will just not work or crash. Currently, chrome froze, so I'm using firefox to post all this.

I will really appreciate any help that can be provided. I'm also curious what the kernel oops means. What exaclty is going wrong?

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 kernel[0].

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc4-utopic/

[Daniel Hollocher (chogydan)]

well, it is hard to say whether it is fixed or not. For now, it seems to have lasted longer than ever. Ie, it seems to be lasting long enough that I could acutally use it.

I will mark it fixed upstream, and just change it back if I run into the error again.