kernel NULL pointer dereference at 00000000000001f0

[Fabio Marconi]

performing an installation of 20120131 amd64 desktop

Last checked in 20120206 3.2.0-14.23 amd64

ProblemType: KernelOopsDistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-12-generic
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 4499 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'ICH'/'Intel ICH with ALC850 at irq 23'
   Mixer name : 'Realtek ALC850 rev 0'
   Components : 'AC97a:414c4790'
   Controls : 42
   Simple ctrls : 27
CasperVersion: 1.302
Date: Tue Jan 31 16:50:43 2012
Failure: oopsLiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120131.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 005: ID 0718:0628 Imation Corp.
 Bus 002 Device 002: ID 046d:c313 Logitech, Inc. Internet 350 Keyboard
 Bus 002 Device 003: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=it keyboard-configuration/layoutcode?=it
PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-1ubuntu18
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: noSourcePackage: linux
Title: kernel NULL pointer dereference at 00000000000001f0
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.asset.tag: 00000000
dmi.board.name: K8NF4G-SATA2
dmi.board.version: 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd11/03/2005:svn:pnK8NF4G-SATA2:pvr1.00:rvn:rnK8NF4G-SATA2:rvr1.00:
dmi.product.name: K8NF4G-SATA2
dmi.product.version: 1.00

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/924400

[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 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)]

@Fabio,

Do you happen to know the daily build when this issue started happening?

[Joseph Salisbury (jsalisbury)]

Actually, I see that the issue happened on this build: 20120131

To clarify, is this the first daily build when this happened? Do you know the last daily build when this did not happen?

[Fabio Marconi (fabiomarconi)]

Hello Joseph
In this hardware surely it wasn't present the 19 january
Unfortunately I started to test with gigabyte-intel instead of the asrock and the asus that oops.
I have to perform some installations on this gigabyte to see if i can reproduce here too.
Let me just few hours.
Thanks
Fabio
P.S.
reproduced in 3.2.0-12.21 on asrock and asus
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

Well, I've done three installation on the gigabyte-intel machine and I haven't got a crash, then probably the issue is related to the nvidia or nouveau i think.
If useful i link the lshw af the crashing machines:
http://wiki.ubuntu-it.org/FabioMarconi/Lshw-asrock
http://wiki.ubuntu-it.org/FabioMarconi/Lshw-asus1

in case I link the working one:

http://wiki.ubuntu-it.org/FabioMarconi/Lshw-gigabyte

Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

Again, just tested the intel and it works, tested the nvidia and it crash
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Joseph Salisbury (jsalisbury)]

Hi Fabio,

I added this bug to the kernel team hot list[0].

[0] http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/_kernel_hot_.html

[Joseph Salisbury (jsalisbury)]

Hi Fabio,

So it sounds like only systems with nvidia devices are having this issue?

[Tim Gardner (timg-tpi)]

According to the stack trace in OopsText.txt this is a file system problem.

[Tim Gardner (timg-tpi)]

Fabio - can you run a memtest on the machine that is failing ? This crash just seems weird.

[Fabio Marconi (fabiomarconi)]

Let me explain what happen:
the screen is black wit h the written of the kernel null pointer.. for some seconds, then the session restart but the graphics is garbled, but I can see windows and written but obviously not usable.
Performing a ram test
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

hello
I've tested ram two times but no errors detected
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

This is random, not ever happens, just happened before and now i'm installing ok on this machine.
Attaching part of syslog:

Feb 2 21:02:42 ubuntu kernel: [ 210.291757] VFS: Busy inodes after unmount of sda1. Self-destruct in 5 seconds. Have a nice day...
Feb 2 21:02:42 ubuntu kernel: [ 210.291871] BUG: unable to handle kernel NULL pointer dereference at 00000000000001f0
Feb 2 21:02:42 ubuntu kernel: [ 210.291904] IP: [<ffffffff81218799>] ext4_evict_inode+0x39/0x450
Feb 2 21:02:42 ubuntu kernel: [ 210.291930] PGD 75258067 PUD 7507f067 PMD 0
Feb 2 21:02:42 ubuntu kernel: [ 210.291944] Oops: 0000 [#1] SMP
Feb 2 21:02:42 ubuntu kernel: [ 210.291956] CPU 0
Feb 2 21:02:42 ubuntu kernel: [ 210.291960] Modules linked in: xfs reiserfs jfs ext2 dm_crypt lp ppdev snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm arc4 snd_seq_midi rt61pci crc_itu_t rt2x00pci snd_rawmidi rt2x00lib snd_seq_midi_event mac80211 snd_seq snd_timer snd_seq_device snd psmouse cfg80211 edac_core serio_raw dm_multipath eeprom_93cx6 soundcore edac_mce_amd k8temp snd_page_alloc nv_tco i2c_nforce2 parport_pc ns558 gameport parport mac_hid bnep bluetooth squashfs overlayfs nls_iso8859_1 nls_cp437 vfat fat dm_raid45 xor dm_mirror dm_region_hash dm_log btrfs zlib_deflate libcrc32c nouveau ttm drm_kms_helper usbhid hid usb_storage drm forcedeth sata_nv pata_amd i2c_algo_bit mxm_wmi wmi video floppy
Feb 2 21:02:42 ubuntu kernel: [ 210.292023]
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] Pid: 4588, comm: gvfsd-trash Not tainted 3.2.0-12-generic #21-Ubuntu K8NF4G-SATA2/K8NF4G-SATA2
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] RIP: 0010:[<ffffffff81218799>] [<ffffffff81218799>] ext4_evict_inode+0x39/0x450
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] RSP: 0018:ffff880071cfbe48 EFLAGS: 00010206
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] RAX: ffff880035a48800 RBX: ffff880073b0dc30 RCX: ffff88007b16a000
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] RDX: 0000000000000000 RSI: 0000000000000018 RDI: ffff880073b0dc30
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] RBP: ffff880071cfbe68 R08: e000000000000000 R09: 9038000000000000
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] R10: ff6e4f40241b3207 R11: 0000000000000000 R12: ffff880073b0dd70
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] R13: ffff880073b0dd28 R14: ffff8800764a6264 R15: ffff880073b0dc30
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] FS: 00007fb0423f67c0(0000) GS:ffff88007ae00000(0000) knlGS:0000000000000000
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] CR2: 00000000000001f0 CR3: 0000000074053000 CR4: 00000000000006f0
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] Process gvfsd-trash (pid: 4588, threadinfo ffff880071cfa000, task ffff8800744844a0)
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] Stack:
Feb 2 21:02:42 ubuntu kernel: [ 210.292023] ffffffff81827500 ffff880073b0dc30 ffff880073b0dd28...

[Fabio Marconi (fabiomarconi)]

entire desktop after resuming from the black screen with the oops message, we can look the pointer too
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

Another detail
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[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 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.

[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 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.

[Fabio Marconi (fabiomarconi)]

Attaching screenshoots of the oops that this time lock the system without restart session.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

Sorry mispoken earlier, after 5 minutes sesssion rerstart with the same garbled graphic and pointer mouvable (xorg running)
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[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 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.

[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 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.

[Mathieu Marquer (slasher-fun)]

Occured to me as well, Dell Vostro 1500 with nVidia 8600M GT on live session.

* Started installer
* After choosing language and keyboard, the installer told me that my SD card was mounted and asked if I wanted to unmount it
* Clicked yes
--> kernel NULL pointer dereference

[Fabio Marconi (fabiomarconi)]

present on another machine, even nvidia, but with another number (140 instead 1f0)
Even during installation and just before partman starts
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

other machine, but this time session don't restart, mouse mouvable sysrq not working
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[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 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.

[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 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.

[Fabio Marconi (fabiomarconi)]

Yes, seems fixed after 5 or more installation in various days.
Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Fabio Marconi (fabiomarconi)]

reopened
present in desktop amd64 20120226 beta1 at the first attemp of installation of this build .
In the previous largely tested with many installation (20120225) this problem don't occour.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[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 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)]

Hi Fabio,

So this bug went away for a few daily builds, but it came back in the 20120226 build? Is it still happening in the current daily build. If so, is the kernel oops reporting the same information, for example:

RIP: 0010:[<ffffffff81218799>] [<ffffffff81218799>] ext4_evict_inode+0x39/0x450

[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 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)]

Hi Fabio,

Does this bug still exist in the beta release?

[Joseph Salisbury (jsalisbury)]

Also, do you have a way to reproduce this issue? Does it only happen during an installation?

[Fabio Marconi (fabiomarconi)]

Hello Joseph
Actually it seemed fixed but I've seen it again I think in .17 and ever only during installations, never on running systems and apparently random, but actually much more less present than before, pratically inexistent during the beta testing cycle.
I will update as soon as it appear again.
Thanks
Fabio
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Joseph Salisbury (jsalisbury)]

Thanks for the update, Fabio.

[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 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)]

This bug appears to be a duplicate of bug 922906

[Joseph Salisbury (jsalisbury)]

There is a test kernel available for this bug at:
  http://people.canonical.com/~apw/lp922906-precise/

Can you test this kernel and report back in bug 922906 where or not the test kernel resolved this bug?