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: <4606AFC8.40104@kpfleming.us>
Date:	Sun, 25 Mar 2007 10:22:16 -0700
From:	"Kevin P. Fleming" <lkml@...leming.us>
To:	Greg KH <greg@...ah.com>
CC:	Jan Beulich <jbeulich@...ell.com>, Alan Cox <alan@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: drivers/pci/probe.c patch in 2.6.20.4 causes 'cannot adjust	BAR0
 (not I/O)' on NVidia MCP51

Greg KH wrote:

> Kevin, does 2.6.21-rc4 work properly for you?

No, it seems to exhibit the same behavior. However, I should note that
this laptop is not 100% stable under any kernel release anyway... in
text console mode it frequently locks up tight (although not with the
NVidia closed-source driver running and X started <G>).

I tried booting 2.6.21-rc4 five times and only once did it get pass
these messages during PCI probing, but it hung during the forcedeth
driver initialization.

I also forgot to note in my initial problem report that the PCI device
being referred to in the messages is the MCP51 IDE interface (although
that could have been assumed from what the patch is supposed to do).
-
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/