BUG: Bad page map in process HTMLParserThrea pte:6c004700690070 pmd:0008f067

[Iain Lane]

This seems to be something chromium-ish which died (my tabs were all "He's dead, Jim", but I don't know where the bug lies.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-21-generic 3.16.0-21.28
ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
Uname: Linux 3.16.0-21-generic x86_64
NonfreeKernelModules: nvidia wl
Annotation: Your system might become unstablenow and might need to be restarted.
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: laney 2981 F.... pulseaudio
Date: Mon Oct 13 21:35:08 2014
Failure: oops
HibernationDevice: RESUME=UUID=2e47774e-17bc-4401-b353-8adf33732c5e
InstallationDate: Installed on 2012-10-18 (725 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MachineType: Apple Inc. MacBookPro7,1
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=e57ded1c-a0ed-4f14-944c-1353387547ed 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: Bad page map in process HTMLParserThrea pte:6c004700690070 pmd:0008f067
UpgradeStatus: Upgraded to utopic on 2014-07-30 (75 days ago)
dmi.bios.date: 03/25/10
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP71.88Z.0039.B05.1003251322
dmi.board.name: Mac-F222BEC8
dmi.board.vendor: Apple Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F222BEC8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP71.88Z.0039.B05.1003251322:bd03/25/10:svnAppleInc.:pnMacBookPro7,1:pvr1.0:rvnAppleInc.:rnMac-F222BEC8:rvr:cvnAppleInc.:ct10:cvrMac-F222BEC8:
dmi.product.name: MacBookPro7,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Do you have a way to reproduce this? If so, would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 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.18-rc1-utopic/