From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org
Cc: Nicholas Miell <nmiell@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: VIA x86-64 bootlogs needed
Date: Wed, 26 Jul 2006 00:18:04 +0200 [thread overview]
Message-ID: <200607260018.04851.ak@suse.de> (raw)
In-Reply-To: <1153848759.2661.5.camel@entropy>
> 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?
-Andi
next prev parent reply other threads:[~2006-07-25 22:29 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 ` Andi Kleen [this message]
2006-07-25 23:05 ` [discuss] " Nicholas Miell
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=200607260018.04851.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nmiell@comcast.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox