You are not logged in.

Pages: 1

#1 2013-02-03 18:36:51

DnF
Member
Registered: 2010-08-15
Posts: 19

Box with UEFI+GPT+raid5+lvm+ext4 freezes (kernel BUG)

Hi all,

my box with fresh install sometimes freezes. After reboot everything seems OK again. In journalctl I have found bold red line like this:
kernel BUG at fs/ext4/inode.c:1401!
but far more scary, if you see it in your log... on a machine where my photos should be saved ...

I have UEFI+GPT+raid5+lvm2+ext4 setup, all works good and is configured step by step with wiki and man pages, I have checked what I could, but this bug appeared twice up to this point, both times when data was copied via samba, but no samba errors are in the log.
about the box:

[root@merkur ~]# uname -a
Linux merkur 3.7.4-1-ARCH #1 SMP PREEMPT Mon Jan 21 23:05:29 CET 2013 x86_64 GNU/Linux

my disk layout, the same is for sdb, c and d:

[root@merkur ~]# lsblk
NAME                   MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
sda                      8:0    0  1.8T  0 disk  
├─sda1                   8:1    0  600M  0 part  
├─sda2                   8:2    0  200M  0 part  
├─sda3                   8:3    0   50G  0 part  
│ └─md1                  9:1    0   50G  0 raid1 
│   ├─vg1-bout (dm-0)  254:0    0  200M  0 lvm   /boot
│   ├─vg1-rout (dm-1)  254:1    0   40G  0 lvm   /
│   └─vg1-swaup (dm-2) 254:2    0  9.8G  0 lvm   
└─sda4                   8:4    0  1.8T  0 part  
  └─md0                  9:0    0  5.3T  0 raid5 
    ├─vg0-vaur (dm-3)  254:3    0   30G  0 lvm   /var
    └─vg0-houm (dm-4)  254:4    0    5T  0 lvm   /home

and the full error log. I can identify only names of some modules there, but I understand only what few of them are... 

Feb 03 16:57:07 merkur kernel: ------------[ cut here ]------------
Feb 03 16:57:07 merkur kernel: kernel BUG at fs/ext4/inode.c:1401!
Feb 03 16:57:07 merkur kernel: invalid opcode: 0000 [#1] PREEMPT SMP 
Feb 03 16:57:07 merkur kernel: Modules linked in: nls_cp437 vfat fat i915 coretemp kvm crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 iTCO_wdt
Feb 03 16:57:07 merkur kernel: CPU 3 
Feb 03 16:57:07 merkur kernel: Pid: 392, comm: flush-254:4 Not tainted 3.7.4-1-ARCH #1 System manufacturer System Product Name/P8H77-I
Feb 03 16:57:07 merkur kernel: RIP: 0010:[<ffffffffa02003a8>]  [<ffffffffa02003a8>] mpage_da_submit_io+0x598/0x5e0 [ext4]
Feb 03 16:57:07 merkur kernel: RSP: 0018:ffff8804006d7778  EFLAGS: 00010246
Feb 03 16:57:07 merkur kernel: RAX: 020000000000282c RBX: 0000000000001365 RCX: 0000000000000000
Feb 03 16:57:07 merkur kernel: RDX: 0000000000000000 RSI: ffff880004d96788 RDI: ffff8804006d7b10
Feb 03 16:57:07 merkur kernel: RBP: ffff8804006d78b8 R08: 5200000000000000 R09: 0000000000001000
Feb 03 16:57:07 merkur kernel: R10: ffff8804006d7838 R11: 0000000000000000 R12: ffff8804006d78f0
Feb 03 16:57:07 merkur kernel: R13: ffffea000bd56a00 R14: 0000000000001365 R15: 0000000029330365
Feb 03 16:57:07 merkur kernel: FS:  0000000000000000(0000) GS:ffff88041fb80000(0000) knlGS:0000000000000000
Feb 03 16:57:07 merkur kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 03 16:57:07 merkur kernel: CR2: 00007f9bd41ae7b4 CR3: 000000000280c000 CR4: 00000000001407e0
Feb 03 16:57:07 merkur kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 03 16:57:07 merkur kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Feb 03 16:57:07 merkur kernel: Process flush-254:4 (pid: 392, threadinfo ffff8804006d6000, task ffff880402088000)
Feb 03 16:57:07 merkur kernel: Stack:
Feb 03 16:57:07 merkur kernel:  ffff88031b7fb208 0000000000001000 ffff8804006d7830 ffff880004d968d8
Feb 03 16:57:07 merkur kernel:  ffff8804006d7820 ffff8804006d7b10 0000000000000000 000000000000090d
Feb 03 16:57:07 merkur kernel:  ffff8804006d7888 0000000000001366 ffff880004d96788 00000000000016fb
Feb 03 16:57:07 merkur kernel: Call Trace:
Feb 03 16:57:07 merkur kernel:  [<ffffffffa02028da>] mpage_da_map_and_submit+0x17a/0x4d0 [ext4]
Feb 03 16:57:07 merkur kernel:  [<ffffffffa0203128>] write_cache_pages_da+0x418/0x490 [ext4]
Feb 03 16:57:07 merkur kernel:  [<ffffffffa0203530>] ext4_da_writepages+0x390/0x690 [ext4]
Feb 03 16:57:07 merkur kernel:  [<ffffffffa00864e7>] ? raid5_unplug+0x87/0x90 [raid456]
Feb 03 16:57:07 merkur kernel:  [<ffffffff8112cb4e>] do_writepages+0x1e/0x40
Feb 03 16:57:07 merkur kernel:  [<ffffffff811ac9bb>] __writeback_single_inode+0x3b/0x190
Feb 03 16:57:07 merkur kernel:  [<ffffffff8107b9be>] ? wake_up_bit+0x2e/0x40
Feb 03 16:57:07 merkur kernel:  [<ffffffff811ae7da>] writeback_sb_inodes+0x2ba/0x4a0
Feb 03 16:57:07 merkur kernel:  [<ffffffff811aea5f>] __writeback_inodes_wb+0x9f/0xd0
Feb 03 16:57:07 merkur kernel:  [<ffffffff811aeda3>] wb_writeback+0x313/0x340
Feb 03 16:57:07 merkur kernel:  [<ffffffff811af8b8>] wb_do_writeback+0x258/0x260
Feb 03 16:57:07 merkur kernel:  [<ffffffff811af953>] bdi_writeback_thread+0x93/0x2d0
Feb 03 16:57:07 merkur kernel:  [<ffffffff811af8c0>] ? wb_do_writeback+0x260/0x260
Feb 03 16:57:07 merkur kernel:  [<ffffffff8107b050>] kthread+0xc0/0xd0
Feb 03 16:57:07 merkur kernel:  [<ffffffff81010000>] ? perf_trace_xen_mmu_set_pte_at+0xb0/0x100
Feb 03 16:57:07 merkur kernel:  [<ffffffff8107af90>] ? kthread_freezable_should_stop+0x70/0x70
Feb 03 16:57:07 merkur kernel:  [<ffffffff814b42ac>] ret_from_fork+0x7c/0xb0
Feb 03 16:57:07 merkur kernel:  [<ffffffff8107af90>] ? kthread_freezable_should_stop+0x70/0x70
Feb 03 16:57:07 merkur kernel: Code: 00 00 00 08 0f 84 00 fb ff ff 3d 00 08 00 00 74 07 3d 00 0c 00 00 75 4a c7 85 f0 fe ff ff 00 00 00 00 e9 e3 fa ff ff 0f 0b 0f 0b <0f> 0b 0f 0b 49 8b 45 00 f6 c4 01 0f 84 e8 fd ff ff 44 89 ce 4c 
Feb 03 16:57:07 merkur kernel: RIP  [<ffffffffa02003a8>] mpage_da_submit_io+0x598/0x5e0 [ext4]
Feb 03 16:57:07 merkur kernel:  RSP <ffff8804006d7778>
Feb 03 16:57:07 merkur kernel: ---[ end trace 0d93004092202083 ]---
Feb 03 16:57:07 merkur kernel: ------------[ cut here ]------------
Feb 03 16:57:07 merkur kernel: WARNING: Feb 03 16:57:07 merkur kernel:  [<ffffffff8105750f>] warn_slowpath_common+0x7f/0xc0
Feb 03 16:57:07 merkur kernel:  [<ffffffff8105756a>] warn_slowpath_null+0x1a/0x20
Feb 03 16:57:07 merkur kernel:  [<ffffffff8105ceb5>] do_exit+0x55/0x940
Feb 03 16:57:07 merkur kernel:  [<ffffffff814a375f>] ? printk+0x4d/0x4f
Feb 03 16:57:07 merkur kernel:  [<ffffffff8105ad41>] ? kmsg_dump+0xc1/0xd0
Feb 03 16:57:07 merkur kernel:  [<ffffffff814adcbd>] oops_end+0x9d/0xe0
Feb 03 16:57:07 merkur kernel:  [<ffffffff81018ed8>] die+0x58/0x90
Feb 03 16:57:07 merkur kernel:  [<ffffffff814ad59b>] do_trap+0x6b/0x170
Feb 03 16:57:07 merkur kernel:  [<ffffffff81016465>] do_invalid_op+0x95/0xb0
Feb 03 16:57:07 merkur kernel:  [<ffffffffa02003a8>] ? mpage_da_submit_io+0x598/0x5e0 [ext4]
Feb 03 16:57:07 merkur kernel:  [<ffffffff811ba634>] ? __bio_add_page.part.19+0xf4/0x230
Feb 03 16:57:07 merkur kernel:  [<ffffffff814b54de>] invalid_op+0x1e/0x30
Feb 03 16:57:07 merkur kernel:  [<ffffffffa02003a8>] ? mpage_da_submit_io+0x598/0x5e0 [ext4]
Feb 03 16:57:07 merkur kernel:  [<ffffffffa020030c>] ? mpage_da_submit_io+0x4fc/0x5e0 [ext4]
Feb 03 16:57:07 merkur kernel:  [<ffffffffa02028da>] mpage_da_map_and_submit+0x17a/0x4d0 [ext4]
Feb 03 16:57:07 merkur kernel:  [<ffffffffa0203128>] write_cache_pages_da+0x418/0x490 [ext4]
Feb 03 16:57:07 merkur kernel:  [<ffffffffa0203530>] ext4_da_writepages+0x390/0x690 [ext4]
Feb 03 16:57:07 merkur kernel:  [<ffffffffa00864e7>] ? raid5_unplug+0x87/0x90 [raid456]
Feb 03 16:57:07 merkur kernel:  [<ffffffff8112cb4e>] do_writepages+0x1e/0x40
Feb 03 16:57:07 merkur kernel:  [<ffffffff811ac9bb>] __writeback_single_inode+0x3b/0x190
Feb 03 16:57:07 merkur kernel:  [<ffffffff8107b9be>] ? wake_up_bit+0x2e/0x40
Feb 03 16:57:07 merkur kernel:  [<ffffffff811ae7da>] writeback_sb_inodes+0x2ba/0x4a0
Feb 03 16:57:07 merkur kernel:  [<ffffffff811aea5f>] __writeback_inodes_wb+0x9f/0xd0
Feb 03 16:57:07 merkur kernel:  [<ffffffff811aeda3>] wb_writeback+0x313/0x340
Feb 03 16:57:07 merkur kernel:  [<ffffffff811af8b8>] wb_do_writeback+0x258/0x260
Feb 03 16:57:07 merkur kernel:  [<ffffffff811af953>] bdi_writeback_thread+0x93/0x2d0
Feb 03 16:57:07 merkur kernel:  [<ffffffff811af8c0>] ? wb_do_writeback+0x260/0x260
Feb 03 16:57:07 merkur kernel:  [<ffffffff8107b050>] kthread+0xc0/0xd0
Feb 03 16:57:07 merkur kernel:  [<ffffffff81010000>] ? perf_trace_xen_mmu_set_pte_at+0xb0/0x100
Feb 03 16:57:07 merkur kernel:  [<ffffffff8107af90>] ? kthread_freezable_should_stop+0x70/0x70
Feb 03 16:57:07 merkur kernel:  [<ffffffff814b42ac>] ret_from_fork+0x7c/0xb0
Feb 03 16:57:07 merkur kernel:  [<ffffffff8107af90>] ? kthread_freezable_should_stop+0x70/0x70
Feb 03 16:57:07 merkur kernel: ---[ end trace 0d93004092202084 ]---
at kernel/exit.c:817 do_exit+0x55/0x940()
Feb 03 16:57:07 merkur kernel: Hardware name: System Product Name
Feb 03 16:57:07 merkur kernel: Modules linked in: nls_cp437 vfat fat i915 coretemp kvm crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 iTCO_wdt
Feb 03 16:57:07 merkur kernel: Pid: 392, comm: flush-254:4 Tainted: G      D      3.7.4-1-ARCH #1
Feb 03 16:57:07 merkur kernel: Call Trace:

Well, what should I do now? Help, please!

Offline

#2 2013-02-06 00:30:34

DnF
Member
Registered: 2010-08-15
Posts: 19

Re: Box with UEFI+GPT+raid5+lvm+ext4 freezes (kernel BUG)

Bump this, I crawled through all logs my system produce, but with no luck, no other error or even warning exists in my logs for past few days, only the one kernel bug. I need at least point where to start with something ... anyone?

Offline

#3 2013-02-06 00:46:20

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: Box with UEFI+GPT+raid5+lvm+ext4 freezes (kernel BUG)

Update to the current kernel.

Note: that is not a fix, but Arch is a rolling release...

There are a heap of bug reports from a couple of years back with a similar error; if it persists, you could look through those for clues.

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#4 2013-02-06 08:39:09

DnF
Member
Registered: 2010-08-15
Posts: 19

Re: Box with UEFI+GPT+raid5+lvm+ext4 freezes (kernel BUG)

thanks for head-up, I know about arch nature, this is my fourth arch installation smile but first kernel bug.
I found two similar threads here on arch, but one solved as disk hardware issue, which is not applicable here, I have no similar hardware errors in smart as the other guy. Second one was simply left, so maybe new kernel did the trick..

I will wait for some kernel updates, and will see.

Thanks for the reply.

Offline

#5 2013-02-06 18:23:35

DnF
Member
Registered: 2010-08-15
Posts: 19

Re: Box with UEFI+GPT+raid5+lvm+ext4 freezes (kernel BUG)

So, it seems that nothing but the last writed data is affected by the bug (both times smbd) so I'm using the box in some "safe mode", and waiting for the bug. I will prepare some traps, like logs, to find where is the problem.

what is now in effect:
- deleted 'quiet' from kernel line in grub
- forced samba to make some more log entries

Offline

Pages: 1

Board footer

Powered by FluxBB