From: Nicholas Miell <nmiell@comcast.net>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: VIA x86-64 bootlogs needed
Date: Tue, 25 Jul 2006 16:05:14 -0700 [thread overview]
Message-ID: <1153868714.2661.18.camel@entropy> (raw)
In-Reply-To: <200607260018.04851.ak@suse.de>
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@comcast.net>
next prev parent reply other threads:[~2006-07-25 23:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 16:24 VIA x86-64 bootlogs needed Andi Kleen
2006-07-25 17:32 ` Nicholas Miell
2006-07-25 22:18 ` [discuss] " Andi Kleen
2006-07-25 23:05 ` Nicholas Miell [this message]
2006-07-25 19:58 ` Bongani Hlope
2006-07-25 23:10 ` [discuss] " Jon Mason
2006-07-26 12:26 ` Sergio Monteiro Basto
2006-07-27 1:33 ` Andi Kleen
2006-07-27 1:35 ` Sergio Monteiro Basto
2006-07-27 1:29 ` Sergio Monteiro Basto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1153868714.2661.18.camel@entropy \
--to=nmiell@comcast.net \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.