From owner-freebsd-bugs Fri Aug 14 22:30:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19087 for freebsd-bugs-outgoing; Fri, 14 Aug 1998 22:30:07 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19080 for ; Fri, 14 Aug 1998 22:30:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id WAA17931; Fri, 14 Aug 1998 22:30:01 -0700 (PDT) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18858 for ; Fri, 14 Aug 1998 22:28:36 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id AAA02508; Sat, 15 Aug 1998 00:28:06 -0500 (CDT) Message-Id: <199808150528.AAA02508@home.dragondata.com> Date: Sat, 15 Aug 1998 00:28:06 -0500 (CDT) From: toasty@dragondata.com Reply-To: toasty@dragondata.com To: FreeBSD-gnats-submit@FreeBSD.ORG X-Send-Pr-Version: 3.2 Subject: kern/7619: odd nfs server not responding messages appear Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 7619 >Category: kern >Synopsis: odd nfs server not responding messages appear >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Aug 14 22:30:00 PDT 1998 >Last-Modified: >Originator: Kevin Day >Organization: DragonData Internet Services >Release: FreeBSD 2.2.7-STABLE i386 >Environment: I have a 2.2.5 NFS server, and a 2.2.7 NFS client. >Description: Occasionally, the 2.2.7 client spits out a message that the NFS server isn't responding, then instantly says it's OK afterwards. Meanwhile, transfers are still going on, and everything seems ok... It appears harmless, but it makes me wonder if i'm not slowly corrupting things when this happens. >How-To-Repeat: No clue, it seems rather random. Here's a dmesg from the client... Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.7-RELEASE #0: Thu Jul 30 16:42:02 CDT 1998 root@shell1.dragondata.com:/usr/src/sys/compile/SHELL1 CPU: Pentium II (quarter-micron) (398.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183f9ff,,MMX,> real memory = 402653184 (393216K bytes) avail memory = 391720960 (382540K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0:0 chip1 rev 2 on pci0:1:0 chip2 rev 2 on pci0:7:0 chip3 rev 1 on pci0:7:1 chip4 rev 1 int d irq 9 on pci0:7:2 chip5 rev 2 on pci0:7:3 de0 rev 34 int a irq 11 on pci0:14:0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:05:43:a3:a3 de1 rev 34 int a irq 10 on pci0:15:0 de1: 21140A [10-100Mb/s] pass 2.2 de1: address 00:40:05:42:dd:26 Probing for devices on PCI bus 1: vga0 rev 92 on pci1:0:0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found at 0xffffffff psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, dma, iordy wcd0: 2412/5512Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: no disc inside, unlocked npx0 flags 0x1 on motherboard npx0: INT 16 interface de0: enabling Full Duplex 100baseTX port de1: enabling 100baseTX port nfs server home.internal:/home: not responding nfs server home.internal:/home: is alive again nfs server home.internal:/home: not responding nfs server home.internal:/home: not responding nfs server home.internal:/home: is alive again nfs server home.internal:/home: is alive again nfs server home.internal:/home: not responding nfs server home.internal:/home: is alive again nfs server home.internal:/home: not responding nfs server home.internal:/home: is alive again >Fix: Unknown. >Audit-Trail: >Unformatted: Kevin Day To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message