BUG: unable to handle kernel paging request at 35fe1000

[dino99]

Precise i386 logged as gnome-classic

with nvidia 295.33 and xserver-xorg 1.12.0 (edgers ppa)
virtualbox 4.1.10-76795 (download.virtualbox.org)

ProblemType: KernelOops
DistroRelease: Ubuntu 12.04
Package: linux-image-3.3.0-030300-generic-pae
Uname: Linux 3.3.0-030300-generic-pae i686
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
Date: Fri Mar 23 11:16:14 2012
Failure: oops
SourcePackage: linux
---
ApportVersion: 1.95-0ubuntu1
Architecture: i386
DistroRelease: Ubuntu 12.04
NonfreeKernelModules: nvidia
Package: linux (not installed)
Tags: precise
Uname: Linux 3.3.0-030300-generic-pae i686
UnreportableReason: Ce paquet n'est pas officiellement pris en charge par Ubuntu. Veuillez désinstaller tout paquet tiers et réessayer.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio avahi avahi-autoipd boinc cdrom couchdb crontab daemon debian-tor dialout disk fuse haldaemon klog kmem libuuid lpadmin mail messagebus mlocate mysql mythtv netdev ntp operator plugdev polkituser powerdev pulse root sambashare saned scanner shadow ssh ssl-cert sudo syslog tty users utmp vboxusers video voice whoopsie www-data

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 962964

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[dino99 (9d9)]

apport information

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Joseph Salisbury (jsalisbury)]

Do you have a way to reproduce this oops?

[dino99 (9d9)]

get it on each first cold boot: the booting process start after picking the bgrub boot line, and immediatly seems to receive a stop order; then i found the crash logged. The second cold boot works normally.

[dino99 (9d9)]

- first cold boot fails again today: does not get a kernel, it seems to have received a stop order, and get a crash again
- 2d cold boot try works but with some warnings/errors: see boot.log & kern33boot.txt

[dino99 (9d9)]

trace

[dino99 (9d9)]

from : module-init-tools.log

FATAL: Error inserting w83627ehf (/lib/modules/3.3.0-030300-generic-pae/kernel/drivers/hwmon/w83627ehf.ko): Device or resource busy

from : flush-early-job-log.log

initctl: invalid command: flush-early-job-log

from : ureadahead-other.log

ureadahead:/var/lib/ureadahead/home.pack: No such file or directory

[Joseph Salisbury (jsalisbury)]

It looks like you are booting an upstream kernel. Does this happen on a supported precise kernel?

[dino99 (9d9)]

hi Joseph,

in fact you have requested to test that upstream kernel to compare with that issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/962113

The main problem is that reboot/first cold boot always failed : sometimes i can grab an error like that one

[dino99 (9d9)]

Reported on bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=43002

[Maarten Bezemer (veger)]

Thanks for taking the time to report this bug in the upstream bug tracking system this is a tremendous help. Launchpad has the ability to watch lots of upstream bug trackers and this can be done by following the procedure documented at https://wiki.ubuntu.com/Bugs/Watches. I've added the bug watch for this bug report.

[dino99 (9d9)]

might be related : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/740857

[dino99 (9d9)]

Latest bios + kernel 3.3.1 fwts results

[Luis Henriques (henrix)]

This looks like a duplicate of bug #960204

[dino99 (9d9)]

Still have, randomly, that issue: actually with RR i386, get the driver issue posted into #9 above. This happen very early when the ramdisk is created. So maybe its a compression issue.