linux-kernel - Re: linux-2.6.19-rc2 PCI problem

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: <b6a2187b0610280324s66b06067od4691fa9f79420a7@mail.gmail.com>
Date:	Sat, 28 Oct 2006 18:24:58 +0800
From:	"Jeff Chua" <jeff.chua.linux@...il.com>
To:	"Adrian Bunk" <bunk@...sta.de>
Cc:	gregkh@...e.de, linux-kernel@...r.kernel.org,
	"David Miller" <davem@...emloft.net>,
	linux-pci@...ey.karlin.mff.cuni.cz,
	"Yinghai Lu" <yinghai.lu@....com>
Subject: Re: linux-2.6.19-rc2 PCI problem

On 10/28/06, Adrian Bunk <bunk@...sta.de> wrote:
> Greg, is this 2.6.19-rc1 regression anything you've already heard about,
> or should Jeff bisect for the commit that broke it?

> So it's a PCI problem, not a tg3 issue.
> And tg3 is even not the first driver that fails after this...

Adrian, thanks for the lead, so I decided to try different PCI setting.

Setting to "BIOS" make tg3 works again.

Up to 2.6.18, I was using "PCI access mode (Any)" and had no problem,
but from  2.6.19-rc1 onwards, setting to "ANY" doesn't seem to work
anymore.

I've just tested all 2.6.19-rc[123] and all are working with the
"BIOS" setting, but not "ANY".

New setting in .config ...

CONFIG_PCI_GOBIOS=y
# CONFIG_PCI_GOANY is not set

Thanks for all your help!

Jeff.
-
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/