Xref: utzoo comp.unix.ultrix:4406 comp.sys.dec:3922 Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!mtecv2!mtecv2.mty.itesm.mx!josevela From: josevela@mtecv2.mty.itesm.mx (Jose Angel Vela Avila) Newsgroups: comp.unix.ultrix,comp.sys.dec Subject: ULTRIX problems, problems and problems Message-ID: Date: 1 Sep 90 05:21:54 GMT References: <2039@gmuvax2.gmu.edu> <1990Aug30.131419.1831@dsuvax.uucp> Sender: josevela@mtecv2.mty.itesm.mx Followup-To: comp.unix.ultrix Distribution: na Organization: Instituto Tecnologico y de Estudios Superiores de Monterrey Lines: 48 In-reply-to: ghelmer@dsuvax.uucp's message of 30 Aug 90 13:14:19 GMT >>>>> On 30 Aug 90 13:14:19 GMT, ghelmer@dsuvax.uucp (Guy Helmer) said: > In <2039@gmuvax2.gmu.edu> rauletta@gmuvax2.gmu.edu (R. J. Auletta) writes: >>the following errors are reported on the console and by uerf >>occasionally after a dialin session is terminated. >>The rd and sd lights on the modem are full on. >>MESSAGE dhu1, line4: recv. fifo overflow > We've had a couple of different 2400 baud modems on our MicroVAX, > and with both the machine would crank out the same errors > ("dhu0, line0: recv. fifo overflow"). > One night the system console ran through about 100 pages of paper while > printing error messages before the paper jammed. > The modem lights rd and sd were on constantly when we got these errors, too. > We replaced the 2400 baud modem with a Telebit T2500, and we have not > seen the trouble since. > -- > Guy Helmer > work: DSU Computing Services, Business & Education Institute (605) 256-5315 > play: MidIX System Support Services (605) 256-2788 > dsuvax!ghelmer@cs.utexas.edu, ...!bigtex!loft386!dsuvax!ghelmer We have a problem like yours, we have a VAX 6310 running Ultrix 3.0, and if we put some modems in the serial ports then a while later the machine completly hangs. IS THIS FROM ULTRIX ?????? ^^^^^^ We ask to our DEC representants and just said tha we must change our version to ULTRIX 3.1, then we receive the upgrade, but it doesn't works (a sintax error when compiling the new Kernel, so we can't build the new Kernel), the problem is in the gfs_data.c archive, we told them and just send us a new copy of it that doesn't works either. Help me please......!!!! Thanks ! Atte. Jose A. Vela Avila. josevela@mtecv2.mty.itesm.mx