All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: ls and xfs = unhandled exception / reset
Date: Wed, 16 May 2007 08:39:59 +0200	[thread overview]
Message-ID: <20070516063959.GD22567@aragorn> (raw)
In-Reply-To: <8c0c43de0705151747i243e0detd42c2367523b5058@mail.gmail.com>

On Tue, May 15, 2007 at 08:47:03PM -0400, Alex Roman wrote:
> Hello,
> 
> I've got a linux system with the / partition as xfs (and no /boot
> partition, blame kUbuntu's installer for that :)). I wanted to try to
> boot the system from a grub2 floppy I made (so I can still boot my
> system, no worries).
> 
> I do:
> insmod ls
> insmod pc
> insmod xfs
> 
> Then if I do:
> ls (hd0,1) -- my xfs partition
> 
> ... the system just resets.
> 
> I verified that if I insmod ext2 and ls on an ext3 partition, it will
> work as expected and not reset my PC. Also, if I ls on the xfs
> partition, without the xfs module loaded, GRUB will just print
> Filesystem type unknown, but won't reset.
> 
> Given that I'll also be working on adding CD-ROM boot support to GRUB
> as part of GSoC, I figure this would be a great opportunity to start
> fixing some bugs to get familiar with the code.
> 
> Now, I've no idea how to debug this issue, how to get a debugging log,
> etc... Could anyone please point me at the right document to read or
> give me some advice how I could start working on this?

See:  http://grub.enbug.org/HowToDebug

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.



  reply	other threads:[~2007-05-16  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16  0:47 ls and xfs = unhandled exception / reset Alex Roman
2007-05-16  6:39 ` Robert Millan [this message]
2007-05-16  7:40 ` Marco Gerards

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=20070516063959.GD22567@aragorn \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.org \
    /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.