Skip to contentSkip to conversation

2.6.0-test4-mm5 SMP got stuck when configuring the NIC

DISCUSSION Helge Hafting 2 participants 4 messages Sep 5, 2003 – Sep 11, 2003

lore
Share & tools
lore
#0 lore raw

test4-mm5 seems to work on UP, but got stuck on SMP when the initscripts ran pump.

It responded to sysrq+S, & sysrq+U,
so it seems block io was still working.
There was no fsck on the next boot into plain 2.6.0-test4.

sysrq+P showed:
Pid 38, comm: pump
EIP at __mod_timer+0x34/0x270
do_IRQ
common_interrupt
del_timer
del_timer_sync
schedule_timeout
process_timeout
dev_close
dev_change_flags
devinet_ioctl
inet_ioctl
sock_ioctl
syscall_call
auth_domain_drop

sysrq+T
showed pump as the R process, syslogd Z, and others S.

I'll try without the elv-insertion-fix thing later today.

Helge Hafting

#1 lore raw

Re: 2.6.0-test4-mm5 SMP (and mm6 and plain test5) got stuck during boot

2.6.0-test4-mm4, mm6 and plain 2.6.0-test5 are all useless on my dual celeron. The machine get stuck when initscripts tries to configure networking. I can break
out of that with ctrl+c, but then it gets
stuck on something else shortly thereafter,
so I can't get as far as logging in.

The machine runs debian testing, and is fine with
2.6.0-test4.

Helge Hafting

#2 lore raw

Re: 2.6.0-test4-mm5 SMP (and mm6 and plain test5) got stuck during boot

Quoted 7 lines · Helge Hafting

2.6.0-test4-mm4, mm6 and plain 2.6.0-test5 are all useless on my dual celeron. The machine get stuck when initscripts tries to configure networking. I can break
out of that with ctrl+c, but then it gets
stuck on something else shortly thereafter,
so I can't get as far as logging in.

Please try test5-mm1. If it still gets stuck then use sysrq-P and sysrq-T to work out where it is hanging.

#3 lore raw

Re: 2.6.0-test4-mm5 SMP (and mm6 and plain test5) got stuck during boot

On Wed, Sep 10, 2003 at 09:55:59AM -0700, Andrew Morton wrote:
[...]

Quoted 2 lines

Please try test5-mm1. If it still gets stuck then use sysrq-P and sysrq-T to work out where it is hanging.

test5-mm1 came up, I'm using it for writing this message. :-)

Helge Hafting