Skip to contentSkip to conversation

2.6.22.15: kernel processes stuck in D state

DISCUSSION CaT 2 participants 5 messages Jan 11, 2008 – Jan 14, 2008

lore
Share & tools
lore

CaT

author
#0 lore raw

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.

Signature · 3 lines
    "To the extent that we overreact, we proffer the terrorists the
    greatest tribute."
    	- High Court Judge Michael Kirby
#1 lore raw
Quoted 1 line · CaT

Not sure what other info to provide

Is the bug present in 2.6.24-rc7?

Signature · 3 lines
Stefan Richter
-=====-==--- ---= -=-==
http://arcgraph.de/sr/
author
#2 lore raw
Quoted 4 lines · Stefan Richter
Quoted 1 line · CaT

Not sure what other info to provide

Is the bug present in 2.6.24-rc7?

Can't rightly say. I didn't try it before because 2.6.23 fails to compile under debian sarge. 2.6.24-rc7 did compile but it has failed to come back up. Don't know why as the box is remote (though it wasn't in use again yet due to the afore mentioned problems so this is merely an annoyance). I'll find out more on Monday.

Signature · 3 lines
    "To the extent that we overreact, we proffer the terrorists the
    greatest tribute."
    	- High Court Judge Michael Kirby
author
#3 lore raw
Quoted 11 lines · CaT
Quoted 4 lines · Stefan Richter
Quoted 1 line · CaT

Not sure what other info to provide

Is the bug present in 2.6.24-rc7?

Can't rightly say. I didn't try it before because 2.6.23 fails to compile under debian sarge. 2.6.24-rc7 did compile but it has failed to come back up. Don't know why as the box is remote (though it wasn't in use again yet due to the afore mentioned problems so this is merely an annoyance). I'll find out more on Monday.

Ok. Not sure why it didn't boot the first time (black screen) but it booted the second time. This time both CPUs got initialised and are in use, no kernel oops during init and no kernel processes stuck in D state. Should've tried .24 earlier but .23 failed to compile under sarge due to a buggy binutils so I figured .24 would too.

Signature · 3 lines
    "To the extent that we overreact, we proffer the terrorists the
    greatest tribute."
    	- High Court Judge Michael Kirby
author
#4 lore raw
In reply to CaT
Quoted 7 lines · CaT

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]
Quoted 6 lines

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.

Quoted 6 lines

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.

Quoted 7 lines

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.

Quoted 1 line

Initializing CPU#1

...

Quoted 1 line
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! :)

Signature · 3 lines
    "To the extent that we overreact, we proffer the terrorists the
    greatest tribute."
    	- High Court Judge Michael Kirby