LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: "Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>,
	"Kevin P. Fleming" <lkml@kpfleming.us>,
	"Greg KH" <greg@kroah.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Alan Cox" <alan@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: drivers/pci/probe.c patch in 2.6.20.4 causes 'cannot adjust BAR0 (not I/O)' on NVidia MCP51
Date: Mon, 26 Mar 2007 07:58:46 +0100	[thread overview]
Message-ID: <46078B46.76E4.0078.0@novell.com> (raw)
In-Reply-To: <20070325161144.GA12155@kroah.com>

>>> Greg KH <greg@kroah.com> 25.03.07 18:11 >>>
>On Sun, Mar 25, 2007 at 08:23:23AM -0700, 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)
>> 
>> 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.
>
>Jan, any thoughts about this?
>
>Should this be backed out of the -stable releases?

I don't think so - the message (as Alan also said) tells the user that the
intended adjustment is *not* being done, kind of as a warning. I would
agree, though, that the flags adjustment (namely, adding
IORESOURCE_IO) is somewhat questionable; this isn't a change the
patch did, though, it was that way already before. But otoh with the
legacy flag set in progif, these BARs *should* be I/O ones...

Jan


  parent reply	other threads:[~2007-03-26  6:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25 15:23 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 [this message]
2007-03-26 10:55     ` Alan Cox
2007-03-25 16:43 ` Gabriel C
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=46078B46.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@redhat.com \
    --cc=bzolnier@gmail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@kpfleming.us \
    --subject='Re: drivers/pci/probe.c patch in 2.6.20.4 causes '\''cannot adjust BAR0 (not I/O)'\'' on NVidia MCP51' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).