From owner-freebsd-current@FreeBSD.ORG Tue May 13 05:38:13 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 732E4106566B for ; Tue, 13 May 2008 05:38:13 +0000 (UTC) (envelope-from caelian@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id E9B148FC1B for ; Tue, 13 May 2008 05:38:12 +0000 (UTC) (envelope-from caelian@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so4426536fgb.35 for ; Mon, 12 May 2008 22:38:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type:content-transfer-encoding; bh=EwFw0SGwunT5kyZruOpqE/s+Hoec7+GqMByGuDgsFuI=; b=rm64hthkKCxc6GmrxzyOs1b/07ejx5VMrctKRohpcbduCi1eO4JP3FQFuzXPKVQwTtdi48f5FPURbCOpSodUQpJrCGabOXJq4K32Re6TuWrUuluNXKvWu0Ja1t/Rn3XDMb0SrBrF3AAj5Hz6DtBPG5Jlu41bMIPEh0iQhaqTMbM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type:content-transfer-encoding; b=OUHRdQakTEyzhevkCIlY0mhpSvJx/EE8ljWgi0VpTeCcnb/cCeP0/DSRKJyprkzG5Noc6sOTfc73t7Mk0oJfqDaf4a1IR9Nz+yoSWvdokCkivziT0Ez7b0dKwNDx62+Av/VwMuBmAl+pIgqcGXf77SDyg6mz6J5z+of0qejj5a4= Received: by 10.86.50.8 with SMTP id x8mr15712279fgx.29.1210657091401; Mon, 12 May 2008 22:38:11 -0700 (PDT) Received: from nebuchadnezzar ( [87.151.45.81]) by mx.google.com with ESMTPS id o11sm12962733fkf.16.2008.05.12.22.38.10 (version=SSLv3 cipher=RC4-MD5); Mon, 12 May 2008 22:38:10 -0700 (PDT) Date: Tue, 13 May 2008 07:38:09 +0200 From: Pascal Hofstee To: pyunyh@gmail.com Message-ID: <20080513073809.3b163baa@nebuchadnezzar> In-Reply-To: <20080513020927.GD32942@cdnetworks.co.kr> References: <20080512181259.04a2f542@nebuchadnezzar> <20080513020927.GD32942@cdnetworks.co.kr> X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: current@freebsd.org, yongari@freebsd.org Subject: Re: nfe0 watchdog timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 05:38:13 -0000 On Tue, 13 May 2008 11:09:27 +0900 Pyun YongHyeon wrote: > Can you see link state change reports of nfe(4) in your dmesg file? > If you find any entries related with nfe(4) please show them to me. > It may have a couple of link UP/DOWN messages and watchdog timeouts. You are right i initially overlooked the link state messages. They're no longer in dmesg ... but i copy/pasted a small set from /var/log/messages instead: May 10 15:59:31 trinity kernel: ums0: at uhub0 port 1 (addr 2) disconnected May 10 15:59:31 trinity kernel: ums0: detached May 10 15:59:33 trinity kernel: nfe0: link state changed to DOWN May 10 15:59:33 trinity avahi-daemon[811]: Received packet from invalid interface. May 10 15:59:33 trinity acpi: resumed at 20080510 15:59:33 May 10 15:59:34 trinity root: Unknown USB device: vendor 0x046d product 0xc404 bus uhub0 May 10 15:59:34 trinity kernel: ums0: on uhub0 May 10 15:59:34 trinity kernel: ums0: 3 buttons and Z dir. May 10 15:59:45 trinity kernel: nfe0: link state changed to UP May 10 15:59:53 trinity kernel: nfe0: watchdog timeout (missed Tx interrupts) -- recovering May 10 16:00:35 trinity last message repeated 5 times May 10 16:01:53 trinity last message repeated 9 times I opted to include the usb-related messages as well since i find it somewhat odd my Trackball decided to disconnect since i never take it off ... Followed by the ACPI resumed message ... this to me feels like the system may have been in some sort of power saving mode ? > When you know nfe(4) is not working anymore, would you check Rx MAC > is still able to see incoming packets by invoking tcpdump on > nfe(4) interface? Once it happens again i'll make sure to check on it. > It would be even better I can see verbosed boot messages related > with nfe(4). Will provide once i can reboot the system again (it's currently in the middle of a somewhat lengthy build process). With kind regards, -- Pascal Hofstee