mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jörn Nettingsmeier" <nettings@folkwang-hochschule.de>
To: linux-kernel@vger.kernel.org, netfilter@lists.samba.org
Cc: nettings@folkwang-hochschule.de
Subject: kernel lockup in 2.4.5-ac3 and 2.4.6-pre7 (netfilter ?)
Date: Mon, 16 Jul 2001 11:02:57 +0200	[thread overview]
Message-ID: <3B52ADC1.95012614@folkwang-hochschule.de> (raw)

hello everyone !

i have had reproducible lockups in 2.4.5-ac3.
the box is a cyrix@120 mhz with a via apollo chipset and two
ethercards.
it's used as a masquerading firewall/dsl router.

now when i have an ftp session from a machine on the private network
to the internet and it gets stuck or i ctrl-c out of it, this causes
the box to lock up hard. i was able to reproduce this a few times.
no syslog entries survive. alt-sysrq-sync seems to work, but
-killall and -umount don't, so after alt-sysrq-boot i have to go
through 20gigs of fsck.

i have upgraded to 2.4.7-pre6, and the problem has reappeared, this
time when closing a stuck ssh connection. same sysrq behaviour, no
logs.

when not forwarding ftp or ssh sessions, the box has had uptimes of
more than a week, so i think the problem may be netfilter related.
see below for my netfilter setting. (the same setting has run w/o
problems in earlier 2.4 kernels.)

i'd welcome hints to nail down the problem. if you want me to run
further tests or need more info, let me know.

yours,

jörn

ps: if possible, cc: me on followups, because i only read lkml
through the archive.


----

#iptables -L -v 
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source              
destination
67171   27M block      all  --  any    any     anywhere            
anywhere
 
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source              
destination
  285 16924 TCPMSS     tcp  --  any    any     anywhere            
anywhere           tcp flags:SYN,RST/SYN TCPMSS clamp to PMTU
 6690 3628K block      all  --  any    any     anywhere            
anywhere
 
Chain OUTPUT (policy ACCEPT 67143 packets, 47732223 bytes)
 pkts bytes target     prot opt in     out     source              
destination
 
Chain block (2 references)
 pkts bytes target     prot opt in     out     source              
destination
71441   30M ACCEPT     all  --  any    any     anywhere            
anywhere           state RELATED,ESTABLISHED
 1848  152K ACCEPT     all  --  !ppp0  any     anywhere            
anywhere           state NEW
    0     0 ACCEPT     tcp  --  any    any     anywhere            
anywhere           tcp dpt:ssh
    0     0 ACCEPT     tcp  --  any    any     anywhere            
anywhere           tcp dpt:http
   38  1792 ACCEPT     tcp  --  any    any     anywhere            
anywhere           tcp dpts:1024:65535
  534 31915 DROP       all  --  any    any     anywhere            
anywhere

-- 
Jörn Nettingsmeier     
home://Kurfürstenstr.49.45138.Essen.Germany      
phone://+49.201.491621
http://icem-www.folkwang-hochschule.de/~nettings/
http://www.linuxdj.com/audio/lad/

             reply	other threads:[~2001-07-16  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16  9:02 Jörn Nettingsmeier [this message]
     [not found] ` <20010716110522.A1985@hapablap.dyn.dhs.org>
2001-07-19 13:36   ` Jörn Nettingsmeier
     [not found] ` <3B534D06.5090405@earthlink.net>
     [not found]   ` <3B56E91F.12C1AB9B@folkwang-hochschule.de>
     [not found]     ` <3B56FE85.2080802@suche.org>
2001-07-19 16:32       ` Jörn Nettingsmeier
2001-07-19 20:43         ` Jörn Nettingsmeier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B52ADC1.95012614@folkwang-hochschule.de \
    --to=nettings@folkwang-hochschule.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfilter@lists.samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®