[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <45182585.6010004@goop.org>
Date: Mon, 25 Sep 2006 11:52:53 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Andrew Morton <akpm@...l.org>
CC: Andi Kleen <ak@....de>, Chuck Ebbert <76306.1226@...puserve.com>,
Zachary Amsden <zach@...are.com>,
Jan Beulich <jbeulich@...ell.com>, linux-kernel@...r.kernel.org
Subject: Re: i386 pda patches
Andrew Morton wrote:
> I am unable to correlate what's in Andi's tree with the PDA-related emails
> on this list. Why is this?
>
> Anyway, the PDA patches are causing my little old dual-pIII to reboot about
> one second into the boot process.
>
> Bisection says:
>
> x86_64-mm-i386-pda-asm-offsets.patch
> x86_64-mm-i386-pda-basics.patch OK
> x86_64-mm-i386-pda-init-pda.patch oops
> x86_64-mm-i386-pda-use-gs.patch reboot
> x86_64-mm-i386-pda-user-abi.patch BAD
> x86_64-mm-i386-pda-vm86.patch
> x86_64-mm-i386-pda-smp-processorid.patch
> x86_64-mm-i386-pda-current.patch
>
>
> So x86_64-mm-i386-pda-init-pda.patch causes the below oops and
> x86_64-mm-i386-pda-use-gs.patch causes the instareboot.
>
Hm, I can't repro this. I just rolled a new set of i386-pda patches
against 2.6.18-mm1, and tried your .config, but it boots fine for me. I
may have fixed a problem in the process of generating new patches, but
nothing stands out. The oops you're getting is pretty bad; it doesn't
seem like it should be .config-dependent or in any way intermittent (ie,
everyone should be seeing this if anyone does).
Anyway, could you try again with the new i386-pda patches? I'll post
them shortly.
Thanks,
J
-
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