All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tom Cranbrook" <tcranbrook@australia.edu>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
	tcranbrook@australia.edu,
	xen-devel@lists.sourceforge.netIan.Pratt@cl.cam.ac.uk
Subject: Re: a Xandos data dump
Date: Wed, 29 Sep 2004 11:59:06 -0400	[thread overview]
Message-ID: <415bb693.40af.0@australia.edu> (raw)

>> While trying to track down the problem with booting Xandros, I got the
>> attached data dump.  This is the entire console session.  Is this coming
>> from Xen?
>
>Nope. The crashdump is coming from the -xenU kernel. It seems to
>be crashing in reiserfs, but I suspect this isn't the real
>problem.
>
>"unable to open initial console" is interesting. Has your
>reiserfs root filesystem got a /dev/console device? What's the
>major/minor?
>

Not sure what you are asking.  The nonrunning root fs /dev is unpopulated,
it is there on a normal boot of the partition, and I can't see it as a Xen
domain.



>Further, the "obsolete bdflush system call" suggests that the
>file system is intended for an older 2.4 kernel rather than 2.6
>(have you tried building a 2.4 Xen kernel -- "make linux24")?
>

I'll do this.  The distro does run a 2.4

>The "set iopl to 3" is harmless, but suggests that something in
>your init scripts is trying to access hardware very early on. 
>This is unlikely to cause things to break, but it's worth
>eliminating. Perhaps there's a hwclock invocation in rc.sysinit?
>

Xandros does do a very through device detection run on each boot.  Any
chance this might be causing an issue?



>One other thing to watch out for is that your /etc/fstab should
>contain real device names rather than LABEL= lines. Also, don't
>use devfs.
>
>If you're able, put a tar ball of the installation up somewhere
>on the web so that we can download and try and reproduce (tar
>-zcpf).
>

:(  too big, I'm afraid.  It's about a 7gig fs.  If this problem persists,
I've sure I cant trim that for testing.






-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl

             reply	other threads:[~2004-09-29 15:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29 15:59 Tom Cranbrook [this message]
2004-09-29 16:23 ` a Xandos data dump Ian Pratt
2004-09-29 16:42   ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2004-09-29 21:22 Tom Cranbrook
2004-09-29 19:25 Tom Cranbrook
2004-09-28 20:28 Tom Cranbrook
2004-09-28 21:00 ` Ian Pratt
2004-09-28 21:16   ` Mark A. Williamson

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=415bb693.40af.0@australia.edu \
    --to=tcranbrook@australia.edu \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.netIan.Pratt \
    /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.