Re: SATA exceptions with 2.6.20-rc5
- From: Björn Steinbrink <B.Steinbrink@xxxxxx>
- Date: Sun, 21 Jan 2007 05:54:38 +0100
On 2007.01.20 22:34:27 -0500, Jeff Garzik wrote:
Robert Han*** wrote:
change in 2.6.20-rc is either causing or triggering this problem. It
would be useful if you could try git bisect between 2.6.19 and
2.6.20-rc5, keeping the latest sata_nv.c each time, and see if that
Yes, 'git bisect' would be the next step in figuring out this puzzle.
Anybody up for it?
I'll go for it, but could I get an explanation how that could lead to a
different result than my last bisection? I see the difference of keeping
sata_nv.c but my brain can't wrap around it right now (woke up in the
middle of the night and still not up to speed...).
Thanks,
Björn
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: SATA exceptions with 2.6.20-rc5
- From: Robert Han***
- Re: SATA exceptions with 2.6.20-rc5
- References:
- Re: SATA exceptions with 2.6.20-rc5
- From: Alistair John Strachan
- Re: SATA exceptions with 2.6.20-rc5
- From: Robert Han***
- Re: SATA exceptions with 2.6.20-rc5
- From: Chr
- Re: SATA exceptions with 2.6.20-rc5
- From: Robert Han***
- Re: SATA exceptions with 2.6.20-rc5
- From: Jeff Garzik
- Re: SATA exceptions with 2.6.20-rc5
- Prev by Date: Re: [PATCH 9/12] repost: cciss: add busy_configuring flag
- Next by Date: RE: Serial port blues
- Previous by thread: Re: SATA exceptions with 2.6.20-rc5
- Next by thread: Re: SATA exceptions with 2.6.20-rc5
- Index(es):