From owner-freebsd-isdn Sun Feb 18 4:58:44 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from worker.thw-IP.NET (worker.thw-IP.NET [192.76.134.35]) by hub.freebsd.org (Postfix) with ESMTP id A957537B401 for ; Sun, 18 Feb 2001 04:58:38 -0800 (PST) Received: from localhost (1366 bytes) by worker.thw-IP.NET via rmail with P:stdio/R:inet_mx_hosts/T:inet_zone_smtp (sender: ) (ident using unix) id for ; Sun, 18 Feb 2001 13:58:37 +0100 (CET) (Smail-3.2.0.111 2000-Feb-17 #18 built 2000-Oct-9) Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 82E7C52ACD; Sun, 18 Feb 2001 13:30:59 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id 4A5A79B24; Sun, 18 Feb 2001 13:30:59 +0100 (CET) Subject: Re: Dialing into FreeBSD box using modem In-Reply-To: from Stefan Walter at "Feb 17, 2001 3:18: 8 pm" To: stefan.walter@stud.udo.edu (Stefan Walter) Date: Sun, 18 Feb 2001 13:30:59 +0100 (CET) Cc: freebsd-isdn@freebsd.org Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 368 Message-Id: <20010218123059.4A5A79B24@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Stefan Walter wrote: > is there any possibility to dial into a FreeBSD box with an ISDN card > using a modem? Yes, there is a 300Baud software-modem available in the i4b 0.96 tar- distribution. hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sun Feb 18 12:37: 2 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (Postfix) with ESMTP id 95EA637B401 for ; Sun, 18 Feb 2001 12:36:59 -0800 (PST) Received: from news.cs.tu-berlin.de (mh@news.cs.tu-berlin.de [130.149.17.10]) by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id VAA20364 for ; Sun, 18 Feb 2001 21:33:04 +0100 (MET) Received: (from mh@localhost) by news.cs.tu-berlin.de (8.9.3/8.9.3) id VAA13632 for freebsd-isdn@freebsd.org; Sun, 18 Feb 2001 21:33:04 +0100 (MET) Date: Sun, 18 Feb 2001 21:33:04 +0100 From: Matthias Heidbrink To: freebsd-isdn@freebsd.org Subject: Problem with i4b 0.90/FreeBSD 4.0 Message-ID: <20010218213303.A6381@news.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I often get the following error message during opening a connection: Feb 18 20:58:41 mh3 /kernel: i4b-L4-i4b_l4_setup_timeout: 982526321: ERROR: idle time[240]+earlyhup[5] > unitlength[150]! After that the call seems to be active, but the dynamical IP address is not assigned, it stays 0.0.0.0. Usually it does not happen during the first dial-up, but that might be pure chance. My configuration: Teles S0 16.3 Card, Kernel PPP and natd. I'm just playing around with the firewall configuration [1], but the above seems not to be related to it, it also happens if I switch the packet filter off (pass through everything). Any ideas? Ciao, Matthias [1] Maybe some of you remember that I wrote about problems with setting up a firewall long ago - the problem is still not solved, although it now looks like I'm close to a solution, except the problem above. -- Matthias Heidbrink E-Mail: Bundesratufer 12 Matthias_Heidbrink@b.maus.de 10555 Berlin, Germany mh@cs.tu-berlin.de Tel. +49-30-8536361 Mobil +49-179-3981150 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Thu Feb 22 23:52:48 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from zorg.agsmedia.pl (mystique.agsmedia.pl [212.76.39.5]) by hub.freebsd.org (Postfix) with ESMTP id 2457D37B67D for ; Thu, 22 Feb 2001 23:52:42 -0800 (PST) (envelope-from wtp@agsmedia.pl) Received: from pooh.panska.agsmedia.pl (pooh.panska.agsmedia.pl [169.254.253.6]) by zorg.agsmedia.pl (Postfix) with ESMTP id 864627C008 for ; Fri, 23 Feb 2001 08:53:09 +0100 (CET) Date: Fri, 23 Feb 2001 08:52:24 +0100 (CET) From: Krzysztof Stryjek X-Sender: To: Subject: Fax over ISDN? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! I'm new with ISDN technology (and also still new with FBSD :-)). I was asked to setup fax machine to receive faxes over ISDN line? I was reading /usr/share/examples/isdn/*, but there's too little to answer my questions: * Is it possible at all? * Have I to run isdnd or fax server only? * Which fax server will work with ISDN? Thank's a lot for any help -- Krzysztof Stryjek email: wtp@agsmedia.pl ICQ: 79525071 Honi soit la vache qui rit. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 23 0:21:23 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id 5EF2737B503 for ; Fri, 23 Feb 2001 00:21:21 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 2AAA25D12; Fri, 23 Feb 2001 09:21:20 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id 00C0D3A1; Fri, 23 Feb 2001 09:21:19 +0100 (MET) Subject: Re: Fax over ISDN? In-Reply-To: "from Krzysztof Stryjek at Feb 23, 2001 08:52:24 am" To: Krzysztof Stryjek Date: Fri, 23 Feb 2001 09:21:19 +0100 (MET) Cc: isdn@FreeBSD.org Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010223082119.00C0D3A1@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Krzysztof Stryjek: > I'm new with ISDN technology (and also still new with FBSD :-)). I was > asked to setup fax machine to receive faxes over ISDN line? I was reading > /usr/share/examples/isdn/*, but there's too little to answer my questions: > * Is it possible at all? No. hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 23 1: 6:11 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from zorg.agsmedia.pl (mystique.agsmedia.pl [212.76.39.5]) by hub.freebsd.org (Postfix) with ESMTP id C61AC37B503 for ; Fri, 23 Feb 2001 01:06:06 -0800 (PST) (envelope-from wtp@agsmedia.pl) Received: from pooh.panska.agsmedia.pl (pooh.panska.agsmedia.pl [169.254.253.6]) by zorg.agsmedia.pl (Postfix) with ESMTP id 902237C00F; Fri, 23 Feb 2001 10:06:33 +0100 (CET) Date: Fri, 23 Feb 2001 10:05:48 +0100 (CET) From: Krzysztof Stryjek X-Sender: To: Hellmuth Michaelis Cc: Subject: Re: Fax over ISDN? In-Reply-To: <20010223082119.00C0D3A1@hcswork.hcs.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello again! On Fri, 23 Feb 2001, Hellmuth Michaelis wrote: > >From the keyboard of Krzysztof Stryjek: > > > I'm new with ISDN technology (and also still new with FBSD :-)). I was > > asked to setup fax machine to receive faxes over ISDN line? I was reading > > /usr/share/examples/isdn/*, but there's too little to answer my questions: > > * Is it possible at all? > > No. So is there any workaround? Regards -- Krzysztof Stryjek email: wtp@agsmedia.pl ICQ: 79525071 So much depends upon a red wheel barrow glazed with rain water beside the white chickens. -- William Carlos Williams, "The Red Wheel Barrow" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 23 2:39:26 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (Postfix) with ESMTP id E7B5D37B401 for ; Fri, 23 Feb 2001 02:39:23 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de (hcswork.hcs.de [192.76.124.5]) by hcshh.hcs.de (Postfix) with ESMTP id 0A8095D12; Fri, 23 Feb 2001 11:39:23 +0100 (CET) Received: by hcswork.hcs.de (Postfix, from userid 200) id D34CF38F; Fri, 23 Feb 2001 11:39:22 +0100 (MET) Subject: Re: Fax over ISDN? In-Reply-To: "from Krzysztof Stryjek at Feb 23, 2001 10:05:48 am" To: Krzysztof Stryjek Date: Fri, 23 Feb 2001 11:39:22 +0100 (MET) Cc: isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL84 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <20010223103922.D34CF38F@hcswork.hcs.de> From: hm@hcs.de (Hellmuth Michaelis) Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From the keyboard of Krzysztof Stryjek: > > > I'm new with ISDN technology (and also still new with FBSD :-)). I was > > > asked to setup fax machine to receive faxes over ISDN line? I was reading > > > /usr/share/examples/isdn/*, but there's too little to answer my questions: > > > * Is it possible at all? > > > > No. > So is there any workaround? The recommended workaround is to recycle an old (supported) analog modem, connect it to an analog phone line and install hylafax on the machine ;-) hellmuth -- Hellmuth Michaelis Tel +49 40 55 97 47-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 55 97 47-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de D-22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 23 2:48:41 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from zorg.agsmedia.pl (mystique.agsmedia.pl [212.76.39.5]) by hub.freebsd.org (Postfix) with ESMTP id 8C8BD37B491 for ; Fri, 23 Feb 2001 02:48:39 -0800 (PST) (envelope-from wtp@agsmedia.pl) Received: from pooh.panska.agsmedia.pl (pooh.panska.agsmedia.pl [169.254.253.6]) by zorg.agsmedia.pl (Postfix) with ESMTP id 25B857C009; Fri, 23 Feb 2001 11:49:02 +0100 (CET) Date: Fri, 23 Feb 2001 11:48:16 +0100 (CET) From: Krzysztof Stryjek X-Sender: To: Hellmuth Michaelis Cc: Subject: Re: Fax over ISDN? In-Reply-To: <20010223103922.D34CF38F@hcswork.hcs.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! Well, I'am seraching... I've found that AVM supports capi4linux (http://www.capi.org). Well I unpacked that and there's a "patch" (or the interface) for ISDN. So as I think I can install linux emulation, then install that software (I didn't found it in ports) and try run fax over ISDN. Question is: what's about devices. I think that devices are different under Linux and FreeBSD... Could it be a problem? Regards -- Krzysztof Stryjek email: wtp@agsmedia.pl ICQ: 79525071 Cheese -- milk's leap toward immortality. -- Clifton Fadiman, "Any Number Can Play" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Fri Feb 23 3:43:26 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from vasta.saunalahti.fi (postitoimisto.saunalahti.fi [195.197.53.226]) by hub.freebsd.org (Postfix) with ESMTP id E262737B4EC for ; Fri, 23 Feb 2001 03:43:19 -0800 (PST) (envelope-from jml@cubical.fi) Received: from gw.cubical.fi (gw.cubical.fi [195.218.69.227]) by vasta.saunalahti.fi (8.10.1/8.10.1) with ESMTP id f1NBi9800673; Fri, 23 Feb 2001 13:44:09 +0200 (EET) Received: from cubical.fi (dhcp-45.intra.net [192.168.42.45]) by gw.cubical.fi (8.9.3/8.9.3) with ESMTP id NAA18323; Fri, 23 Feb 2001 13:43:15 +0200 (EET) (envelope-from jml@cubical.fi) Message-ID: <3A964D1A.20C483ED@cubical.fi> Date: Fri, 23 Feb 2001 13:44:26 +0200 From: Juha-Matti Liukkonen Organization: Cubical Solutions Ltd X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Krzysztof Stryjek Cc: Hellmuth Michaelis , isdn@FreeBSD.ORG Subject: Re: Fax over ISDN? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, there is a /dev/capi20 device in Linux, which is basically a userland message tunnel to a CAPI compliant device. The capi client software requires this device to work. I am testing capi device support for i4b right now (using AVM T1), but I have not included this device yet, and I am not actively planning to do so at the moment. - Juha Krzysztof Stryjek wrote: > > Hello! > > Well, I'am seraching... I've found that AVM supports capi4linux > (http://www.capi.org). Well I unpacked that and there's a "patch" (or the > interface) for ISDN. So as I think I can install linux > emulation, then install that software (I didn't found it in ports) and try > run fax over ISDN. Question is: what's about devices. I think that devices > are different under Linux and FreeBSD... Could it be a problem? > > Regards > -- > Krzysztof Stryjek > email: wtp@agsmedia.pl > ICQ: 79525071 > > Cheese -- milk's leap toward immortality. > -- Clifton Fadiman, "Any Number Can Play" > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message -- Juha-Matti Liukkonen, Cubical Solutions Ltd Phone: +358(0)405280142 Email: jml@cubical.fi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 24 2:25: 0 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.freebsd.org (Postfix) with ESMTP id 5BEDF37B401; Sat, 24 Feb 2001 02:24:35 -0800 (PST) (envelope-from D.Rock@t-online.de) Received: from fwd01.sul.t-online.com by mailout04.sul.t-online.com with smtp id 14WbsO-0006zK-00; Sat, 24 Feb 2001 11:24:32 +0100 Received: from server.rock.net (340029380333-0001@[62.226.180.86]) by fmrl01.sul.t-online.com with esmtp id 14WbsA-0vGqXYC; Sat, 24 Feb 2001 11:24:18 +0100 Received: from t-online.de (server [172.23.7.1]) by server.rock.net (8.11.2/8.11.2/Rock) with ESMTP id f1OANbX57657; Sat, 24 Feb 2001 11:24:16 +0100 (MET) Message-ID: <3A978BA9.7D1A1B01@t-online.de> Date: Sat, 24 Feb 2001 11:23:37 +0100 From: Daniel Rock X-Mailer: Mozilla 4.76 [de] (X11; U; SunOS 5.8 i86pc) X-Accept-Language: de, en MIME-Version: 1.0 To: current@freebsd.org, isdn@freebsd.org Subject: Unstable ISDN with interrupt preemption? Content-Type: multipart/mixed; boundary="------------74C1EE39D62317C0F9597B9B" X-Sender: 340029380333-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dies ist eine mehrteilige Nachricht im MIME-Format. --------------74C1EE39D62317C0F9597B9B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I just noticed very unstable ISDN connections since the introduction of preempted interrupt threads (Jan 31st). Most errors are uncritical though, an active connection continues to work, sometimes I have to restart isdnd, and sometimes I even have to reboot the machine. The "i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout!" seem to have been introduced by the SMPng code, but with interrupt preemption they appear more often (I switched th SMPng on Jan 25th) As you can also see on the output: On Feb 9th I rebooted the machine with a newly built kernel. All other errors besides the one mentioned above suddenly disappeared. A quick look at the change logs revealed: preemption was accidently removed for interrupt threads on Feb 9th - and reintroduced a few hours later. It seems I was running such a kernel for a week (Feb 9th - 18th) Anyone else having the same problem? -- Daniel --------------74C1EE39D62317C0F9597B9B Content-Type: text/plain; charset=us-ascii; name="messages" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="messages" Jan 27 18:24:08 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Jan 28 06:26:32 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 00:26:13 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 12:23:38 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 12:33:38 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 12:35:38 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 14:53:38 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 15:05:00 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 3 15:26:08 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 6 00:26:15 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 6 12:14:49 gate /boot/kernel/kernel: i4b-L2 i4b_rxd_ack: ((N(R)-1)=115) != (UA=116) !!! Feb 7 00:19:47 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 7 06:21:56 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 7 06:27:56 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 7 12:24:55 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 7 21:54:51 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 8 00:24:50 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 8 00:31:50 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 9 20:53:51 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 9 20:53:51 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 9 21:07:33 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 9 21:13:56 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 9 21:14:25 gate /boot/kernel/kernel: i4b-L3 T305_timeout: DISC not answered, cr = 126 Feb 9 21:14:26 gate /boot/kernel/kernel: i4b-L3 T308_timeout: REL not answered, cr = 126 Feb 9 21:14:36 gate /boot/kernel/kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 108 Feb 9 21:17:44 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 9 21:17:44 gate /boot/kernel/kernel: i4b-L2 F_ILL: FSM function F_ILL executing Feb 9 21:17:44 gate /boot/kernel/kernel: i4b-L2 i4b_next_l2state: FSM illegal state, state = ST_TEI_UNAS, event = EV_T200EXP! Feb 9 21:17:49 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE Feb 9 21:17:49 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE Feb 10 18:24:22 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 13 18:20:48 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 16 18:21:03 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 18 00:24:59 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 18 00:25:59 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 18 02:05:00 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 18 02:05:00 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 18 02:23:05 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 18 02:23:05 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 18 02:23:05 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 19 00:27:30 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 19 23:35:50 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 20 18:25:00 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 21 12:16:08 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 21 12:56:08 gate /boot/kernel/kernel: i4b-L1 isic_hscx_waitxfw: HSCX wait for XFW timeout! Feb 22 12:26:37 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 23 20:51:57 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 23 20:51:57 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 23 20:51:57 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 23 22:29:54 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 23 23:59:30 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 24 00:05:25 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 24 00:06:01 gate /boot/kernel/kernel: i4b-L3 T305_timeout: DISC not answered, cr = 80 Feb 24 00:06:01 gate /boot/kernel/kernel: i4b-L3 next_l3state: FSM illegal state, state = ST_U10 - Active, event = EV_T305EXP - T305 timeout! Feb 24 00:47:20 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 24 00:47:20 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: unit = 0, location = F_MF07 Feb 24 00:47:20 gate /boot/kernel/kernel: i4b-L2 i4b_mdl_error_ind: error = MDL_ERR_F: peer initiated re-establishment - SABME Feb 24 02:22:57 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 24 02:28:54 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 24 02:29:23 gate /boot/kernel/kernel: i4b-L3 T305_timeout: DISC not answered, cr = 105 Feb 24 02:29:23 gate /boot/kernel/kernel: i4b-L3 T308_timeout: REL not answered, cr = 105 Feb 24 02:29:34 gate /boot/kernel/kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 75 Feb 24 10:02:08 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 24 10:02:08 gate /boot/kernel/kernel: i4b-L2 F_ILL: FSM function F_ILL executing Feb 24 10:02:08 gate /boot/kernel/kernel: i4b-L2 i4b_next_l2state: FSM illegal state, state = ST_TEI_UNAS, event = EV_T200EXP! Feb 24 10:02:08 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE Feb 24 10:02:08 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE Feb 24 10:26:19 gate /boot/kernel/kernel: i4b-L1 isic_isac_exir_hdlr: EXIRQ Rx Frame Overflow Feb 24 10:32:16 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 24 10:32:45 gate /boot/kernel/kernel: i4b-L3 T305_timeout: DISC not answered, cr = 1 Feb 24 10:32:45 gate /boot/kernel/kernel: i4b-L3 T308_timeout: REL not answered, cr = 1 Feb 24 10:32:56 gate /boot/kernel/kernel: i4b-L3 T303_timeout: SETUP not answered, cr = 125 Feb 24 10:42:35 gate /boot/kernel/kernel: i4b-L2 i4b_T200_timeout: unit 0, RC = 0 Feb 24 10:42:35 gate /boot/kernel/kernel: i4b-L2 F_ILL: FSM function F_ILL executing Feb 24 10:42:35 gate /boot/kernel/kernel: i4b-L2 i4b_next_l2state: FSM illegal state, state = ST_TEI_UNAS, event = EV_T200EXP! Feb 24 10:43:17 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE Feb 24 10:43:17 gate /boot/kernel/kernel: i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf NULL after IF_DEQUEUE --------------74C1EE39D62317C0F9597B9B Content-Type: text/plain; charset=us-ascii; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg" Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #525: Sat Feb 24 01:12:00 CET 2001 root@gate.rock.net:/usr/src/sys/compile/ROCK Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf AMD Features=0x80000800 real memory = 67043328 (65472K bytes) avail memory = 61329408 (59892K bytes) Preloaded elf kernel "kernel" at 0xc03e3000. WARNING: size of kinfo_proc (648) should be 644!!! VESA: v2.0, 8192k memory, flags:0x1, mode table:0xc0367b20 (1000060) VESA: Number Nine Visual Technology Corporation - REVOLUTION(tm) 3D Using $PIR table, 8 entries at 0xc00fdef0 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 agp0: mem 0xe2000000-0xe2ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) ohci0: mem 0xe7101000-0xe7101fff irq 11 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered isab0: at device 7.0 on pci0 isa0: on isab0 sym0: <815> port 0xe000-0xe0ff mem 0xe7102000-0xe71020ff irq 10 at device 8.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-10, SE, parity checking sym0: open drain IRQ line driver sym0: using NCR-generic firmware. pci0: at 9.0 (no driver attached) fxp0: port 0xe400-0xe41f mem 0xe7000000-0xe70fffff,0xe7100000-0xe7100fff irq 12 at device 10.0 on pci0 fxp0: Ethernet address 00:a0:c9:ef:69:8d atapci0: port 0xf000-0xf00f irq 0 at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isic0: at port 0x100-0x107 irq 3 on isa0 isic0: passive stack unit 0 unknown: can't assign resources pca0: at port 0x61 on isa0 unknown: can't assign resources fdc0: at port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f,0x778-0x77a irq 7 drq 3 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/1 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 unknown: can't assign resources i4bctl: ISDN system control port attached DUMMYNET initialized (010124) i4btrc: 2 ISDN trace device(s) attached IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, unlimited logging i4b: ISDN call control device attached i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 2 raw B channel access device(s) attached ad0: 4103MB [8894/15/63] at ata0-master UDMA33 ad1: 1221MB [2482/16/63] at ata1-master WDMA2 Waiting 2 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/ad0a da1 at sym0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8) da1: 995MB (2039283 512 byte sectors: 64H 32S/T 995C) da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 2150MB (4404489 512 byte sectors: 255H 63S/T 274C) cd0 at sym0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present WARNING: / was not properly dismounted --------------74C1EE39D62317C0F9597B9B Content-Type: text/plain; charset=us-ascii; name="kernel.config" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="kernel.config" machine i386 ident ROCK hints "ROCK.hints" maxusers 8 cpu I486_CPU cpu I586_CPU options COMPAT_43 options SYSVSHM options SYSVSEM options SYSVMSG options KTRACE #kernel tracing options UCONSOLE options INET device ether device sppp device loop 1 device bpf device tun options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_FORWARD options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT options DUMMYNET options FFS options NFS options PROCFS options DEVFS options SOFTUPDATES options FFS_EXTATTR options QUOTA device md options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options HZ=1000 device pty device snp options MSGBUF_SIZE=40960 device isa options AUTO_EOI_1 device atkbdc 1 device atkbd options ATKBD_DFLT_KEYMAP makeoptions ATKBD_DFLT_KEYMAP="german.iso" options KBD_INSTALL_CDEV device vga options VGA_WIDTH90 options VESA device splash device sc 1 options SC_DFLT_FONT makeoptions SC_DFLT_FONT=iso options SC_PIXEL_MODE device npx device ata device atadisk options ATA_ENABLE_ATAPI_DMA options ATA_ENABLE_TAGS device fdc device sio options BREAK_TO_DEBUGGER device pca device apm device pmtimer device joy device pci device agp device miibus device rl device fxp device isic options SEDLBAUER device "i4bq921" device "i4bq931" device "i4b" device "i4btrc" 2 device "i4bctl" device "i4brbch" 2 device "i4btel" 2 device ppc options PPC_PROBE_CHIPSET device ppbus device lpt device ppi device random device scbus device da device sa device cd device pass device sym device amd options SCSI_DELAY=2000 device aic device ohci device usb device ugen device uhid device ukbd device umass device ums device smbus device alpm device smb options COMPAT_LINUX options NETGRAPH options NETGRAPH_ASYNC options NETGRAPH_BPF options NETGRAPH_ETHER options NETGRAPH_IFACE options NETGRAPH_KSOCKET options NETGRAPH_MPPC_ENCRYPTION options NETGRAPH_PPP options NETGRAPH_PPPOE options NETGRAPH_PPTPGRE options NETGRAPH_SOCKET options NETGRAPH_TEE options NETGRAPH_TTY options NETGRAPH_UI options NETGRAPH_VJC --------------74C1EE39D62317C0F9597B9B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message From owner-freebsd-isdn Sat Feb 24 2:27:34 2001 Delivered-To: freebsd-isdn@freebsd.org Received: from mail01.this.net (erasmus.VHS.De [195.254.37.20]) by hub.freebsd.org (Postfix) with ESMTP id A6B8437B401 for ; Sat, 24 Feb 2001 02:27:27 -0800 (PST) (envelope-from andreas.haug@this.net) Received: Received: from jessie.this.net (p3EE2FDE7.dip.t-dialin.net [62.226.253.231]) by mail01.this.net (8.9.3/8.9.3) with ESMTP id LAA03423 for (from envelope sender ) Sat, 24 Feb 2001 11:27:26 +0100 (CET) Received: from jul (jul.this.net [195.254.107.17]) by jessie.this.net (8.11.1/8.11.1) with SMTP id f1OAd5P95512 for ; Sat, 24 Feb 2001 11:39:05 +0100 (CET) (envelope-from andreas.haug@this.net) From: "Andreas Haug" To: Subject: TCP Data corruption 0.96/4.2/T-online Date: Sat, 24 Feb 2001 11:28:11 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I have a very stange problem on i4b beta Version 0.96.00 / October 2000. Whenever I transmit some data, for example by SMTP or FTP, it gets corrupted. Since this day I thought that any transfer through TCP is protected by a good enough check sum. Perhaps this was a bad assumption. Example: On a remote machine, I generate a file # bash-2.00$ dd if=/dev/zero of=zero bs=1k count=1024 It looks quite empty: # bash-2.00$ od -a zero # 0000000 nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul # * then I ftp it on my system. No problem. Then I ftp it back to the remote system. There, it now looks like this: # bash-2.00$ od -a zero # 0000000 nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul # * # 0063740 @ nul nul nul nul nul nul nul nul ack nul dc4 c3 fe % nak # 0063760 > 9e dc4 c de 92 cr 91 dc ; Y m ba G bf b2 # 0064000 nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul # * # 0353740 @ nul nul nul nul nul nul nul nul ack nul dc4 c3 fe % nak # 0353760 > 9e dc4 c de 92 cr 91 dc ; Y m R a9 c0 b2 # 0354000 nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul # * # 2523740 @ nul nul nul nul nul nul nul nul ack nul dc4 c3 fe % nak # 2523760 > 9e dc4 c de 92 cr 91 dc ; Y m F 98 c9 b2 # 2524000 nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul # * # 2663740 @ nul nul nul nul nul nul nul nul ack nul dc4 c3 fe % nak # 2663760 > 9e dc4 c de 92 cr 91 dc ; Y m ^ C ca b2 # 2664000 nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul # * # 2753740 @ nul nul nul nul nul nul nul nul ack nul dc4 c3 fe % nak # 2753760 > 9e dc4 c de 92 cr 91 dc ; Y m > cc ca b2 # 2754000 nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul # * # 3223740 @ nul nul nul nul nul nul nul nul ack nul dc4 c3 fe % nak # 3223760 > 9e dc4 c de 92 cr 91 dc ; Y m 9e vt cc b2 # 3224000 nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul nul # * # 4000000 Another try gives the same problem(s), only a different offset. My system is running # FreeBSD jessie.this.net 4.2-RELEASE # FreeBSD 4.2-RELEASE #2: Sun Dec 3 18:49:19 CET 2000 # root@jessie.this.net:/usr/src/sys/compile/AJH0011 i386 With the i4b part of the kernel config AJH0011 looking like # options "TEL_S0_16_3" # device isic0 at isa? port 0xd80 irq 5 flags 3 # pseudo-device "i4bq921" # pseudo-device "i4bq931" # pseudo-device "i4b" # pseudo-device "i4btrc" 4 # pseudo-device "i4bctl" # pseudo-device "i4brbch" 4 # pseudo-device "i4btel" 2 # options IPR_VJ # pseudo-device "i4bipr" 4 # pseudo-device "i4bisppp" 4 The remote system is an old FreeBSD machine but I have verifyed the problem to occur on other systems, too, so the remote system can't be the problem. I am dialing into T-Online. As I said: Downloading anything isn't a problem, only uploading. Any hint where I should look to find the problem? Thanks. Thanks, andreas. P.S.: In hex, ist looks like this: 0727740 0040 0000 0000 0000 0600 1400 fec3 1525 0727760 e23e e7fd e7c1 b30d 9063 9f20 005c f113 0730000 0000 0000 0000 0000 0000 0000 0000 0000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message