From: Ville Herva <vherva@mail.niksula.cs.hut.fi>
To: linux-kernel@vger.kernel.org
Subject: initrd oops [was Re: Linux 2.4.5-ac1]
Date: Mon, 28 May 2001 00:12:20 +0300 [thread overview]
Message-ID: <20010528001220.M11981@niksula.cs.hut.fi> (raw)
In-Reply-To: <20010526225825.A31713@lightning.swansea.linux.org.uk> <20010527192650.H11981@niksula.cs.hut.fi>
In-Reply-To: <20010527192650.H11981@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Sun, May 27, 2001 at 07:26:50PM +0300
On Sun, May 27, 2001 at 07:26:50PM +0300, you [Ville Herva] claimed:
> On Sat, May 26, 2001 at 10:58:25PM +0100, you [Alan Cox] claimed:
> >
> > o Free the initial ramdisk correctly
>
> Who made this fix, or who can I contact?
>
> I have a reproducible oops on 2.4.4ac17 (see
> http://marc.theaimsgroup.com/?l=linux-kernel&m=99079948404775&w=2 for
> details) that seems to be related:
Ok, some more info:
2.4.2-2 (redhat) BOOTS OK
2.4.4ac17 OOPS
2.4.4ac17+av OOPS
2.4.5 OOPS
2.4.5ca1+av OOPS
2.4.4 BOOTS OK
2.4.4ac9 BOOTS OK
2.4.4ac10 BOOTS OK
2.4.4ac11 BOOTS OK
2.4.4ac12 fails to mount root ("Checking root filesystem.
/dev/sdb is mounted.")
2.4.4ac14 fails to mount root
2.4.4ac15 OOPS
This is:
600Mhz Xeon
256MB
megaraid RAID and sym53c875 (from which I boot)
gcc-2.96-85 (tried .91 as well)
So I gather the ac12 and ac15 Linux tree / av merges are the culprit?
-- v --
v@iki.fi
next prev parent reply other threads:[~2001-05-27 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-26 21:58 Linux 2.4.5-ac1 Alan Cox
2001-05-27 16:26 ` [OOPS] " Ville Herva
2001-05-27 21:12 ` Ville Herva [this message]
2001-05-28 7:25 ` initrd oops; still happens with 2.4.5ac2 Ville Herva
2001-05-28 8:51 ` Ville Herva
2001-05-28 9:02 ` Masaru Kawashima
2001-05-28 10:05 ` initrd oops with 2.4.5ac2: FIXED by Kawashima (the other oops may remain) Ville Herva
2001-05-28 10:28 ` initrd oops with 2.4.5ac2: Tthe other oops remains (one fixed) Ville Herva
2001-05-28 10:48 ` initrd oops with 2.4.5ac2: megaraid OOPSes Ville Herva
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=20010528001220.M11981@niksula.cs.hut.fi \
--to=vherva@mail.niksula.cs.hut.fi \
--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®