Re: x86 bootmem corruption

2001-05-11 Thread Andrea Arcangeli

On Fri, May 11, 2001 at 05:18:35PM +0100, Alan Cox wrote:
> > reserved.  This is the fix against 2.4.5pre1. This might explain weird
> > crashes and "reserved twice" error messages at boot on highmem systems.
> 
> Reserved twice occurs for two known reasons
> 
> BIOS reporting the same region twice or overlaps (fixed in -ac sent to Linus)
> find_smp_config blindly reserves pages that may already be marked as ROM and
> thus reserved anyway

when it happens because of a double reserve that's fine I know, it _can_
be harmless, I'm not trying to hide those messages. What I'm saying is
that it can _also_ indicate somebody allocated the page before we reserved
it and currently x86 allocates from the bootmem allocator before
reserving all its pages, that's a bug and I provided the fix.

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



Re: x86 bootmem corruption

2001-05-11 Thread Alan Cox

> reserved.  This is the fix against 2.4.5pre1. This might explain weird
> crashes and "reserved twice" error messages at boot on highmem systems.

Reserved twice occurs for two known reasons

BIOS reporting the same region twice or overlaps (fixed in -ac sent to Linus)
find_smp_config blindly reserves pages that may already be marked as ROM and
thus reserved anyway

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



Re: x86 bootmem corruption

2001-05-11 Thread Alan Cox

 reserved.  This is the fix against 2.4.5pre1. This might explain weird
 crashes and reserved twice error messages at boot on highmem systems.

Reserved twice occurs for two known reasons

BIOS reporting the same region twice or overlaps (fixed in -ac sent to Linus)
find_smp_config blindly reserves pages that may already be marked as ROM and
thus reserved anyway

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



Re: x86 bootmem corruption

2001-05-11 Thread Andrea Arcangeli

On Fri, May 11, 2001 at 05:18:35PM +0100, Alan Cox wrote:
  reserved.  This is the fix against 2.4.5pre1. This might explain weird
  crashes and reserved twice error messages at boot on highmem systems.
 
 Reserved twice occurs for two known reasons
 
 BIOS reporting the same region twice or overlaps (fixed in -ac sent to Linus)
 find_smp_config blindly reserves pages that may already be marked as ROM and
 thus reserved anyway

when it happens because of a double reserve that's fine I know, it _can_
be harmless, I'm not trying to hide those messages. What I'm saying is
that it can _also_ indicate somebody allocated the page before we reserved
it and currently x86 allocates from the bootmem allocator before
reserving all its pages, that's a bug and I provided the fix.

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