New iflib/e1000 panic (vlan) report [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-08-10 Thread Harry Schmalzbauer
Am 08.05.2018 um 11:52 schrieb Kevin Bowling: On Tue, May 8, 2018 at 2:43 AM, Harry Schmalzbauer wrote: Bezüglich Kevin Bowling's Nachricht vom 08.05.2018 11:26 (localtime): iflib in stable/11 only affects bnxt at this time. You should try out HEAD and let us know for the rest of your questio

'devctl detach' panic after resume [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-23 Thread Harry Schmalzbauer
Am 08.05.2018 um 11:52 schrieb Kevin Bowling: On Tue, May 8, 2018 at 2:43 AM, Harry Schmalzbauer wrote: Bezüglich Kevin Bowling's Nachricht vom 08.05.2018 11:26 (localtime): iflib in stable/11 only affects bnxt at this time. You should try out HEAD and let us know for the rest of your questio

Re: iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-20 Thread Harry Schmalzbauer
Am 11.05.2018 um 19:24 schrieb Harry Schmalzbauer: Bezüglich Stephen Hurd's Nachricht vom 10.05.2018 21:55 (localtime): Ok, the review is updated with the EBR. If you can update your tree to r333466 or newer, apply the patch and retest, that would be great. It seems to be working here. I took

Re: iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-11 Thread Harry Schmalzbauer
Bezüglich Stephen Hurd's Nachricht vom 10.05.2018 21:55 (localtime): > Ok, the review is updated with the EBR. If you can update your tree to > r333466 or newer, apply the patch and retest, that would be great. It > seems to be working here. I took out the sys/net/if.c, sys/net/if_var.h and sys/

Re: iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-10 Thread Stephen Hurd
Ok, the review is updated with the EBR. If you can update your tree to r333466 or newer, apply the patch and retest, that would be great. It seems to be working here. On Thu, May 10, 2018 at 2:29 PM, Harry Schmalzbauer wrote: > Bezüglich Stephen Hurd's Nachricht vom 10.05.2018 20:07 (localtime

Re: iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-10 Thread Harry Schmalzbauer
Bezüglich Stephen Hurd's Nachricht vom 10.05.2018 20:07 (localtime): > No need to test the latest revision unless/until you get a LOR or a > panic (both should be possible with the revision you currently have). > With the recent addition of a simple EBR API, mmacy@ is working on a > better solutio

Re: iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-10 Thread Stephen Hurd
No need to test the latest revision unless/until you get a LOR or a panic (both should be possible with the revision you currently have). With the recent addition of a simple EBR API, mmacy@ is working on a better solution. If possible, it would be great to have you re-test it once that is up. O

Re: iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-10 Thread Harry Schmalzbauer
Bezüglich Harry Schmalzbauer's Nachricht vom 10.05.2018 19:54 (localtime): … > Please excuse that I'm not familar with the phabricator and just did > "raw diff download" after briefly flying over the comments. > According to st_mtime this was on May 9th, 08:14:02 UTC (10:14 local > (CEST) time). >

Re: iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-10 Thread Harry Schmalzbauer
Bezüglich Stephen Hurd's Nachricht vom 08.05.2018 20:58 (localtime): > Can you test the review here: https://reviews.freebsd.org/D15355 > > It looks like there are two different locks protecting the same data > everywhere but in lagg_ioctl(). This is a rough first-pass, and there may > be some li

Re: iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-08 Thread Stephen Hurd
Can you test the review here: https://reviews.freebsd.org/D15355 It looks like there are two different locks protecting the same data everywhere but in lagg_ioctl(). This is a rough first-pass, and there may be some lingering recursion and performance regressions with it. On Tue, May 8, 2018 at

Re: iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-08 Thread Harry Schmalzbauer
Bezüglich Sean Bruno's Nachricht vom 08.05.2018 18:44 (localtime): > > > On 05/08/18 10:23, Harry Schmalzbauer wrote: >> Bezüglich Kevin Bowling's Nachricht vom 08.05.2018 11:52 (localtime): >> … But if the simple iflib/hw-support test with kawela+hartwell helps I'm happy to do. >>> >>>

iflib-if_igb tests with HEAD success [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-08 Thread Harry Schmalzbauer
Bezüglich Kevin Bowling's Nachricht vom 08.05.2018 11:52 (localtime): > On Tue, May 8, 2018 at 2:43 AM, Harry Schmalzbauer wrote: … >> But if the simple iflib/hw-support test with kawela+hartwell helps I'm >> happy to do. > > At this point it would be helpful, we think e1000 is nearing pretty > g

Re: iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-08 Thread Sean Bruno
On 05/08/18 10:23, Harry Schmalzbauer wrote: > Bezüglich Kevin Bowling's Nachricht vom 08.05.2018 11:52 (localtime): > … >>> But if the simple iflib/hw-support test with kawela+hartwell helps I'm >>> happy to do. >> >> At this point it would be helpful, we think e1000 is nearing pretty >> good sh

iflib-if_em tests with HEAD and lagg panic [Was: Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys]

2018-05-08 Thread Harry Schmalzbauer
Bezüglich Kevin Bowling's Nachricht vom 08.05.2018 11:52 (localtime): … >> But if the simple iflib/hw-support test with kawela+hartwell helps I'm >> happy to do. > > At this point it would be helpful, we think e1000 is nearing pretty > good shape and I need to become familiar with any outstanding

Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys

2018-05-08 Thread Kevin Bowling
On Tue, May 8, 2018 at 2:43 AM, Harry Schmalzbauer wrote: > Bezüglich Kevin Bowling's Nachricht vom 08.05.2018 11:26 (localtime): >> iflib in stable/11 only affects bnxt at this time. >> >> You should try out HEAD and let us know for the rest of your questions. > > Ic, sorry for the noise – should

Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys

2018-05-08 Thread Harry Schmalzbauer
Bezüglich Kevin Bowling's Nachricht vom 08.05.2018 11:26 (localtime): > iflib in stable/11 only affects bnxt at this time. > > You should try out HEAD and let us know for the rest of your questions. Ic, sorry for the noise – should have read the commits before wasting others' time :-( Thanks for

Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys

2018-05-08 Thread Kevin Bowling
iflib in stable/11 only affects bnxt at this time. You should try out HEAD and let us know for the rest of your questions. Regards, Kevin On Tue, May 8, 2018 at 2:19 AM, Harry Schmalzbauer wrote: > Bezüglich Stephen Hurd's Nachricht vom 07.05.2018 23:42 (localtime): >> Author: shurd >> Date: M

Re: svn commit: r333338 - in stable/11/sys: dev/bnxt kern net sys

2018-05-08 Thread Harry Schmalzbauer
Bezüglich Stephen Hurd's Nachricht vom 07.05.2018 23:42 (localtime): > Author: shurd > Date: Mon May 7 21:42:22 2018 > New Revision: 38 > URL: https://svnweb.freebsd.org/changeset/base/38 > > Log: > Merge iflib changes to 11-STABLE > > MFC r300147, r300153, r300154, r300215, r30156