You are not logged in.
Hello,
I sometimes get a kernel error while shutting down since a while. I think I observed it for the first time after an update at the beginning of september but I am not sure which update caused this exactly. The problem is that the error is a little difficult to reproduce because it does not happen on every shutdown. This is what I could find in the journal:
Oct 03 02:15:07 amalthea systemd[1]: Unmounting /videos...
Oct 03 02:15:07 amalthea kernel: EXT4-fs (sda4): sb orphan head is 36175881
Oct 03 02:15:07 amalthea kernel: sb_info orphan list:
Oct 03 02:15:07 amalthea kernel: inode sda4:36175881 at ffff8800374724f8: mode 100664, nlink 0, next 0
Oct 03 02:15:07 amalthea kernel: ------------[ cut here ]------------
Oct 03 02:15:07 amalthea kernel: kernel BUG at fs/ext4/super.c:818!
Oct 03 02:15:08 amalthea kernel: invalid opcode: 0000 [#1] PREEMPT SMP
Oct 03 02:15:07 amalthea systemd[1]: videos.mount mount process exited, code=killed status=11
Oct 03 02:15:07 amalthea systemd[1]: Unmounted /videos.
Oct 03 02:15:07 amalthea systemd[1]: Unit videos.mount entered failed state.
Oct 03 02:15:07 amalthea systemd[1]: Starting Unmount All Filesystems.
Oct 03 02:15:07 amalthea systemd[1]: Reached target Unmount All Filesystems.
Oct 03 02:15:07 amalthea systemd[1]: Stopping Local File Systems (Pre).
Oct 03 02:15:07 amalthea systemd[1]: Stopped target Local File Systems (Pre).
Oct 03 02:15:07 amalthea systemd[1]: Stopping Remount Root and Kernel File Systems...
Oct 03 02:15:07 amalthea systemd[1]: Stopped Remount Root and Kernel File Systems.
Oct 03 02:15:07 amalthea systemd[1]: Starting Shutdown.
Oct 03 02:15:07 amalthea systemd[1]: Reached target Shutdown.
Oct 03 02:15:08 amalthea systemd[1]: Starting Final Step.
Oct 03 02:15:08 amalthea systemd[1]: Reached target Final Step.
Oct 03 02:15:08 amalthea systemd[1]: Starting Power-Off...
Oct 03 02:15:08 amalthea kernel: Modules linked in: rfcomm bluetooth rfkill rpcsec_gss_krb5 nfsd nfs_acl auth_rpcgss oid_registry nfsv4 uinput joydev x
Oct 03 02:15:08 amalthea kernel: Oct 03 02:15:08 amalthea kernel: CPU: 0 PID: 12120 Comm: umount Tainted: P O 3.11.1-2-ARCH #1
Oct 03 02:15:08 amalthea kernel: Hardware name: /DH67BL, BIOS BLH6710H.86A.0156.2012.0615.1908 06/15/2012
Oct 03 02:15:08 amalthea kernel: task: ffff88005460edb0 ti: ffff8800546f4000 task.ti: ffff8800546f4000
Oct 03 02:15:08 amalthea kernel: RIP: 0010:[<ffffffffa023d073>] [<ffffffffa023d073>] ext4_put_super+0x353/0x360 [ext4]
Oct 03 02:15:08 amalthea kernel: RSP: 0018:ffff8800546f5e30 EFLAGS: 00010202
Oct 03 02:15:08 amalthea kernel: RAX: 0000000000000047 RBX: ffff88007afbe000 RCX: 0000000000000006
Oct 03 02:15:08 amalthea kernel: RDX: 0000000000000007 RSI: 0000000000000046 RDI: 0000000000000246
Oct 03 02:15:08 amalthea kernel: RBP: ffff8800546f5e60 R08: 0000000000000000 R09: 000000000000033d
Oct 03 02:15:08 amalthea kernel: R10: 0000000000000001 R11: 0000000000aaaaaa R12: ffff88007afbe200
Oct 03 02:15:08 amalthea kernel: R13: ffff88007afbe800 R14: ffff88007afbe190 R15: ffff88007afbe200
Oct 03 02:15:08 amalthea kernel: FS: 00007fe105535780(0000) GS:ffff88007e600000(0000) knlGS:0000000000000000
Oct 03 02:15:08 amalthea kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 03 02:15:08 amalthea kernel: CR2: 0000000000793d20 CR3: 000000007551d000 CR4: 00000000000407f0
Oct 03 02:15:08 amalthea kernel: Stack:
Oct 03 02:15:08 amalthea kernel: ffff880000000000 ffff88007afbe800 ffff88007afbe8a0 ffffffffa0267880
Oct 03 02:15:08 amalthea kernel: ffff88007a008740 ffff88007a008720 ffff8800546f5e88 ffffffff811a0fe6
Oct 03 02:15:08 amalthea kernel: ffff88007a4e8e00 0000000000000083 ffff88007a008720 ffff8800546f5ea8
Oct 03 02:15:08 amalthea kernel: Call Trace:
Oct 03 02:15:08 amalthea kernel: [<ffffffff811a0fe6>] generic_shutdown_super+0x56/0xe0
Oct 03 02:15:08 amalthea systemd[1]: Shutting down.
Oct 03 02:15:08 amalthea kernel: [<ffffffff811a12a7>] kill_block_super+0x27/0x70
Oct 03 02:15:08 amalthea kernel: [<ffffffff811a160d>] deactivate_locked_super+0x3d/0x60
Oct 03 02:15:08 amalthea kernel: [<ffffffff811a1bf6>] deactivate_super+0x46/0x60
Oct 03 02:15:08 amalthea kernel: [<ffffffff811bd1af>] mntput_no_expire+0xef/0x150
Oct 03 02:15:08 amalthea kernel: [<ffffffff811be3b1>] SyS_umount+0x91/0x3b0
Oct 03 02:15:08 amalthea kernel: [<ffffffff814e91dd>] system_call_fastpath+0x1a/0x1f
Oct 03 02:15:08 amalthea kernel: Code: a0 48 8d b0 30 03 00 00 41 8b 47 c4 89 04 24 31 c0 e8 1f ad 29 e1 4d 8b 3f 4d 39 fc 75 c4 4c 3b a3 00 02 00 00 0
Oct 03 02:15:08 amalthea kernel: RIP [<ffffffffa023d073>] ext4_put_super+0x353/0x360 [ext4]
Oct 03 02:15:09 amalthea kernel: RSP <ffff8800546f5e30>I already tried to recreate the filesystem on sda4 but that didn't change anything.
The critical thing is that this machine is my PVR and is supposed to shutdown and wake up unattended. But after this error it just sits and displayes the call trace on the console.
Has anyone an idea how to fix this or to debug it further? Any more information I could provide?
Last edited by voeck (2013-10-04 10:32:09)
Offline
I think I have found a probably cause for this problem. It actually seems to be a bug in the NFS server code which was fixed in kernel 3.12-rc1. See https://bugzilla.kernel.org/show_bug.cgi?id=61631 was more details. So I believe I would just have to sit this out and wait until 3.12 is released and hits the repos. Until then I will avoid delete files over NFS. But I'll already mark this as solved for now.
Last edited by voeck (2013-10-04 10:33:40)
Offline