Date: Mon, 23 Nov 1998 19:48:35 -0500 (EST) From: Brian Feldman <green@unixhelp.org> To: Mike Smith <mike@smith.net.au> Cc: Tom Bartol <bartol@salk.edu>, Doug Rabson <dfr@nlsystems.com>, freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current Message-ID: <Pine.BSF.4.05.9811231945090.14696-100000@janus.syracuse.net> In-Reply-To: <199811231730.JAA19160@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 23 Nov 1998, Mike Smith wrote: > > Please ask a primary school teacher about "paragraphs". Sorry, I'm working on a good solutio, but basically right now I'm piping all my outgoing mail through fmt and losing any special formatting... I'll come up with a real solution soon. > > Please also make it clear whether you're using the old 'lpt' driver or > the newer ppbus code, so that we can work out what needs attention... I'm using the newer ppbus code entirely: controller ppbus0 device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? device pps0 at ppbus? controller ppc0 at isa? port ? tty irq 7 vector ppcintr ppc: parallel port found at 0x378 ppc0 at 0x378 irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode nlpt0: <generic printer> on ppbus 0 nlpt0: Interrupt-driven port ppi0: <generic parallel i/o> on ppbus 0 lppps0: <Pulse per second Timing Interface> on ppbus 0 plip0: <PLIP network interface> on ppbus 0 > > > I'm having different problems. For instance, using FreeBSD 3.0-CURRENT > > (yesterday) as an NFS server, utilizing PLIP as my connection to > > a FreeBSD 3.0-RELEASE boot disk on an old WinBook. I was backing > > up the hard drive (cp /dev/rwd0a /mnt) and I tried running top > > because both systems were getting slow. Top on the desktop showed > > 8x% interrupt, is that software or hardware interrupts? After this, > > I wanted to see the traffic, so I did a trafshow -i lp0, and all > > of a sudden a flood of Fatal trap 12's happened on the desktop > > system. Basically, I could do nothing at this point, and had to do > > a hard reset. So, letting you know, something is broken here. Can > > I disable DDB for fatal traps, not just panic()'s, because I only > > wanted it enabled so I could drop into it at will to examine kernel > > state....? > > > > Brian Feldman _ __ ___ ___ ___ > > green@unixhelp.org _ __ ___ | _ ) __| \ > > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > I'll go check out the PR archives for info on BPF over PLIP, anyway. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9811231945090.14696-100000>