From: Tejun Heo <tj@kernel.org>
To: linux-kernel@vger.kernel.org
Subject: Re: SATA Cold Boot problems on >2.6.25 with NV
Date: Sat, 30 Aug 2008 11:14:39 +0200 [thread overview]
Message-ID: <48B90F7F.8040308@kernel.org> (raw)
In-Reply-To: <20080829212146.GA4321@anita>
Konstantin Kletschke wrote:
> Am 2008-08-29 16:52 +0200 schrieb Tejun Heo:
>
>> http://article.gmane.org/gmane.linux.ide/34077
>
> I have this patch actually applied and had switched off the computer
> afterwards completely for more than one hour two times. Each time it
> booted then (this was the patch you suggested initially to Many Maxwell
> this month to this list).
>
> Everything seems to work fine, but my dmesg and /var/log/messages is
> flooded with this now:
>
> Aug 29 23:20:39 zappa ata1: EH complete
> Aug 29 23:20:41 zappa ata1: EH complete
> Aug 29 23:20:47 zappa ata1: EH complete
> Aug 29 23:20:49 zappa ata1: EH complete
> Aug 29 23:20:51 zappa ata1: EH complete
> Aug 29 23:20:53 zappa ata1: EH complete
> Aug 29 23:20:55 zappa ata1: EH complete
> Aug 29 23:20:56 zappa ata1: EH complete
> Aug 29 23:20:59 zappa ata1: EH complete
> Aug 29 23:21:01 zappa ata1: EH complete
Hmm... Can you post full dmesg output? We used to see things like above
when ATAPI CHECK SENSE handling somehow failed to tell EH that it was an
exception not worth whining about. Maybe EH action mask is not being
cleared properly?
> I am curious if it boots tomorrow after sleeping for one night :-P
I somehow feel pretty optimistic about that part. :-)
--
tejun
next prev parent reply other threads:[~2008-08-30 9:16 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 [this message]
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
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=48B90F7F.8040308@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@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 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.