Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Feb 2000 16:29:32 +0100 (CET)
From:      Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>
To:        freebsd-isdn@freebsd.org
Subject:   doctor, it hurts - anamesis
Message-ID:  <200002211529.QAA08839@gil.physik.rwth-aachen.de>

next in thread | raw e-mail | index | archive | help
(FreeBSD 3.4R, i4b 0.83)

Hellmuth - Dr. i4b - ;-) I'm sending you this syslog
from a couple of minutes ago when my isdn connection
went down and only a reboot of the system could
revive it.

I have solved the 'Putzfrau' syndrome by a cable strap meanwhile so
it an unplugged cable cannot be the cause.

I only can say that the situation has worsened since I'm using
i4bisppp instead of hdlc/raw IP and fixed IP addresses before.

Actually I've never seen this kind of problems before using i4bispp.

-- 
Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de

Feb 21 08:39:30 isdn-gtwy squid[266]: Starting Squid Cache version 1.1.10 for i386-unknown-freebsd3.0... 
Feb 21 08:39:31 isdn-gtwy sshd[272]: log: RSA key generation complete.
Feb 21 08:39:33 isdn-gtwy /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3
Feb 21 08:39:33 isdn-gtwy /kernel: i4b: unit 0, assigned TEI = 101 = 0x65
Feb 21 08:39:36 isdn-gtwy squid[266]: Unlinkd pipe opened on FD 13 
Feb 21 08:39:37 isdn-gtwy squid[266]: Ready to serve requests. 
Feb 21 08:39:41 isdn-gtwy login: login on ttyv0 as kuku
Feb 21 16:04:55 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:04:57 isdn-gtwy last message repeated 2 times
Feb 21 16:04:57 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07
Feb 21 16:04:57 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME
Feb 21 16:04:58 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:04:58 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07
Feb 21 16:04:58 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME
Feb 21 16:04:59 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:04:59 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07
Feb 21 16:04:59 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME
Feb 21 16:05:00 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:05:00 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07
Feb 21 16:05:00 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME
Feb 21 16:05:01 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:05:01 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:05:01 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07
Feb 21 16:05:01 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME
Feb 21 16:05:02 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:05:02 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:05:02 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07
Feb 21 16:05:02 isdn-gtwy /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME
Feb 21 16:05:03 isdn-gtwy /kernel: i4b: unit 0, removed TEI = 101 = 0x65
Feb 21 16:05:03 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:05:03 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:05:05 isdn-gtwy /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3
Feb 21 16:05:05 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:05:05 isdn-gtwy /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 2
Feb 21 16:05:05 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:05:07 isdn-gtwy /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3
Feb 21 16:05:07 isdn-gtwy /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F7 Activated
Feb 21 16:15:13 isdn-gtwy su: kuku to root on /dev/ttyp4
Feb 21 16:15:21 isdn-gtwy /kernel: i4b-L2-i4b_dl_data_req: unit 0 ERROR in state [ST_EST_AW_TEI], freeing mbuf
Feb 21 16:15:51 isdn-gtwy /kernel: i4b-L3-T305_timeout: DISC not answered, cr = 82
Feb 21 16:15:51 isdn-gtwy /kernel: i4b-L2-i4b_dl_data_req: unit 0 ERROR in state [ST_EST_AW_TEI], freeing mbuf
Feb 21 16:15:51 isdn-gtwy /kernel: pid 370 (qvwm), uid 100: exited on signal 6 (core dumped)
Feb 21 16:15:55 isdn-gtwy /kernel: i4b-L3-T308_timeout: REL not answered, cr = 82
Feb 21 16:16:00 isdn-gtwy /kernel: i4b-L2-F_ILL: FSM function F_ILL executing
Feb 21 16:16:00 isdn-gtwy /kernel: i4b-L2-i4b_next_l2state: FSM illegal state, state = ST_EST_AW_TEI, event = EV_DLESTRQ!
Feb 21 16:16:04 isdn-gtwy /kernel: i4b-L3-T303_timeout: SETUP not answered, cr = 43
Feb 21 16:16:04 isdn-gtwy /kernel: i4b-L3-next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout!
Feb 21 16:16:22 isdn-gtwy su: kuku to root on /dev/ttyv0


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002211529.QAA08839>