From owner-freebsd-hackers Sat Feb 8 12:13:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA26839 for hackers-outgoing; Sat, 8 Feb 1997 12:13:15 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA26832 for ; Sat, 8 Feb 1997 12:13:11 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id HAA24173; Sun, 9 Feb 1997 07:02:19 +1100 Date: Sun, 9 Feb 1997 07:02:19 +1100 From: Bruce Evans Message-Id: <199702082002.HAA24173@godzilla.zeta.org.au> To: bde@zeta.org.au, dk+@ua.net Subject: Re: 2.2 panic in i586_bc1 call from nfs_writerpc() Cc: dk@farm.org, dk@genesyslab.com, freebsd-hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >(btw, gdb cannot disassemble functions in support.s ;-( but it's easy >> ^^^^^^^^^^^ backtrace >> >to see that it's within i586_bc1 anyway (next label is i586_global_bcopy, >> >and that address is higher than fault's). > >well - I type `disas i586_bc1' so I can look up instruction by address, >and gdb refuses to do so. gdb handles this poorly, but you can disassemble almost anything (perhaps not data) by giving absolute start and end addresses, e.g., `disas i586_bc1 i586_bc1+123'. >yes, the mount was v3 (and probably even TCP). The NFS server is >NetApp F330, running Data ONTAP 4.0.1c (that's a dedicated NFS server, >essentially a Pentium PC with additional SCSI disk shelves, rackmounted. >The entire OS fits into 1 floppy disk and has a command-line interface >with similarities to Unix command set. It does up to 1Mb/s for both NFS >writes and reads - I wish FreeBSD can do that.) Perhaps it doesn't handle large file offsets right :-). Bruce