Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 23 Jan 2003 19:02:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 23 Jan 2003 19:02:56 -0500 Received: from WARSL402PIP3.highway.telekom.at ([195.3.96.97]:33104 "HELO email01.aon.at") by vger.kernel.org with SMTP id ; Thu, 23 Jan 2003 19:02:53 -0500 Reply-To: From: "Daniel Khan" To: "GrandMasterLee" Cc: Subject: AW: 2.4.20 CPU lockup - Now with OOPS message Date: Fri, 24 Jan 2003 01:11:59 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <1043366749.28748.124.camel@UberGeek> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, > > I reported frequently system lockups today. > > Now after some playing around (cause I don't know anything about kernel > > debugging - Thanks to Mark Hahn for the tipps) > > I found a way to reproduce the lock and to get the OOPS. [..] > Can I ask how you reproduced this? I've got several systems with TG3's > and they only get lockups during network backups. httpd session on the host which has big logfiles to get them changed. Starting rsync to sync the logfiles and other stuff to the backup host. Sometimes I have to retry 2-3 times but it crashes very reliable. It's quite the same as the network backups you mentioning. Daniel Khan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/