From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Andi Kleen <ak@muc.de>, Chuck Ebbert <76306.1226@compuserve.com>,
Zachary Amsden <zach@vmware.com>,
Jan Beulich <jbeulich@novell.com>,
linux-kernel@vger.kernel.org
Subject: Re: i386 pda patches
Date: Mon, 25 Sep 2006 11:52:53 -0700 [thread overview]
Message-ID: <45182585.6010004@goop.org> (raw)
In-Reply-To: <20060924013521.13d574b1.akpm@osdl.org>
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
prev parent reply other threads:[~2006-09-25 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 8:35 i386 pda patches Andrew Morton
2006-09-25 0:40 ` Jeremy Fitzhardinge
2006-09-25 2:37 ` Randy Dunlap
2006-09-25 5:34 ` Andrew Morton
2006-09-25 5:37 ` QMC driver for MPC8272 Tang
2006-09-25 5:38 ` i386 pda patches Jeremy Fitzhardinge
2006-09-25 6:05 ` Andrew Morton
2006-09-25 6:29 ` Jeremy Fitzhardinge
2006-09-25 6:40 ` Andrew Morton
2006-09-25 18:52 ` Jeremy Fitzhardinge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45182585.6010004@goop.org \
--to=jeremy@goop.org \
--cc=76306.1226@compuserve.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zach@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.