Date: Fri, 28 Dec 2001 11:35:25 -0000 From: "David Hedley" <david@inty.net> To: <freebsd-isdn@freebsd.org> Subject: RE: ifpi2 problems Message-ID: <NEBBKDONLMHNHKCKHHAIGEAMKPAA.david@inty.net> In-Reply-To: <20011224235808.T86622-100000@server.arg.sj.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> I have been trying out the ifpi2 driver. I first tried in a -current > machine and all worked OK (though I didn't thrash it particularly hard). > I am now trying to use it in a 486 running -stable. > > The setup is (at present) just using the ISDN for single-channel outgoing > calls with user-ppp/rbch. If I use it 'gently' it all works fine - I have > been online for an hour or so reading mail via ssh with no problem. > However, if I try web browsing to graphics-heavy sites, it stops working > within about 2 minutes. > > The failure state is as if interrupts from the card have become disabled: > the ppp process is still running and eventually times out the connection > and attempts to redial, but isdnd thinks that the connection is in use, > and if I make a voice call to the line, ISDND doesn't report anything. > Only a reboot seems to clear the latched up state. Hmm, well this probably doesn't help, but we've been testing the v2 Fritz card using Gary's drivers for a while now and haven't hit any major problems like this (this is with 4.4 and i4b from -stable). The only problem we've seen is when we plug both a v1 fritz and a v2 fritz into the same box, where you get an instant kernel panic when the v2 fritz card tries to dial out. (panics in avma1pp_set_linktab, so may not be specific to v2 fritz). What happens if you just restart isdnd? I occasionally see problems when user-ppp and isdnd stop talking to each other (ppp will be trying to dial out but isdnd won't respond for some reason), although this always goes away when isdnd is restarted. > > PS. are you sure that having a device name ending in a digit is a good > idea? It gives very confusing effects if you forget the quotes around the > device "ifpi2" > line in the kernel config file, as well as the rather odd > ifpi20: blah > messages on the console. > I second this. I actually ended up renaming the driver entirely - I didn't realise you could put quotes around it to get it to work! Happy New Year... David -- Dr David Hedley, R&D Director, Intelligent Network Technology Ltd, Bristol, UK http://www.inty.net/ ----------------------------------------------- Information in this electronic mail message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient any use, disclosure, copying or distribution of this message is prohibited and may be unlawful. When addressed to our customers, any information contained in this message is subject to Intelligent Network Technology Ltd Terms & Conditions. ----------------------------------------------- Take part in the intY 2001 Email Usage survey online at http://www.inty.net/email/survey.html ----------------------------------------------- intY has automatically scanned this email with Sophos Anti-Virus (www.inty.net) 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?NEBBKDONLMHNHKCKHHAIGEAMKPAA.david>