Re: kern/52211: vioif stops on dmamap load error

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

On 2017/05/11 17:20, J. Hannken-Illjes wrote:
> The following reply was made to PR kern/52211; it has been noted by GNATS.
>
> From: "J. Hannken-Illjes" <hannken%eis.cs.tu-bs.de@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Cc:
> Subject: Re: kern/52211: vioif stops on dmamap load error
> Date: Thu, 11 May 2017 10:18:09 +0200
>
>   > On 11. May 2017, at 10:10, Masanobu SAITOH <msaitoh%execsw.org@localhost> wrote:
>   >
>   >   Coudl you show me the output of ifconfig vioif0?
>   
>   vioif0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
>   	address: XX:XX:XX:XX:XX:XX
>   	inet XXX.XXX.XXX.XXX netmask 0xffffff00 broadcast XXX.XXX.XXX.255
>   	inet6 fe80::XXXX:XXXX:XXXX:XXXX%vioif0 prefixlen 64 scopeid 0x1
>   	inet6 XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX prefixlen 64

Yes, it has neither TSO nor JUMBO_MTU.

If a lof of mbuf chain is a normal case for vioif(4) it would
worth to try m_defrag(), but I suspect it's not a normal case
and it's caused by a bug in vioif or the upper layer.

>   --
>   J. Hannken-Illjes - hannken%eis.cs.tu-bs.de@localhost - TU Braunschweig (Germany)
>   


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