[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110413064609.GA18777@elte.hu>
Date: Wed, 13 Apr 2011 08:46:09 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Joerg Roedel <joro@...tes.org>, Yinghai Lu <yinghai@...nel.org>
Cc: Alex Deucher <alexdeucher@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
dri-devel@...ts.freedesktop.org, "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>, Tejun Heo <tj@...nel.org>
Subject: Re: Linux 2.6.39-rc3
* Joerg Roedel <joro@...tes.org> wrote:
> > > The problem does not happen with 2.6.38. I try to bisect this further
> > > down to a commit. Alex, please let me know if you need any further
> > > information.
> >
> > If you can bisect it, that would be great. Thanks,
>
> Bisecting actually gave a very weird result. It points to
>
> d2137d5af4259f50c19addb8246a186c9ffac325
>
> which is a merge-commit in the x86 tree. Even more weird is that this
> notebook is the only machine with these symptoms, all my other boxes are
> fine.
>
> During the bisect I tested commits from Yinghai which were good. It seems
> like the problem appeared with the merge.
There's a similar looking bug being debugged here:
https://bugzilla.kernel.org/show_bug.cgi?id=33012
Could you please send the before/after bootlog (in particular all memory init
messages included) and your .config?
before: f005fe12b90c: x86-64: Move out cleanup higmap [_brk_end, _end) out of init_memory_mapping()
after: d2137d5af425: Merge branch 'linus' into x86/bootmem
I've Cc:-ed more people who might have an idea about it.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists