From: FAVRE Gregoire <greg@ulima.unil.ch>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.4-ac10: Oops -> 2.4.4
Date: Fri, 18 May 2001 22:02:23 +0200 [thread overview]
Message-ID: <20010518220223.A23508@ulima.unil.ch> (raw)
In-Reply-To: <20010518200023.A22231@ulima.unil.ch> <E150pa7-0007XV-00@the-village.bc.nu>
In-Reply-To: <E150pa7-0007XV-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, May 18, 2001 at 08:06:35PM +0100
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
Thus spake Alan Cox (alan@lxorguk.ukuu.org.uk):
> Can you boot a kernel without fdomain.c compiled in next
Yes, but I am too stupid: there were a faillure in my
patch-2.4.4-ac10.bz2, which is 0 bits.... so I have bunzip -c
patch-2.4.4-ac10.bz2|patch -p1 -s with an empty file :-((
That mean I compiled a 2.4.4 kernel, and not a 2.4.4-ac10 one.
I know that becauseause I reemoved my fdomain SCSI controller and put an
Adaptec 2940 at the same place, and it booted very well...
So the problem is ME: I am too stupid!!!
Anyway, the bug is in 2.4.4, not in 2.4.4-ac10: I am really sorry for
having loosing your time. With 2.4.4-ac9 with my fdomain, everything is
also working great ;-)
If I can do anything, just let me know ;-)
Thanks you very much,
Greg
________________________________________________________________
http://ulima.unil.ch/greg ICQ:16624071 mailto:greg@ulima.unil.ch
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next parent reply other threads:[~2001-05-18 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010518200023.A22231@ulima.unil.ch>
[not found] ` <E150pa7-0007XV-00@the-village.bc.nu>
2001-05-18 20:02 ` FAVRE Gregoire [this message]
2001-05-18 20:39 ` Alan Cox
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=20010518220223.A23508@ulima.unil.ch \
--to=greg@ulima.unil.ch \
--cc=alan@lxorguk.ukuu.org.uk \
--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®