From mboxrd@z Thu Jan 1 00:00:00 1970 From: Niraj Tolia Subject: Dom0 OOPS - causes restart Date: Mon, 12 Jul 2004 18:28:00 +0100 Sender: xen-devel-admin@lists.sourceforge.net Message-ID: <7e45e2ac04071210287edb0d19@mail.gmail.com> References: <7e45e2ac0407120605781a8c99@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <7e45e2ac0407120605781a8c99@mail.gmail.com> Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: "xen-devel@lists.sourceforge.net" List-Id: xen-devel@lists.xenproject.org ** Forwarding to the list to provide context to a later email ** now that the listserv seems to be back up ---------- Forwarded message ---------- From: Niraj Tolia Date: Mon, 12 Jul 2004 14:05:46 +0100 Subject: Dom0 OOPS - causes restart To: "xen-devel@lists.sourceforge.net" Got an OOPS in dom0 (included below) that caused the machine to reboot. Did a bk pull this morning (-r 1.1069). This is what I did to get the oops. a) loaded iSCSI drivers in dom0 (for the Intel 1000 Pro T iSCSI initiator) b) Created a domain that used one of the partitions from the iSCSI drive that was mounted (giving the 'phy:sda1,hda1,rw' option in the domain config file). The domain uses the xen0 kernel image c) Tried to run Postmark within the newly created domain (not dom0). FWIW, I can run Postmark and IOzone just fine in dom0. I also ran into another problem and I don't know if its related. When trying to create a new domain (same config as specified above), I got an OOPS in dom1 (not 0) just after the point when the kernel says its trying to DHCP for addresses. However, I wasn't quick enough to capture it. Could not reproduce the problem after a reboot. Niraj ksymoops 2.4.9 on i686 2.4.22-1.2194.nptl. Options used -v ./vmlinux-syms-2.4.26-xen0 (specified) -K (specified) -L (specified) -O (specified) -m ./System.map (specified) Unable to handle kernel paging request at virtual address c4986ffe c01c34e8 Oops: 0003 CPU: 0 EIP: 0819:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00213297 eax: 0c0005df ebx: c63ab920 ecx: 00000010 edx: c4986ffe esi: c08eb8f0 edi: c5af9008 ebp: 00000000 esp: c0273b04 ds: 0821 es: 0821 ss: 0821 Process swapper (pid: 0, stackpage=c0273000)<1> Stack: 00000004 c5af9008 c01c30ae c4986ffe c08eb8f0 00000010 00000000 c017af2b c63ab920 c0273b64 00000004 00000000 c5af9008 c0273b44 c01c3070 80000000 c02daf40 c5af9008 c498700e c08eb900 c01c3070 c01c786e 00000002 00000004 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] <0>Kernel panic: Aiee, killing interrupt handler! Warning (Oops_read): Code line not seen, dumping what data is available >>EIP; c01c34e8 <__constant_memcpy+88/110> <===== >>eax; 0c0005df <__start___xen_guest+bffa145/bfff9b66> >>esp; c0273b04 Trace; c01c30ae Trace; c017af2b Trace; c01c3070 Trace; c01c3070 Trace; c01c786e Trace; c01c3070 Trace; c017aba6 Trace; c01c3070 Trace; c017aeea Trace; c01c3070 Trace; c01c31b9 Trace; c01c3070 Trace; c017af2b Trace; c01c3160 Trace; c01c72d6 Trace; c01c3160 Trace; c017af2b Trace; c01c7240 Trace; c01c3160 Trace; c01c7452 Trace; c01c7240 Trace; c017aba6 Trace; c01c3160 Trace; c017aeea Trace; c01c3160 Trace; c01c3291 <__br_forward+61/70> Trace; c01c3160 Trace; c01c3f2f Trace; c017af2b Trace; c01c3e70 Trace; c01c3e70 Trace; c01c6d65 Trace; c01c3e70 Trace; c01c6c50 Trace; c017aba6 Trace; c01c6c50 Trace; c017af2b Trace; c01c6c50 Trace; c01c6c50 Trace; c01c3e70 Trace; c01c7147 Trace; c01c6c50 Trace; c017aba6 Trace; c01c3e70 Trace; c017aeea Trace; c01c3e70 Trace; c01c3e70 Trace; c01c40f9 Trace; c01c3e70 Trace; c0172f69 Trace; c0173156 Trace; c01732b5 Trace; c000dd47 Trace; c00ae29a Trace; c00b2a2f Trace; c00aca8b Trace; c00aa992 1 warning issued. Results may not be reliable. ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com