Re: Problems with em0 driver after upgrade to r303832

Bit more testing on this, and I think it was a false alarm and my problem was actually hardware related. Moving to a different PCI slot stopped the problem happening. The original ethernet card is now dead however, and the slow has burn marks on it - which makes me think ,it isnt software really

Re: Problems with em0 driver after upgrade to r303832

> On 9 August 2016, at 04:40, Kurt Jaeger wrote: > > Hi! > >> I upgraded my local machine to the above revision a few days ago. Since then >> I have seen the local em0 card locking up and getting he following >> messages in dmesg >> >> em0: Watchdog timeout -- resetting >>

Re: Problems with em0 driver after upgrade to r303832

Hi Unfortunately, the revision shown by `uname -a` etc. is NOT the actual newest revision of the branch, because the set of revision numbers is exactly the same throuout every branches. # It relies on when he / she `svn(lite) up`'ed and gets newest rev. So the easiest way to determine the

Re: Problems with em0 driver after upgrade to r303832

> > I thought it was the physical card, but I have swapped this out > > for a completely different one and the problems remain. > > What does pciconf -lvb display for the PCI IDs for this card ? I have just dropped a third card into the machine 9I need to get some work done unfortnately) - for

Re: Problems with em0 driver after upgrade to r303832

Hi! > I upgraded my local machine to the above revision a few days ago. Since then > I have seen the local em0 card locking up and getting he following > messages in dmesg > > em0: Watchdog timeout -- resetting > em0: link state changed to DOWN > em0: link state changed to UP > > > I thought