From: Peter Buckingham <peter@pantasys.com>
To: Sean Bruno <sean.bruno@dsl-only.net>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
Date: Fri, 19 Aug 2005 09:22:09 -0700 [thread overview]
Message-ID: <43060731.10002@pantasys.com> (raw)
In-Reply-To: <1124467902.14825.41.camel@home-lap>
Sean Bruno wrote:
> Well, there doesn't appear to be any reference to a setting in my BIOS
> for this size(IOMMU). So I don't think that I can change it! :(
well, it doesn't really matter since the kernel enables the IOMMU
anyway. if you want to change the size you can pass that as a parameter
on the command line.
> The machine is working quite a bit better with pci=noacpi in leu of
> disabling ACPI in the BIOS, but there are still those nasty errors in
> reference to the ACPI tables being broken:
> ACPI-0362: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace,
> AE_NOT_FOUND
> search_node ffff8101428572c0 start_node ffff8101428572c0 return_node
> 0000000000000000
since it doesn't look like you'll get a bios fix for this you may want
to look at building a custom dsdt. the kernel can load a custom dsdt
from an initrd/initramfs. have a look at the acpi site (acpi.sf.net?).
they talk about what's needed to do this. basically you can get your
dsdt from /proc/acpi/dsdt and disassemble it using the iasl tools, fix
it and then load it with an initrd. note that this is not really a
trivial task :-(
> And this one about the 8254 timer:
> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
i've seen this before.. i think this may be related to the timer
override not being done for your system (again strangely a bios bug...).
why don't you try passing acpi_skip_timer_override on the command line.
> And finally, I think that something else kind of wierd is happening with
> the on-board sensors. lm_sensors is having trouble detecting the fan
> speeds and temperatures of the main board, but I will take that up with
> their developers.
i think this may well be related to the ACPI issues you are having,
since this is how the information is normally gathered.
peter
next prev parent reply other threads:[~2005-08-19 16:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1124401950.14825.13.camel@home-lap.suse.lists.linux.kernel>
2005-08-18 21:59 ` 2.6.13-rc6-git10 test report [x86_64] Andi Kleen
[not found] ` <1124405533.14825.24.camel@home-lap>
2005-08-18 23:03 ` Andi Kleen
2005-08-18 23:26 ` Sean Bruno
2005-08-19 0:19 ` 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE) Sean Bruno
2005-08-19 15:38 ` Peter Buckingham
2005-08-19 15:46 ` Andi Kleen
2005-08-19 15:52 ` Peter Buckingham
2005-08-19 15:53 ` Andi Kleen
2005-08-19 15:59 ` Peter Buckingham
2005-08-19 16:11 ` Sean Bruno
2005-08-19 16:22 ` Peter Buckingham [this message]
2005-08-20 21:35 ` Joseph Fannin
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=43060731.10002@pantasys.com \
--to=peter@pantasys.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.bruno@dsl-only.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 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.