Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

PAE broken on Thinkpad

0 views
Skip to first unread message

john stultz

unread,
Oct 21, 2006, 7:20:08 PM10/21/06
to
Yea. So I know I probably shouldn't run a PAE kernel on my 1Gig laptop,
but in trying to do so I found it won't boot.

All I get on the screen is this (hand copied)
Uncompressing Linux... Ok, booting the kernel.


Int 14: CR2 c1000000 err 00000002 EIP c065d950 CS 00000060 flags 00010006
Stack: c08b3000 00038000 00001000 00000020 c068f5c0 ffffffc0 fffffc2e 00000001


>From gdb that EIP looks to be in __alloc_bootmem_core (string.h:372)

.config attached.

thanks
-john

laptop.config

Arjan van de Ven

unread,
Oct 21, 2006, 10:00:11 PM10/21/06
to
On Sat, 2006-10-21 at 16:18 -0700, john stultz wrote:
> Yea. So I know I probably shouldn't run a PAE kernel on my 1Gig laptop,
> but in trying to do so I found it won't boot.


which CPU do you have? Not all laptop processors support PAE at all...
(for example the pentiumM generations before NX was added)

check /proc/cpuinfo the flags line to see if "pae" is there


--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Andi Kleen

unread,
Oct 21, 2006, 10:10:08 PM10/21/06
to
john stultz <john...@us.ibm.com> writes:

> Yea. So I know I probably shouldn't run a PAE kernel on my 1Gig laptop,
> but in trying to do so I found it won't boot.

You don't say what version?


> Int 14: CR2 c1000000 err 00000002 EIP c065d950 CS 00000060 flags 00010006
> Stack: c08b3000 00038000 00001000 00000020 c068f5c0 ffffffc0 fffffc2e 00000001
>
>
> >From gdb that EIP looks to be in __alloc_bootmem_core (string.h:372)

string.h??

-Andi

Andi Kleen

unread,
Oct 21, 2006, 10:10:12 PM10/21/06
to
Arjan van de Ven <ar...@infradead.org> writes:

> On Sat, 2006-10-21 at 16:18 -0700, john stultz wrote:
> > Yea. So I know I probably shouldn't run a PAE kernel on my 1Gig laptop,
> > but in trying to do so I found it won't boot.
>
>
> which CPU do you have? Not all laptop processors support PAE at all...
> (for example the pentiumM generations before NX was added)

It shouldn't have crashed in bootmem then, just paniced early.

-Andi

john stultz

unread,
Oct 21, 2006, 10:40:06 PM10/21/06
to
On Sun, 2006-10-22 at 04:01 +0200, Andi Kleen wrote:
> john stultz <john...@us.ibm.com> writes:
>
> > Yea. So I know I probably shouldn't run a PAE kernel on my 1Gig laptop,
> > but in trying to do so I found it won't boot.
>
> You don't say what version?

Sorry, the current -git.

-john

Andi Kleen

unread,
Oct 21, 2006, 11:00:09 PM10/21/06
to
On Sunday 22 October 2006 04:30, john stultz wrote:
> On Sun, 2006-10-22 at 04:01 +0200, Andi Kleen wrote:
> > john stultz <john...@us.ibm.com> writes:
> >
> > > Yea. So I know I probably shouldn't run a PAE kernel on my 1Gig laptop,
> > > but in trying to do so I found it won't boot.
> >
> > You don't say what version?
>
> Sorry, the current -git.

Normally the early exception handler should print a backtrace, i wonder
why that didn't work.

Can you change the

static int current_ypos = 25

in arch/x86_64/kernel/early_printk.c to

static int current_ypos = 0

and see if that displays the backtrace?

-Andi

john stultz

unread,
Oct 22, 2006, 6:10:06 PM10/22/06
to
On Sun, 2006-10-22 at 04:50 +0200, Andi Kleen wrote:
> On Sunday 22 October 2006 04:30, john stultz wrote:
> > On Sun, 2006-10-22 at 04:01 +0200, Andi Kleen wrote:
> > > john stultz <john...@us.ibm.com> writes:
> > >
> > > > Yea. So I know I probably shouldn't run a PAE kernel on my 1Gig laptop,
> > > > but in trying to do so I found it won't boot.
> > >
> > > You don't say what version?
> >
> > Sorry, the current -git.
>
> Normally the early exception handler should print a backtrace, i wonder
> why that didn't work.
>
> Can you change the
>
> static int current_ypos = 25
>
> in arch/x86_64/kernel/early_printk.c to
>
> static int current_ypos = 0
>
> and see if that displays the backtrace?

Unfortunately not. :( I just get those two lines up at the top of the
screen.

thanks
-john

Andi Kleen

unread,
Oct 22, 2006, 6:30:14 PM10/22/06
to

>
> Unfortunately not. :( I just get those two lines up at the top of the
> screen.

Have to debug it the hard way then. Can you add lots of
early_printks to let's say setup_arch and then around the
following calls in start_kernel and see how far it gets?

-Andi

Andi Kleen

unread,
Oct 22, 2006, 6:40:10 PM10/22/06
to
On Monday 23 October 2006 00:19, Andi Kleen wrote:
>
> >
> > Unfortunately not. :( I just get those two lines up at the top of the
> > screen.
>
> Have to debug it the hard way then. Can you add lots of
> early_printks to let's say setup_arch and then around the
> following calls in start_kernel and see how far it gets?

Or alternatively if some earlier kernel worked bisect it please

0 new messages