From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964864AbVI0IhU (ORCPT ); Tue, 27 Sep 2005 04:37:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964866AbVI0IhT (ORCPT ); Tue, 27 Sep 2005 04:37:19 -0400 Received: from lucidpixels.com ([66.45.37.187]:4736 "EHLO lucidpixels.com") by vger.kernel.org with ESMTP id S964864AbVI0IhT (ORCPT ); Tue, 27 Sep 2005 04:37:19 -0400 Date: Tue, 27 Sep 2005 04:37:01 -0400 (EDT) From: Justin Piszcz X-X-Sender: jpiszcz@p34 To: linux-kernel@vger.kernel.org Subject: Repeatable crash under 2.6.13.2 + NFS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Simply copy some files *over NFS* from box1 to box2. Or tar them, I did both. The remote machine locks and freezes, no console output. Copied 206MB before the MB/s went to 0 and crashed the remote box. Nasty bug. SCP works fine. I've reported this before w/ .config etc but nobody responded. It still occurs. The nastiest part of all is, when the box that crashed is rebooting, it WILL NOT COME BACK up *IF* the machine that was sending the files to it is up. It is almost like box1 (client) is sending some deadly packets to the other box and it cannot come up (it freezes after it initializes the NIC) until the other box is rebooted/shut down or disconnected from the network.