linux-kernel - Re: [discuss] Re: VIA x86-64 bootlogs needed

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:	Tue, 25 Jul 2006 16:05:14 -0700
From:	Nicholas Miell <nmiell@...cast.net>
To:	Andi Kleen <ak@...e.de>
Cc:	discuss@...-64.org, linux-kernel@...r.kernel.org
Subject: Re: [discuss] Re: VIA x86-64 bootlogs needed

On Wed, 2006-07-26 at 00:18 +0200, Andi Kleen wrote:
>  > MSI Master2-FAR with VIA K8T800, kernel-2.6.17-1.2157_FC5
> 
> Thanks.
> 
> > With any luck, this APIC rework will fix this board's habit of
> > spontaneously turning off interrupts at the IOAPIC level without the
> > kernel's knowledge.
> 
> Unlikely unfortunately. How does it look like when they get turned off?
> 

I stop getting any interrupts from the device in question (either the
on-board UHCI controllers or the on-board SATA controller) -- i.e. mouse
movement gets jerky because uhci-hcd is operating purely by polling or I
start getting libata timeouts in my logs.

I have an abomination of a systemtap script which calls
unmask_IO_APIC_irq directly which instantly "fixes" it when things go
wrong.

I also have another stap script which records stack traces when
mask_IO_APIC_irq and unmask_IO_APIC_irq called in order to check if the
IRQs are actually getting turned off without the kernel's knowledge, but
when I run that in the background, the problem doesn't ever manifest
itself. 

-- 
Nicholas Miell <nmiell@...cast.net>

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