Messages in this thread | | | Date | Fri, 9 Apr 2010 12:43:57 +1000 | Subject | Re: Config NO_BOOTMEM breaks my amd64 box | From | Dave Airlie <> |
| |
On Thu, Apr 8, 2010 at 5:27 PM, Ingo Molnar <mingo@elte.hu> wrote: > > * Yinghai <yinghai.lu@oracle.com> wrote: > >> On 04/07/2010 11:32 PM, Ingo Molnar wrote: >> > >> > * Ingo Molnar <mingo@elte.hu> wrote: >> > >> >> * James Morris <jmorris@namei.org> 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |