Yonghyeon PYUN wrote
in <20130731074341.gc1...@michelle.cdnetworks.com>:
py> On Wed, Jul 31, 2013 at 03:54:06PM +0900, Hiroki Sato wrote:
py> > [Added yougari@ and davidch@ to the To:/Cc: list]
py> >
py> > I confirmed that my issue reported on -current@ is due to the bxe(4)
py> > driver (BCM5
On Wed, Jul 31, 2013 at 03:54:06PM +0900, Hiroki Sato wrote:
> [Added yougari@ and davidch@ to the To:/Cc: list]
>
> I confirmed that my issue reported on -current@ is due to the bxe(4)
> driver (BCM57711). If it is disabled, shutdown works fine without
> NMI.
>
> Also, I received several re
[Added yougari@ and davidch@ to the To:/Cc: list]
I confirmed that my issue reported on -current@ is due to the bxe(4)
driver (BCM57711). If it is disabled, shutdown works fine without
NMI.
Also, I received several reports about the same box that NMI occurred
even on bge(4) (BCM5717) driver
> http://svnweb.freebsd.org/base?view=revision&revision=236216
>
>
Ok, confirmed after ~50 reboots.
There is a timing problem in this revision that I don't fully
understand. Adding printf's inside bce_reset() will cause the existing
code to succeed, and sometimes the existing code in this r
From: Sean Bruno
To: "freebsd-net@freebsd.org"
Sent: Monday, July 29, 2013 8:56 PM
Subject: Re: bce(4) panics, 9.2rc1 [redux]
On Wed, 2013-07-24 at 14:07 -0700, Sean Bruno wrote:
> Running 9.2 in production load mail servers. We&#
On Wed, 2013-07-24 at 14:07 -0700, Sean Bruno wrote:
> Running 9.2 in production load mail servers. We're hitting the
> "watchdog" message and crashing with the stable/9 version. We're
> reverting the change from 2 weeks ago and seeing if it still happens.
> We didn't see this from stable/9 from
