Messages in this thread | | | Date | Wed, 24 Sep 2008 10:48:46 +0200 | From | Konstantin Kletschke <> | Subject | Re: SATA Cold Boot problems on >2.6.25 with NV |
| |
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
| |