linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Dominic Driver <dominic.driver@paragon.co.nz>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI Driver Regression and Missing Code Block?
Date: Tue, 21 Apr 2009 20:09:28 -0600	[thread overview]
Message-ID: <20090422020928.GD1926@parisc-linux.org> (raw)
In-Reply-To: <5313655.7301240361406269.JavaMail.root@mail.paragon.co.nz>

On Wed, Apr 22, 2009 at 12:50:06PM +1200, Dominic Driver wrote:
> Hi Guys,
> 
> I had an interesting experience with my SATA DVD-RW Drives following a Kernel Upgrade from:
> 
> 2.6.27.19-170.2.35.fc10.i686
> to 
> 2.6.28.6 (Vanilla)

One of the problems with trying to diagnose the problem is that you're
going from a distro kernel to a vanilla kernel.  So it's not necessarily
something we've taken out -- it could be something they've put in and
we don't know about.

So it'd be really nice to see if 2.6.27 vanilla behaves like 2.6.28
vanilla or like 2.6.27-fc.  You might also want to try 2.6.29 as Fedora
do backport patches from later kernels.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2009-04-22  2:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <30274704.7281240360796458.JavaMail.root@mail.paragon.co.nz>
2009-04-22  0:50 ` SCSI Driver Regression and Missing Code Block? Dominic Driver
2009-04-22  2:09   ` Matthew Wilcox [this message]
     [not found] <9573387.7901240380756993.JavaMail.root@mail.paragon.co.nz>
     [not found] ` <7297889.7921240382112001.JavaMail.root@mail.paragon.co.nz>
2009-04-22 11:52   ` Matthew Wilcox

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=20090422020928.GD1926@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=dominic.driver@paragon.co.nz \
    --cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).