Re: Yet another SMB oddity (cpu1: failed to become ready)

To: Vincent <10.50%free.fr@localhost>
Subject: Re: Yet another SMB oddity (cpu1: failed to become ready)
From: Andrew Doran <ad%netbsd.org@localhost>
Date: Sun, 17 Feb 2008 22:53:07 +0000

On Sun, Feb 17, 2008 at 09:14:46PM +0100, Vincent wrote:

> I am still fighting to get the Core 2 duo of my DELL Inspiron to work 
> correctly. With today current sources, apparently I get no supervisor 
> page fault anymore, but I can't start the second core:

...

> cpu1 at mainbus0 apid 1: (application processor)
> cpu1: failed to become ready

How long does it wait between these two messages?

Thanks,
Andrew

Follow-Ups:
- Re: Yet another SMB oddity (cpu1: failed to become ready)
  - From: Vincent
- Re: Yet another SMB oddity (cpu1: failed to become ready)
  - From: Vincent

References:
- Yet another SMB oddity (cpu1: failed to become ready)
  - From: Vincent

Prev by Date: Atheros AR5212 suspension breaks WPA
Next by Date: Re: veriexec
Previous by Thread: Yet another SMB oddity (cpu1: failed to become ready)
Next by Thread: Re: Yet another SMB oddity (cpu1: failed to become ready)
Indexes:

Home | Main Index | Thread Index | Old Index