public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Dave Jones <davej@suse.de>,
	Sebastian Dr?ge <sebastian.droege@gmx.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Current Reiserfs Update / 2.5.2-dj7 Oops
Date: Thu, 31 Jan 2002 09:09:32 +0300	[thread overview]
Message-ID: <20020131090932.B4574@namesys.com> (raw)
In-Reply-To: <20020130151420.40e81aef.sebastian.droege@gmx.de> <20020130173715.B2179@namesys.com> <20020130163951.13daca94.sebastian.droege@gmx.de> <20020130190905.A820@namesys.com> <20020130174011.L24012@suse.de> <20020130201054.6e150f78.sebastian.droege@gmx.de> <20020130201757.Q24012@suse.de>
In-Reply-To: <20020130201757.Q24012@suse.de>

Hello!

On Wed, Jan 30, 2002 at 08:17:57PM +0100, Dave Jones wrote:
> On Wed, Jan 30, 2002 at 08:10:54PM +0100, Sebastian Dr?ge wrote:
>  > I have 3 partitions. Two reiserfs partitions, one mounted on /, one on /home
>  Ok, my test box for reiserfs uses ext3 root, and reiser on a scratch disk.
>  It could be Oleg's earlier guess that it may be reiser-on-root related.
No. I can reproduce with ext2 root & reiserfs mounted separately.
depmod -a -b /mnt causes a crash for me 100% of time.
(of course you need correct /lib/modules/... for that)

>  > It happens with the IDE layer version as in the dj tree and with
>  > acb-io-2.5.3-p2.01212002 update (why haven't you included this in your tree,
>  > Dave?)
>  I never saw Andre pushing it on Linux-kernel (which is unusual for Andre 8)
I dug the original message,
it's subject is "DO NOT USE IT (Re: linux-2.5.3-pre1 and IDE Driver Trouble) FATAL"
msgid is <Pine.LNX.4.10.10201161259270.29434-100000@master.linux-ide.org>
It warns about 2.5.3-pre1 and 2.5.2 is unstable with IDE because there are
conflicts between BIO & ACB. He promised to come up with the fix later.
After that there were no messages from him with patches.
At least not in the lkml.

Bye,
    Oleg

  reply	other threads:[~2002-01-31  6:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 14:14 Current Reiserfs Update / 2.5.2-dj7 Oops Sebastian Dröge
2002-01-30 14:37 ` Oleg Drokin
2002-01-30 15:39   ` Sebastian Dröge
2002-01-30 16:09     ` Oleg Drokin
2002-01-30 16:40       ` Dave Jones
2002-01-30 16:44         ` Oleg Drokin
2002-01-30 16:55           ` Dave Jones
2002-01-30 17:07             ` Oleg Drokin
2002-01-30 19:10         ` Sebastian Dröge
2002-01-30 19:17           ` Dave Jones
2002-01-31  6:09             ` Oleg Drokin [this message]
2002-01-31  9:24             ` Oleg Drokin
2002-01-31 12:49               ` Dave Jones
2002-01-31 12:53                 ` Oleg Drokin
2002-01-31 13:11                   ` Dave Jones
2002-01-31 16:44                     ` Oleg Drokin
2002-01-31 17:23                       ` Sebastian Dröge
2002-01-31 17:45                       ` Chris Mason
  -- strict thread matches above, loose matches on Subject: below --
2002-01-31 10:10 Martin Bahlinger
2002-01-31 13:03 ` Oleg Drokin
2002-01-31 17:20   ` Martin Bahlinger
2002-01-31 17:44 Martin Bahlinger
2002-01-31 20:44 ` Martin Bahlinger
2002-02-01  5:55   ` Oleg Drokin
2002-02-01 22:17     ` Martin Bahlinger
2002-02-02  8:30       ` Oleg Drokin

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=20020131090932.B4574@namesys.com \
    --to=green@namesys.com \
    --cc=davej@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sebastian.droege@gmx.de \
    /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