From owner-freebsd-bugs@FreeBSD.ORG Wed Aug 16 14:20:21 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 005FC16A4DF for ; Wed, 16 Aug 2006 14:20:20 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A8B143D46 for ; Wed, 16 Aug 2006 14:20:20 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k7GEKJwe072071 for ; Wed, 16 Aug 2006 14:20:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k7GEKJAC072070; Wed, 16 Aug 2006 14:20:19 GMT (envelope-from gnats) Date: Wed, 16 Aug 2006 14:20:19 GMT Message-Id: <200608161420.k7GEKJAC072070@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Dmitry Petrov" Cc: Subject: Re: kern/100858: [bce] Broadcom bce driver and SMP hangup X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dmitry Petrov List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Aug 2006 14:20:21 -0000 The following reply was made to PR kern/100858; it has been noted by GNATS. From: "Dmitry Petrov" To: bug-followup@FreeBSD.org, roart@nvg.ntnu.no Cc: Subject: Re: kern/100858: [bce] Broadcom bce driver and SMP hangup Date: Wed, 16 Aug 2006 10:15:03 -0400 I have a similar problem with bce driver on FreeBSD 6.1-stable. I tried it with and without SMP with the same result. The machine does not freeze, only the network interface goes up/down which makes the whole system unusable: Aug 16 09:24:23 nch1 kernel: bce0: link state changed to DOWN Aug 16 09:24:26 nch1 kernel: bce0: link state changed to UP Aug 16 09:26:57 nch1 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(5032): Watchdog timeout occurred, resetting! Aug 16 09:26:57 nch1 kernel: bce0: link state changed to DOWN Aug 16 09:27:00 nch1 kernel: bce0: link state changed to UP Aug 16 09:28:13 nch1 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(5032): Watchdog timeout occurred, resetting! Aug 16 09:28:13 nch1 kernel: bce0: link state changed to DOWN Aug 16 09:28:16 nch1 kernel: bce0: link state changed to UP Aug 16 09:30:13 nch1 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(5032): Watchdog timeout occurred, resetting! Aug 16 09:30:13 nch1 kernel: bce0: link state changed to DOWN Aug 16 09:30:16 nch1 kernel: bce0: link state changed to UP Aug 16 09:32:06 nch1 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(5032): Watchdog timeout occurred, resetting! Aug 16 09:32:06 nch1 kernel: bce0: link state changed to DOWN Aug 16 09:32:09 nch1 kernel: bce0: link state changed to UP Aug 16 09:34:28 nch1 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(5032): Watchdog timeout occurred, resetting! Aug 16 09:34:28 nch1 kernel: bce0: link state changed to DOWN Aug 16 09:34:31 nch1 kernel: bce0: link state changed to UP Aug 16 09:36:05 nch1 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(5032): Watchdog timeout occurred, resetting! Aug 16 09:36:05 nch1 kernel: bce0: link state changed to DOWN Aug 16 09:36:08 nch1 kernel: bce0: link state changed to UP Aug 16 09:37:18 nch1 kernel: bce0: /usr/src/sys/dev/bce/if_bce.c(5032): Watchdog timeout occurred, resetting! It usually works for some time (hours) after reboot before it starts happening. Coincidentally, the machine I have is also Dell PowerEdge 1950 with dual Broadcom NetXtreme II BCM5708C 1000Base-T interfaces (bot only one is configured currently). I saw a similar error mentioned elsewhere in other lists. E.g. check freebsd-current: http://lists.freebsd.org/pipermail/freebsd-current/2006-August/065001.html Another things I noticed (which may or may not be related, but is worth mentioning as it involes ACPI) is that sometimes the machine does not reboot on "reboot" command, instead it seems to be staying in halted state. -- Dmitry Petrov phone: (212) 641-3235 -- *** DISCLAIMER *** This message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this message in error, please notify the sender by reply transmission and delete the message. The contents of this message that do not relate to the official business of our company shall be understood as neither given nor endorsed by it. ------------------