[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.61.0609211602130.30511@chaos.analogic.com>
Date: Thu, 21 Sep 2006 16:05:41 -0400
From: "linux-os \(Dick Johnson\)" <linux-os@...logic.com>
To: "Andrew Morton" <akpm@...l.org>
Cc: "Bernhard Rosenkraenzer" <bero@...linux.org>,
"Linux kernel" <linux-kernel@...r.kernel.org>,
"Chuck Ebbert" <76306.1226@...puserve.com>,
"Andi Kleen" <ak@....de>
Subject: Re: "Int 6: CR2" on bootup w/ 2.6.18-rc7-mm1
On Thu, 21 Sep 2006, Andrew Morton wrote:
> On Thu, 21 Sep 2006 14:12:08 +0200
> Bernhard Rosenkraenzer <bero@...linux.org> wrote:
>
>> This happens when trying to boot 2.6.18-rc7-mm1 on a truly ancient
>> (Pentium 1)
>> box:
>>
>> Uncompressing Linux... Ok, booting the kernel.
>>
>> Int 6: CR2 00000000 err 00000000 EIP c0381719 CS 00000060 flags 00010046
>> Stack: 00000000 c036f4d1 00000000 c0100199 000001b8 0505c600 00c036cc
> 001f0fc3
>>
>> (No further details even with initcall_debug loglevel=7).
>> c0381719 appears to be in ACPI code -- but the Int 6 error happens even with
>> acpi=off.
>
> Well Chuck's new early-fault handler has gone and handled an early fault.
>
> I assume that machine runs 2.6.18 OK with the same .config?
> -
Interrupt 6 is an invalid opcode interrupt. The caller might check
the kind of CPU for which the kernel was compiled. You can't boot
a '486 with '686 opcodes. "Truly ancient" probably explains it all.
Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.66 BogoMips).
New book: http://www.AbominableFirebug.com/
_
..
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@...logic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
-
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