public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Bruno <sean.bruno@dsl-only.net>
To: Peter Buckingham <peter@pantasys.com>
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:11:42 -0700	[thread overview]
Message-ID: <1124467902.14825.41.camel@home-lap> (raw)
In-Reply-To: <430601C5.5080505@pantasys.com>

On Fri, 2005-08-19 at 08:59 -0700, Peter Buckingham wrote:
> Andi Kleen wrote:
> > On Fri, Aug 19, 2005 at 08:52:15AM -0700, Peter Buckingham wrote:
> > 
> >>Andi Kleen wrote:
> >>
> >>>At least his original error message can only happen when  CONFIG_GART_IOMMU
> >>>is disabled.
> >>>
> >>>PCI-DMA:  More that 4GB of RAM and no IOMMU                                
> >>>PCI-DMA:  32bit PCI IO may malfunction.<6>PCI-DMA:  Disabling IOMMU        
> >>
> >>Yeah, I agree. In the later dmesgs, though, it seems to be enabled.
> > 
> > 
> > Those don't show any failure.
> 
> no they don't. basically it just says your bios hasn't configured enough 
> IOMMU space, so the kernel is going to do it anyway. it's really just a 
> warning or an fyi rather than an error. i may have chosen the word 
> poorly ;-)
> 
> in short Sean, this isn't a big deal. you only really need to change 
> this if you want to remove a warning from your dmesg output.
> 
> peter

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!  :(

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

And this one about the 8254 timer:
..MP-BIOS bug: 8254 timer not connected to IO-APIC

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.

Sean



  reply	other threads:[~2005-08-19 16:11 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 [this message]
2005-08-19 16:22                     ` Peter Buckingham
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=1124467902.14825.41.camel@home-lap \
    --to=sean.bruno@dsl-only.net \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@pantasys.com \
    /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