Xref: utzoo comp.unix.ultrix:964 comp.sys.dec:1302
Path: utzoo!utgpu!attcan!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.ultrix,comp.sys.dec
Subject: Re: chained packet panic on DEQNA (uvaxII) ?
Message-ID: <6971@cbmvax.UUCP>
Date: 24 May 89 21:28:24 GMT
References: <2717@helios.ee.lbl.gov>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 21

In article <2717@helios.ee.lbl.gov> envbvs@epb2.lbl.gov (Brian V. Smith) writes:
> We are crashing on our Microvax II with a DEQNA with the panic message
> "qe: chained packet".
> 
> Any idea on what this means?  It usuallly happens when "rlogin"ing
> or "ftp"ing to a remote host.

It means that the deqna driver has received a packet > 2K bytes long.
Normal ethernet packets are limited to ~1500 bytes, but many systems
will generate longer packets if left to their own ends.  If you have
a Sun on your net, you should be able to use the etherfind/tcpdump
utilities to get some handle on this.

I've heard that sun NFS will use big packets, but there are parameters
in fstab to control this.  I don't see right off why you would have
problems with rlogin/telnet type protocols though.

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)