linux-kernel - Re: libata and legacy ide pcmcia failure

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: <4651D40B.7080907@gmail.com>
Date:	Mon, 21 May 2007 19:16:59 +0200
From:	Robert de Rooy <robert.de.rooy@...il.com>
To:	Tejun Heo <htejun@...il.com>
CC:	linux-kernel@...r.kernel.org, alan@...hat.com, bzolnier@...il.com,
	jgarzik@...ox.com, linux-pcmcia@...ts.infradead.org
Subject: Re: libata and legacy ide pcmcia failure

I don't know if linux-pcmcia is members only, so this might not reach 
that list.

Here are some log files...

Tejun Heo wrote:
> Robert de Rooy wrote:
>   
>> Hmm, good question. I do not have any other PCMCIA device to test.
>> The only other device I have is a Cardbus Wi-Fi adapter without Linux
>> support (Marvell). If I insert that adapter lspci seems to list it
>> properly, but without resorting to ndiswrapper I have no way of testing
>> it. In any case, seeing how Cardbus is PCI based this is probably
>> pointless to resolving this issue.
>>
>> Would any other log data from the controller initialization or lspci help?
>>     
>
> Hmmm... I don't really know much about PCMCIA.  cc'ing linux-pcmcia.
>
> The original thread can be read from the following URL.
>
>   http://thread.gmane.org/gmane.linux.kernel/530099
>
> It seems we're losing interrupts from the CFA device.  Any ideas?
>
> Thanks.
>
>   


View attachment "pccardctl.txt" of type "text/plain" (223 bytes)

View attachment "dmesg.txt" of type "text/plain" (34153 bytes)

View attachment "lspci.txt" of type "text/plain" (20000 bytes)