All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niraj Tolia <ntolia@gmail.com>
To: "xen-devel@lists.sourceforge.net" <xen-devel@lists.sourceforge.net>
Subject: Another OOPS while creating domains
Date: Tue, 13 Jul 2004 16:11:12 +0100	[thread overview]
Message-ID: <7e45e2ac04071308112e252ce5@mail.gmail.com> (raw)

After a bk pull today morning, I am getting reproducible OOPes when
trying to create a new domain. Happens when the new domain kernel is
trying to DHCP.

There are the kernel messages before the OOPS

Sending DHCP requests ...... timed out!
IP-Config: Reopening network devices...
Sending DHCP requests .

(there might have been a few "?" signs after the "." following the
"Sending DHCP requests message that got eaten up by the oops)

The oops passed through ksymoops is as follows. My kernel binaries can
be found at <http://www.cs.cmu.edu/~ntolia/xen>. Let me know if you
need anything else from me.

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 NULL pointer dereference at virtual address 00000076
c0167996
Oops: 0000
CPU:    0
EIP:    0819:[<c0167996>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000   ebx: c164b160   ecx: 00000002   edx: 00000001
esi: 00000001   edi: 00000006   ebp: c164b000   esp: c159ded4
ds: 0821   es: 0821   ss: 0821
Process swapper (pid: 1, stackpage=c159d000)<1>
Stack: dfdfbc80 000016e1 c1642054 00000006 c164b160 c0167cce c164b000 00000000
       00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
       00000000 00000000 c164b000 dfdfbc80 c164b07c c017b9ef dfdfbc80 c164b000
Call Trace: [<c0167cce>] [<c017b9ef>] [<c017b4b0>] [<c0172a5f>] [<c0003880>]
   [<c00aab9e>] [<c0003870>]
 <0>Kernel panic: Aiee, killing interrupt handler!
Warning (Oops_read): Code line not seen, dumping what data is available
 
 
>>EIP; c0167996 <network_tx_buf_gc+66/100>   <=====
 
Trace; c0167cce <network_start_xmit+fe/270>
Trace; c017b9ef <qdisc_restart+4f/d0>
Trace; c017b4b0 <eth_header+0/110>
Trace; c0172a5f <dev_queue_xmit+1af/280>
Trace; c0003880 <init+10/100>
Trace; c00aab9e <arch_kernel_thread+2e/40>
Trace; c0003870 <init+0/100>
 
 
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

             reply	other threads:[~2004-07-13 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 15:11 Niraj Tolia [this message]
2004-07-13 16:12 ` Another OOPS while creating domains Ian Pratt
2004-07-13 17:26   ` Keir Fraser
2004-07-13 20:59     ` Niraj Tolia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7e45e2ac04071308112e252ce5@mail.gmail.com \
    --to=ntolia@gmail.com \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.