From owner-freebsd-isdn Thu Jan 4 2: 3:32 2001 From owner-freebsd-isdn@FreeBSD.ORG Thu Jan 4 02:03:30 2001 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.139.170]) by hub.freebsd.org (Postfix) with ESMTP id 4ED4037B402 for ; Thu, 4 Jan 2001 02:03:29 -0800 (PST) Received: (from brian@localhost) by storm.FreeBSD.org.uk (8.11.1/8.11.1) id f04A3SZ45131; Thu, 4 Jan 2001 10:03:28 GMT (envelope-from brian) Date: Thu, 4 Jan 2001 10:03:28 GMT From: Brian Somers Message-Id: <200101041003.f04A3SZ45131@storm.FreeBSD.org.uk> To: freebsd-isdn@FreeBSD.org Subject: ISDN ``SABME'' event ? Cc: brian@Awfulhak.org Sender: brian@storm.FreeBSD.org.uk Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I've got a machine that occasionally loses it's ISDN connection in such a way that I need to kill and restart isdnd to get things to work again. I have no details at the moment except to say that it does this every few days of continuous connection, and the attached appeared on my screen today when I was remotely logged in as root to do some maintenance on /home. Is this ``SABME'' event something unusual ? Should isdnd/i4b recover ok from it ? I'm (of course :) using the i4brbch0 device and don't expect anything else to be going on (although it's possible that I received an incoming call or that my wife made an outgoing call via a TA connected to the same bus). The machine's -stable from about 1 week ago. If this info isn't enough, I can crank up logging etc, this message is only really a probe to see if these errors are enough in themselves to mean something :-) Cheers. -- Brian Don't _EVER_ lose your sense of humour ! Jan 4 09:35:41 gate /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Jan 4 09:35:41 gate /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Jan 4 09:35:41 gate /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Jan 4 09:35:41 gate /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Jan 4 09:35:42 gate /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Jan 4 09:35:42 gate /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Jan 4 09:35:42 gate /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Jan 4 09:35:42 gate /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Jan 4 09:35:43 gate /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Jan 4 09:35:43 gate /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Jan 4 09:35:43 gate /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Jan 4 09:35:43 gate /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Jan 4 09:35:44 gate /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Jan 4 09:35:44 gate /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_MF07 Jan 4 09:35:44 gate /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Jan 4 09:35:44 gate /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message