From: Jeff Garzik <jeff@garzik.org>
To: Manny Maxwell <mannymax@mannymax.net>,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: Re: [Bug #11343] SATA Cold Boot Problems with 2.6.27-rc[23] on nVidia 680i
Date: Sat, 23 Aug 2008 18:34:47 -0400 [thread overview]
Message-ID: <48B09087.3090202@garzik.org> (raw)
In-Reply-To: <VSpL6AnBTS.A.m3H.3aGsIB@albercik>
Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.26. Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=11343
> Subject : SATA Cold Boot Problems with 2.6.27-rc[23] on nVidia 680i
> Submitter : Manny Maxwell <mannymax@mannymax.net>
> Date : 2008-08-14 4:16 (10 days old)
> References : http://marc.info/?l=linux-kernel&m=121868782917600&w=4
hmmmm. Looking at changes between the two csets listed in the email
(623fa57..8f616cd), all of them are driver-specific and unrelated to
Manny's hardware except for
commit 2486fa561a3192bbbec39c7feef87a1e07bd6342
Author: Tejun Heo <tj@kernel.org>
Date: Thu Jul 31 07:52:40 2008 +0900
libata: update atapi disable handling
So you could try to revert that and see what happens. But given that
small range of changes, it really seems like something else, maybe in
the PCI subsystem (random guess).
Looking at the entire kernel, nothing jumps out, either. Its mostly fs
updates (ext4, xfs), a networking update, an ARM update, and a libata
update.
Also, some reset-related fixes just went in, so re-testing the latest
-git would be helpful as well.
Jeff
parent reply other threads:[~2008-08-23 22:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <VSpL6AnBTS.A.m3H.3aGsIB@albercik>]
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=48B09087.3090202@garzik.org \
--to=jeff@garzik.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mannymax@mannymax.net \
--cc=rjw@sisk.pl \
/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).