Re: 2.6.23 boot failures on x86-64.

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.

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.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: 2.6.23 boot failures on x86-64.
    • From: Dave Jones <[email protected]>

• References:
  • 2.6.23 boot failures on x86-64.
    • From: Dave Jones <[email protected]>

• Prev by Date: Re: vm_ops.page_mkwrite() fails with vmalloc on 2.6.23
• Next by Date: [PATCH/RFC] register_cpu __devinit or __cpuinit
• Previous by thread: Re: [stable] 2.6.23 boot failures on x86-64.
• Next by thread: Re: 2.6.23 boot failures on x86-64.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]