From: Nicholas Miell <nmiell@comcast.net>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: VIA x86-64 bootlogs needed
Date: Tue, 25 Jul 2006 10:32:39 -0700 [thread overview]
Message-ID: <1153848759.2661.5.camel@entropy> (raw)
In-Reply-To: <200607251824.30504.ak@suse.de>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
On Tue, 2006-07-25 at 18:24 +0200, Andi Kleen wrote:
> Hi,
>
> For some APIC code rework I would like to collect some statistics on
> VIA APIC setups.
>
> If you have a system with VIA chipset running a recent (2.6.16+) x86-64 kernel
> please boot the system with apic=verbose on the kernel command and send me
>
> - boot output (/var/log/boot.msg or dmesg -s100000000 output after boot)
> - dmidecode output
> - lspci -v output
MSI Master2-FAR with VIA K8T800, kernel-2.6.17-1.2157_FC5
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.
--
Nicholas Miell <nmiell@comcast.net>
[-- Attachment #2: dmesg-MSI_Master2-FAR.txt.bz2 --]
[-- Type: application/x-bzip, Size: 7113 bytes --]
[-- Attachment #3: dmidecode-MSI_Master2-FAR.txt.bz2 --]
[-- Type: application/x-bzip, Size: 2977 bytes --]
[-- Attachment #4: lspci-MSI_Master2-FAR.txt.bz2 --]
[-- Type: application/x-bzip, Size: 1542 bytes --]
next prev parent reply other threads:[~2006-07-25 17:32 UTC|newest]
Thread overview: 11+ 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 [this message]
2006-07-25 22:18 ` [discuss] " Andi Kleen
2006-07-25 23:05 ` 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
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 17:46 Hans-Frieder Vogt
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=1153848759.2661.5.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.