mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Zbigniew Baniewski <zb@ispid.com.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "modularized" 2.4.34.4  ->  ide-core "unresolved symbols"
Date: Wed, 9 May 2007 00:39:22 +0200	[thread overview]
Message-ID: <20070508223922.GB31591@1wt.eu> (raw)
In-Reply-To: <20070508221425.GA18244@localhost.localdomain>

On Wed, May 09, 2007 at 12:14:25AM +0200, Zbigniew Baniewski wrote:
> On Tue, May 08, 2007 at 11:16:46PM +0200, Willy Tarreau wrote:
> 
> > depmod:         init_cmd640_vlb
> 
> There wasn't such message.

No, because it seems that your debian scripts hide it (or log it somewhere
else). But if you do "make modules_install" from the kernel tree (as I did),
you get it.

> I made another kernel (config below) - unfortunately, this time it gives up
> completely, saying:
> 
> -------------------------------
> ...ordinary boot messages, ending with "hda:... sectors... w/Cache..."
> /dev/ide/host0/bus0/target0/lun0:<1>Unable to handle kernel paging request at virtual address ffffff00
> printing eip:
> 
> ...several verses of sanscrit-like language...

This "sanscrit-like" language is an oops (in fact a kernel panic, but the
dump format is called an oops). It is what developers use to find bugs.

I see that you're using devfs. It is unfortunate for you that you're using
all the parts which are not reputed for their reliability :-/ I'm pretty
sure that initialization order matters here but you cannot interact much
with it, except by forcing some drivers to "=y".

Are you aware of any kernel version on which this config worked ? I'd
like to help you get the minimal working config, ie: the one with the
lower number of hard-linked drivers.

> <0>Kernel panic: Attempted to kill the idle task!
> In idle task - not syncing.
> --------------------------------
> 
> Moved the disk to quite different machine - with the same result. So, I'm
> afraid, it's not hardware-related problem.

Do not worry about the hardware here. The problem lies in the
initialization path of some sensible drivers. Did you enable DEVFS for a
particular reason, or just because you enabled almost everything ? If the
later, then you should retry with it disabled. It's absolutely not certain
that it will work, but it may.

If you're pretty certain that you need DEVFS, then for a test, please
set a max of IDE options to YES instead of MODULE. At least all the ones
you need to boot on this system.

As I said, it's a tricky area, and it's for this reason that distros
enable IDE to YES as well as some other entries I don't have in mind.

Regards,
Willy


  reply	other threads:[~2007-05-08 22:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05 19:49 Zbigniew Baniewski
2007-05-06  4:36 ` Willy Tarreau
2007-05-08 20:23   ` Zbigniew Baniewski
2007-05-08 21:16     ` Willy Tarreau
2007-05-08 22:14       ` Zbigniew Baniewski
2007-05-08 22:39         ` Willy Tarreau [this message]
2007-05-08 22:53           ` Zbigniew Baniewski
2007-05-09 22:05           ` Zbigniew Baniewski
2007-05-10  9:21             ` Willy Tarreau
2007-05-12 11:08             ` Willy Tarreau
     [not found] <fa.rg7bSh1mNv1yib9QUzNuRvWTPe8@ifi.uio.no>
2007-05-06  2:41 ` Robert Hancock

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=20070508223922.GB31591@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zb@ispid.com.pl \
    /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®