Re: Problems with em0 driver after upgrade to r303832

[Pete French]

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 ;) Appologies for the noise, it just
coincided with an upgrade and I didnt expect the slot to be at fault after
trying three cards (though that was the logical next step)

-pete.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with em0 driver after upgrade to r303832

[Doug Hardie]

> 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
>> em0: link state changed to DOWN
>> em0: link state changed to UP
>> 
>> 
>> 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 ?
> 
> If you use r303832, this is CURRENT (12.x) ? Then maybe the
> question should be discussed on curr...@freebsd.org.


I am seeing this on 11.0-BETA3/4.

bge0@pci0:3:0:0:class=0x02 card=0x168614e4 chip=0x168614e4 rev=0x01 
hdr=0x00
vendor = 'Broadcom Corporation'
device = 'NetXtreme BCM57766 Gigabit Ethernet PCIe'
class  = network
subclass   = ethernet
bar   [10] = type Prefetchable Memory, range 64, base 0xa070, size 
65536, enabled
bar   [18] = type Prefetchable Memory, range 64, base 0xa071, size 
65536, enabled

It does not occur on another machine with:

bge0@pci0:2:0:0:class=0x02 card=0x16b414e4 chip=0x16b414e4 rev=0x10 
hdr=0x00
vendor = 'Broadcom Corporation'
device = 'NetXtreme BCM57765 Gigabit Ethernet PCIe'
class  = network
subclass   = ethernet
bar   [10] = type Prefetchable Memory, range 64, base 0x9040, size 
65536, enabled
bar   [18] = type Prefetchable Memory, range 64, base 0x9041, size 
65536, enabled

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with em0 driver after upgrade to r303832

[Tomoaki AOKI]

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 actual revision is, for this case,
to look into the pipermail archive of freebsd-src-stable10 and look for
the maximum nunber NOT EXCEEDING the revision shown.

This case, the actual revision Pete has should be r303827.

On Tue, 9 Aug 2016 13:40:23 +0200
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
> > em0: link state changed to DOWN
> > em0: link state changed to UP
> > 
> > 
> > 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 ?
> 
> If you use r303832, this is CURRENT (12.x) ? Then maybe the
> question should be discussed on curr...@freebsd.org.
> 
> -- 
> p...@opsec.eu+49 171 3101372 4 years to 
> go !
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 


-- 
Tomoaki AOKI
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with em0 driver after upgrade to r303832

[Pete French]

> > 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 this the output is 

em0@pci0:3:2:0: class=0x02 card=0x13768086 chip=0x107c8086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '82541PI Gigabit Ethernet Controller'
class  = network
subclass   = ethernet
bar   [10] = type Memory, range 32, base 0xfebc, size 131072, enabled
bar   [14] = type Memory, range 32, base 0xfeba, size 131072, enabled
bar   [18] = type I/O Port, range 32, base 0xe400, size 64, enabled

I will let you know if it locks up, or if it doesnt -I swapped
PCI slots as well in case this is actually a hardware issue.

> If you use r303832, this is CURRENT (12.x) ? Then maybe the
> question should be discussed on curr...@freebsd.org.

Its 10.3-STABLE according to uname -a

-pete.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Problems with em0 driver after upgrade to r303832

[Kurt Jaeger]

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 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 ?

If you use r303832, this is CURRENT (12.x) ? Then maybe the
question should be discussed on curr...@freebsd.org.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Problems with em0 driver after upgrade to r303832

[Pete French]

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 it was the physical card, but I have swapped this out
for a completely different one and the problems remain. Am am concerned
as we run a lot of em0 cards in production and started upgrading those too,
as I had not associated the problem with the software upgrade until just now.

Any siggestions ? Am reluctant to start rolling this back, and it is
only showing up on one machine for now - is anyone else seeing this ?

-pete.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"