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

On Wed, May 09, 2007 at 12:39:22AM +0200, Willy Tarreau wrote:

> 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.

Of course, I'm aware. ;)

> I see that you're using devfs.

No, I'm not. No idea, why it has been enabled... :-O  just added grsecurity
patch to the previous .config, switched ata-module to be compiled directly
into kernel - and made new compilation.

> 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.

OK, I'll repeat the compilation making sure, that devfs is disabled.
-- 
				pozdrawiam / regards

						Zbigniew Baniewski

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05 19:49 "modularized" 2.4.34.4 -> ide-core "unresolved symbols" 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
2007-05-08 22:53           ` Zbigniew Baniewski [this message]
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=20070508225333.GA19063@localhost.localdomain \
    --to=zb@ispid.com.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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