On Fri, Mar 01, 2013 at 09:07:52AM -0800, Linus Torvalds wrote:
> On Fri, Mar 1, 2013 at 8:50 AM, Greg KH wrote:
> >
> > What ever happened with this? Did something go into Linus's tree to
> > resolve this issue that I need to pull into a stable release?
>
> This was fixed by commit
On Fri, Mar 1, 2013 at 8:50 AM, Greg KH wrote:
>
> What ever happened with this? Did something go into Linus's tree to
> resolve this issue that I need to pull into a stable release?
This was fixed by commit 7c45512df987 ("mm: fix pageblock bitmap allocation").
And you already put it in,
On Sat, Feb 16, 2013 at 09:29:54AM +0100, Ingo Molnar wrote:
>
> * Greg KH wrote:
>
> > On Fri, Feb 15, 2013 at 12:44:26PM +0100, Ingo Molnar wrote:
> > >
> > > [ Greg: -stable was Cc:-ed for this potentially buggy commit. ]
> > >
> > > * Yinghai Lu wrote:
> > >
> > > > On Thu, Feb 14, 2013
On Sat, Feb 16, 2013 at 09:29:54AM +0100, Ingo Molnar wrote:
* Greg KH g...@kroah.com wrote:
On Fri, Feb 15, 2013 at 12:44:26PM +0100, Ingo Molnar wrote:
[ Greg: -stable was Cc:-ed for this potentially buggy commit. ]
* Yinghai Lu ying...@kernel.org wrote:
On Thu, Feb
On Fri, Mar 1, 2013 at 8:50 AM, Greg KH gre...@linuxfoundation.org wrote:
What ever happened with this? Did something go into Linus's tree to
resolve this issue that I need to pull into a stable release?
This was fixed by commit 7c45512df987 (mm: fix pageblock bitmap allocation).
And you
On Fri, Mar 01, 2013 at 09:07:52AM -0800, Linus Torvalds wrote:
On Fri, Mar 1, 2013 at 8:50 AM, Greg KH gre...@linuxfoundation.org wrote:
What ever happened with this? Did something go into Linus's tree to
resolve this issue that I need to pull into a stable release?
This was fixed by
On 2/18/2013 6:46 AM, Mel Gorman wrote:
On Sat, Feb 16, 2013 at 10:26:30AM -0800, Linus Torvalds wrote:
On Fri, Feb 15, 2013 at 3:44 AM, Ingo Molnar wrote:
c060f943d092 may be related as you config does not have
CONFIG_SPARSEMEM defined.
Right, that's the commit causing the x86 regression:
On Sat, Feb 16, 2013 at 10:26:30AM -0800, Linus Torvalds wrote:
> On Fri, Feb 15, 2013 at 3:44 AM, Ingo Molnar wrote:
> >>
> >> c060f943d092 may be related as you config does not have
> >> CONFIG_SPARSEMEM defined.
> >
> > Right, that's the commit causing the x86 regression:
> >
> >
* Linus Torvalds wrote:
> > Right, that's the commit causing the x86 regression:
> >
> > c060f943d0929f3e429c5d9522290584f6281d6e is the first bad commit
> > commit c060f943d0929f3e429c5d9522290584f6281d6e
> > Date: Fri Jan 11 14:31:51 2013 -0800
> >
> > mm: use aligned zone start for
* Linus Torvalds torva...@linux-foundation.org wrote:
Right, that's the commit causing the x86 regression:
c060f943d0929f3e429c5d9522290584f6281d6e is the first bad commit
commit c060f943d0929f3e429c5d9522290584f6281d6e
Date: Fri Jan 11 14:31:51 2013 -0800
mm: use aligned
On Sat, Feb 16, 2013 at 10:26:30AM -0800, Linus Torvalds wrote:
On Fri, Feb 15, 2013 at 3:44 AM, Ingo Molnar mi...@kernel.org wrote:
c060f943d092 may be related as you config does not have
CONFIG_SPARSEMEM defined.
Right, that's the commit causing the x86 regression:
On 2/18/2013 6:46 AM, Mel Gorman wrote:
On Sat, Feb 16, 2013 at 10:26:30AM -0800, Linus Torvalds wrote:
On Fri, Feb 15, 2013 at 3:44 AM, Ingo Molnar mi...@kernel.org wrote:
c060f943d092 may be related as you config does not have
CONFIG_SPARSEMEM defined.
Right, that's the commit causing the
On Sat, Feb 16, 2013 at 11:38 AM, Yinghai Lu wrote:
>
> but you forgot to update setup_usemap() for SPARSEMEM
Heh. I tried desperately to find a config to test my patch in, because
I couldn't see how to even disable SPARSEMEM for my normal x86-64
build. But then I *only* tested it for that
On Sat, Feb 16, 2013 at 10:26 AM, Linus Torvalds
wrote:
> On Fri, Feb 15, 2013 at 3:44 AM, Ingo Molnar wrote:
>>>
>>> c060f943d092 may be related as you config does not have
>>> CONFIG_SPARSEMEM defined.
>>
>> Right, that's the commit causing the x86 regression:
>>
>>
On Fri, Feb 15, 2013 at 3:44 AM, Ingo Molnar wrote:
>>
>> c060f943d092 may be related as you config does not have
>> CONFIG_SPARSEMEM defined.
>
> Right, that's the commit causing the x86 regression:
>
> c060f943d0929f3e429c5d9522290584f6281d6e is the first bad commit
> commit
* Greg KH wrote:
> On Fri, Feb 15, 2013 at 12:44:26PM +0100, Ingo Molnar wrote:
> >
> > [ Greg: -stable was Cc:-ed for this potentially buggy commit. ]
> >
> > * Yinghai Lu wrote:
> >
> > > On Thu, Feb 14, 2013 at 7:08 AM, Ingo Molnar wrote:
> > > > these three:
> > > >
> > > >
* Ingo Molnar wrote:
> Revert attached below - it reverts cleanly and I'll test this
> today, to see whether this solves the sporadic lockups.
Ok, the revert survived a day of hundreds of randconfigs - while
it would lock up within 100 randconfigs before.
So this commit appears to be the
* Ingo Molnar mi...@kernel.org wrote:
Revert attached below - it reverts cleanly and I'll test this
today, to see whether this solves the sporadic lockups.
Ok, the revert survived a day of hundreds of randconfigs - while
it would lock up within 100 randconfigs before.
So this commit
* Greg KH g...@kroah.com wrote:
On Fri, Feb 15, 2013 at 12:44:26PM +0100, Ingo Molnar wrote:
[ Greg: -stable was Cc:-ed for this potentially buggy commit. ]
* Yinghai Lu ying...@kernel.org wrote:
On Thu, Feb 14, 2013 at 7:08 AM, Ingo Molnar mi...@kernel.org wrote:
these
On Fri, Feb 15, 2013 at 3:44 AM, Ingo Molnar mi...@kernel.org wrote:
c060f943d092 may be related as you config does not have
CONFIG_SPARSEMEM defined.
Right, that's the commit causing the x86 regression:
c060f943d0929f3e429c5d9522290584f6281d6e is the first bad commit
commit
On Sat, Feb 16, 2013 at 10:26 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
On Fri, Feb 15, 2013 at 3:44 AM, Ingo Molnar mi...@kernel.org wrote:
c060f943d092 may be related as you config does not have
CONFIG_SPARSEMEM defined.
Right, that's the commit causing the x86 regression:
On Sat, Feb 16, 2013 at 11:38 AM, Yinghai Lu ying...@kernel.org wrote:
but you forgot to update setup_usemap() for SPARSEMEM
Heh. I tried desperately to find a config to test my patch in, because
I couldn't see how to even disable SPARSEMEM for my normal x86-64
build. But then I *only* tested
On Fri, Feb 15, 2013 at 12:44:26PM +0100, Ingo Molnar wrote:
>
> [ Greg: -stable was Cc:-ed for this potentially buggy commit. ]
>
> * Yinghai Lu wrote:
>
> > On Thu, Feb 14, 2013 at 7:08 AM, Ingo Molnar wrote:
> > > these three:
> > >
> > > 10d73e655cef mm: bootmem: fix
[ Greg: -stable was Cc:-ed for this potentially buggy commit. ]
* Yinghai Lu wrote:
> On Thu, Feb 14, 2013 at 7:08 AM, Ingo Molnar wrote:
> > these three:
> >
> > 10d73e655cef mm: bootmem: fix free_all_bootmem_core() with odd bitmap
> > alignment
> > c060f943d092 mm: use aligned zone start
[ Greg: -stable was Cc:-ed for this potentially buggy commit. ]
* Yinghai Lu ying...@kernel.org wrote:
On Thu, Feb 14, 2013 at 7:08 AM, Ingo Molnar mi...@kernel.org wrote:
these three:
10d73e655cef mm: bootmem: fix free_all_bootmem_core() with odd bitmap
alignment
c060f943d092 mm:
On Fri, Feb 15, 2013 at 12:44:26PM +0100, Ingo Molnar wrote:
[ Greg: -stable was Cc:-ed for this potentially buggy commit. ]
* Yinghai Lu ying...@kernel.org wrote:
On Thu, Feb 14, 2013 at 7:08 AM, Ingo Molnar mi...@kernel.org wrote:
these three:
10d73e655cef mm: bootmem: fix
26 matches
Mail list logo
