2010-04-01 12:52:40

by Ingo Molnar

[permalink] [raw]
Subject: Re: Config NO_BOOTMEM breaks my amd64 box


* James Morris <[email protected]> wrote:

> On Wed, 31 Mar 2010, H. Peter Anvin wrote:
>
> > On 03/31/2010 04:43 PM, James Morris wrote:
> > >>
> > >> Upgraded how? The problem no longer happens?
> > >
> > > Upgraded to the latest rawhide userland -- I have not since tested with
> > > bootmem off. I'll try and do so again when I get a chance.
> > >
> >
> > That would be great. The sooner the better, obviously.
>
> I'm not seeing any problems now, with current Linus and rawhide. I'll leave
> bootmem off and see if anything comes up again.

(a current bootlog would still be nice)

Dave, can you reproduce any of these problems with Linus's latest?

Ingo


2010-04-08 06:32:56

by Ingo Molnar

[permalink] [raw]
Subject: Re: Config NO_BOOTMEM breaks my amd64 box


* Ingo Molnar <[email protected]> wrote:

> * James Morris <[email protected]> wrote:
>
> > On Wed, 31 Mar 2010, H. Peter Anvin wrote:
> >
> > > On 03/31/2010 04:43 PM, James Morris wrote:
> > > >>
> > > >> Upgraded how? The problem no longer happens?
> > > >
> > > > Upgraded to the latest rawhide userland -- I have not since tested with
> > > > bootmem off. I'll try and do so again when I get a chance.
> > > >
> > >
> > > That would be great. The sooner the better, obviously.
> >
> > I'm not seeing any problems now, with current Linus and rawhide. I'll leave
> > bootmem off and see if anything comes up again.
>
> (a current bootlog would still be nice)
>
> Dave, can you reproduce any of these problems with Linus's latest?

ping? Can you or Dave reproduce the bug with -rc3 or later kernels? (If not
then it probably means that the bug you triggered was already fixed at the
time you reported it, as hpa suspected.)

Thanks,

Ingo

2010-04-08 07:04:27

by Yinghai Lu

[permalink] [raw]
Subject: Re: Config NO_BOOTMEM breaks my amd64 box

On 04/07/2010 11:32 PM, Ingo Molnar wrote:
>
> * Ingo Molnar <[email protected]> wrote:
>
>> * James Morris <[email protected]> wrote:
>>
>>> On Wed, 31 Mar 2010, H. Peter Anvin wrote:
>>>
>>>> On 03/31/2010 04:43 PM, James Morris wrote:
>>>>>>
>>>>>> Upgraded how? The problem no longer happens?
>>>>>
>>>>> Upgraded to the latest rawhide userland -- I have not since tested with
>>>>> bootmem off. I'll try and do so again when I get a chance.
>>>>>
>>>>
>>>> That would be great. The sooner the better, obviously.
>>>
>>> I'm not seeing any problems now, with current Linus and rawhide. I'll leave
>>> bootmem off and see if anything comes up again.
>>
>> (a current bootlog would still be nice)
>>
>> Dave, can you reproduce any of these problems with Linus's latest?
>
> ping? Can you or Dave reproduce the bug with -rc3 or later kernels? (If not
> then it probably means that the bug you triggered was already fixed at the
> time you reported it, as hpa suspected.)

James already reported -rc3 fix the problem for him.

Dave implied -rc3 fixed problem for him

Thanks

Yinghai

2010-04-08 07:27:50

by Ingo Molnar

[permalink] [raw]
Subject: Re: Config NO_BOOTMEM breaks my amd64 box


* Yinghai <[email protected]> wrote:

> On 04/07/2010 11:32 PM, Ingo Molnar wrote:
> >
> > * Ingo Molnar <[email protected]> wrote:
> >
> >> * James Morris <[email protected]> wrote:
> >>
> >>> On Wed, 31 Mar 2010, H. Peter Anvin wrote:
> >>>
> >>>> On 03/31/2010 04:43 PM, James Morris wrote:
> >>>>>>
> >>>>>> Upgraded how? The problem no longer happens?
> >>>>>
> >>>>> Upgraded to the latest rawhide userland -- I have not since tested with
> >>>>> bootmem off. I'll try and do so again when I get a chance.
> >>>>>
> >>>>
> >>>> That would be great. The sooner the better, obviously.
> >>>
> >>> I'm not seeing any problems now, with current Linus and rawhide. I'll leave
> >>> bootmem off and see if anything comes up again.
> >>
> >> (a current bootlog would still be nice)
> >>
> >> Dave, can you reproduce any of these problems with Linus's latest?
> >
> > ping? Can you or Dave reproduce the bug with -rc3 or later kernels? (If not
> > then it probably means that the bug you triggered was already fixed at the
> > time you reported it, as hpa suspected.)
>
> James already reported -rc3 fix the problem for him.
>
> Dave implied -rc3 fixed problem for him

Hm, i'm confused, does this mean that it was all fixed upstream already when
Dave and James sent their complaints?

Would be nice to have a confirmation from Dave for that (beyond 'implying'
it), to not keep this thread open-ended.

Thanks,

Ingo

2010-04-08 08:06:37

by James Morris

[permalink] [raw]
Subject: Re: Config NO_BOOTMEM breaks my amd64 box

On Thu, 8 Apr 2010, Ingo Molnar wrote:

> ping? Can you or Dave reproduce the bug with -rc3 or later kernels? (If not
> then it probably means that the bug you triggered was already fixed at the
> time you reported it, as hpa suspected.)

I haven't seen it since.


- James
--
James Morris
<[email protected]>

2010-04-08 08:22:42

by Ingo Molnar

[permalink] [raw]
Subject: Re: Config NO_BOOTMEM breaks my amd64 box


* James Morris <[email protected]> wrote:

> On Thu, 8 Apr 2010, Ingo Molnar wrote:
>
> > ping? Can you or Dave reproduce the bug with -rc3 or later kernels? (If not
> > then it probably means that the bug you triggered was already fixed at the
> > time you reported it, as hpa suspected.)
>
> I haven't seen it since.

Great, thanks!

Ingo

2010-04-09 02:44:04

by Dave Airlie

[permalink] [raw]
Subject: Re: Config NO_BOOTMEM breaks my amd64 box

On Thu, Apr 8, 2010 at 5:27 PM, Ingo Molnar <[email protected]> wrote:
>
> * Yinghai <[email protected]> wrote:
>
>> On 04/07/2010 11:32 PM, Ingo Molnar wrote:
>> >
>> > * Ingo Molnar <[email protected]> wrote:
>> >
>> >> * James Morris <[email protected]> wrote:
>> >>
>> >>> On Wed, 31 Mar 2010, H. Peter Anvin wrote:
>> >>>
>> >>>> On 03/31/2010 04:43 PM, James Morris wrote:
>> >>>>>>
>> >>>>>> Upgraded how? ?The problem no longer happens?
>> >>>>>
>> >>>>> Upgraded to the latest rawhide userland -- I have not since tested with
>> >>>>> bootmem off. ?I'll try and do so again when I get a chance.
>> >>>>>
>> >>>>
>> >>>> That would be great. ?The sooner the better, obviously.
>> >>>
>> >>> I'm not seeing any problems now, with current Linus and rawhide. ?I'll leave
>> >>> bootmem off and see if anything comes up again.
>> >>
>> >> (a current bootlog would still be nice)
>> >>
>> >> Dave, can you reproduce any of these problems with Linus's latest?
>> >
>> > ping? Can you or Dave reproduce the bug with -rc3 or later kernels? (If not
>> > then it probably means that the bug you triggered was already fixed at the
>> > time you reported it, as hpa suspected.)
>>
>> James already reported -rc3 fix the problem for him.
>>
>> Dave implied -rc3 fixed problem for him
>
> Hm, i'm confused, does this mean that it was all fixed upstream already when
> Dave and James sent their complaints?

When I reported it, it was only at rc2 stage so not fixed upstream at all.

>
> Would be nice to have a confirmation from Dave for that (beyond 'implying'
> it), to not keep this thread open-ended.

Okay I built a linus head and it booted on the previously broken machine.
with CONFIG_NO_BOOTMEM=y

Dave.