From owner-freebsd-bugs Thu Jul 27 08:41:10 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id IAA26122 for bugs-outgoing; Thu, 27 Jul 1995 08:41:10 -0700 Received: from nomad.osmre.gov (nomad.osmre.gov [192.243.129.244]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id IAA26114 for ; Thu, 27 Jul 1995 08:41:03 -0700 Received: (from gfoster@localhost) by nomad.osmre.gov (8.6.11/8.6.9) id LAA03135; Thu, 27 Jul 1995 11:40:46 -0400 Date: Thu, 27 Jul 1995 11:40:46 -0400 From: Glen Foster Message-Id: <199507271540.LAA03135@nomad.osmre.gov> To: freebsd-bugs@freebsd.org Subject: NFS+SAMBA == crash in 2.0.5R Sender: bugs-owner@freebsd.org Precedence: bulk Folks, I apologize in advance for the incompleteness of this bug report but I do not know how to discover more (please tell me how to get a backtrace and I will be happy to provide it). I will be happy to provide additional details on request. A client of mine reports that attempting to execute a DOS program under Windows 95 from a SAMBA exported drive that was NFS mounted from another machine, i.e. like this: disk-on-machine-A --NFS--> machine-B --SAMBA--> Windows95 silently crashes machine B, there is no panic or reboot, screen is blank, keyboard, ethernet, and serial port unresponsive, CPU appears to have halted. Both machine A and B are running FreeBSD 2.0.5R. He says that it is repeatable and happens with every DOS executable attempted. Reading and writing files in this configuration works without problems, DOS executes from machine B SAMBA exported local volumes are OK. This leads me to the hypothesis that something in the NFS code is causing this behaviour. My client has been in contact with the author of SAMBA who feels it is a FreeBSD bug and has asked me to report it to the FreeBSD development team. Glen Foster