Bug#602935: xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27
Angelo Pantano a.pant...@siodata.it writes: since I cannot dump a core if the machine has already crashed I dumped it right after launching the migration command I'm afraid that dump is not going to be very useful. There must be a way to trigger dumping on crash? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8439r4c4jh@sauna.l.org
Bug#602935: xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27
Hi, Google finds the same crash at http://www.chiark.greenend.org.uk/~xensrcts/logs/2449/test-amd64-amd64-pair/guest-debian.guest.osstest-console which is apparently some sort of testsuite log. It says that the version was 28a160746815. Then in the same directory hierarchy I found that the first non-failing version is http://www.chiark.greenend.org.uk/~xensrcts/logs/2473/test-amd64-amd64-pair/guest-debian.guest.osstest-console which says this 6c72eadd151f6f1b904989532a83988af0ea661a, baseline d0054d672ff0ebf6116cee27bae3fc2591c726af -- I have no idea if the bug was fixed or the test was changed. Ian, I noticed you were hosting the testsuite results so I hope it's ok to Cc you about this bug. Can you enlighten us on whether the failing test has already been fixed? For reference here's the beginning of the failing flight 2449: [ 37.107944] BUG: unable to handle kernel paging request at 7f7f850b0098 [ 37.107944] IP: [8105eb42] fill_pmd+0x13/0xec [ 37.107944] PGD 0 [ 37.107944] Oops: [#1] SMP [ 37.107944] last sysfs file: /sys/kernel/uevent_seqnum [ 37.107944] CPU 0 [ 37.107944] Modules linked in: [last unloaded: scsi_wait_scan] [ 37.107944] Pid: 1509, comm: kstop/0 Not tainted 2.6.32.24 #1 [ 37.107944] RIP: e030:[8105eb42] [8105eb42] fill_pmd+0x13/0xec [ 37.107944] RSP: e02b:88001fd1fd20 EFLAGS: 00010082 [ 37.107944] RAX: 0ff8 RBX: c7f8 RCX: ff57a000 [ 37.107944] RDX: 8000cf4d2063 RSI: ff57a000 RDI: c7f8 [ 37.107944] RBP: 88001fd1fd40 R08: R09: 88001fc64008 [ 37.107944] R10: 0396 R11: 8103bb01 R12: 8000cf4d2063 [ 37.107944] R13: ff57a000 R14: e8fe96c8 R15: 88001fcda5d0 [ 37.107944] FS: 7fb35eb96790() GS:8800026b2000() knlGS: [ 37.107944] CS: e033 DS: ES: CR0: 8005003b [ 37.107944] CR2: 7f7f850b0098 CR3: 204a7000 CR4: 2660 [ 37.107944] DR0: DR1: DR2: [ 37.107944] DR3: DR6: 0ff0 DR7: 0400 [ 37.107944] Process kstop/0 (pid: 1509, threadinfo 88001fd1e000, task 88001fcda5d0) [ 37.107944] Stack: [ 37.107944] 88001fd1fd70 ff57a000 8000cf4d2063 e8fe96c0 [ 37.107944] 0 88001fd1fd70 8105ec40 00012ed2d067 8000cf4d2063 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/84fwv9h31l@sauna.l.org
Bug#602935: xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27
since I cannot dump a core if the machine has already crashed I dumped it right after launching the migration command it's about a 250mb file, if you cannot reproduce the bug let me know how to extract the information from the core cheers -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cda770e.9050...@siodata.it
Bug#602935: xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27
Package: xen-linux-system-2.6.32-5-xen-amd64 Version: 2.6.32-27 Severity: normal Tags: sid -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xen-linux-system-2.6.32-5-xen-amd64 depends on: ii linux-image-2.6.32-5-xen-amd6 2.6.32-27 Linux 2.6.32 for 64-bit PCs, Xen d ii xen-hypervisor-4.0-amd64 [xen 4.0.1-1The Xen Hypervisor on AMD64 xen-linux-system-2.6.32-5-xen-amd64 recommends no packages. xen-linux-system-2.6.32-5-xen-amd64 suggests no packages. -- no debconf information Hello there, this is related to bug #600992 (now closed). After the fix to that bug this kernel allows migration but as the live migration completes (without error on the dom0) the domU spits the following stack trace: [157949.641828] BUG: unable to handle kernel paging request at 7f11dc370180 [157949.641828] IP: [810327d2] fill_pmd+0xe/0xec [157949.641828] PGD 0 [157949.641828] Oops: [#1] SMP [157949.641828] last sysfs file: /sys/module/parport/initstate [157949.641828] CPU 0 [157949.641828] Modules linked in: ppdev lp parport evdev ext3 jbd mbcache dm_mod raid1 md_mod xen_netfront xen_blkfront [157949.641828] Pid: 2936, comm: kstop/0 Not tainted 2.6.32-5-xen-amd64 #1 [157949.641828] RIP: e030:[810327d2] [810327d2] fill_pmd+0xe/0xec [157949.641828] RSP: e02b:88000f203d40 EFLAGS: 00010082 [157949.641828] RAX: 0ff8 RBX: ff57b000 RCX: ff57b000 [157949.641828] RDX: 80008ac55063 RSI: ff57b000 RDI: c7f8 [157949.641828] RBP: c7f8 R08: R09: 7fff [157949.641828] R10: 8100e5b5 R11: c9082000 R12: ff57b000 [157949.641828] R13: 8800033f5ee0 R14: 88000ee82a60 R15: 88000ee82a60 [157949.641828] FS: 7fb68931e700() GS:8800033d8000() knlGS: [157949.641828] CS: e033 DS: ES: CR0: 8005003b [157949.641828] CR2: 7f11dc370180 CR3: 0fecb000 CR4: 2660 [157949.641828] DR0: DR1: DR2: [157949.641828] DR3: DR6: 0ff0 DR7: 0400 [157949.641828] Process kstop/0 (pid: 2936, threadinfo 88000f202000, task 88000ee82a60) [157949.641828] Stack: [157949.641828] c9082000 8100c287 ff57b000 0884 [157949.641828] 0 80008ac55063 810328d1 899d8067 80008ac55063 [157949.641828] 0 81001000 80008ac55063 8800033f5ed8 810369db [157949.641828] Call Trace: [157949.641828] [8100c287] ? __raw_callee_save_xen_pgd_val+0x11/0x1e [157949.641828] [810328d1] ? set_pte_vaddr_pud+0x21/0x4b [157949.641828] [810369db] ? __native_set_fixmap+0x24/0x2c [157949.641828] [8100d009] ? xen_set_fixmap+0xcc/0xfb [157949.641828] [8100c39e] ? pfn_to_mfn+0xe/0x22 [157949.641828] [8100bedf] ? xen_setup_shared_info+0x2d/0x56 [157949.641828] [8100ef5d] ? xen_post_suspend+0x11/0x90 [157949.641828] [811f3083] ? xen_suspend+0x9a/0xc4 [157949.641828] [8108ba3e] ? stop_cpu+0x83/0xc6 [157949.641828] [810625ff] ? worker_thread+0x188/0x21d [157949.641828] [8108b9bb] ? stop_cpu+0x0/0xc6 [157949.641828] [81065c2a] ? autoremove_wake_function+0x0/0x2e [157949.641828] [81062477] ? worker_thread+0x0/0x21d [157949.641828] [8106595d] ? kthread+0x79/0x81 [157949.641828] [81012baa] ? child_rip+0xa/0x20 [157949.641828] [81011d61] ? int_ret_from_sys_call+0x7/0x1b [157949.641828] [8101251d] ? retint_restore_args+0x5/0x6 [157949.641828] [81012ba0] ? child_rip+0x0/0x20 [157949.641828] Code: 00 00 48 ba 00 f0 ff ff ff 3f 00 00 41 5a 49 8d 04 04 48 21 d1 5b 5d 48 01 c8 41 5c c3 41 54 49 89 f4 55 48 89 fd 53 48 83 ec 10 48 83 3f 00 0f 85 95 00 00 00 e8 23 57 2c 00 48 89 c7 48 89 c3 [157949.641828] RIP [810327d2] fill_pmd+0xe/0xec [157949.641828] RSP 88000f203d40 [157949.641828] CR2: 7f11dc370180 [157949.641828] ---[ end trace 728cde46d51bd637 ]--- [157949.641828] [ cut here ] [157949.641828] WARNING: at /build/mattems-linux-2.6_2.6.32-27-amd64-IsDpkI/linux-2.6-2.6.32/debian/build/source_amd64_xen/kernel/time/timekeeping.c:249 ktime_get+0x22/0xb7() [157949.641828] Modules linked in: ppdev lp parport evdev ext3 jbd mbcache dm_mod raid1 md_mod xen_netfront xen_blkfront [157949.641828] Pid: 0, comm: swapper Tainted: G D 2.6.32-5-xen-amd64 #1 [157949.641828] Call Trace: [157949.641828] [8106d1ab] ? ktime_get+0x22/0xb7 [157949.641828] [8106d1ab] ? ktime_get+0x22/0xb7 [157949.641828]
Bug#602935: xen-linux-system-2.6.32-5-xen-amd64: domU stack trace error when migrating with xen kernel 2.6.32-27
Angelo Pantano tecn...@advert.it writes: if there is anything else we can provide let us know regards Just in case the problem becomes hard to reproduce you probably want to save the state of the crashed child with xm dump-core DOMAIN FILE If you have lots of private data you obviously can not share that dump but we might be able to guide you to extract the information that is needed. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/841v6uiiwx@sauna.l.org
