Justin, Have you found a solution to the NIC issue yet?
FYI, I was working with Broadcom's test team but they pretty much dropped the ball on me.... So it is all up to us to find a solution! Please share if you know how to get the NIC not to drop out intermitently. thank you, TP On Thu, May 28, 2015 at 3:48 AM, Justin Catterall <jus...@masonsmusic.co.uk> wrote: > > > On 27 May 2015, at 17:06, Toan Pham <tpham3...@gmail.com> wrote: > > > > Justin, > > > > > > I've observed a similar symptom on the bcm5762 chip, not the 5720, and > > not sure if the bugs they are related. I've filed a bug report > > (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664), and > > actively working with Broadcom's engineering team to get this bug > > resolved. They are running multiple test cases but could not get this > > bug to surface in a short amount of time. > > > >> In the mean time I've made a bash-script to rmmod and modprobe as > appropriate. I'll set a cron job to ping a couple of other servers on the > LAN and execute the script and restart networking should the pings fail. > > > > This is a patch, not a fix. Have you tested on kernel 4.0? > > I've not tested with 4.0. This machine needs to be rock solid, it will be > Debian stable all the way, 4.x will only get on this machine when stable is > updated to that kernel. > > > > Alternatively, try to get yourself an Intel NIC that works with the igb > >> driver (don't get an Intel NIC that needs the e1000e driver) to replace > >> the hardlock-prone bcm5720 + tg3 combination. > > > > I ended up with an intel NIC instead, but with the e1000e driver. > > What's wrong with the e1000e driver by the way, please update. Thank > > you > > You'll have to hope Henrique is still following this, I don't have an > answer. > > Just thinking out-loud here: I've got an identical server with FreeNAS > installed, that's never disappeared off the network. Also I've had a server > for about 5 years at home with the same on-board NIC, (different mobo), > that's never locked up either, but I was able to force it to lock up with > "/etc/init.d/networking restart". It seems that, at home at least, I've > been fortunate so far. WRT to the FreeNAS, I have no idea how that's > driving the NIC, listing the modules there doesn't show anything I > recognise, and I've minimal experience with *BSD. > > -- > Justin C, by the sea. > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > https://lists.debian.org/a1e820dd-50c4-4708-8816-f9506ad1c...@masonsmusic.co.uk > >
