BUG: unable to handle kernel paging request at 000000008e34dd1c; RIP: 0010:[<000000008e34dd1c>] [<000000008e34dd1c>] 0x8e34dd1b

Bug #1203098 reported by Vladimir Andreev
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

I have Intel server based on S5500BC motherboard. After upgrading from 3.2.0 kernel to any higher version I have system crash during boot.

WORKAROUND: Add 'noefi' as kernel parameter.

Begin: Running /scripts/init-bottom ... done.
[ 38.213167] BUG: unable to handle kernel paging request at 000000008e34dd1c
[ 38.296766] IP: [<000000008e34dd1c>] 0x8e34dd1b
[ 38.351108] PGD 2600e0067 PUD 0
[ 38.389939] Oops: 0010 [#1] SMP
[ 38.428772] Modules linked in: raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx hid_generic raid1 e1000e raid0 ptp usbhid multipath ahci libahci hid pps_core linear
[ 38.646663] CPU 5
[ 38.668628] Pid: 469, comm: mount Not tainted 3.9.0-030900-generic #201304291257 Intel Corporation S5500BC/S5500BC
[ 38.794781] RIP: 0010:[<000000008e34dd1c>] [<000000008e34dd1c>] 0x8e34dd1b
[ 38.878262] RSP: 0018:ffff8802631f9bd8 EFLAGS: 00010086
[ 38.941860] RAX: ffff88008f5a7218 RBX: ffff88026367b408 RCX: ffff88026367b008
[ 39.027316] RDX: ffff88026367b408 RSI: ffff8802631f9d30 RDI: ffff88026367b008
[ 39.112773] RBP: ffff88026367b828 R08: ffff88026367b828 R09: ffff8802631f9d30
[ 39.198230] R10: 0000000000000000 R11: ffffffff81845560 R12: ffff880266bf4690
[ 39.283686] R13: ffffffff81f6b158 R14: ffff88026367b408 R15: ffff88026367b008
[ 39.369141] FS: 00007f34a59fa800(0000) GS:ffff8802672a0000(0000) knlGS:0000000000000000
[ 39.466046] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 39.534851] CR2: 000000008e34dd1c CR3: 0000000260094000 CR4: 00000000000007e0
[ 39.620307] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 39.705762] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 39.791219] Process mount (pid: 469, threadinfo ffff8802631f8000, task ffff88025fdc9750)
[ 39.888122] Stack:
[ 39.912165] ffff88008e3697a3 ffffea00097e24c0 ffff880266c02700 0000000000000000
[ 40.001161] ffff88026383de47 0000000000000000 ffff8802631f9cb0 ffffffff81a74b7d
[ 40.090154] ffff8802631f9c78 ffff8802631f9c30 ffff88008e369768 ffff88026367b008
[ 40.179150] Call Trace:
[ 40.208408] [<ffffffff810559eb>] ? efi_call5+0x4b/0x80
[ 40.270966] [<ffffffff811b5e84>] ? __d_alloc+0x34/0x180
[ 40.334562] [<ffffffff811b5eaf>] ? __d_alloc+0x5f/0x180
[ 40.398162] [<ffffffff81054e5f>] ? virt_efi_get_variable+0x2f/0x40
[ 40.473213] [<ffffffff815a99bb>] ? efivarfs_fill_super+0x1eb/0x2f0
[ 40.548260] [<ffffffff815a97d0>] ? efivarfs_lookup+0x50/0x50
[ 40.617064] [<ffffffff811a2145>] ? mount_single+0xb5/0xe0
[ 40.682744] [<ffffffff815a9418>] ? efivarfs_mount+0x18/0x20
[ 40.750507] [<ffffffff811a2343>] ? mount_fs+0x43/0x1b0
[ 40.813066] [<ffffffff811bbd43>] ? find_filesystem+0x63/0x80
[ 40.881869] [<ffffffff811bcf16>] ? vfs_kern_mount+0x76/0x120
[ 40.950672] [<ffffffff811be354>] ? do_new_mount+0xa4/0x1f0
[ 41.017393] [<ffffffff811bfb56>] ? do_mount+0x1e6/0x220
[ 41.080994] [<ffffffff811bfc20>] ? sys_mount+0x90/0xe0
[ 41.143552] [<ffffffff8170d4dd>] ? system_call_fastpath+0x1a/0x1f
[ 41.217556] Code: Bad RIP value.
[ 41.257432] RIP [<000000008e34dd1c>] 0x8e34dd1b
[ 41.312810] RSP <ffff8802631f9bd8>
[ 41.354552] CR2: 000000008e34dd1c
[ 41.394212] ---[ end trace 3864a6ce97098ad5 ]---
[ 41.468067] Adding 9757564k swap on /dev/md1. Priority:-1 extents:1 across:9757564k
[ 41.598047] EXT4-fs (md0): re-mounted. Opts: errors=remount-ro
[ 41.863427] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 42.054903] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-49-generic 3.2.0-49.75
ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46
Uname: Linux 3.2.0-49-generic x86_64
AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Jul 19 10:01 seq
 crw-rw---T 1 root audio 116, 33 Jul 19 10:01 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.3
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
Date: Fri Jul 19 19:59:20 2013
HibernationDevice: RESUME=UUID=ae05a2f7-1352-4fa6-bb69-2eef41db0282
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth0 no wireless extensions.
MachineType: Intel Corporation S5500BC
MarkForUpload: True
PciMultimedia:

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

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-49-generic root=UUID=c5530fcd-f58c-4374-b0db-da1f8c3bc4aa ro console=ttyS0 noefi
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-49-generic N/A
 linux-backports-modules-3.2.0-49-generic N/A
 linux-firmware 1.79.4
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: S5500.86B.01.00.0061.030920121535
dmi.board.name: S5500BC
dmi.board.vendor: Intel Corporation
dmi.board.version: ..........
dmi.chassis.type: 17
dmi.modalias: dmi:bvnIntelCorp.:bvrS5500.86B.01.00.0061.030920121535:bd03/09/2012:svnIntelCorporation:pnS5500BC:pvr....................:rvnIntelCorporation:rnS5500BC:rvr..........:cvn:ct17:cvr:
dmi.product.name: S5500BC
dmi.product.version: ....................
dmi.sys.vendor: Intel Corporation
---
AlsaDevices:
 total 0
 crw-rw---T 1 root audio 116, 1 Jul 19 20:19 seq
 crw-rw---T 1 root audio 116, 33 Jul 19 20:19 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.3
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
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=ae05a2f7-1352-4fa6-bb69-2eef41db0282
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth0 no wireless extensions.
MachineType: Intel Corporation S5500BC
MarkForUpload: True
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 SHELL=/bin/bash
 LANG=ru_RU.UTF-8
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-49-generic root=UUID=c5530fcd-f58c-4374-b0db-da1f8c3bc4aa ro console=ttyS0
ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-49-generic N/A
 linux-backports-modules-3.2.0-49-generic N/A
 linux-firmware 1.79.4
RfKill: Error: [Errno 2] No such file or directory
Tags: precise
Uname: Linux 3.2.0-49-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare storage sudo
dmi.bios.date: 03/09/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: S5500.86B.01.00.0061.030920121535
dmi.board.name: S5500BC
dmi.board.vendor: Intel Corporation
dmi.board.version: ..........
dmi.chassis.type: 17
dmi.modalias: dmi:bvnIntelCorp.:bvrS5500.86B.01.00.0061.030920121535:bd03/09/2012:svnIntelCorporation:pnS5500BC:pvr....................:rvnIntelCorporation:rnS5500BC:rvr..........:cvn:ct17:cvr:
dmi.product.name: S5500BC
dmi.product.version: ....................
dmi.sys.vendor: Intel Corporation

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
Revision history for this message
Vladimir Andreev (bigtucan) wrote : AcpiTables.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Vladimir Andreev (bigtucan) wrote : BootDmesg.txt

apport information

Revision history for this message
Vladimir Andreev (bigtucan) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Vladimir Andreev (bigtucan) wrote : Lspci.txt

apport information

Revision history for this message
Vladimir Andreev (bigtucan) wrote : Lsusb.txt

apport information

Revision history for this message
Vladimir Andreev (bigtucan) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Vladimir Andreev (bigtucan) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Vladimir Andreev (bigtucan) wrote : ProcModules.txt

apport information

Revision history for this message
Vladimir Andreev (bigtucan) wrote : UdevDb.txt

apport information

Revision history for this message
Vladimir Andreev (bigtucan) wrote : UdevLog.txt

apport information

Revision history for this message
Vladimir Andreev (bigtucan) wrote : WifiSyslog.txt

apport information

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote : Re: Kernel crash on EFI system

Hi,
  I know there are lots of EFI fixes that are going in for people; so what's the newest kernel you've tried; I'd try the newest
thing that you can; try the instructions at:
https://wiki.ubuntu.com/Kernel/BugTriage/Responses#Please_Test_Latest_Upstream
to get the latest.

Dave

Revision history for this message
Vladimir Andreev (bigtucan) wrote :

I tried to use kernel version 3.9 (latest available revision on thursday or friday).

I decided to try latest kernel available here http://kernel.ubuntu.com/~kernel-ppa/mainline/ to be sure it doesn't solve my problem... but it works!

System successfully loaded and now running.

Will you prompt me how I can recognize what was the reason of kernel panic in 3.9 versions?

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

OK, so can you just confirm exactly which version you tested that worked; ideally if you can add
the tag explaining this as per:
https://wiki.ubuntu.com/Kernel/BugTriage/Responses#Please_Test_Latest_Upstream

Dave

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-bug-exists-upstream-v.3.9.11 kernel-fixed-upstream-v.3.10.1
Revision history for this message
Vladimir Andreev (bigtucan) wrote :

I have specially tested today all latest kernels to find point after which kernel works well.

3.9.11 kernel panics, but 3.10.1 and 3.10.2 boot stable. I tried to reboot my system many times and found no crashes.

penalvch (penalvch)
summary: - Kernel crash on EFI system
+ BUG: unable to handle kernel paging request at 000000008e34dd1c; RIP:
+ 0010:[<000000008e34dd1c>] [<000000008e34dd1c>] 0x8e34dd1b
description: updated
penalvch (penalvch)
tags: added: bios-outdated-61.01292013
tags: added: needs-reverse-bisect
removed: efi
Revision history for this message
Vladimir Andreev (bigtucan) wrote :

I understood that this crash was related to efivarfs auto mount in kernel 3.9. Kernel 3.10 and 3.11 doesn't do it automatically, that leads to successful boot. But manual attempt to mount efivarfs in these versions of kernel also leads to system crash.

Revision history for this message
Vladimir Andreev (bigtucan) wrote :

Christopher, BIOS version does'n play significant role in this case. Latest BIOS v.63 doesn't help to solve this problem.

Revision history for this message
penalvch (penalvch) wrote :

Vladimir Andreev, thank you for your comments. In your Precise install, could you please test https://launchpad.net/ubuntu/+source/linux-meta-lts-saucy and advise if this works for you?

Changed in linux (Ubuntu):
importance: High → Low
status: Confirmed → Incomplete
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.