Bug#399113: xen kernel infinite loop processing core dump
tags 399113 + confirmed stop On Fri, Jan 12, 2007, Knock, Bob wrote: If you enable core dumps, I would expect to see the described crash when using a broken kernel, and Aborted (core dumped) when using a working one. Oh, my mistake, indeed I forgot to follow this step and I reproduce the crash now. -- Loïc Minier [EMAIL PROTECTED]
Bug#399113: xen kernel infinite loop processing core dump
Hi, On Thu, Nov 30, 2006, Knock, Bob wrote: Duplicated with linux-image-2.6.18-3-xen-686. Does not occur with the 2.6.16.29-xen kernel pulled from Xen 3.0.3 LiveCD. Has anyone else duplicated this? Would there be any benefit to posting a VMWare image? Hmm, I tried reproducing your bug in a vmware, and was not able to. Do you still get the bug? I installed a vanilla Etch system from the daily business card ISO, dist-upgraded to sid, installed xen-linux-system-2.6.18-3-xen-686 version 2.6.18-8, rebooted, installed build-essential, built crash.c. ./crash results in Aborted, and only that, nothing new in dmesg. Bye, -- Loïc Minier [EMAIL PROTECTED]
Bug#399113: xen kernel infinite loop processing core dump
Hmm, I tried reproducing your bug in a vmware, and was not able to. Do you still get the bug? Yes, it still happens for me using 2.6.18-8. ./crash results in Aborted, and only that, nothing new in dmesg. It would do that if you failed to enable core dumps via ulimit -c unlimited. If you enable core dumps, I would expect to see the described crash when using a broken kernel, and Aborted (core dumped) when using a working one. Bob
Bug#399113: xen kernel infinite loop processing core dump
Dnia piątek, 5 stycznia 2007 02:41, Janusz Krzysztofik napisał: I always get: qemu:~# ./crash Aborted (core dumped) qemu:~# and nothing in logs. But on my i386 laptop it realy breaks the system. Janusz
Bug#399113: xen kernel infinite loop processing core dump
I am not able to reproduce this bug on my Core2 Duo (2GB RAM) PC running linux-image-2.6.18-3-xen-amd64 with amd64 etch. - linux-image-2.6.18-3-i386 and linux-image-2.6.18-3-k7 (2.6.18-7) Did you try the -xen-686 flavor? I have not seen anyone actually explicitly confirm that the debian kernel team reproduced it, but http://lists.debian.org/debian-kernel/2006/12/msg00347.html and http://lists.debian.org/debian-kernel/2006/12/msg00488.html indicate they did, and are able to avoid the problem by enabling PAE. Bob
Bug#399113: xen kernel infinite loop processing core dump
Dnia piątek, 5 stycznia 2007 19:30, Knock, Bob napisał: - linux-image-2.6.18-3-i386 and linux-image-2.6.18-3-k7 (2.6.18-7) Did you try the -xen-686 flavor? Yes, I meant -xen-686 and -xen-k7 flawours, sorry for my mistake. Janusz
Bug#399113: xen kernel infinite loop processing core dump
Dnia czwartek, 30 listopada 2006 23:47, Knock, Bob napisał: Has anyone else duplicated this? I am not able to reproduce this bug on my Core2 Duo (2GB RAM) PC running linux-image-2.6.18-3-xen-amd64 with amd64 etch. I have also tried to reproduce it on qemu running i386 etch in different configurations: - qemu (Pentium II) and qemu-system-x86_64 (both without kqemu), - single and dual processor, - different memory sizes from 128 to 2000 MB, - linux-image-2.6.18-3-i386 and linux-image-2.6.18-3-k7 (2.6.18-7) I always get: qemu:~# ./crash Aborted (core dumped) qemu:~# and nothing in logs. Janusz
Bug#399113: xen kernel infinite loop processing core dump
Duplicated with linux-image-2.6.18-3-xen-686. Does not occur with the 2.6.16.29-xen kernel pulled from Xen 3.0.3 LiveCD. Has anyone else duplicated this? Would there be any benefit to posting a VMWare image?
Bug#399113: xen kernel infinite loop processing core dump
Package: linux-image-2.6.18-2-xen-686 Version: 2.6.18-5 Severity: critical Executing program crash with core dumps enabled (ulimit -c unlimited) results in kernel looping the following message: Bad pte = 0033e0a0, process = crash, vm_flags = 100070, vaddr = b7602000 [c0144b5d] vm_normal_page+0x98/0xb0 [c0145116] follow_page+0xe8/0x182 [c0146b49] get_user_pages+0x288/0x2f1 [c017b1db] elf_Core_dump+0x972/0xb4b [c015ee74] do_coredump+0x4a8/0x4fc [c012399c] dequeue_signal+0x15/0x9c [c0123fed] get_signal_to_deliver+0x39e/0x3d0 [c0103ee7] do_notify_resume+0x71/0x5e9 [c0156153] __fput+0x11c/0x13f [c0151fd6] kmem_cache_free+0x44/0x7d [c0110b5a] do_page_fault+0x39f/0x7c8 [c012449f] sys_rt_sigprocmask+0x4b/0xc5 [c012449f] sys_rt_sigprocmask+0x4b/0xc5 [c01048b5] work_notifysig+0x13/0x1a repeats infinitely The program aborts and dumps core without issue with the kernel from linux-image-2.6.18-2-686. The system is a Sarge machine with enough packages pulled from unstable to install xen-linux-system-2.6.18-2-xen-686. I have triggered the problem both in Dom0 and a DomU, on both real hardware (opteron) and inside VMWare (p4). gcc crash.c -o crash -ldl -lpthread crash.c (any library appears to work equivalently in the dlopen): - #include dlfcn.h #include pthread.h #include stdlib.h #include unistd.h void* crash(void* arg) { dlopen(libm.so.6, RTLD_LAZY); abort(); return 0; } int main(int argc, char** argv) { pthread_t t; pthread_create(t, NULL, crash, NULL); while (1) { usleep(10); } return (0); }