From: Gabriel C <nix.or.die@googlemail.com>
To: "Kevin P. Fleming" <lkml@kpfleming.us>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@redhat.com>,
Jan Beulich <jbeulich@novell.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: drivers/pci/probe.c patch in 2.6.20.4 causes 'cannot adjust BAR0 (not I/O)' on NVidia MCP51
Date: Sun, 25 Mar 2007 18:43:28 +0200 [thread overview]
Message-ID: <4606A6B0.4010601@googlemail.com> (raw)
In-Reply-To: <460693EB.9080203@kpfleming.us>
Kevin P. Fleming wrote:
> I just upgraded from 2.6.20.2 to 2.6.20.4 on my Compaq V6000 laptop,
> which has an NVidia core chipset. It has the MCP51 and uses it for PATA
> and SATA.
>
> Booting the 2.6.20.4 kernel causes two messages (and a kernel lockup)
> like this:
>
> 0000:00:0d.0: cannot adjust BAR0 (not I/O)
> 0000:00:0d.0: cannot adjust BAR1 (not I/O)
>
BTW I see this too on my laptop ( older PackardBell EasyNote K ) if I
use P-ATA but I can boot for some reason.
snip
...
[ 18.754623] Enabling SiS 96x SMBus.
[ 18.754812] 0000:00:02.5: cannot adjust BAR0 (not I/O)
[ 18.754816] 0000:00:02.5: cannot adjust BAR1 (not I/O)
[ 18.754819] 0000:00:02.5: cannot adjust BAR2 (not I/O)
[ 18.754822] 0000:00:02.5: cannot adjust BAR3 (not I/O)
...
> Booting without ACPI, without APIC, without LAPIC makes no usable
> difference (although sometimes I will also receive a message about BAR2).
>
> This patch:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ed8ccee0918ad063a4741c0656fda783e02df627;hp=9e5755bce00bb563739aeb0f09932a1907521167
>
> is the cause... backing it out results in a working 2.6.20.4 kernel on
> my laptop.
>
> I'll be happy to provide any assistance I can debugging this problem.
> Thanks.
>
Reagrds,
Gabriel
next prev parent reply other threads:[~2007-03-25 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-25 15:23 drivers/pci/probe.c patch in 2.6.20.4 causes 'cannot adjust BAR0 (not I/O)' on NVidia MCP51 Kevin P. Fleming
2007-03-25 16:11 ` Greg KH
2007-03-25 17:22 ` Kevin P. Fleming
2007-03-25 20:08 ` Alan Cox
2007-03-25 19:21 ` Adrian Bunk
2007-03-26 2:25 ` Kevin P. Fleming
2007-03-26 3:08 ` Adrian Bunk
2007-03-26 6:58 ` Jan Beulich
2007-03-26 10:55 ` Alan Cox
2007-03-25 16:43 ` Gabriel C [this message]
2007-03-25 18:13 ` Torsten Kaiser
2007-03-25 19:09 ` Grzegorz Chwesewicz
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=4606A6B0.4010601@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@kpfleming.us \
/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.