mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Lash <jkl@sarvega.com>
To: "Niel Lambrechts" <antispam@telkomsa.net>
Cc: "'Burton Windle'" <bwindle@fint.org>, <linux-kernel@vger.kernel.org>
Subject: Re: kernel panic after changing processor arch
Date: Mon, 6 Dec 2004 13:07:43 -0600	[thread overview]
Message-ID: <20041206130743.6c5f0fd3@homer.sarvega.com> (raw)
In-Reply-To: <000101c4dbc5$96844e70$0a00000a@MERCKX>

On Mon, 6 Dec 2004 20:58:33 +0200
"Niel Lambrechts" <antispam@telkomsa.net> wrote:

> > 
> > my first guess would be that the reiserfs module on your 
> > initrd needs to be recompiled using the PENTIUMM arch.....
> > 
> > --john
> 
> No.
> 
> I did:
> make menuconfig - change from i686 to pentiumm - save settings.
> make 
> make install
> mkinitrd -s 1024x768 -k "bzImage.2.6.8-24.5-default" -I "initrd" -m
> "reiserfs"
> lilo
> 
> If I "mount -o loop" the new initrd, modinfo shows the type of
> reiserfs.ko to be "PENTIUMM" as I would expect...
> 
> I have also tried compiling reiserfs support directly into the kernel
> and dropping reiserfs from the -m option, to no avail.
> 
> -Niel
> 

so much for the first guess. try modifying the initrd to pop open an interactive
shell that you can use before it actually fails. You can poke around and see
what's going on. Depending on how it's set up, you might be able to get away
with something this simple in the linuxrc:

	/bin/sh </dev/console >/dev/console 2>/dev/console

If you ramdisk has strace and some other use utilities, it might help you track
down the bad apple.

--john

  reply	other threads:[~2004-12-06 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20041206123705.5fbac5b4@homer.sarvega.com>
2004-12-06 18:58 ` Niel Lambrechts
2004-12-06 19:07   ` John Lash [this message]
2004-12-07 18:14 Niel Lambrechts
  -- strict thread matches above, loose matches on Subject: below --
2004-12-06 18:29 Niel Lambrechts

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=20041206130743.6c5f0fd3@homer.sarvega.com \
    --to=jkl@sarvega.com \
    --cc=antispam@telkomsa.net \
    --cc=bwindle@fint.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®