Kernel panic with fresh current, probably nfs related

2015-08-22 Thread Joel Dahl
Hi, I hit a kernel panic running a fresh -CURRENT today. This machine is my home NFS server and it exports src and obj to a bunch of other machines. During an installkernel on one of the other machines (using the src and obj exports from the NFS server) the NFS server kernel paniced. I took a qui

Re: Kernel panic with fresh current, probably nfs related

2015-08-22 Thread Rick Macklem
Joel Dahl wrote: > Hi, > > I hit a kernel panic running a fresh -CURRENT today. This machine is my home > NFS > server and it exports src and obj to a bunch of other machines. During an > installkernel on one of the other machines (using the src and obj exports > from > the NFS server) the NFS ser

Re: Kernel panic with fresh current, probably nfs related

2015-08-22 Thread Rick Macklem
Joel Dahl wrote: > Hi, > > I hit a kernel panic running a fresh -CURRENT today. This machine is my home > NFS > server and it exports src and obj to a bunch of other machines. During an > installkernel on one of the other machines (using the src and obj exports > from > the NFS server) the NFS ser

Re: Kernel panic with fresh current, probably nfs related

2015-08-22 Thread Sean Bruno
> I'm going to guess that you're using an "em" net driver, since that is the > only one that sets if_hw_tsomax > IP_MAXPACKET (65535) from what I can see. > > Sean, EM_TSO_SIZE is defined as (65535 + sizeof(struct ether_vlan_header)), > which makes it > IP_MAXPACKET. The value of if_hw_tsomax m

Re: Kernel panic with fresh current, probably nfs related

2015-08-23 Thread Yonghyeon PYUN
On Sat, Aug 22, 2015 at 11:25:58AM -0700, Sean Bruno wrote: > > > > > I'm going to guess that you're using an "em" net driver, since that is the > > only one that sets if_hw_tsomax > IP_MAXPACKET (65535) from what I can see. > > > > Sean, EM_TSO_SIZE is defined as (65535 + sizeof(struct ether_v

Re: Kernel panic with fresh current, probably nfs related

2015-08-24 Thread Joel Dahl
On Sat, Aug 22, 2015 at 08:57:40AM -0400, Rick Macklem wrote: > Joel Dahl wrote: > > Hi, > > > > I hit a kernel panic running a fresh -CURRENT today. This machine is my home > > NFS > > server and it exports src and obj to a bunch of other machines. During an > > installkernel on one of the other

Re: Kernel panic with fresh current, probably nfs related

2015-08-24 Thread Sean Bruno
-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) @@

Re: Kernel panic with fresh current, probably nfs related

2015-08-25 Thread Joel Dahl
On Mon, Aug 24, 2015 at 11:18:00AM -0700, Sean Bruno wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > > > On 08/23/15 18:36, Yonghyeon PYUN wrote: > > Index: sys/dev/e1000/if_em.c > > === > > > > > - --- sys/dev/e100

Re: Kernel panic with fresh current, probably nfs related

2015-08-25 Thread Sean Bruno
On 08/25/15 12:10, Joel Dahl wrote: >> > 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. > I see several patches

Re: Kernel panic with fresh current, probably nfs related

2015-08-29 Thread Joel Dahl
On Tue, Aug 25, 2015 at 12:55:02PM -0700, Sean Bruno wrote: > > > On 08/25/15 12:10, Joel Dahl wrote: > >> > 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

Re: Kernel panic with fresh current, probably nfs related

2015-08-31 Thread Sean Bruno
On 08/29/15 00:38, Joel Dahl wrote: > On Tue, Aug 25, 2015 at 12:55:02PM -0700, Sean Bruno wrote: >> >> >> On 08/25/15 12:10, Joel Dahl wrote: > 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 >