Hi Petr, Am 16.03.2015 um 16:12 schrieb Petr Mladek:
On Sat 2015-03-14 23:16:20, Stefan Seyfried wrote:
Am 14.03.2015 um 22:58 schrieb Stefan Seyfried:
Hi all,
in 4.0.0-rc I have seen a few crashes, always when running KVM guests (IIRC). Today I was able to capture a crash dump, this is the backtrace from dmesg.txt:
I would not totally rule out a hardware problem, since this machine had another weird crash where it crashed and the bios beeper was constant on until I hit the power button for 5 seconds. Does the above state indicate hardware/memory problem, or is it time to try to really dive into that crash dump?
Too bad, that is not an option:
susi:/var/crash/2015-03-14-22:46 # crash vmlinux-4.0.0-rc3-2.gd5c547f-desktop vmcore
crash 7.1.0 [...] This GDB was configured as "x86_64-unknown-linux-gnu"...
WARNING: kernels compiled by different gcc versions: vmlinux-4.0.0-rc3-2.gd5c547f-desktop: (unknown) vmcore kernel: 4.8.3
WARNING: kernel version inconsistency between vmlinux and dumpfile
crash: incompatible arguments: vmlinux-4.0.0-rc3-2.gd5c547f-desktop is not SMP -- vmcore is SMP
I fixed that by applying an upstream patch so that kernel 4.0 is recognized, SR#290838 to Kernel:kdump Unfortunately, the dump does not tell me much more :-)
Well, the dmesg messages are valid even if the kernel and vmcore are incompatible. But the above snippet does not help much. There were most likely one or more errors printed before. A previous error probably triggered show_stack_log_lv failed with the double fault. Also the kernel is already tainted, so there was probably an error message when it has happened.
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.
By other words, could you please send the whole dmesg log that is accessible from the vmcore?
http://paste.opensuse.org/48196621 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. 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