lockup when doing networking stuff - again

Jonas Jochum (jonas@jonas-jochum.de)
Tue, 9 Nov 1999 15:55:52 +0100 (MET)

Hi!
A day or two ago I already reported a lockup after my computer dialed up
on the Internet / disconnected from the Internet.
Jens Axboe told me that noone would care about the bug report if the cpu
is overclocked. So after that mail I clocked it down to the original 350
Mhz. Proof:
root@mahatma:~ # cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 5
model : 8
model name : AMD-K6(tm) 3D processor
stepping : 12
cpu MHz : 350.807430
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mmx 3dnow
bogomips : 699.60

Now that lockup happened again - in fact, 2.3.26 (I decided to
upgrade from 2.3.24 to see if the lockups don't occur any more) was
running at that time. I'm back to 2.2.10 now to write this email. The 2.2
kernels all boot fine on my pc, only the 2.3 series screws up when using
ISDN (that's my suspicion (sp?)
I'm just trying out a couple of other things, disabling/enabling power
management, disabling/enabling the 3dfx framebuffer etc.
But it appears to be ISDN, as said before, since the last log entries were
all related to ISDN.

--- the last log entries -------------->

Nov 9 14:13:10 mahatma kernel: ippp0: dialing 1 0191011...
Nov 9 14:13:11 mahatma kernel: isdn_net: ippp0 connected
Nov 9 14:13:11 mahatma kernel: isdn_net: chargetime of ippp0 now 222671
Nov 9 14:14:36 mahatma kernel: isdn_net: local hangup ippp0
Nov 9 14:14:36 mahatma kernel: ippp0: Chargesum is 0
Nov 9 14:14:36 mahatma kernel: ippp, open, slot: 0, minor: 0, state: 0000
Nov 9 14:14:36 mahatma kernel: ippp_ccp: allocating reset data structure
Nov 9 14:15:10 mahatma kernel: ippp0: dialing 1 0191011...
Nov 9 14:15:11 mahatma kernel: isdn_net: ippp0 connected
Nov 9 14:15:11 mahatma kernel: isdn_net: chargetime of ippp0 now 234653
Nov 9 14:16:36 mahatma kernel: isdn_net: local hangup ippp0
Nov 9 14:16:36 mahatma kernel: ippp0: Chargesum is 0
Nov 9 14:16:36 mahatma kernel: ippp, open, slot: 1, minor: 0, state: 0000
Nov 9 14:16:36 mahatma kernel: ippp_ccp: allocating reset data structure
Nov 9 14:17:10 mahatma kernel: ippp0: dialing 1 0191011...
Nov 9 14:17:11 mahatma kernel: isdn_net: ippp0 connected
Nov 9 14:17:11 mahatma kernel: isdn_net: chargetime of ippp0 now 246663
Nov 9 14:18:35 mahatma kernel: isdn_net: local hangup ippp0
Nov 9 14:18:35 mahatma kernel: ippp0: Chargesum is 0
Nov 9 14:18:35 mahatma kernel: ippp, open, slot: 0, minor: 0, state: 0000
Nov 9 14:18:35 mahatma kernel: ippp_ccp: allocating reset data structure

[LOCKUP - pc rebooted itself]

Nov 9 14:27:00 mahatma kernel: klogd 1.3-3, log source = /proc/kmsg
started.
[some stuff snipped]
Nov 9 14:27:00 mahatma kernel: HiSax: DSS1 Rev. 2.19
Nov 9 14:27:00 mahatma kernel: HiSax: 2 channels added
Nov 9 14:27:00 mahatma kernel: HiSax: MAX_WAITING_CALLS added
Nov 9 14:27:00 mahatma kernel: HiSax: debugging flags card 1 set to 4
Nov 9 14:27:00 mahatma kernel: ippp, open, slot: 0, minor: 0, state: 0000
Nov 9 14:27:00 mahatma kernel: ippp_ccp: allocating reset data structure
Nov 9 14:27:00 mahatma kernel: ip_conntrack.o v0.1.12
Nov 9 14:27:00 mahatma kernel: nf_register_hook: pf=2 hook=0.
Nov 9 14:27:00 mahatma kernel: nf_register_hook: pf=2 hook=3.
Nov 9 14:27:00 mahatma kernel: ip_conntrack_ftp.o v0.1.12
Nov 9 14:27:00 mahatma kernel: nf_register_hook: pf=2 hook=0.
Nov 9 14:27:00 mahatma kernel: nf_register_hook: pf=2 hook=3.
Nov 9 14:27:00 mahatma kernel: nf_register_hook: pf=2 hook=0.
Nov 9 14:27:00 mahatma kernel: nf_register_hook: pf=2 hook=4.
Nov 9 14:27:00 mahatma kernel: nf_register_hook: pf=2 hook=3.
Nov 9 14:27:00 mahatma kernel: ip_nat_map_masquerade v0.1.12
Nov 9 14:27:00 mahatma kernel: ip_nat_map_redirect v0.1.12
Nov 9 14:27:00 mahatma kernel: ip_nat_map_static v0.1.12
Nov 9 14:27:00 mahatma kernel: nf_register_hook: pf=2 hook=1.
Nov 9 14:27:00 mahatma kernel: nf_register_hook: pf=2 hook=2.
Nov 9 14:27:00 mahatma kernel: nf_register_hook: pf=2 hook=3.
Nov 9 14:27:00 mahatma kernel: netfilter module v0.1.12: may you live in
interesting times
Nov 9 14:27:01 mahatma kernel: ippp0: dialing 1 0191011...
Nov 9 14:35:27 mahatma kernel: klogd 1.3-3, log source = /proc/kmsg
started.

[between 14:27 and 14:35 it locked up and rebooted itself again]

[some stuff snipped]
Nov 9 14:35:27 mahatma kernel: HiSax: Elsa driver Rev. 2.17
Nov 9 14:35:27 mahatma kernel: Elsa: QS 1000 PCI defined at 0xb000/0xb400
IRQ 9
Nov 9 14:35:27 mahatma kernel: Elsa: IPAC version 1
Nov 9 14:35:27 mahatma kernel: Elsa PCI: IRQ 9 count 0
Nov 9 14:35:27 mahatma kernel: Elsa PCI: IRQ 9 count 5
Nov 9 14:35:27 mahatma kernel: HiSax: DSS1 Rev. 2.18
Nov 9 14:35:27 mahatma kernel: HiSax: 2 channels added
Nov 9 14:35:27 mahatma kernel: HiSax: MAX_WAITING_CALLS added
Nov 9 14:35:27 mahatma kernel: HiSax: debugging flags card 1 set to 4
Nov 9 14:35:27 mahatma kernel: ippp, open, slot: 0, minor: 0, state: 0000
Nov 9 14:35:27 mahatma kernel: ippp_ccp: allocating reset data structure
Nov 9 14:35:28 mahatma kernel: ippp0: dialing 1 0191011...
Nov 9 14:35:29 mahatma kernel: isdn_net: ippp0 connected
Nov 9 14:35:29 mahatma kernel: isdn_net: chargetime of ippp0 now 43146
Nov 9 14:37:31 mahatma kernel: isdn_net: local hangup ippp0
Nov 9 14:37:31 mahatma kernel: ippp0: Chargesum is 0
Nov 9 14:37:31 mahatma kernel: ippp, open, slot: 1, minor: 0, state: 0000
Nov 9 14:37:31 mahatma kernel: ippp_ccp: allocating reset data structure
Nov 9 14:39:36 mahatma kernel: ippp0: dialing 1 0191011...
Nov 9 14:39:38 mahatma kernel: isdn_net: ippp0 connected
Nov 9 14:39:38 mahatma kernel: isdn_net: chargetime of ippp0 now 68003
Nov 9 14:43:04 mahatma kernel: Kernel logging (proc) stopped.
Nov 9 14:43:04 mahatma kernel: Kernel log daemon terminating.

[LOCKUP - the pc rebooted itself again]

Nov 9 15:27:23 mahatma kernel: klogd 1.3-3, log source = /proc/kmsg
started.

<----------------------------------------

these are all the log entries I have, no oops or anything like that.
btw, some files were corrupted (e.g. /var/log/messages:

Nov 9 14:43:04 mahatma named[176]: USAGE 942154984 942154528
CPU=0.01u/0.01s CH
Nov 9 14:43:04 mahatma named[176]: NSTATS 942154984
942154528
Nov 9 14:43:04 mahatma named[176]: XSTATS 942154984 942154528 RR=1 RNXD=0
RFwdR
Nov 9 14:43:04 mahatma kernel: Kernel logging (proc) stopped.
Nov 9 14:43:04 mahatma kernel: Kernel log daemon terminating.
Nov 9 14:43:05 mahatma exiting on signal 15
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
Oct 23 13:40:58 mahatma kernel: nf_iterate: NF_STOLEN for 00000000.
Oct 23 13:40:58 mahatma kernel: nf_iterate: NF_STOLEN for 00000000.
Oct 23 13:40:58 mahatma kernel: nf_iterate: NF_STOLEN for c907d1a0.

but I guess, this only occured because of the lockup.
(btw, what are the NF_STOLEN messages? To me they don't seem to be
critical, so I switched them off...)

On request, I'll forward my old bug report to the list again.

Reg.,
Jonas Jochum

P.S.: I hope this was an at least somewhat usable bug report this time :)

--
http://www.jonas-jochum.de      | email@jonas-jochum.de


I'm signature virus '99. Copy me into your ~/.signature to help me spread.




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/