From: Konstantin Kletschke <lists@ku-gbr.de>
To: linux-kernel@vger.kernel.org
Subject: Re: SATA Cold Boot problems on >2.6.25 with NV
Date: Wed, 24 Sep 2008 10:48:46 +0200 [thread overview]
Message-ID: <20080924084846.GA2094@anita> (raw)
In-Reply-To: <48D89C85.2080104@panasas.com>
Am 2008-09-23 10:36 +0300 schrieb Benny Halevy:
> are printed for a disconnected ATA port that's a neighbor
> of one that's occupied.
Hey, I did not realize this yet!
My only SATA device seems to be connected to Port2:
Sep 24 07:12:47 zappa ata2: SATA max UDMA/133 cmd 0xe80 ctl 0xe00 bmdma 0xd808 irq 21
Sep 24 07:12:47 zappa ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Sep 24 07:12:47 zappa ata2.00: ATA-7: SAMSUNG HD753LJ, 1AA01106, max UDMA7
Sep 24 07:12:47 zappa ata2.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Sep 24 07:12:47 zappa ata2.00: configured for UDMA/133
Whereas my message log is still flooded by ata1 stuff:
Sep 21 11:34:57 zappa ata1: EH complete
Sep 21 11:34:57 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Sep 21 11:34:58 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen t4
Sep 21 11:34:58 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen t3
Sep 21 11:34:58 zappa ata1: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen t2
Tijo, is there any stuff I should try out? I mean, if I got this right,
the boot problems itself were fixed by removing nv_hardreset, but is
there a way around getting the log flooded by "EH complete" now?
Kind regards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
next prev parent reply other threads:[~2008-09-24 8:49 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 [this message]
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=20080924084846.GA2094@anita \
--to=lists@ku-gbr.de \
--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.