On Fri, Jan 11, 2008 at 07:12:33PM +1100, CaT wrote:
> I recently upgraded from an amd 64bit system to an intel one and changed my
> kernekl accordingly. Everything's great except this:
>
> root 6 0.0 0.0 0 0 ? D< 17:11 0:00 [migration/1]
> root 7 0.0 0.0 0 0 ? D< 17:11 0:00 [ksoftirqd/1]
> root 8 0.0 0.0 0 0 ? D< 17:11 0:00 [watchdog/1]
>
> I've tried various kernel configs and that stays the same, including a
> constant load of 3. My current kernel config and dmesg is attached
> (compressed as I think the ml limit is 40k).
>
> Not sure what other info to provide so if anything else would be
> helpful, please shout.
I'm just taking a closer look at things now that I've recovered from
spending a day in a nice, loud server room and things are popping up
that make me wonder if 2.6.22.15 is just too old for this motherboard.
> MPTABLE: OEM ID: OEM00000 MPTABLE: Product ID: PROD00000000 MPTABLE: APIC at:
> 0xFEE00000
> Processor #0 (Bootup-CPU)
> Processor #1
> I/O APIC #4 at 0xFEC00000.
> Setting APIC routing to flat
> Processors: 2
As it should be. Dual core.
> Booting processor 1/2 APIC 0x1
> Not responding.
> Inquiring remote APIC #1...
> ... APIC #1 ID: failed
> ... APIC #1 VERSION: failed
> ... APIC #1 SPIV: failed
> Brought up 1 CPUs
Ook? Shouldn't that be 2? Infact, /proc/cpuinfo confirms this. I only
have one core up.
> Initializing CPU#1
...
> Kernel panic - not syncing: smp_callin: CPU1 started up but did not get a
> callout!
Eek! This doesn't look so good.
So I now have a nice, brand new, spiffy motherboard and a dual core
cpu... with one core not in use, a weird panic relating to CPUs and
kernel processes hung in D state. Whee! :)
--
"To the extent that we overreact, we proffer the terrorists the
greatest tribute."
- High Court Judge Michael Kirby
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
