Public bug reported:
Binary package hint: linux-image-2.6.38-8-server
We are running several servers with Ubuntu 10.10 without any problem so
far. After updating two of the servers to 11.04 and thus kernel 2.6.38
we are seeing the following kernel crash/report showing up:
-- cut here --
[77459.430193] BUG: Dentry ffff8804552403c0{i=167d27,n=/} still in use (1)
[unmount of autofs autofs]
[77459.430271] ------------[ cut here ]------------
[77459.430296] kernel BUG at /build/buildd/linux-2.6.38/fs/dcache.c:947!
[77459.430323] invalid opcode: 0000 [#1] SMP
[77459.430349] last sysfs file:
/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
[77459.430392] CPU 8
[77459.430396] Modules linked in: binfmt_misc parport_pc ppdev ocfs2_dlmfs
ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs autofs4
mptctl k8temp nfsd exportfs nfs lockd fscache nfs_acl lm75 auth_rpcgss sunrpc
lm87 hwmon_vid ipmi_watchdog ipmi_poweroff psmouse radeon serio_raw ttm ipmi_si
drm_kms_helper ipmi_devintf ipmi_msghandler nv_tco drm i2c_nforce2
amd64_edac_mod lp edac_core i2c_algo_bit edac_mce_amd parport k10temp ghes
joydev hed usbhid hid usb_storage qla2xxx mptsas mptscsih scsi_transport_fc
mptbase e1000e scsi_transport_sas scsi_tgt
[77459.430679]
[77459.430699] Pid: 31606, comm: automount Not tainted 2.6.38-8-server
#42-Ubuntu SUN MICROSYSTEMS SUN BLADE X8440 SERVER MODULE/Sun Blade X8440
Server Module
[77459.430761] RIP: 0010:[<ffffffff81179be5>] [<ffffffff81179be5>]
shrink_dcache_for_umount_subtree+0x285/0x290
[77459.430814] RSP: 0018:ffff88047dd19de8 EFLAGS: 00010296
[77459.430839] RAX: 000000000000006c RBX: ffff88045524041c RCX: 00000000ffffffff
[77459.430868] RDX: 0000000000000000 RSI: 0000000000000086 RDI: 0000000000000246
[77459.430896] RBP: ffff88047dd19e28 R08: 0000000000000000 R09: ffffffff816423e0
[77459.430924] R10: 0000000000000000 R11: 0000000000000000 R12: ffff88045524041c
[77459.430953] R13: ffff8804552403c0 R14: ffff880455240460 R15: 00007f72bf923330
[77459.430981] FS: 00007f72bd73a700(0000) GS:ffff88068fc00000(0000)
knlGS:00000000f68b2700
[77459.431025] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[77459.431050] CR2: 00007f7916fa1eb0 CR3: 000000047ed7e000 CR4: 00000000000006e0
[77459.431079] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[77459.431107] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[77459.431136] Process automount (pid: 31606, threadinfo ffff88047dd18000, task
ffff88047ef92dc0)
[77459.431180] Stack:
[77459.431199] ffff88027df22258 ffff88067c5df000 ffff88047dd19e08
ffff88027df22000
[77459.431245] ffff88045524041c ffff8804552403c0 00007f72bf923960
00007f72bf923330
[77459.431291] ffff88047dd19e58 ffffffff8117c521 ffff88047dd19e48
ffff88027df22000
[77459.431337] Call Trace:
[77459.431361] [<ffffffff8117c521>] shrink_dcache_for_umount+0x51/0x90
[77459.431392] [<ffffffff811670ac>] generic_shutdown_super+0x2c/0x100
[77459.431420] [<ffffffff81167216>] kill_anon_super+0x16/0x60
[77459.431446] [<ffffffff81167287>] kill_litter_super+0x27/0x30
[77459.431477] [<ffffffffa047b4d8>] autofs4_kill_sb+0x48/0x60 [autofs4]
[77459.431505] [<ffffffff81167685>] deactivate_locked_super+0x45/0x70
[77459.431533] [<ffffffff8116830a>] deactivate_super+0x4a/0x70
[77459.431562] [<ffffffff811834a4>] mntput_no_expire+0xa4/0xf0
[77459.431588] [<ffffffff81184530>] sys_umount+0x60/0xd0
[77459.431615] [<ffffffff8100bfc2>] system_call_fastpath+0x16/0x1b
[77459.431641] Code: 8b 40 28 4c 8b 08 49 8b 45 30 48 85 c0 74 07 48 8b 90 a8
00 00 00 48 89 34 24 48 c7 c7 c0 a6 7e 81 4c 89 ee 31 c0 e8 30 af 45 00 <0f> 0b
0f 0b 0f 1f 80 00 00 00 00 55 48 89 e5 48 83 ec 20 48 89
[77459.431796] RIP [<ffffffff81179be5>]
shrink_dcache_for_umount_subtree+0x285/0x290
[77459.431839] RSP <ffff88047dd19de8>
[77459.432152] ---[ end trace 6814107156e603e1 ]---
-- cut here --
The two servers have different hardware (this one is from a SunBlade X8440
module), but the crash log is always the same.
The action to trigger that problem is still unclear as the Process it crashes
in is always "automount". We are using autofs for automatically mounting home
and data directories. We see that in case we have a long process running over
certain directory structures which trigger autofs this crash shows up.
Finally the machine ends up in an unstable state which requires a hard reboot
(simply 'reboot' command does not work).
When switching back to kernel linux-image-2.6.35-28-server from Ubuntu
10.10 immediately solves the problem.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: bug kernel oops
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781792
Title:
kernel crash in /build/buildd/linux-2.6.38/fs/dcache.c:947
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
