Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.hawaii.edu!ames!purdue!yuma!csn!nntp-xfer-2.csn.net!symbios.com!southwind.net!complete.org!not-for-mail From: jgoerzen@complete.org (John Goerzen) Newsgroups: comp.unix.bsd.freebsd.misc Subject: SERIOUS 2.1.0 bug/problem! Date: 11 Jan 1996 16:59:39 -0600 Organization: Communications Centre (+1 316 367 8490) Lines: 66 Message-ID: <4d44or$6l@complete.org> NNTP-Posting-Host: complete.org X-Newsreader: TIN [version 1.2 PL2] 2.1.0 just locked up on me for the first time today, forcing a cold boot (reset switch). Here is the relevant portion of my /var/log/messages file (wrapping inserted): Jan 11 10:49:22 complete /kernel: sio0: 822 more interrupt-level buffer overflows (total 822) Jan 11 10:49:23 complete /kernel: sio0: 3219 more interrupt-level buffer overflows (total 4041) Jan 11 10:49:24 complete /kernel: sio0: 782 more interrupt-level buffer overflows (total 4823) Jan 11 10:49:25 complete /kernel: sio0: 1590 more interrupt-level buffer overflows (total 6413) Jan 11 10:49:26 complete /kernel: sio0: 1566 more interrupt-level buffer overflows (total 7979) Let me give you a rundown of what was happening at the time. I was logged on remotely and on the remote machine (using the modem) had typed +++ to the communications program to allow me to look at the modem's configuration. After I typed ATO, I could not receive anything from the FreeBSD machine. I hung up and called back, only to have it ring and ring without answering. When I got home, the following lights on the Courier V.34 modem were SOLID: HS AA cd oh RD SD TR MR rs CS syn arg/fax The ones in caps were solid. Yes, RD and SD too. (Which is very unusual for the Courier. Its lights are not solid unless there really is data constantly going in and out.) The RS light is the RTS line; and the CS light is the CTS line. The AA light should not have been on. I don't know why it was, unless some data got garbled that was sent to it. (mgetty does not use the modem's auto-answer; instead, it monitors for a "RING" signal from the modem) Some details on the lock...I was able to use the Alt-F? keys to switch between VTY's (all were empty and at login prompt except the one at Alt-F1 which was at login prompt but showed the messages shown above). The system did not respond to my keyboard commands. There was no cursor. Incidentally, pressing Print Screen switched VTYs also. Ctrl-Alt-Del did not reboot. Incidentally, FreeBSD has always worked perfectly with communications prior to this. It also doesn't appear to be the modem's problem. After FreeBSD rebooted (the RD and SD lights went off immediately when I pressed the Reset switch), it properly initialized the modem and the modem is now working fine without me ever having to touch it or send any manual commands to it. Relevant configuration information: FreeBSD version: 2.1.0 RELEASE Kernel: Custom (but no source mods or anything that would effect this) Modem: USR Courier/V.Everything v.34 + 33.6 upgrade DTE: 115200 Flow control: RTS/CTS Serial card: 16550 series (A or AFN or something like that) Thanks for any help! -- John Goerzen -- John Goerzen, programmer and owner | Use #10 for your Win95 CD: it makes | Communications Centre, Goessel, KS | an excellent cupholder. | Main e-mail: jgoerzen@complete.org | #11: Nice decorations 2 hang on wall|