Hi Petr, Am 17.03.2015 um 11:06 schrieb Petr Mladek:
On Mon 2015-03-16 19:39:24, Stefan Seyfried wrote:
There was a warning hours before: [199863.599115] usb 2-1: USB disconnect, device number 11 [199863.602226] blk_update_request: I/O error, dev sdb, sector 392872 [199863.602238] Buffer I/O error on dev sdb6, logical block 981, lost async page write [199863.656036] Buffer I/O error on dev sdb3, logical block 16385, lost sync page write [199863.656041] JBD2: Error -5 detected when updating journal superblock for sdb3-8. [199863.656071] Buffer I/O error on dev sdb3, logical block 1, lost sync page write [199863.656126] ------------[ cut here ]------------ [199863.656133] WARNING: CPU: 0 PID: 23916 at ../fs/block_dev.c:57 __blkdev_put+0x1b7/0x200() [199863.656135] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat ppp_deflate bsd_comp ppp_async crc_ccitt ppp [199863.656189] videobuf2_vmalloc videobuf2_memops thinkpad_acpi videobuf2_core btusb v4l2_common videodev i2c_ [199863.656221] CPU: 0 PID: 23916 Comm: umount Not tainted 4.0.0-rc3-2.gd5c547f-desktop #1 [199863.656223] Hardware name: LENOVO 74665EG/74665EG, BIOS 6DET71WW (3.21 ) 12/13/2011 [199863.656225] 0000000000000000 ffffffff81a6733a ffffffff8167ab5d 0000000000000000 [199863.656229] ffffffff81063af1 ffff880189b708c0 ffff880189b70a38 ffff880189b709b0 [199863.656232] ffff8801c2f60000 ffff880189b708d8 ffffffff8120f957 ffff880189b708d8 [199863.656235] Call Trace: [199863.656248] [<ffffffff8100576c>] dump_trace+0x8c/0x340 [199863.656253] [<ffffffff81005ac3>] show_stack_log_lvl+0xa3/0x190 [199863.656257] [<ffffffff81007221>] show_stack+0x21/0x50 [199863.656263] [<ffffffff8167ab5d>] dump_stack+0x47/0x67 [199863.656269] [<ffffffff81063af1>] warn_slowpath_common+0x81/0xb0 [199863.656273] [<ffffffff8120f957>] __blkdev_put+0x1b7/0x200 [199863.656280] [<ffffffff811da7e7>] deactivate_locked_super+0x47/0x80 [199863.656286] [<ffffffff811f6c8b>] cleanup_mnt+0x3b/0x80 [199863.656291] [<ffffffff8107f724>] task_work_run+0xc4/0xe0 [199863.656295] [<ffffffff81002f89>] do_notify_resume+0x69/0x90 [199863.656301] [<ffffffff8168166b>] int_signal+0x12/0x17 [199863.656311] [<00007f9ea4b03ae7>] 0x7f9ea4b03ae7 [199863.656313] ---[ end trace 8f65dffbbd0d78f0 ]--- [199863.676157] Buffer I/O error on dev sdb6, logical block 1606581, lost sync page write [199863.676161] JBD2: Error -5 detected when updating journal superblock for sdb6-8. [199863.676208] Buffer I/O error on dev sdb6, logical block 0, lost sync page write
I don't think is is related, but who knows.
To be honest, I am still not much experienced with debugging such problems, so I am not sure. Anyway, it seems that this warning caused that the kernel was tainted.
I think so, too, that the "W"arn taint is from this warning.
Unfortunately, I am unable to see more useful information in the final PANIC. The doulble fault has happened when showing stack. It might help to know who triggered showing the stack but I do not see it anywhere.
By other words, could you please send the whole dmesg log that is accessible from the vmcore?
There are also several segfaults from libvirt_driver_interface.so. IMHO, they should not break kernel but they are suspicious. This partial problem seems to be related to https://bugzilla.opensuse.org/show_bug.cgi?id=920551
They are definitely related to that, again they should not crash the kernel.
Thanks for having a look. I have for now gone bak to 3.19.1. If it is a hardware problem, I should trigger it there, too.
It is worth try, definitely.
It's all I can do now anyway :-) I'll start some stress-testing inside the VM an will watch out for crashes. Thanks for looking, I have also sent this problem to the linux-kernel list, but apparently I'm the only one having those issues. Best regards, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org