NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

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



The following reply was made to PR kern/52876; it has been noted by GNATS.

From: clare%csel.org@localhost
To: SAITOH Masanobu <msaitoh%execsw.org@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/52876: The vlan(4) over wm(4) behaves something strange
Date: Sat, 30 Dec 2017 11:12:38 +0900

 On Fri, 29 Dec 2017 12:27:01 +0900
 SAITOH Masanobu <msaitoh%execsw.org@localhost> wrote:
 
 > 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
 
 I couldn't find any messages generated from wm in /var/log/messages.
 
 > 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.
 
 I placed the log to following URL:
 https://www.csel.org/netbsd/pr/52876/vmstat-ev-wm-20171230.txt
 
 
 -- 
 Shinichi Doyashiki <clare%csel.org@localhost>
 


Home | Main Index | Thread Index | Old Index