mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: impulze <impulze@impulze.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@suse.de>, Allen Martin <AMartin@nvidia.com>,
	Robert Hancock <hancockr@shaw.ca>, Len Brown <lenb@kernel.org>,
	Andy Currid <ACurrid@nvidia.com>
Subject: Re: ASUS M2NPV-VM APIC/ACPI Bug (patched)
Date: Wed, 01 Nov 2006 15:27:08 +0100	[thread overview]
Message-ID: <1162391232.23744.21.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <4548AD4E.8050007@impulze.org>


> Anyway i chatted around the globus and someone also mentioned that my 
> IRQs for sound and several others are very high. I'm not sure if this is 
> a board issue or a kernel issue. But since the sound chip on board (hda 
> intel) is having problems too I guess it's a kernel related thing. I 
> wonder if this will be fixed in newer versions.

btw if you have bios problems you can always use the linux-ready
firmware developer kit to test how well it does; see
http://www.linuxfirmwarekit.org for details

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org


  reply	other threads:[~2006-11-01 14:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.09mXx81eXfIStK3wap/U1OZn+kg@ifi.uio.no>
     [not found] ` <fa.1/QTOTFQC91cwKwinVDxrePnGHo@ifi.uio.no>
2006-10-19  0:42   ` Robert Hancock
2006-10-19 12:44     ` Andi Kleen
2006-10-19 15:52     ` Allen Martin
2006-10-19 16:11       ` Andi Kleen
2006-10-20  1:08         ` Allen Martin
2006-10-20 13:04           ` Andi Kleen
2006-11-01 14:21             ` impulze
2006-11-01 14:27               ` Arjan van de Ven [this message]
2006-10-18  6:44 Daniel Mierswa
2006-10-18  7:30 ` Len Brown
2006-10-19 12:41   ` Andi Kleen

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=1162391232.23744.21.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=ACurrid@nvidia.com \
    --cc=AMartin@nvidia.com \
    --cc=ak@suse.de \
    --cc=hancockr@shaw.ca \
    --cc=impulze@impulze.org \
    --cc=lenb@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®