From owner-freebsd-stable@FreeBSD.ORG Thu Nov 2 17:43:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1144516A40F for ; Thu, 2 Nov 2006 17:43:37 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D06F43D5C for ; Thu, 2 Nov 2006 17:43:36 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by nz-out-0102.google.com with SMTP id o37so143123nzf for ; Thu, 02 Nov 2006 09:43:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XE9f0TJxGWAoy2rwYDZvLXkt+rRUpeq4Zrbgl2Tteawoa2uiTLsxSgYM08RS2dHfXuDwmBtJtMLExi1qogRJQ/DRcHebhWKzcxdb/cjuhlQn0iXb137kTZs/8yiVPmsz1eIWrHQDvK6p50SX+ZFojFKjr1ErBO6QFh+exGozq8I= Received: by 10.35.125.16 with SMTP id c16mr1351598pyn.1162489415109; Thu, 02 Nov 2006 09:43:35 -0800 (PST) Received: by 10.35.118.6 with HTTP; Thu, 2 Nov 2006 09:43:34 -0800 (PST) Message-ID: <2a41acea0611020943p9c91b6fv1e61cd9ea0082b77@mail.gmail.com> Date: Thu, 2 Nov 2006 09:43:34 -0800 From: "Jack Vogel" To: "Patrick M. Hausen" In-Reply-To: <20061102094332.GA15810@hugo10.ka.punkt.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061102094332.GA15810@hugo10.ka.punkt.de> Cc: freebsd-stable@freebsd.org, zenker@punkt.de Subject: Re: New em driver - still watchdog timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2006 17:43:37 -0000 Yes, I know this is still happening. I also have pretty good data now that its a bogus problem, meaning due to scheduling issues the watchdog does not get reset even though the system is just fine as far as transmit descriptors is concerned. I have a patch that detects this and keeps the watchdog from erroneously resetting you, it has been running on my test system for days now without problems. Jack On 11/2/06, Patrick M. Hausen wrote: > Hello! > > Our central backup server is still experiencing the same > random problems. The timouts occur every other night or so, > when the server has got high CPU load (compressing the > backups) and transfers large amounts of data at the same > time. > > Nov 2 02:19:34 datatomb kernel: em1: watchdog timeout -- resetting > Nov 2 02:19:34 datatomb kernel: em1: link state changed to DOWN > Nov 2 02:19:34 datatomb kernel: vlan23: link state changed to DOWN > Nov 2 02:19:34 datatomb kernel: vlan22: link state changed to DOWN > Nov 2 02:19:36 datatomb kernel: em1: link state changed to UP > Nov 2 02:19:36 datatomb kernel: vlan23: link state changed to UP > Nov 2 02:19:36 datatomb kernel: vlan22: link state changed to UP > > Jack, the hardware should be easy for you or someone else > at Intel to get your hands on: > > http://www.intel.com/design/servers/storage/ssr212cc/index.htm > > Unfortunately I cannot give you root access to _that_ one. > > Regards, > Patrick > -- > punkt.de GmbH Internet - Dienstleistungen - Beratung > Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 > 76137 Karlsruhe http://punkt.de > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >