On Mon, 2007-10-29 at 11:37 -0700, Linus Torvalds wrote:
> Martin - it would be great if you could try out your failing machine with
> 2.6.24-rc1 (or a nightly snapshot or current git.. the more recent the
> better).
>
> But if I'm right, that commit should be reverted from 2.6.24 just because
On Mon, Oct 29, 2007 at 11:37:40AM -0700, Linus Torvalds wrote:
>
>
> On Mon, 29 Oct 2007, Greg KH wrote:
> >
> > I'll be glad to revert it in -stable, if it's also reverted in Linus's
> > tree first :)
>
> We've had some changes since 2.6.23, and afaik, the
> "alloc_bootmem_high_node()" code
On Mon, 29 Oct 2007, Siddha, Suresh B wrote:
> But I can't explain how 2e1c49db4c640b35df13889b86b9d62215ade4b6 can be
> the root cause of Dave's issue in 2.6.23.
2.6.23 has no VMEMMAP support for x86_64.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Mon, Oct 29, 2007 at 11:37:40AM -0700, Linus Torvalds wrote:
>
>
> On Mon, 29 Oct 2007, Greg KH wrote:
> >
> > I'll be glad to revert it in -stable, if it's also reverted in Linus's
> > tree first :)
>
> We've had some changes since 2.6.23, and afaik, the
> "alloc_bootmem_high_node()" code
On Mon, 29 Oct 2007, Linus Torvalds wrote:
> We've had some changes since 2.6.23, and afaik, the
> "alloc_bootmem_high_node()" code is alreadt effectively dead there. It's
> only called if CONFIG_SPARSEMEM_VMEMMAP is *not* enabled, and I *think* we
> enable it by force on x86-64 these days.
On Mon, 29 Oct 2007, Greg KH wrote:
>
> I'll be glad to revert it in -stable, if it's also reverted in Linus's
> tree first :)
We've had some changes since 2.6.23, and afaik, the
"alloc_bootmem_high_node()" code is alreadt effectively dead there. It's
only called if CONFIG_SPARSEMEM_VMEMMAP
On Mon, Oct 29, 2007 at 01:50:14PM -0400, 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.
>
> Martin tracked this down to the following
On Mon, Oct 29, 2007 at 01:50:14PM -0400, 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.
Martin tracked this down to the following commit.
On Mon, 29 Oct 2007, Greg KH wrote:
I'll be glad to revert it in -stable, if it's also reverted in Linus's
tree first :)
We've had some changes since 2.6.23, and afaik, the
alloc_bootmem_high_node() code is alreadt effectively dead there. It's
only called if CONFIG_SPARSEMEM_VMEMMAP is
On Mon, Oct 29, 2007 at 11:37:40AM -0700, Linus Torvalds wrote:
On Mon, 29 Oct 2007, Greg KH wrote:
I'll be glad to revert it in -stable, if it's also reverted in Linus's
tree first :)
We've had some changes since 2.6.23, and afaik, the
alloc_bootmem_high_node() code is alreadt
On Mon, 29 Oct 2007, Siddha, Suresh B wrote:
But I can't explain how 2e1c49db4c640b35df13889b86b9d62215ade4b6 can be
the root cause of Dave's issue in 2.6.23.
2.6.23 has no VMEMMAP support for x86_64.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On Mon, 29 Oct 2007, Linus Torvalds wrote:
We've had some changes since 2.6.23, and afaik, the
alloc_bootmem_high_node() code is alreadt effectively dead there. It's
only called if CONFIG_SPARSEMEM_VMEMMAP is *not* enabled, and I *think* we
enable it by force on x86-64 these days.
On Mon, 2007-10-29 at 11:37 -0700, Linus Torvalds wrote:
Martin - it would be great if you could try out your failing machine with
2.6.24-rc1 (or a nightly snapshot or current git.. the more recent the
better).
But if I'm right, that commit should be reverted from 2.6.24 just because
On Mon, Oct 29, 2007 at 11:37:40AM -0700, Linus Torvalds wrote:
On Mon, 29 Oct 2007, Greg KH wrote:
I'll be glad to revert it in -stable, if it's also reverted in Linus's
tree first :)
We've had some changes since 2.6.23, and afaik, the
alloc_bootmem_high_node() code is alreadt
14 matches
Mail list logo
