NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/44224: -current double-fault at boot



For the record, -current from yesterday still not boot. I rebuild the
toolchain to be sure, but nothing much different. I cannot boot an
amd64 on the machine as the bootloader (an old grub), do not know how
to deal with 64bit ELF.

On Sun, Dec 12, 2010 at 11:07 PM, Arnaud Lacombe <lacombar%gmail.com@localhost> 
wrote:
> here is the (partial) screen output (with a PAE enabled kernel):
>
> mapped with 3 large  pages and 338 normal pages
> fault in user mode
> code c010caf9 eip 8 cs 246 eflags 10 cr2 23eba6dd ilevel 0
> trap double fault, code=0
> 0.1 (system) at 0x8: invalid address
>
> The kernel is MULTIBOOT'ed by grub.
>
>
> On Sun, Dec 12, 2010 at 6:00 PM, Arnaud Lacombe 
> <lacombar%gmail.com@localhost> wrote:
>> The following reply was made to PR kern/44224; it has been noted by GNATS.
>>
>> From: Arnaud Lacombe <lacombar%gmail.com@localhost>
>> To: gnats-bugs%netbsd.org@localhost
>> Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
>> netbsd-bugs%netbsd.org@localhost
>> Subject: Re: kern/44224: -current double-fault at boot
>> Date: Sun, 12 Dec 2010 17:58:55 -0500
>>
>>  Hi,
>>
>>  On Sun, Dec 12, 2010 at 5:15 PM, Martin Husemann 
>> <martin%duskware.de@localhost> wrote=
>>  :
>>  > The following reply was made to PR kern/44224; it has been noted by GNATS=
>>  .
>>  >
>>  > From: Martin Husemann <martin%duskware.de@localhost>
>>  > To: gnats-bugs%NetBSD.org@localhost
>>  > Cc:
>>  > Subject: Re: kern/44224: -current double-fault at boot
>>  > Date: Sun, 12 Dec 2010 23:10:40 +0100
>>  >
>>  > =A0On Sun, Dec 12, 2010 at 07:10:01PM +0000, lacombar%gmail.com@localhost 
>> wrote:
>>  > =A0> cpu0 at mainbus0 apid 0: Intel 686-class, 2154MHz, id 0x6fd
>>  >
>>  > =A0What kind of cpu is that exactly?
>>  Despite what the dmesg say, it should be the following CPU:
>>
>>  Intel Core 2 (Merom) (686-class), 1795.62 MHz, id 0x6fd
>>
>>  this would match the fact that `machdep.est.frequency.available' does
>>  not display any frequency above 1800MHz.
>>
>>  Full dmesg is here:
>>
>>  http://mail-index.netbsd.org/current-users/2010/04/17/msg013120.html
>>
>>  - Arnaud
>>
>>  ps: it would seem 5.99.25 misdetects the CPU, as 5.99.13 was detecting
>>  the right frequency.
>>
>>
>


Home | Main Index | Thread Index | Old Index