Re: kern/52876: The vlan(4) over wm(4) behaves something strange

[SAITOH Masanobu <msaitoh%execsw.org@localhost>]

Hi.

On 2017/12/29 10:05, clare%csel.org@localhost wrote:
> The following reply was made to PR kern/52876; it has been noted by GNATS.
> 
> From: clare%csel.org@localhost
> To: gnats-bugs%NetBSD.org@localhost
> Cc: 
> Subject: Re: kern/52876: The vlan(4) over wm(4) behaves something strange
> Date: Fri, 29 Dec 2017 10:02:55 +0900
> 
>  disabling TSO is workaround of the problem.
>  
>  -- 
>  Shinichi Doyashiki <clare%csel.org@localhost>
>  
> 

Have you ever check /var/log/message?
One of possibilities is:

>                 error = bus_dmamap_load_mbuf(sc->sc_dmat, dmamap, m0,
>                     BUS_DMA_WRITE | BUS_DMA_NOWAIT);
>                 if (error) {
>                         if (error == EFBIG) {
>                                 WM_Q_EVCNT_INCR(txq, txdrop);
>                                 log(LOG_ERR, "%s: Tx packet consumes too many "
>                                     "DMA segments, dropping...\n",
>                                     device_xname(sc->sc_dev));
>                                 wm_dump_mbuf_chain(sc, m0);
>                                 m_freem(m0);
>                                 continue;
>                         }
>                         /* Short on resources, just stop for now. */
>                         DPRINTF(WM_DEBUG_TX,
>                             ("%s: TX: dmamap load failed: %d\n",
>                             device_xname(sc->sc_dev), error));
>                         break;
>                 }

This error is by log(LOG_ERR), so it's not printed in dmesg but
in /var/log/message

And, could you test with "options WM_EVENT_COUNTERS" in your
kernel config and show me the output of "vmstat -ev |grep wm"
after problem occurred.

 Thanks in advance.

-- 
-----------------------------------------------
                SAITOH Masanobu (msaitoh%execsw.org@localhost
                                 msaitoh%netbsd.org@localhost)