Re: 2.6.32: x86_32: Destination address is too large.

From: H. Peter Anvin
Date: Thu Dec 17 2009 - 10:09:23 EST

Next message: Greg KH: "Re: [50/90] e100: Use pci pool to work around GFP_ATOMIC order 5memory allocation failure"
Previous message: Eric W. Biederman: "Re: [PATCH] SYSCTL: Fix sysctl breakage on systems with older glibc"
In reply to: Alexander Beregalov: "Re: 2.6.32: x86_32: Destination address is too large."
Next in thread: H. Peter Anvin: "Re: 2.6.32: x86_32: Destination address is too large."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 12/17/2009 06:49 AM, Alexander Beregalov wrote:
> Config for 2.6.32 is attached

Actually, could you please send me you bzImage file?

-hpa

--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.

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

Next message: Greg KH: "Re: [50/90] e100: Use pci pool to work around GFP_ATOMIC order 5memory allocation failure"
Previous message: Eric W. Biederman: "Re: [PATCH] SYSCTL: Fix sysctl breakage on systems with older glibc"
In reply to: Alexander Beregalov: "Re: 2.6.32: x86_32: Destination address is too large."
Next in thread: H. Peter Anvin: "Re: 2.6.32: x86_32: Destination address is too large."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]