linux-kernel - Re: drivers/pci/probe.c patch in 2.6.20.4 causes 'cannot adjust BAR0 (not I/O)' on NVidia MCP51

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4606A6B0.4010601@googlemail.com>
Date:	Sun, 25 Mar 2007 18:43:28 +0200
From:	Gabriel C <nix.or.die@...glemail.com>
To:	"Kevin P. Fleming" <lkml@...leming.us>
CC:	linux-kernel@...r.kernel.org, Alan Cox <alan@...hat.com>,
	Jan Beulich <jbeulich@...ell.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: drivers/pci/probe.c patch in 2.6.20.4 causes 'cannot adjust BAR0
 (not I/O)' on NVidia MCP51

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/