linux-kernel - Re: [PATCH] VIA IRQ quirk fixup only in XT

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: <1154145126.10955.100.camel@bastov.localdomain>
Date:	Sat, 29 Jul 2006 04:52:06 +0100
From:	Sergio Monteiro Basto <sergio@...giomb.no-ip.org>
To:	Andrew Morton <akpm@...l.org>
Cc:	linux-kernel@...r.kernel.org, dsd@...too.org,
	alan@...rguk.ukuu.org.uk, cw@...f.org, greg@...ah.com,
	jeff@...zik.org, harmon@....edu
Subject: Re: [PATCH] VIA IRQ quirk fixup only in XT_PIC mode Take 2

ok, 
Begging by answer the question, Daniel Drake, clearly, say:
"Nobody really has a full understanding of the problem and the
issues ...". 
As I can understand, make a sort of blacklist with IDs of the
problematic VIAs, which probably will always miss some IDs, but the main
problem is in lasts lines of this email. The way how is design the list,
could be one excellent idea, inclusive for other situations on VIAs, I
don't put this in question. 

After reviewing what I had write about this, the changelog: 
(please correct me the English and cut some parts) 
Well, a good new, I already have my old laptop again which have the most
problematic VIA (PCI_DEVICE_ID_VIA_82C686). At the time I bought it, I
had problematic stuffs when kernel was trying enable APIC, on this
laptop, was one Local APIC, later we had the boot option nolapic to
workaround this. So the VIA works very well without lapic enabled.
Someone give to this problem a name of "the APIC victims", happened on
VIAs, Nvidias and probably on others boards. 
But this laptop need the quirks; nobody have put this in question,
VIA_82C686 has been always on list of the quirks. And btw, is important,
_need_ ACPI, with acpi=off, 1/2 of the computer: power manager and
hot-key, don't work at all. 
A few of the story about my laptop http://sergiomb.no-ip.org/laptop/

So, a few month ago, I bought, what I bought, one VIA of course :) with
this IDs: PCI_DEVICE_ID_VIA_82C586_1 and _2.
With this new VIA, I have exactly, the opposite problem, I found, on
this VIA with IO-APIC working well, that quirks aren't good/needed .
After, I found this interesting email http://lkml.org/lkml/2005/8/13/30
by Karsten Wiese, after, Alan Cox writes this
http://lkml.org/lkml/2005/8/16/160 (on same thread) and Karsten Wiese
end ups with the solution on http://lkml.org/lkml/2005/8/18/92, which I
want try to implement and that's it, come this idea, that may the full
understanding the problem.  
Conclusion, I have 2 VIAs with almost same IDs (others reporters have
with exactly the same IDs) and in ones I need the quirks and in others
don't, why ? one don't have apics enabled, the other have it !?!

Thanks, 

On Fri, 2006-07-28 at 12:24 -0700, Andrew Morton wrote:
> On Fri, 28 Jul 2006 14:01:01 +0100
> Sergio Monteiro Basto <sergio@...giomb.no-ip.org> wrote:
> 
> > Hi, this patch (now for 2.6.18-rc2) is more readable.
> 
> It has no changelog, and this sort of patch does need a lenghty one, please.
> 
> What relationship does it have to
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc2/2.6.18-rc2-mm1/broken-out/pci-quirk_via_irq-behaviour-change.patch?
>  If it is better, why?
-- 
Sérgio M.B.

Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (2166 bytes)