linux-kernel - Re: ICH8 CF timeout (regression)...

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]

Date:	Thu, 02 Aug 2007 18:42:41 -0400
From:	Mark Lord <lkml@....ca>
To:	Daniel J Blueman <daniel.blueman@...il.com>
Cc:	Tejun Heo <htejun@...il.com>, jgarzik@...ox.com,
	linux-ide@...r.kernel.org,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: ICH8 CF timeout (regression)...

Daniel J Blueman wrote:
> On 02/08/07, Tejun Heo <htejun@...il.com> wrote:
>> Daniel J Blueman wrote:
>>> I'll grab kernel logs from the legacy ATA boot; what else can help
>>> debug this issue? No problem testing patches too.
>> Yeap, please post the old log.
> 
> Not much actually - perhaps I need to enable some debugging:
> 
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> hdc: SanDisk SDCFX-4096, CFA DISK drive
> ide1 at 0x170-0x177,0x376 on irq 15
> hdc: max request size: 128KiB
> hdc: 8027712 sectors (4110 MB) w/1KiB Cache, CHS=7964/16/63
>  hdc: hdc1 hdc2 hdc3
> 
>>> --- [2]
>>> ata2.00: limiting speed to UDMA/33:PIO4
>>> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
>>> ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 in
>>>          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
>>> ata2: soft resetting port
>>> ata2.00: configured for UDMA/33
>>> ata2: EH complete
>> What happens after this?
> 
> More EH occurs - I've left it for ~5 mins, but let me know if longer
> would give more information, eg if it converges on a lower speed.
> 
> Would it be useful to compare some of the port setup registers in the
> working and non-working cases? Or any other debug I can grab?

I'm betting that this is the exact same problem we recently debugged
for someone else here:  there's a Marvell PATA->SATA bridge chip between
that CF card and the SATA controller, and it only works with PIO modes.

Tejun.. perhaps (for debugging) a simple patch to disallow DMA completely,
just to see if PIO works?

Cheers

-
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/