linux-kernel - Re: regarding VIA quirk fix

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] [day] [month] [year] [list]

Message-ID: <455DF7CF.7020203@gentoo.org>
Date:	Fri, 17 Nov 2006 12:56:31 -0500
From:	Daniel Drake <dsd@...too.org>
To:	Tejun Heo <htejun@...il.com>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: regarding VIA quirk fix

Tejun Heo wrote:
> Hello, Alan.
> 
> We've been getting bug reports from sata_via users for quite sometime 
> now.  The first IRQ driven command (IDENTIFY) times out and thus device 
> detection fails.  The following patch seems to fix it for many users.
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=116300291505638
> 
> But, not for all.
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=7415
> 
> Any ideas how to proceed on this bug?

I'm not certain, but I think that this is an unrelated issue. Both the 
working kernel and the failing kernels quirk the device in the same way:

PCI: VIA IRQ fixup for 0000:00:0f.0, from 11 to 2

Both the working kernel (2.6.17-gentoo-r8) and the first failing kernel 
(2.6.18-gentoo) have the same patch for 'fixing' the quirk issues: 
Chris's changes were reverted, the VIA IRQ quirk was back in the 2.6.16 
state. Since then the same issues have been observed with unpatched 
2.6.19-rc.

This is not definitive but suggests the issue is elsewhere.

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