WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] panic in e100_exec_cb()

To: Paul Dorman <pauld@xxxxxxxxx>
Subject: Re: [Xen-devel] panic in e100_exec_cb()
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 21 Sep 2004 21:45:56 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 21 Sep 2004 21:51:49 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Wed, 22 Sep 2004 07:42:25 +1200." <200409220742.25878.pauld@xxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> On Tuesday 21 September 2004 07:37 pm, Ian Pratt wrote:
> > > > With today's build, my domain 0 crashes during boot when it tries to
> > > > bring eth0 up (it's an E100).
> > > >
> > > > cb->prev (eax) is NULL in e100_exec_cb() (e100.c:827).  Just from code
> > > > inspection, I don't see how this can be.  e100_alloc_cbs() was just
> > > > called, which looks like it should have correctly linked up all the
> > > > cb->prev/cb->next pointers.
> > > >
> > > > Has anyone else seen this?
> >
> > Yep -- I can reproduce. It appears to be something e100 specific,
> > as I've tested that tg3, e1000 and 3c95x all work fine.
> 
> Ooh! Looks like I have a different problem then! Any ideas? I imagine it 
> could 
> be the no modules issue. I'll investigate over the next few hours.

Definitely only have one 'console=' option on DOM0's command line. It
may be that some infomration is only getting output to a device that
you are not looking at. It's very unlikely that the machine will
reboot with no visible error message at all.

Are you viewing DOM0 booting over serial line or on the VGA console?
If the former, then specify console=ttyS0 on DOM0's command line. If
the latter then specify console=tty0.

Not that for all other domains you should always specify console=tty0.

 -- Keir


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel