Hello list, This morning I noticed that my machine was frozen (would not respond to keyboard or mouse, so couldn't ctrl+alt+func_key to a terminal or anything, I couldn't ping it either). I reset it and started chugging along... or so I thought. This machine is my firewall. Everytime a client attempts to connect to eth1, the machine crashes. Prior to the most recent crash I switched to a console session so I could see messages coming to the screen and I saw something to the tune of:
BUG: soft lockup detected on cpu#0! ... dump trace 0x69/ox1af show_trace_log lvl +0x18/0x2... show_trace+0xf/0x11 dump_stack 0x15/ 0x12 softlockup_tick 0xad/0xc4 ... smp_apic_timer_interrupt 0x9f/0xbb apic_timer_interrupt 0x2a/0x30 _do_softirq_0x68/0xeb do_softirq ox4a/0xc3 =============== I can induce the crash at will by: 1. booting the firewall 2. booting the client that is connected to eth1 or (if the client is booted) 1. boot the firewall 2. disconnect the cable that is plugged into eth1 and plug it into eth2 (if the client is booted) 1. boot the firewall 2. change the ip parameters on the client and ping the firewall I'm running 2.6.19-r1. I've been using that kernel for probably 1 month or so. The most recent change I made to the machine was installing Shorewall and recompiling the kernel to add the ip masq stuff. The machine ran all weekend with no hitches. Last night my wife's laptop was connected to eth1 and she was surfing the net just fine, I disconnected her laptop and connected my laptop and I surfed the net just fine. I woke up this morning and noticed this trouble? Have any of yous guys seen anything like this before? Thanks, Shawn "Doing linear scans over an associative array is like trying to club someone to death with a loaded Uzi." Larry Wall
