| 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
| ||
|
Message-ID: <20071029184747.GB1650@redhat.com> Date: Mon, 29 Oct 2007 14:47:47 -0400 From: Dave Jones <davej@...hat.com> To: Andi Kleen <ak@...e.de> Cc: Linux Kernel <linux-kernel@...r.kernel.org>, Martin Ebourne <fedora@...urne.me.uk>, Zou Nan hai <nanhai.zou@...el.com>, Suresh Siddha <suresh.b.siddha@...el.com>, stable@...nel.org, Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: 2.6.23 boot failures on x86-64. On Mon, Oct 29, 2007 at 07:18:43PM +0100, Andi Kleen wrote: > On Monday 29 October 2007 18:50:14 Dave Jones wrote: > > We've had a number of people reporting that their x86-64s stopped booting > > when they moved to 2.6.23. It rebooted just after discovering the AGP bridge > > as a result of the IOMMU init. > > It's probably the usual "nobody tests sparsemem at all" issue. We've been using SPARSEMEM in Fedora for a *long* time. So long in fact, I forget why we moved away from DISCONTIGMEM, so there's a significant number of users using that configuration for some time. > But if allocating bootmem >4G doesn't work on these systems > most likely they have more problems anyways. It might be better > to find out what goes wrong exactly. Any ideas on what to instrument ? Dave -- http://www.codemonkey.org.uk - 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/
Powered by blists - more mailing lists