From: Ed Tomlinson <edt@aei.ca>
To: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com,
linux-scsi@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: 2.6.16-rc1-mm2 (mm5 too) panics
Date: Sat, 4 Feb 2006 18:43:27 -0500 [thread overview]
Message-ID: <200602041843.28214.edt@aei.ca> (raw)
In-Reply-To: <200601280846.23279.edt@aei.ca>
Hi,
I need some help figuring this one out. I cannot use git bisect and applying the 2.6.15-1 reiserfs4
patch does not work with newer 2.6.16 levels - looks like the mutex conversion hits it hard. Looking
in mm there are about 50 reiser4 patches...
To reproduce this problem I need reiser4 though the issue maybe in libata or scsi. Does anyone
have an idea how I can proceed to find what makes newer kernels get io errors which trigger a reiser4
panic? The panic is a zam-597 (fs/reiser4/txnmgr.c) with an rc=-5
Anyone have a git tree tracking linus with reiser4 patches applied staring before 2.6.15 - if so git
bisect could be used to find the change causing the problem.
One datapoint. In 2.6.15 + reiser4 2.6.15-1 works fine - the resiser4 filesystem is heavily used with
no errors. Smart report no problems with the drive being used. The libata driver used is sata_nv.
Please reply to my email - I am only subscribed to lkml.
Help!
Ed Tomlinson
ret = reiser4_write_logs(nr_submitted);
if (ret < 0)
reiser4_panic("zam-597", "write log failed (%ld)\n", ret);
On Saturday 28 January 2006 08:46, Ed Tomlinson wrote:
> On Friday 27 January 2006 09:53, you wrote:
> > Ed Tomlinson wrote:
> > > Summarizing all this. There are two problems here.
> > >
> > > 1. reserifs4 panics when it gets io errors - I remember this was an issue that
> > > needed to be fixed in the R4 code before it moves to mainline...
> > >
> > > 2. Why does a drive which is fine with 2.6.15-rc5-mm3, return a -5 with 2.6.16-mm3
> > > and above? Smart reports no problems with the drive hardware. What has changed
> > > in the libata/scsi stacks?
> >
> > That's a long answer. Could you assist in narrowing down the versions
> > which are affected?
> >
> > It would also be useful if you could try vanilla kernels, and help us
> > discover whether problems surfaces in 2.6.15, 2.6.15-git[1234],
> > 2.6.16-rc1, etc.
>
> Jeff,
>
> I'll see what I can do with git bisect. Given that reserifs4 is in the picture this may be
> fun... I expect it will be a slow process (kernels take 40min to build here).
>
> Thanks
> Ed Tomlinson
>
>
next prev parent reply other threads:[~2006-02-04 23:43 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 11:15 2.6.16-rc1-mm2 Andrew Morton
2006-01-20 11:33 ` 2.6.16-rc1-mm2 Pekka Enberg
2006-01-20 11:40 ` 2.6.16-rc1-mm2 Andrew Morton
2006-01-20 11:56 ` 2.6.16-rc1-mm2 Pekka J Enberg
2006-01-20 15:19 ` 2.6.16-rc1-mm2 Valdis.Kletnieks
2006-01-20 13:58 ` [PATCH] zone_reclaim cpus_empty needs a real variable Andy Whitcroft
2006-01-20 16:28 ` Christoph Lameter
2006-01-20 21:34 ` Andrew Morton
2006-01-20 14:05 ` 2.6.16-rc1-mm2 Dave Jones
2006-01-20 16:23 ` Iptables error [Was: 2.6.16-rc1-mm2] Jiri Slaby
2006-01-20 16:36 ` Harald Welte
2006-01-20 16:41 ` Jiri Slaby
2006-01-20 16:43 ` Benoit Boissinot
2006-01-20 16:49 ` Linus Torvalds
2006-01-20 16:58 ` Benoit Boissinot
2006-01-20 17:38 ` Benoit Boissinot
2006-01-20 16:59 ` Jiri Slaby
2006-01-20 17:02 ` Jiri Slaby
2006-01-20 17:11 ` Carlos Silva
2006-01-20 19:32 ` Harald Welte
2006-01-20 19:46 ` Iptables error David S. Miller
2006-01-21 11:05 ` Harald Welte
2006-01-20 20:02 ` David S. Miller
2006-01-23 2:03 ` Iptables error [Was: 2.6.16-rc1-mm2] Herbert Xu
2006-01-23 2:23 ` Keith Owens
2006-01-23 20:53 ` Eric W. Biederman
2006-01-20 18:13 ` Valdis.Kletnieks
2006-01-20 19:52 ` Iptables error David S. Miller
2006-01-20 21:26 ` 2.6.16-rc1-mm2: arch/arm26/kernel/fiq.c still doesn't compile Adrian Bunk
2006-01-20 21:57 ` Alexey Dobriyan
2006-01-20 23:22 ` 2.6.16-rc1-mm2 Reuben Farrelly
2006-01-21 15:14 ` 2.6.16-rc1-mm2 Ed Tomlinson
2006-01-21 16:39 ` 2.6.16-rc1-mm2 Ed Tomlinson
2006-01-21 18:45 ` 2.6.16-rc1-mm2 Barry K. Nathan
2006-01-21 21:36 ` 2.6.16-rc1-mm2 Ed Tomlinson
2006-01-21 23:57 ` 2.6.16-rc1-mm2 Barry K. Nathan
2006-01-23 12:39 ` 2.6.16-rc1-mm2 Ed Tomlinson
2006-01-27 14:53 ` 2.6.16-rc1-mm2 Jeff Garzik
[not found] ` <200601280846.23279.edt@aei.ca>
2006-02-04 23:43 ` Ed Tomlinson [this message]
2006-02-24 1:57 ` 2.6.16-rc4-mm1 & 2.6.16-rc1-mm2 (mm5 too) panics Ed Tomlinson
2006-01-24 3:51 ` 2.6.16-rc1-mm2 Neil Brown
2006-01-23 18:41 ` 2.6.16-rc1-mm2 Serge E. Hallyn
2006-01-23 18:47 ` 2.6.16-rc1-mm2 Christoph Lameter
2006-01-23 19:32 ` 2.6.16-rc1-mm2 Serge E. Hallyn
2006-01-23 19:39 ` 2.6.16-rc1-mm2 Christoph Lameter
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=200602041843.28214.edt@aei.ca \
--to=edt@aei.ca \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=reiserfs-dev@namesys.com \
/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