Bug 134731

Summary: machine locks up hard (ipsec related)
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Michael Matz <matz>
Component: KernelAssignee: Olaf Kirch <okir>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: mt
Version: RC 4   
Target Milestone: ---   
Hardware: x86   
OS: Linux   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: conntrack copy
output of netstat -tuna

Description Michael Matz 2005-11-21 18:42:39 UTC 
I've recently updated my home machine to 10.0 where I use openswan to connect
to the beta RAS server.  This all was working fine under 8.2, which I had
before.  Now I get random lockups of that machine.  Unfortunately I can't
provide much more information than just this.  There is nothing in the logs
no possibility to do any sysrq-t (it locks up X, and hence no keyboard
entry is possible anymore).  I don't have a serial console :-(  The machine
still pings, but for instance login via ssh is not possible anymore.

So I have a hard time finding out anything at all.  It sometimes happened
while I was using the machine (browsing web, entering commands, hovering
with mouse), and sometimes while I was away and the machine just idled
around.  I believe I had ipsec active each time.  I mention ipsec because
Christoph Thiel has a similar problem and said that he can sometimes avoid
the lockup by restarting RAS every ten minutes.  Hence I hope that ipsec
somehow is related.  I already found bug 133513, but this seems to be a
problem with the ipw2200 driver, which I don't use.  I have an 8139-based
network card.

Any advice how to get more info?  Perhaps watchdog activated sysrq-t or so?
Comment 1 Olaf Kirch 2005-11-22 08:27:29 UTC 
We have two open bugs for ipsec crashes - bug 117749 and bug 115200
There's little progress on either of them... please try to work on
the console to see if there's any output there (klogconsole -l8 -r0)
Please try nmi_watchdog as well.

If nothing helps, not even nmi_watchdog, please try using a different
network card to see if it's driver/hw related.
Comment 2 Dirk Mueller 2005-11-26 01:49:52 UTC 

*** This bug has been marked as a duplicate of 117749 ***
Comment 3 Michael Matz 2008-02-07 18:25:09 UTC 
Created attachment 193703 [details]
conntrack copy
Comment 4 Michael Matz 2008-02-07 18:25:44 UTC 
Created attachment 193704 [details]
output of netstat -tuna
Comment 5 Michael Matz 2008-02-07 18:27:03 UTC 
Oops, sorry, attached to the wrong bug :-(