linux-kernel - Re: 2.6.18-rc2 Intermittent failures to detect sata disks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <44C5B2B4.4090300@pobox.com>
Date:	Tue, 25 Jul 2006 01:57:08 -0400
From:	Jeff Garzik <jgarzik@...ox.com>
To:	Keith Owens <kaos@....com.au>
CC:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.18-rc2 Intermittent failures to detect sata disks

Keith Owens wrote:
> Keith Owens (on Fri, 21 Jul 2006 16:18:47 +1000) wrote:
>> I am seeing an intermittent failures to detect sata disks on
>> 2.6.18-rc2.  Dell SC1425, PIIX chipset, gcc 4.1.0 (opensuse 10.1).
>> Sometimes it will detect both disks, sometimes only one, sometimes none
>> at all.  AFAICT it only occurs after a soft reboot, and possibly only
>> after an emergency reboot.  Alas the problem is so intermittent that it
>> is hard to tell what conditions will trigger it.
> 
> I applied the debug patch below, turn on prink timing and set
> initdefault to 6 so the machine was in a continual soft reboot cycle.
> After multiple cycles I got this trace.  piix_sata_prereset() reads a
> zero config byte for almost 15 seconds then it changes to 0x11,
> followed by a hang.  Why is the config byte initially zero, and what
> makes it change?  The normal value for pcs is 0x33.

Can you try 2.6.18-rc2-git3?

	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/