From: Andreas Franck <afranck@gmx.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: florin@iucha.net (Florin Iucha), linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19pre1-ac1
Date: Thu, 28 Feb 2002 01:13:23 +0100 [thread overview]
Message-ID: <02022800441601.01097@dg1kfa> (raw)
In-Reply-To: <E16gDhO-0006OL-00@the-village.bc.nu>
In-Reply-To: <E16gDhO-0006OL-00@the-village.bc.nu>
Hi Alan and folks,
> What compiler firstly, and what I/O subsystem. Are you using highmem,
> did you build from a clean tree ?
gcc 2.95.2, I/O subsystem is PIIX4 IDE here. No problems with "pure" reading
and writing however, so it really seems to be connected to something special
done by patch. Build was fresh from a clean tree.
> I also think your report is unrelated to the reiserfs one. 2.4.18 proper
> and -ac have a small reiserfs fix which is a viable candidate for
> reiserfs funnies while what you report is somewhat different
Perhaps - but strange both are only triggered by "patch"? Or maybe the
reiserfs errors are later consequences of the same problem.
> Maybe a candidate
> shared memory filesystem fixes (also used for sys5 shm
> and anonymous shared maps)
> [copy mm/shmem.c from the working -ac to the current -ac
> and retest]
Will try this now, sounds possible - but does patch really use shared memory?
I will try to narrow it down a bit. There also were some changes to
mm/memory.c between 2.4.18-rc2-ac2 and 2.4.18-ac1. Also a possibility?
> Small pnpbios update (only relevant if building with PNPBIOS)
> [Build without PNPbios and retest]
Have bios enabled in all kernels, will try without. But there were no PNPBIOS
changes between the working 2.4.18-rc2-ac2 and the failing 2.4.18-ac1, so
I would rule this out.
> Wildly improbable
> Correct NULL check in the sd scsi code
> open fix for ps2 driver
Not using sd driver or ps2 at all.
> Hw specific (check your hardware and config and you can rule these out I
> guess) JFS specific fixes
> A sparc64 specific compile fix
> An off by one fix for loop that only affects using a specific
> option with maxloop=256
> Patches that only impact users of nbd
> An AMD ELan specific driver for watchdog - no affect on others
> Locking fixes for the softdog driver
> A serverworks specific ide=nodma fix
> LS220 experimental code (which shouldnt be enabled or matter)
> Tiny tweaks to the margi DVD card driver
> Ifdef of two lines specific to promise sx6000 raid
> 3c359 token ring driver (doesnt touch generic code)
> olypmic token ring specific locking change
> netrom specific fixes
Use nothing at all of them, just compiled most things as modules, which are
not loaded.
Greetings,
Andreas
next prev parent reply other threads:[~2002-02-28 0:14 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 [this message]
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
[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=02022800441601.01097@dg1kfa \
--to=afranck@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=florin@iucha.net \
--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.