linux-kernel - Re: [BUG 2.6.31-rc1] HIGHMEM64G causes hang in PCI init on 32-bit x86

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: <19014.36968.722952.729071@pilspetsen.it.uu.se>
Date:	Sat, 27 Jun 2009 23:34:32 +0200
From:	Mikael Pettersson <mikpe@...uu.se>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Mikael Pettersson <mikpe@...uu.se>,
	Grant Grundler <grundler@...isc-linux.org>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: [BUG 2.6.31-rc1] HIGHMEM64G causes hang in PCI init on 32-bit
 x86

H. Peter Anvin writes:
 > Mikael Pettersson wrote:
 > > 
 > > Sure. This is from 2.6.31-rc1 with the commit commented out and
 > > replaced by a debug printk:
 > > 
 > > identify_cpu: ->x86_phys_bits == 36, would change iomem_resource.end from 0xffffffffffffffff to 0x0000000fffffffff
 > > 
 > > which looks correct for HIGHMEM64G.
 > 
 > OK, I'm going to revert the checkin... however, we still need to figure
 > out what the right answer here is, and why this broke (and why none of
 > my tests showed this failure...)
 > 
 > However, it is clear that the answer is more complex than we originally
 > anticipated.  Mikael, would you be willing to run some experiments over
 > the near future?

Yes

/Mikael
--
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/