From owner-freebsd-bugs@FreeBSD.ORG Sat Dec 17 21:43:37 2011 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E624D106564A for ; Sat, 17 Dec 2011 21:43:37 +0000 (UTC) (envelope-from james@mansionfamily.plus.com) Received: from avasout07.plus.net (avasout07.plus.net [84.93.230.235]) by mx1.freebsd.org (Postfix) with ESMTP id 48E188FC15 for ; Sat, 17 Dec 2011 21:43:36 +0000 (UTC) Received: from server.barnhouse ([80.229.150.39]) by avasout07 with smtp id AMV91i0080rF08o01MVAgl; Sat, 17 Dec 2011 21:29:10 +0000 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.0 cv=KLrY/S5o c=1 sm=1 a=KcaHU+F0vwy42TIp8RsFnw==:17 a=lIqQTE_t3hsA:10 a=t9yhkdSSS9cA:10 a=8nJEP1OIZ-IA:10 a=Y_sqAMplG3v9mnD2PskA:9 a=gpz4_SZuynA-k90iRNMA:7 a=wPNLvfGTeEIA:10 a=QvcZSmMg-kAUEzAn:21 a=D7PrHc6w-kGgA8c1:21 a=KcaHU+F0vwy42TIp8RsFnw==:117 Received: from [192.168.0.96] (workstation.barnhouse [192.168.0.96]) by server.barnhouse (Postfix) with ESMTP id D0419681900 for ; Sat, 17 Dec 2011 21:30:33 +0000 (GMT) Message-ID: <4EED09A4.4000905@mansionfamily.plus.com> Date: Sat, 17 Dec 2011 21:29:08 +0000 From: James Mansion User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-bugs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Small NAS keeps hanging: 9.0 RC3 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2011 21:43:38 -0000 I'm trying to run Windows backup to my NAS, which is running 9.0rc3. nas# uname -a FreeBSD nas 9.0-RC3 FreeBSD 9.0-RC3 #0: Sun Dec 4 08:56:36 UTC 2011 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 nas# I'm using Samba on a ZFS pool. System stops responding to the network, nothing untoward visible on top, pressing the reset button initiates a halt and reboot and it all comes back up. Failure is after 38.46GB of file backup and 138.56GB of system image. Backup does not complete - the drive goes away. Putty sessions are dropped and sshd is unresponsive. I get this in syslog: Dec 17 13:34:49 nas kernel: msk0: watchdog timeout Dec 17 13:34:49 nas kernel: msk0: prefetch unit stuck? Dec 17 13:34:49 nas kernel: msk0: initialization failed: no memory for Rx buffers Dec 17 13:38:09 nas ntpd[1685]: sendto(193.110.251.9) (fd=22): Network is down Dec 17 13:39:09 nas ntpd[1685]: sendto(194.71.144.71) (fd=22): Network is down Dec 17 13:41:20 nas ntpd[1685]: sendto(194.109.64.200) (fd=22): Network is down Symptom is always the same. nas# ifconfig msk0: flags=8843 metric 0 mtu 1500 options=c011b ether 00:50:43:00:12:40 inet 192.168.0.82 netmask 0xffffff00 broadcast 192.168.0.255 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active dmesg has: msk0: on mskc0 msk0: Ethernet address: 00:50:43:00:12:40 miibus0: on msk0 e1000phy0: PHY 0 on miibus0 e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow This is an addin card. I also have an adapter on the motherboard in the system which I *could* use: msk1: on mskc1 msk1: Ethernet address: dc:9c:52:07:a5:7f miibus1: on msk1 e1000phy1: PHY 0 on miibus1 e1000phy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow And I could swap the card for an Intel CT desktop adapter if its likely to be an improvement. Is it worth trying the other Marvell chip at all? (This happened with RC2 but I didn't capture the cause. Uptime with RC3 had seemed better, but i think that's because I hadn't initiated a full backup with system image.) James