All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Neil Brown <neilb@suse.de>, Jurriaan <thunder7@xs4all.nl>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: sata badness in 2.6.20-rc1? [Was: Re: md patches in -mm]
Date: Fri, 15 Dec 2006 16:49:46 -0500	[thread overview]
Message-ID: <4583187A.4020602@garzik.org> (raw)
In-Reply-To: <200612152215.23629.rjw@sisk.pl>

Rafael J. Wysocki wrote:
> The other box is mine and it works just fine with 2.6.20-rc1.
> 
>> I think something bad happened in sata land just recently.
> 
> Yup.  Please see, for example:
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=116621656432500&w=2
> 
> It looks like the breakage is in sata, in the patches that went in after
> 2.6.19-rc6-mm2 (that one worked for me like charm).


So.... 2.6.20-rc1 works for you?

	Jeff

  reply	other threads:[~2006-12-15 21:49 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20061204203410.6152efec.akpm@osdl.org>
     [not found] ` <17780.63770.228659.234534@cse.unsw.edu.au>
     [not found]   ` <20061205061623.GA13749@amd64.of.nowhere>
     [not found]     ` <20061205062142.GA14784@amd64.of.nowhere>
     [not found]       ` <20061204224323.2e5d0494.akpm@osdl.org>
     [not found]         ` <20061205105928.GA6482@amd64.of.nowhere>
     [not found]           ` <17782.28505.303064.964551@cse.unsw.edu.au>
2006-12-15 19:21             ` md patches in -mm thunder7
2006-12-15 20:06               ` Andrew Morton
2006-12-15 20:50               ` sata badness in 2.6.20-rc1? [Was: Re: md patches in -mm] Neil Brown
2006-12-15 21:05                 ` Andrew Morton
2006-12-15 21:18                   ` Rafael J. Wysocki
2006-12-15 21:39                   ` Andrew Morton
2006-12-15 21:46                     ` Rafael J. Wysocki
2006-12-15 22:06                     ` Alan
2006-12-15 22:04                       ` Rafael J. Wysocki
2006-12-15 22:19                       ` Jeff Garzik
2006-12-15 22:27                         ` Rafael J. Wysocki
2006-12-15 22:22                     ` Rafael J. Wysocki
2006-12-15 22:24                       ` Jeff Garzik
2006-12-15 23:38                         ` Rafael J. Wysocki
2006-12-16  9:56                           ` Rafael J. Wysocki
2006-12-16 11:16                             ` Rafael J. Wysocki
2006-12-17 11:00                               ` Rafael J. Wysocki
2006-12-17 11:05                                 ` Andrew Morton
2006-12-17 16:00                                   ` thunder7
2006-12-19 23:26                                     ` Luben Tuikov
2006-12-19 23:26                                       ` Luben Tuikov
2006-12-20  0:08                                       ` Andrew Morton
2006-12-17 14:08                                 ` Jiri Slaby
2006-12-15 21:48                   ` Jeff Garzik
2006-12-16  6:03                     ` thunder7
2006-12-15 21:15                 ` Rafael J. Wysocki
2006-12-15 21:49                   ` Jeff Garzik [this message]
2006-12-15 21:56                     ` Rafael J. Wysocki

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=4583187A.4020602@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=rjw@sisk.pl \
    --cc=thunder7@xs4all.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.