[lkml]   [2006]   [Sep]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 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?

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.

> 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]
> 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?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-09-25 02:43    [W:0.104 / U:7.200 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site