linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Ed Tomlinson <edt@aei.ca>
Cc: "Barry K. Nathan" <barryn@pobox.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com,
	linux-scsi@vger.kernel.org
Subject: Re: 2.6.16-rc1-mm2
Date: Fri, 27 Jan 2006 09:53:13 -0500	[thread overview]
Message-ID: <43DA33D9.5080701@pobox.com> (raw)
In-Reply-To: <200601230739.45525.edt@aei.ca>

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




  reply	other threads:[~2006-01-27 14:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060120031555.7b6d65b7.akpm@osdl.org>
     [not found] ` <43D170CB.8080802@reub.net>
     [not found]   ` <200601211014.44041.edt@aei.ca>
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             ` Jeff Garzik [this message]
     [not found]               ` <200601280846.23279.edt@aei.ca>
2006-02-04 23:43                 ` 2.6.16-rc1-mm2 (mm5 too) panics Ed Tomlinson
2006-02-24  1:57                   ` 2.6.16-rc4-mm1 & " Ed Tomlinson

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=43DA33D9.5080701@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=barryn@pobox.com \
    --cc=edt@aei.ca \
    --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;
as well as URLs for NNTP newsgroup(s).