public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Voluspa <voluspa@bigfoot.com>
Cc: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.6-pre3 Kernel panic: VFS: Unable to mount root fs on 03:02
Date: Thu, 07 Mar 2002 17:57:28 +0100	[thread overview]
Message-ID: <3C879BF8.7040606@evision-ventures.com> (raw)
In-Reply-To: <20020307114845.530abcfa.voluspa@bigfoot.com>	<Pine.GSO.4.21.0203070601100.26116-100000@weyl.math.psu.edu> <20020307172946.55044bb9.voluspa@bigfoot.com>

Voluspa wrote:
> PS. I've got a rather good grip of my Linux From Scratch system - with a BSD style init for even better control - and only load modules for one NIC and ALSA stuff here. Never have had file systems modulari(z)(s)ed DS.

OK I didn't actually get around to test pre3 in life. But at least
it's nice to hear that this is apparently not my fault ;-).

> 
> On Thu, 7 Mar 2002 06:09:04 -0500 (EST)
> Alexander Viro <viro@math.psu.edu> wrote:
> 
> 
>>It boots fine from ext2 on IDE here.  Do you have any oddities in
>>.config? (e.g. something silly enabled - CONFIG_PREEMPT, etc.)
>>
> 
> Silly :-) A P166 needs every boost possible. Yes, I have preempt enabled. And yes, you are right on the mark. Compiling without preempt the booting of 2.5.6-pre3 runs flawlessly. And after a few tests no file corruption visible. But 2.5.6-pre2 + preempt-UP-bug-patch worked like a charm. So there's something else involved, it seems.
> 
> During the compilation I happened to get a brief glimpse of a warning in ide.c Don't know C so can't evaluate its severity. Went something like this: 'In function choose_drive Warning: distinkt pointer lacks a cast'.
That's spurious and will vanish soon. I just peplaced IDE_MAX and 
IDE_MIN with the generic min() max(), which are showing nicely where
int entities of different size are compared.

> 
> 
>>.config might be really useful.  Or not - it may boil down to checking
>>
> 
> I judge it a moot point to dump all those lines now. If I'm in err, nudge me.
> 
> Thanks for the discussion.
> MJ
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 
> 



-- 
- phone: +49 214 8656 283
- job:   eVision-Ventures AG, LEV .de (MY OPINIONS ARE MY OWN!)
- langs: de_DE.ISO8859-1, en_US, pl_PL.ISO8859-2, last ressort: ru_RU.KOI8-R


  reply	other threads:[~2002-03-07 16:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07  6:21 2.5.6-pre3 Kernel panic: VFS: Unable to mount root fs on 03:02 Voluspa
2002-03-07  6:29 ` Alexander Viro
2002-03-07  7:56   ` Voluspa
2002-03-07  8:42     ` Alexander Viro
2002-03-07  9:21       ` Voluspa
2002-03-07 10:48       ` Voluspa
2002-03-07 11:09         ` Alexander Viro
2002-03-07 16:29           ` Voluspa
2002-03-07 16:57             ` Martin Dalecki [this message]
2002-03-07 12:37 ` Martin Dalecki

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=3C879BF8.7040606@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    --cc=voluspa@bigfoot.com \
    /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