Re: Kernel panic with fresh current, probably nfs related

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512



On 08/23/15 18:36, Yonghyeon PYUN wrote:
> Index: sys/dev/e1000/if_em.c 
> ===================================================================
>
> 
- --- sys/dev/e1000/if_em.c	(revision 287087)
> +++ sys/dev/e1000/if_em.c	(working copy) _at__at_ -3044,7 +3044,7 _at__at_
> em_setup_interface(device_t dev, struct adapter *a 
> if_setioctlfn(ifp, em_ioctl); if_setgetcounterfn(ifp,
> em_get_counter); /* TSO parameters */ -	ifp->if_hw_tsomax =
> EM_TSO_SIZE; +	ifp->if_hw_tsomax = IP_MAXPACKET; 
> ifp->if_hw_tsomaxsegcount = EM_MAX_SCATTER; 
> ifp->if_hw_tsomaxsegsize = EM_TSO_SEG_SIZE;


Seems to work. However, I cannot reproduce the user panic in the first
place.  What's the scenario that seems to work here?  NFS seems happy
with/without the patch so I'm not confident in anything we are doing her
e.

sean
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQF8BAEBCgBmBQJV21/UXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kjswH/jL+GwJmehiEZVSUdjCMhYkK
sk10m+y8s64yrU5RuR8LqVd4RabmiVqmH8Xh1QKRkLpZT21AsYJVcBWJ6U4/iCMe
PqeszYGn9xGQ2+Weew/3mHmhdEO+biyK2ECaN5F9qfWhipeuAxd7a9c2OIAWY9FN
WtRQEgljkJyuktT16i5FXcmyL2RsynN18bDYKi/W5A/AKGJDpESBLISl0ye/wAA0
ZMr01tS4sgGalx5VZPaA46PRZOTDORz4gzKP7xfOo2Mpyp9xK3AS7FqpI7DZegmf
NOr3bploKqpjgmJHQP5pw9i464fsoDc3bdV66ktrzl1/aJ00Vk5cYCT8RR9raJ8=
=AN4K
-----END PGP SIGNATURE-----