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:	Sat, 09 Jun 2007 00:06:16 +0200
From:	Robert de Rooy <robert.de.rooy@...il.com>
To:	Mark Lord <mlord@...ox.com>
CC:	Tejun Heo <htejun@...il.com>, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org,
	bzolnier@...il.com, linux-pcmcia@...ts.infradead.org,
	"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>
Subject: Re: libata and legacy ide pcmcia failure

Mark Lord wrote:
> I still don't see much evidence that interrupts are actually 
> functioning here.
> It would be good to see /proc/interrupts before/after libata tries to 
> talk to it.
>
> Let's assume for the moment that interrupts are b0rken.
> The legacy IDE driver can talk to such devices completely without 
> interrupts,
> if the IDE polling patch (below) is applied.
>
> So, Robert:  could you try again with the old IDE driver,
> except apply this patch to it first?  This will give valuable info.
I tried the patch, but a get a kernel panic on boot with it. I can try 
to get a screenshot of it tomorrow.
-
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/