From: Benny Halevy <bhalevy@panasas.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, lists@ku-gbr.de
Subject: Re: SATA Cold Boot problems on >2.6.25 with NV
Date: Sun, 05 Oct 2008 13:18:26 +0200 [thread overview]
Message-ID: <48E8A282.5060201@panasas.com> (raw)
In-Reply-To: <48E899F9.9040206@kernel.org>
On Oct. 05, 2008, 12:42 +0200, Tejun Heo <tj@kernel.org> wrote:
> Benny Halevy wrote:
>> On Oct. 05, 2008, 12:18 +0200, Tejun Heo <tj@kernel.org> wrote:
>>> Benny Halevy wrote:
>>>> On Sep. 24, 2008, 12:36 +0300, Tejun Heo <tj@kernel.org> wrote:
>>>>> Please apply the attached patch and post the resulting log. Please
>>>>> don't forget to turn on KALLSYMS.
>>>>>
>>>>> Thanks.
>>>>>
>>>> With commit 4c1eb90a0908c0c60db2169dce08fb672e7582f1 (v2.6.27-rc8),
>>>> I see no spurious EH complete events as I saw with 2.6.27-rc <= 7.
>>> You're on CK804, right?
>>>
>> No, MCP55 actually:
>>
>> $ lspci | grep IDE
>> 00:04.0 IDE interface: nVidia Corporation MCP55 IDE (rev a1)
>> 00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3)
>> 00:05.1 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3)
>
> Right, the commit fixes generic and CK804 while break nf2/3. Can you
> also try the following patch?
>
> http://article.gmane.org/gmane.linux.ide/34942/raw
>
Log looks clean with this patch as well.
Benny
next prev parent reply other threads:[~2008-10-05 11:18 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.CVrJhjm3R8sjl5Z+EEIzYm7QtW0@ifi.uio.no>
2008-08-29 14:44 ` SATA Cold Boot problems on >2.6.25 with NV Robert Hancock
2008-08-29 14:52 ` Tejun Heo
2008-08-29 21:21 ` Konstantin Kletschke
2008-08-30 9:14 ` Tejun Heo
2008-08-30 20:51 ` Konstantin Kletschke
2008-09-01 11:18 ` Tejun Heo
2008-09-01 17:46 ` Konstantin Kletschke
2008-09-02 4:35 ` Tejun Heo
2008-09-02 5:43 ` Konstantin Kletschke
2008-09-02 5:45 ` Tejun Heo
2008-09-02 6:36 ` Konstantin Kletschke
2008-09-23 7:36 ` Benny Halevy
2008-09-24 8:48 ` Konstantin Kletschke
2008-09-24 9:36 ` Tejun Heo
2008-09-24 10:59 ` Konstantin Kletschke
2008-09-25 8:18 ` Konstantin Kletschke
2008-09-27 21:22 ` Tejun Heo
2008-09-30 8:12 ` Konstantin Kletschke
2008-09-30 14:09 ` Tejun Heo
2008-09-30 15:16 ` Konstantin Kletschke
2008-09-30 16:47 ` Tejun Heo
2008-10-01 7:38 ` Konstantin Kletschke
2008-10-01 7:53 ` Tejun Heo
2008-10-01 19:30 ` Konstantin Kletschke
2008-10-05 10:02 ` Benny Halevy
2008-10-05 10:18 ` Tejun Heo
2008-10-05 10:34 ` Benny Halevy
2008-10-05 10:42 ` Tejun Heo
2008-10-05 11:18 ` Benny Halevy [this message]
2008-10-06 21:19 ` Konstantin Kletschke
2008-10-06 21:23 ` Konstantin Kletschke
2008-10-07 1:02 ` Tejun Heo
2008-10-07 6:04 ` Konstantin Kletschke
2008-10-07 8:10 ` Benny Halevy
2008-10-08 8:08 ` Konstantin Kletschke
2008-10-13 8:36 ` Tejun Heo
2008-10-13 8:38 ` Tejun Heo
2008-10-13 14:29 ` Konstantin Kletschke
2008-10-15 6:15 ` Tejun Heo
2008-10-17 8:08 ` Konstantin Kletschke
2008-10-21 6:08 ` Tejun Heo
2008-10-27 9:22 ` Konstantin Kletschke
2008-11-03 3:04 ` Tejun Heo
2008-11-03 8:32 ` Konstantin Kletschke
2008-12-14 0:49 ` Erich Mounce
2008-12-14 3:51 ` Tejun Heo
2008-10-13 14:25 ` Konstantin Kletschke
2008-09-25 8:15 ` Konstantin Kletschke
2008-08-29 7:47 Konstantin Kletschke
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=48E8A282.5060201@panasas.com \
--to=bhalevy@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@ku-gbr.de \
--cc=tj@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).