From: Florin Iucha <florin@iucha.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andreas Franck <afranck@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19pre1-ac1
Date: Thu, 28 Feb 2002 00:31:13 -0600 [thread overview]
Message-ID: <20020228003113.B4519@iucha.net> (raw)
In-Reply-To: <02022723312400.01097@dg1kfa> <E16gDhO-0006OL-00@the-village.bc.nu>
In-Reply-To: <E16gDhO-0006OL-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Feb 27, 2002 at 11:41:26PM +0000
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On Wed, Feb 27, 2002 at 11:41:26PM +0000, Alan Cox wrote:
> What compiler firstly, and what I/O subsystem. Are you using highmem,
> did you build from a clean tree ?
florin@bee:~$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 (Debian prerelease)
00:05.1 IDE interface: Intel Corp. 82371AB PIIX4 IDE (rev 01)
No highmem (256Mb)
Clean tree 2.4.17 -> 2.4.18 -> 2.4.19-pre1 -> 2.4.19-pre1-ac1
Problem gone in 2.4.19-pre1-ac2, patched from clean tree, built on
2.4.18-rc2-ac1. Weird...
It looks like something is hosed in the 2.4.19-pre1-ac1 patchset.
florin
--
"If it's not broken, let's fix it till it is."
41A9 2BDE 8E11 F1C5 87A6 03EE 34B3 E075 3B90 DFE4
[-- Attachment #2: Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2002-02-28 6:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 22:31 Linux 2.4.19pre1-ac1 Andreas Franck
2002-02-27 23:41 ` Alan Cox
2002-02-28 0:13 ` Andreas Franck
2002-02-28 0:34 ` Alan Cox
2002-02-28 0:27 ` Andreas Franck
2002-02-28 0:32 ` David S. Miller
2002-02-28 1:02 ` Alan Cox
2002-02-28 6:31 ` Florin Iucha [this message]
[not found] <fa.kjtklqv.gnqri3@ifi.uio.no>
[not found] ` <fa.g63p78v.1e7kv8e@ifi.uio.no>
2002-02-28 0:19 ` Jonathan Hudson
[not found] <fa.c7mcedv.1a3esq4@ifi.uio.no>
2002-02-27 22:54 ` Jonathan Hudson
2002-02-27 23:48 ` Alan Cox
[not found] ` <fa.g5iqv0v.11magge@ifi.uio.no>
2002-02-27 23:36 ` Jonathan Hudson
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 1:47 Alan Cox
2002-02-27 21:14 ` Florin Iucha
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=20020228003113.B4519@iucha.net \
--to=florin@iucha.net \
--cc=afranck@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.