Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!swrinde!gatech!newsfeed.internetmci.com!news.sprintlink.net!dfw.nkn.net!rowdy.lonestar.org!nemesis!uhclem From: uhclem@nemesis.lonestar.org (Frank Durda IV) Subject: Re: SERIOUS 2.1.0 bug/problem! X-Newsreader: Tin 1.1 PL5 Organization: The Big Blue Box Message-ID: <DL3rnH.5Kz@nemesis.lonestar.org> References: <4d44or$6l@complete.org> Date: Sat, 13 Jan 1996 04:40:28 GMT Lines: 68 John Goerzen (jgoerzen@complete.org) wrote: [0]2.1.0 just locked up on me for the first time today, forcing a cold boot [0](reset switch). [0] [0]Here is the relevant portion of my /var/log/messages file (wrapping [0]inserted): [0] [0]Jan 11 10:49:22 complete /kernel: [0]sio0: 822 more interrupt-level buffer overflows (total 822) [0]Jan 11 10:49:23 complete /kernel: [0]sio0: 3219 more interrupt-level buffer overflows (total 4041) [0]Jan 11 10:49:24 complete /kernel: [0]sio0: 782 more interrupt-level buffer overflows (total 4823) [0]Jan 11 10:49:25 complete /kernel: [0]sio0: 1590 more interrupt-level buffer overflows (total 6413) [0]Jan 11 10:49:26 complete /kernel: [0]sio0: 1566 more interrupt-level buffer overflows (total 7979) [0] [0]Let me give you a rundown of what was happening at the time. I was logged [0]on remotely and on the remote machine (using the modem) had typed +++ to the [0]communications program to allow me to look at the modem's configuration. [0]After I typed ATO, I could not receive anything from the FreeBSD machine. I [0]hung up and called back, only to have it ring and ring without answering. [0] [0]When I got home, the following lights on the Courier V.34 modem were SOLID: [0]HS AA cd oh RD SD TR MR rs CS syn arg/fax [0] [0]The ones in caps were solid. Yes, RD and SD too. (Which is very unusual [0]for the Courier. Its lights are not solid unless there really is data [0]constantly going in and out.) The RS light is the RTS line; and the CS [0]light is the CTS line. On the modem you called, make sure that you have disabled the +++ sequence detection. When you tried to take your local modem into Command Mode, you typed +++, which still gets sent across the line. The machine on the far end probably echoed those characters (were you at a shell prompt?) and the modem on that end thought someone had told it to go into Command Mode. Set S2 to something other than 43, preferably something greater than 127 so that it will not respond to "+++" when it is handling incoming calls. Be sure to permanently store that value using the AT&W and/or AT&W1 commands. Failing to do this can allow someone to reprogram your modems without even logging into your system or having an account and they can really mess things up. [0] DTE: 115200 Your stuck RD SD lights make me think you also need to set ATE0W2 on the modem that got RD and SD on solid and got the overruns, and store this setting too. If you don't, your modem can get in a war with getty, echoing each character received from the host as fast as they come in, with the occasional "ERROR" message thrown in. Very stressful for sio drivers. The W2 instructs most modems to not report CONNECT and related messages on incoming calls, which can be misinterpreted as the account name being typed at a login: prompt. You will still get the CONNECT messages on outgoing calls, unless you set W1. [0] Flow control: RTS/CTS Yeah, you might have flow control on at the modem, but is it on in your PC? By default it isn't. Frank Durda IV <uhclem@nemesis.lonestar.org>|"The Knights who say "LETNi" or uhclem%nemesis@rwsystr.nkn.net | demand... A SEGMENT REGISTER!!!" ^------(this is the fastest route)|"A what?" or ...letni!rwsys!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983