On Tue, Feb 12, 2008 at 06:54:52AM -0800, Alex Malinovich wrote: > On Tue, 2008-02-12 at 15:44 +0100, Robert Millan wrote: > --snip-- > > Ok. There are two ways we can proceed. Choose the one you prefer. The > > first is if you can reproduce this problem in a (preferrably small) > > filesystem that doesn't contain any sensible output, and upload it > > somewhere. > > > > The second would be to continue debugging this via email (or alternatively, > > via > > IRC). The next step would be to run it in grub-emu and obtain a backtrace: > > > > break kern/disk.c:371 > > run > > backtrace > > I'll try creating a new filesystem tomorrow and see if I can still > reproduce the problem. If not, we can continue this on IRC or Jabber. I > want to get it fixed, but I'm afraid I really don't know much about > grub2 so I'd need someone there with me while I'm troubleshooting.
Ok. If you can't get that image, you can find me in #grub at freenode (my nickname is 'nyu'). Btw, if you want to test filesystem in grub-emu, there's a "loopback" command that will surely come in handy. -- Robert Millan <GPLv2> I know my rights; I want my phone call! <DRM> What use is a phone call… if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
