On Friday, June 1, 2007 12:19:12 Justin Piszcz wrote: > It works ok on > my machine (correctly detects the condition, adjusts end_pfn, and keeps > the machine fast), aside from the fact that X won't start. > > But X won't start? :\ Oh yeah, forgot about that. :) Somehow the patch breaks X startup, probably by doing something bad to the MTRR API... but I don't know what yet. Jesse - 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/
- References:
- Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
- From: Justin Piszcz <[email protected]>
- Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
- From: Jesse Barnes <[email protected]>
- Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
- From: Justin Piszcz <[email protected]>
- Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
- Prev by Date: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
- Next by Date: Re: [patch] CFS scheduler, -v14
- Previous by thread: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
- Next by thread: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
- Index(es):
 |