From: impulze <impulze@impulze.org>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: 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:21:02 +0100 [thread overview]
Message-ID: <4548AD4E.8050007@impulze.org> (raw)
In-Reply-To: <200610201504.51657.ak@suse.de>
Andi Kleen wrote:
>> Well that's the problem. The issue only existed in the nForce2
>> reference BIOS (and maybe early in nForce3) but we still occasionally
>>
>
> Definitely some NF3 too, i've seen it on 64bit boxes.
>
>
>> see shipping customer BIOSes to this day that have this same bug for
>> nForce5 (like M2NPV referenced in this thread).
>>
>> Probably what ASUS is doing in the M2NPV BIOS is copying the ACPI tables
>> from an earlier nForce2 product.
>>
>
> But the timer override is correct or still broken?
>
>
>> Probably what needs to happen is to make the HPET check more robust and
>> only return 1 if HPET is present and enabled.
>>
>
> I think the problem is that those Asus boards also don't have a HPET
> table. So even though NF5 has HPET the kernel doesn't know about it
> and the heuristic "if HPET then NF5 and timer override ok" breaks.
>
> I still suspect doing a
> "if (PCI ID from NF2 or NF3) ignore timer override"
> is probably the best solution right now. But I don't have a full
> list of PCI-IDs for NF2/NF3. Do you have one?
>
> Ok that might still break the NF4. I assume it never needs any
> timer overrides so it might be safe to include it in the PCI-IDs
> too.
>
> Or do you have a better proposal?
>
> -Andi
>
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.
next prev parent reply other threads:[~2006-11-01 14:22 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 ` ASUS M2NPV-VM APIC/ACPI Bug (patched) 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 [this message]
2006-11-01 14:27 ` Arjan van de Ven
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=4548AD4E.8050007@impulze.org \
--to=impulze@impulze.org \
--cc=ACurrid@nvidia.com \
--cc=AMartin@nvidia.com \
--cc=ak@suse.de \
--cc=hancockr@shaw.ca \
--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