linux-kernel - 2.6.33-rc3: pci host bridge windows ignored (works with pci=use

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-next>] [day] [month] [year] [list]

Message-ID: <20100113053736.GA6720@jgarrett.org>
Date:	Tue, 12 Jan 2010 23:37:36 -0600
From:	jeff@...rrett.org (Jeff Garrett)
To:	linux-kernel@...r.kernel.org
Cc:	Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-pci@...r.kernel.org, David Airlie <airlied@...ux.ie>
Subject: 2.6.33-rc3: pci host bridge windows ignored (works with
 pci=use_crs)

Took a stab at getting the right emails.  If I missed anyone, sorry...

I have a desktop machine with a radeon HD 4850, and on recent kernels
the radeon driver has failed with the message "No valid linear
framebuffer address".  lspci on the broken configuration showed the
first memory region at d0000000 of the radeon card to be ignored.  dmesg
showed there to be a host bridge window at that address which was also
ignored.

I haven't quantified "recent" kernel.  I was using the Ubuntu/lucid
kernels and it broke in the 2.6.32-* timeline, at which point I switched
to vanilla 2.6.33-rc3 to see if that worked.  I could probably bisect it
in a day or two when I get a little time.

Following dmesg's instructions, setting pci=use_crs causes the region
not to be ignored, and my video works again.

I'm attaching a dmesg from the broken & working configurations, lspci
-vvv output from the working configuration, and the output of acpidump.

(Between the failed/working, I also applied the patch at
http://bugzilla.kernel.org/show_bug.cgi?id=14954
to get rid of the ACPI-parsing oops.  But that only fixed the oops.)

-Jeff Garrett

View attachment "dmesg.failed" of type "text/plain" (59355 bytes)

View attachment "dmesg.working" of type "text/plain" (51744 bytes)

View attachment "lspci" of type "text/plain" (33704 bytes)

View attachment "acpidump" of type "text/plain" (130524 bytes)