public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jeremy Fitzhardinge <jeremy@goop.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: Sun, 24 Sep 2006 22:34:27 -0700	[thread overview]
Message-ID: <20060924223427.6f42e77c.akpm@osdl.org> (raw)
In-Reply-To: <4517256E.10606@goop.org>

On Sun, 24 Sep 2006 17:40:14 -0700
Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> 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?
> >   
> 
> I'm not sure what's in Andi's tree.  He mentioned that he had trouble 
> merging a previous patch I had, but it wasn't a particularly big change.
> 
> Andi, where can I get your tree?
> 
> > Anyway, the PDA patches are causing my little old dual-pIII to reboot about
> > one second into the boot process.
> >   
> 
> Interesting.  Have there been any other complaints about -mm crashing?  
> There's nothing in here which is "new cpu"; it should work the same all 
> the way back to an i386.

It may be related to the .config, rather than the CPU type.

> > 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.
> >
> >
> >
> > Compat vDSO mapped to ffffe000.
> > Checking 'hlt' instruction... OK.
> > SMP alternatives: switching to UP code
> > CPU0: Intel Pentium III (Coppermine) stepping 03
> > SMP alternatives: switching to SMP code
> > Booting processor 1/1 eip 2000
> > Initializing CPU#1
> > general protection fault: 0080 [#1]
> > SMP 
> > last sysfs file: 
> > Modules linked in:
> > CPU:    1
> > EIP:    0060:[<c010ad63>]    Not tainted VLI
> > EFLAGS: 00010086   (2.6.18 #8) 
> > EIP is at cpu_init+0x153/0x2b0
> >   
> What line does this EIP correspond to?
> 

(gdb) l *0xc010ad63
0xc010ad63 is in cpu_init (arch/i386/kernel/cpu/common.c:748).
743                     BUG();
744             enter_lazy_tlb(&init_mm, current);
745     
746             load_esp0(t, thread);
747             set_tss_desc(cpu,t);
748             load_TR_desc();
749             load_LDT(&init_mm.context);
750     
751     #ifdef CONFIG_DOUBLEFAULT
752             /* Set up doublefault TSS pointer in the GDT */



  parent reply	other threads:[~2006-09-25  5:34 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 [this message]
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

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=20060924223427.6f42e77c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=76306.1226@compuserve.com \
    --cc=ak@muc.de \
    --cc=jbeulich@novell.com \
    --cc=jeremy@goop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox