Bad page map / bad pte

Bug #1462180 reported by Ray Cole
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I have received very similar bugs on 3.13.0-53, 3.13-0.52, 3.13.0-51 and 3.13.0-49. I will be falling back to 3.13.0-45, which is the last kernel where I believe I didn't have this problem.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-49-generic 3.13.0-49.83
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
Date: Thu Jun 4 23:21:23 2015
HibernationDevice: RESUME=UUID=b170f305-49ff-4e37-b417-1a977a8dc002
InstallationDate: Installed on 2014-06-06 (363 days ago)
InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530
IwConfig:
 vboxnet0 no wireless extensions.

 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-49-generic root=UUID=3c298b14-cd0f-4d75-a2ca-c79623676014 ro crashkernel=384M-2G:64M,2G-:128M quiet splash crashkernel=384M-:128M vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-49-generic N/A
 linux-backports-modules-3.13.0-49-generic N/A
 linux-firmware 1.127.11
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/08/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7c
dmi.board.name: GA-MA790GP-UD4H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA790GP-UD4H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Ray Cole (the-other-ray-cole) wrote :
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
tags: added: trusty
Revision history for this message
penalvch (penalvch) wrote :

Ray Cole, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-f6
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Ray Cole (the-other-ray-cole) wrote :

I have installed 4.1.0-040100rc7-generic and will see if this problem happens. It usually takes several days for the problem to appear.

I had fallen back to 3.13.0-45 and it ran over a week without the problem. 3.13.0-49 produced the problem after only a few days. So something between -45 and -49 caused the issue it seems.

Revision history for this message
Ray Cole (the-other-ray-cole) wrote :

So far 4.1.0-040100rc7-generic has been running without a problem. Because this problem is intermittent I want to give it another week of running before marking it as fixed upstream.

Revision history for this message
Ray Cole (the-other-ray-cole) wrote :

I am convinced the problem is resolved upstream as it has run an entire week without causing a problem. Added tags indicating it is fixed upstream. I am also installing 3.13.0-55 to see if this also resolves it.

tags: added: kernel-fixed-upstream kernel-fixed-upstream-4.1.0-040100rc7
Revision history for this message
penalvch (penalvch) wrote :

Ray Cole, if the latest 3.13 kernel does not address the issue, to see if this already fix in Ubuntu, could you please test this in http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

tags: added: kernel-fixed-upstream-4.1-rc7
removed: kernel-fixed-upstream-4.1.0-040100rc7
tags: removed: rebecca
Revision history for this message
Ray Cole (the-other-ray-cole) wrote :

I would be willing to run the kernel from it if I can obtain it somewhere. It takes about a day to reproduce the problem. The first symptom are things randomly crashing (google-chrome, for example) and then not too long after I see messages about pte problems.

3.13.0-46 and below run fine. 3.13.0-49 and above crash. I have not tried 3.13.0-48 but intend to do so in order to nail down which one introduced the problem. It was either 3.13.0-48 or 3.13.0-49 that introduced it (or -47, but that doesn't appear to be available so I assume it was known to be bad).

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.

Other bug subscribers

Remote bug watches

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