On Wed, 04 Oct 2006 11:41:59 -0500 Steve Fox <[EMAIL PROTECTED]> wrote:
> On Wed, 2006-10-04 at 08:45 -0700, Andrew Morton wrote: > > On Wed, 04 Oct 2006 08:42:28 -0500 > > Steve Fox <[EMAIL PROTECTED]> wrote: > > > Sorry for the delay. I was finally able to perform a bisect on this. It > > > turns out the patch that causes this is > > > x86_64-mm-re-positioning-the-bss-segment.patch, which seems like a > > > strange candidate, but sure enough I can boot to login: right up until > > > that patch is applied. > > > > hm, that patch was merged into mainline September 29. Does mainline work? > > -git21 also fails with this same error. > OK, thanks. And we know that x86_64-mm-re-positioning-the-bss-segment.patch triggered this failure. And that patch is non-buggy, and the xfrm code is probably non-buggy. So we don't know squat, and we're going to need to debug this crash. Well. There is one trick we could use: apply x86_64-mm-re-positioning-the-bss-segment.patch to 2.6.18 base and see if it crashes. If it doesn't, then we can theorise that the bug is some buggy post 2.6.18 patch which is being exposed by x86_64-mm-re-positioning-the-bss-segment.patch. A technique I've used before for identifying the buggy patch is to do a git-bisect, but apply x86_64-mm-re-positioning-the-bss-segment.patch by hand at each bisection step. It's pretty straightforward as long as the patch roughly applies at each step. Or we could debug it. Can you send the .config? Let's see if it happens with my toolchain+machine first. Thanks. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
