[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: A hint for my Core 2 Duo MP bug
On Fri, Sep 19, 2008 at 9:50 PM, Roy Marples <roy%marples.name@localhost> wrote:
> On Fri, 2008-09-19 at 21:06 +0200, Vincent wrote:
>> The problem itself is very simple. At boot, cpu0 starts correctly, cpu1
>> won't — I've got the message "cpu1 failed to become ready". The kernel
>> goes further for a while, then stops before it forks init (usually, it
>> hangs while scanning the ATAPI bus).
> Sounds exactly like my issue with -current on my Core2 Quad.
> My solution was to disable the PS2 ports OR boot with a PS2 keyboard
> connected - my default keyboard is USB.
Hmm... that reminds me of the problem I had with a MacBook
(port-i386/37305) in which the second core wouldn't start due to
timing problems associated with USB legacy emulation stuff (timing
calibration was botched due to some SMIs being generated by a "USB
legacy" feature). But that was with NetBSD 4.0...
In that case the problem was solved by disabling such feature.
Main Index |
Thread Index |