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]

Date:	Mon, 21 May 2007 18:11:13 +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
Subject: Re: libata and legacy ide pcmcia failure

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?

Tejun Heo wrote:
> Robert de Rooy wrote:
>   
>> This gets a little bit further again, but now I get lots of new errors....
>>     
>
> Alright, this doesn't seem to be the CF reader's problem anymore.  It
> seems the PCMCIA controller isn't passing interrupts properly.  Does any
> other device work in the slot?
>
>   

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