[Dell PowerEdge R210] BUG: unable to handle kernel NULL pointer dereference at 000000000000020a; RIP: e030:[<ffffffff812ed584>] [<ffffffff812ed584>] common_file_perm+0x14/0xf0

[Saul St. John]

I can semi-reliably trigger a kernel oops on these servers by letting them idle for a while, and then doing something that performs disk io.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-19-generic 3.5.0-19.30
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Uname: Linux 3.5.0-19-generic x86_64
---
AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Dec 13 02:01 seq
 crw-rw---T 1 root audio 116, 33 Dec 13 02:01 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
CurrentDmesg:
 [ 32.263050] device br0 entered promiscuous mode
 [ 32.365646] Event-channel device installed.
 [ 32.944673] init: plymouth-stop pre-start process (1168) terminated with status 1
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=53bbfa22-c883-49e5-84d8-f96b3ec5e8db
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
MachineType: Dell Inc. PowerEdge R210
MarkForUpload: True
Package: linux 3.5.0.19.22
PackageArchitecture: amd64
PciMultimedia:

ProcEnviron:
 LANGUAGE=en_US:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: placeholder root=/dev/mapper/hostname-root ro console=hvc0 earlyprintk=xen ignore_loglevel text splash quiet
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-19-generic N/A
 linux-backports-modules-3.5.0-19-generic N/A
 linux-firmware 1.95
RfKill: Error: [Errno 2] No such file or directory
Tags: quantal
Uname: Linux 3.5.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.2
dmi.board.name: 0M877N
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.9.2:bd05/07/2012:svnDellInc.:pnPowerEdgeR210:pvr:rvnDellInc.:rn0M877N:rvrA01:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R210
dmi.sys.vendor: Dell Inc.

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

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.

[Saul St. John (saul-stjohn)]

apport information

[Saul St. John (saul-stjohn)]

apport information

[Saul St. John (saul-stjohn)]

apport information

[Saul St. John (saul-stjohn)]

apport information

[Saul St. John (saul-stjohn)]

apport information

[Saul St. John (saul-stjohn)]

apport information

[Saul St. John (saul-stjohn)]

apport information

[Saul St. John (saul-stjohn)]

apport information

[Saul St. John (saul-stjohn)]

apport information

[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.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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.7-raring/

[Saul St. John (saul-stjohn)]

I booted four servers a couple hours ago: two stock, one on the kernel from quantal-proposed, and one on 3.7.0-030700-generic. Of them, only the 3.7 box is still up, so I'm tagging this 'kernel-fixed-upstream' and changing back to confirmed.

[Saul St. John (saul-stjohn)]

I'm requesting that this bug priority be changed to at-least 'High', as it "prevents the application or any dependencies from functioning correctly at all," and "renders essential features or functionality of the application or dependencies broken or ineffective."

[penalvch (penalvch)]

Saul St. John, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]