From: Martin Bahlinger <ry42@rz.uni-karlsruhe.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Current Reiserfs Update / 2.5.2-dj7 Oops
Date: 31 Jan 2002 18:44:09 +0100 [thread overview]
Message-ID: <1012499057.704.0.camel@hek411> (raw)
Hi!
Sebastian Dröge wrote:
> Oleg Drokin <green@namesys.com> wrote:
> > Ok, I think we got it. And yes it it was reiserfs fault.
> > What I really cannot understand is how it was working before???
> > Ok, so anybody who sees the oopses should try 2 patches attached.
> > prealloc_init_list_head.diff is just forgotten initialisation
> > and pick_correct_key_version.diff is the real fix.
> > I wonder is anybody will be able to reproduce a bug with these 2
> > fixes
> > (I hope not).
> everything seems to work perfect :)
> my system has booted without any problems
After applying those patches to 2.5.3 I still got an Oops after a
PAP-14030 message. I will try to catch the Oops (have never done this
before, may take some time) and feed it to ksymoops.
bye
Martin
--
Martin Bahlinger <bahlinger@rz.uni-karlsruhe.de> (PGP-ID: 0x98C32AC5)
next reply other threads:[~2002-01-31 17:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 17:44 Martin Bahlinger [this message]
2002-01-31 20:44 ` Current Reiserfs Update / 2.5.2-dj7 Oops Martin Bahlinger
2002-02-01 5:55 ` Oleg Drokin
2002-02-01 22:17 ` Martin Bahlinger
2002-02-02 8:30 ` Oleg Drokin
-- 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-30 14:14 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
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
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=1012499057.704.0.camel@hek411 \
--to=ry42@rz.uni-karlsruhe.de \
--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