Odd networking "bug"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I've had a couple of machines crashing recently, without leaving much of a
trace as to why they are doing so. The first time either of the crashed I
got the following messages in the syslog:

kernel: BUG: soft lockup - CPU#0 stuck for 10s! [pluto:11024]
kernel:
kernel: Pid: 11024, comm: pluto
kernel: EIP: 0060:[<c060fede>] CPU: 0
kernel: EIP is at _spin_lock+0x5/0xf
kernel: EFLAGS: 00200286 Not tainted (2.6.18-128.1.1.el5 #1)
kernel: EAX: c6385dac EBX: c6385d80 ECX: c6385dac EDX: 00000100
kernel: ESI: 00000000 EDI: 00000000 EBP: c6385d80 DS: 007b ES: 007b
kernel: CR0: 8005003b CR2: b2b74fdc CR3: 32fcb000 CR4: 000006d0
kernel: [<c05ad8f8>] release_sock+0x59/0x91
kernel: [<c05ea810>] udp_sendmsg+0x44e/0x514
kernel: [<c05efd4c>] inet_sendmsg+0x35/0x3f
kernel: [<c05ab25c>] sock_sendmsg+0xce/0xe8

I'm not sure if this is connected to the other crashes as there have been
absolutely no indicative messages in the logs, but I do know that one of
the network interfaces stops responding altogether. I haven't managed to get
into the machines after the crash so I can't perform any more diagnosis
until it happens again.

Do these error messages ring any bells for anyone?

-- 
Regards,
Oliver Hookins
Anchor Systems
--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux