wm(4): failed to aquire semaphore

Discussion:

(too old to reply)

Manuel Bouyer

2020-10-22 10:48:16 UTC

Hello,
I have an older desktop system with:
wm0 at pci0 dev 25 function 0: 82801I (AMT) LAN Controller (rev. 0x02)
wm0: interrupting at msi0 vec 0
wm0: PCI-Express bus
wm0: 2048 words FLASH, version 1.1.1
wm0: Ethernet address 00:1a:a0:d5:a0:0d
wm0: 0x2a4480<FLASH,IOH_VALID,PCIE,ASF_FIRM,AMT,WOL>
igphy0 at wm0 phy 1: i82566 10/100/1000 media interface, rev. 0
igphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto

running netbsd 9.1.
Every 5mn, I see in dmesg:
[ 78053.063361] wm0: failed to acquire semaphore
[ 78053.073383] wm0: wm_gmii_i82544_readreg: failed to get semaphore
[ 78353.800448] wm0: failed to acquire semaphore
[ 78353.800448] wm0: wm_gmii_i82544_readreg: failed to get semaphore
[ 78654.537999] wm0: failed to acquire semaphore
[ 78654.537999] wm0: wm_gmii_i82544_readreg: failed to get semaphore
[ 78955.275254] wm0: failed to acquire semaphore
[ 78955.275254] wm0: wm_gmii_i82544_readreg: failed to get semaphore
[ 79256.013287] wm0: failed to acquire semaphore
[ 79256.013287] wm0: wm_gmii_i82544_readreg: failed to get semaphore

and network traffic stops for a few seconds.

Does it ring a bell to someone ? Is it a hardware failure or software issue ?

--
Manuel Bouyer <***@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

SAITOH Masanobu

2020-10-22 11:00:23 UTC

Permalink

Post by Manuel Bouyer
Hello,
wm0 at pci0 dev 25 function 0: 82801I (AMT) LAN Controller (rev. 0x02)
wm0: interrupting at msi0 vec 0
wm0: PCI-Express bus
wm0: 2048 words FLASH, version 1.1.1
wm0: Ethernet address 00:1a:a0:d5:a0:0d
wm0: 0x2a4480<FLASH,IOH_VALID,PCIE,ASF_FIRM,AMT,WOL>
igphy0 at wm0 phy 1: i82566 10/100/1000 media interface, rev. 0
igphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
running netbsd 9.1.
[ 78053.063361] wm0: failed to acquire semaphore
[ 78053.073383] wm0: wm_gmii_i82544_readreg: failed to get semaphore
[ 78353.800448] wm0: failed to acquire semaphore
[ 78353.800448] wm0: wm_gmii_i82544_readreg: failed to get semaphore
[ 78654.537999] wm0: failed to acquire semaphore
[ 78654.537999] wm0: wm_gmii_i82544_readreg: failed to get semaphore
[ 78955.275254] wm0: failed to acquire semaphore
[ 78955.275254] wm0: wm_gmii_i82544_readreg: failed to get semaphore
[ 79256.013287] wm0: failed to acquire semaphore
[ 79256.013287] wm0: wm_gmii_i82544_readreg: failed to get semaphore
and network traffic stops for a few seconds.
Does it ring a bell to someone ? Is it a hardware failure or software issue ?

Does it work without any problem on 9.0?
If so, could you bisect wm's changes between 9.0 and 9.1?

--
-----------------------------------------------
SAITOH Masanobu (***@execsw.org
***@netbsd.org)

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

Manuel Bouyer

2020-10-22 11:11:02 UTC

Permalink

Post by SAITOH Masanobu

Does it work without any problem on 9.0?
If so, could you bisect wm's changes between 9.0 and 9.1?

Before upgrading to 9.1 is was running a 9.0_STABLE kernel from early may.
It had the same issue.

The full story is:
I set up NetBSD on a Dell optiplex 755 early may, it went witout problems
and did the job, running the same kernel since install.
last week-end the hardware died (probably a power supply issue), so I took
the hard drive and plugged it in another optiplex 755, which may not be
strictly identical (different manuf. dates). This problem showed up
immediately. The upgrade to 9.1 was becase of it, but it didn't
change anything.

Next I can try another optiplex 755, I have several of them

Manuel Bouyer

2020-10-22 11:14:39 UTC

Permalink

Some errors are not printed by printf() but by log().
Could you check your machine's /var/log/message?

Here is a full sequence:
Oct 22 13:06:01 fablabproto /netbsd: [ 80458.9641673] wm0: wm_gmii_i82544_readre
g: failed to get semaphore
Oct 22 13:06:02 fablabproto ntpd[391]: Deleting interface #344 wm0, fe80::21a:a0
ff:fed5:a00d%1#123, interface stats: received=0, sent=0, dropped=0, active_time=
296 secs
Oct 22 13:06:06 fablabproto ntpd[391]: Listen normally on 345 wm0 [fe80::21a:a0f
f:fed5:a00d%1]:123
Oct 22 13:11:06 fablabproto /netbsd: [ 80759.6911701] wm0: failed to acquire sem
aphore
Oct 22 13:11:06 fablabproto /netbsd: [ 80759.6911701] wm0: wm_gmii_i82544_readre
g: failed to get semaphore
Oct 22 13:11:06 fablabproto /netbsd: [ 80760.7016063] wm0: failed to acquire sem
aphore
Oct 22 13:11:06 fablabproto /netbsd: [ 80760.7016063] wm0: wm_gmii_i82544_readre
g: failed to get semaphore
Oct 22 13:11:06 fablabproto /netbsd: [ 80761.7020382] wm0: failed to acquire semaphore
Oct 22 13:11:06 fablabproto /netbsd: [ 80761.7020382] wm0: wm_gmii_i82544_readreg: failed to get semaphore
ct 22 13:11:06 fablabproto /netbsd: [ 80762.7024703] wm0: failed to acquire semaphore
Oct 22 13:11:06 fablabproto /netbsd: [ 80762.7024703] wm0: wm_gmii_i82544_readreg: failed to get semaphore
Oct 22 13:11:06 fablabproto /netbsd: [ 80763.7029020] wm0: failed to acquire semaphore
Oct 22 13:11:06 fablabproto /netbsd: [ 80763.7029020] wm0: wm_gmii_i82544_readreg: failed to get semaphore
Oct 22 13:11:06 fablabproto /netbsd: [ 80764.7033339] wm0: failed to acquire semaphore
Oct 22 13:11:06 fablabproto /netbsd: [ 80764.7033339] wm0: wm_gmii_i82544_readreg: failed to get semaphore
Oct 22 13:11:10 fablabproto /netbsd: [ 80765.7037658] wm0: failed to acquire semaphore
Oct 22 13:11:10 fablabproto /netbsd: [ 80765.7037658] wm0: wm_gmii_i82544_readreg: failed to get semaphore
Oct 22 13:11:10 fablabproto /netbsd: [ 80766.7041977] wm0: failed to acquire semaphore
Oct 22 13:11:10 fablabproto /netbsd: [ 80766.7041977] wm0: wm_gmii_i82544_readreg: failed to get semaphore
Oct 22 13:11:10 fablabproto /netbsd: [ 80767.7046296] wm0: failed to acquire semaphore
Oct 22 13:11:10 fablabproto /netbsd: [ 80767.7046296] wm0: wm_gmii_i82544_readreg: failed to get semaphore
Oct 22 13:11:10 fablabproto /netbsd: [ 80768.7050614] wm0: failed to acquire semaphore
Oct 22 13:11:10 fablabproto /netbsd: [ 80768.7050614] wm0: wm_gmii_i82544_readreg: failed to get semaphore
Oct 22 13:11:11 fablabproto ntpd[391]: Deleting interface #345 wm0, fe80::21a:a0ff:fed5:a00d%1#123, interface stats: received=0, sent=0, dropped=0, active_time=296 secs
Oct 22 13:11:14 fablabproto ntpd[391]: Listen normally on 346 wm0 [fe80::21a:a0ff:fed5:a00d%1]:123
Oct 22 13:11:18 fablabproto ntpd[391]: Listen normally on 347 wm0 10.0.0.1:123

e.g.

log(LOG_ERR,
"%s: device timeout (txfree %d txsfree %d txnext %d)\n",
device_xname(sc->sc_dev), txq->txq_free, txq->txq_sfree,
txq->txq_next);

No "device timeout" there

SAITOH Masanobu

2020-10-22 11:05:02 UTC

Permalink

Post by SAITOH Masanobu

Does it work without any problem on 9.0?
If so, could you bisect wm's changes between 9.0 and 9.1?

Some errors are not printed by printf() but by log().
Could you check your machine's /var/log/message?
e.g.

Post by SAITOH Masanobu
log(LOG_ERR,
"%s: device timeout (txfree %d txsfree %d txnext %d)\n",
device_xname(sc->sc_dev), txq->txq_free, txq->txq_sfree,
txq->txq_next);