Re: Stability of 11.1S

[Dewayne Geraghty]

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: [HEADS UP] - OFED/RDMA stack update

[Navdeep Parhar]

iw_cxgbe still doesn't build in the branch because of some socket
changes in head that are not in 11.  I need to add the 11 equivalent of
the dequeue_socket code to iw_cxgbe to get it to compile, and then try
it to see if it actually works.

Regards,
Navdeep

On 03/22/2018 04:36, Meny Yossefi wrote:
> Hi Navdeep, 
> 
> What's the current iWARP status on the project branch? 
> If it's ready we'd like to merge it to FreeBSD11-STABLE immediately. 
> 
> -Meny
> 
> 
> -Original Message-
> From: Navdeep Parhar [mailto:npar...@gmail.com] On Behalf Of Navdeep Parhar
> Sent: Tuesday, March 20, 2018 10:08 PM
> To: Hans Petter Selasky ; Konstantin Belousov 
> ; 'freebsd-infinib...@freebsd.org' 
> ; freebsd-drivers 
> ; Meny Yossefi ; 
> 'FreeBSD-stable@FreeBSD.org' ; freebsd-arch 
> 
> Subject: Re: [HEADS UP] - OFED/RDMA stack update
> 
> On 03/17/2018 13:03, Hans Petter Selasky wrote:
>> On 03/17/18 20:52, Navdeep Parhar wrote:
>>> Hold your horses.  Do you have confirmation from the affected party 
>>> that the shims are adequate for them?  I have been waiting for that 
>>> before looking at this branch.
>>
>> Hi Navdeep,
>>
>> Mellanox has received an API list from at least one party, and has 
>> taken the action to support all the required APIs.
>>
>>> Is the iw_cxgbe breakage a simple merge conflict as previously 
>>> discussed or do the shims require driver changes?
>>
>> It is a merge conflict. The code already compiles in 12-current.
> 
> I tried backing out r329391 and r329017 in a local copy and then was able to 
> merge r320418, r323082, and r326169 in that order without any conflicts.  But 
> iw_cxgbe/cm.c still doesn't compile in the projects branch because it has 
> some socket code that relies on some of glebius's changes available only in 
> head (I checked with him and they aren't MFC'able).  I'm trying to figure out 
> what to do about those.
> 
> And what about the cxgb breakage?  Is there any simple way to make an old 
> style driver work with the new stack?  T3 iw_cxgb in head was retired before 
> the ofed overhaul.
> 
> Regards,
> Navdeep
> 


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: panic: vdrop: holdcnt 0

[Warner Losh]

On Thu, Mar 22, 2018 at 7:37 AM, Eugene M. Zheganin 
wrote:

> Hello,
>
> On 22.03.2018 18:05, Eugene M. Zheganin wrote:
>
>> today I eventyally got "panic: vdrop: holdcnt 0" on an iSCSI host, on an
>> 11.1. Since I don't see any decent information on this - I just wanted to
>> ask - what this kind of panic generally mean ? And where do I go with this.
>> The only PR I see is about 9.[, and the author there got multiple
>> reproducing crashes, not just one.
>>
> To be more specific - here's a backtrace:
>
> Unread portion of the kernel message buffer:
> panic: vdrop: holdcnt 0
> cpuid = 11
> KDB: stack backtrace:
> #0 0x80aadac7 at kdb_backtrace+0x67
> #1 0x80a6bba6 at vpanic+0x186
> #2 0x80a6ba13 at panic+0x43
> #3 0x80b28739 at _vdrop+0x3e9
> #4 0x80b295d8 at vputx+0x2f8
> #5 0x80b38342 at vn_close1+0x182
> #6 0x82639d1a at ctl_be_block_ioctl+0x86a
> #7 0x82632bdc at ctl_ioctl+0x48c
> #8 0x8093ae38 at devfs_ioctl_f+0x128
> #9 0x80ac9415 at kern_ioctl+0x255
> #10 0x80ac914f at sys_ioctl+0x16f
> #11 0x80ee0394 at amd64_syscall+0x6c4
> #12 0x80ec39bb at Xfast_syscall+0xfb
> Uptime: 1d17h36m25s
>
> I also have the full crashdump and stuff, in case someone will show an
> interest. This is currently the only panic I got, but this
> happened on a production system, which is, by the way 11.1-RELEASE-p6
> r329259M, an iSCSI host and M stands for iscsi holdoff patch
> which was recently MFC'd, but appeared later than the 11.1 was released.


Can you try the latest -current with https://reviews.freebsd.org/D14792?

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: panic: vdrop: holdcnt 0

[Eugene M. Zheganin]

Hello,

On 22.03.2018 18:05, Eugene M. Zheganin wrote:
today I eventyally got "panic: vdrop: holdcnt 0" on an iSCSI host, on 
an 11.1. Since I don't see any decent information on this - I just 
wanted to ask - what this kind of panic generally mean ? And where do 
I go with this. The only PR I see is about 9.[, and the author there 
got multiple reproducing crashes, not just one.

To be more specific - here's a backtrace:

Unread portion of the kernel message buffer:
panic: vdrop: holdcnt 0
cpuid = 11
KDB: stack backtrace:
#0 0x80aadac7 at kdb_backtrace+0x67
#1 0x80a6bba6 at vpanic+0x186
#2 0x80a6ba13 at panic+0x43
#3 0x80b28739 at _vdrop+0x3e9
#4 0x80b295d8 at vputx+0x2f8
#5 0x80b38342 at vn_close1+0x182
#6 0x82639d1a at ctl_be_block_ioctl+0x86a
#7 0x82632bdc at ctl_ioctl+0x48c
#8 0x8093ae38 at devfs_ioctl_f+0x128
#9 0x80ac9415 at kern_ioctl+0x255
#10 0x80ac914f at sys_ioctl+0x16f
#11 0x80ee0394 at amd64_syscall+0x6c4
#12 0x80ec39bb at Xfast_syscall+0xfb
Uptime: 1d17h36m25s

I also have the full crashdump and stuff, in case someone will show an 
interest. This is currently the only panic I got, but this
happened on a production system, which is, by the way 11.1-RELEASE-p6 r329259M, 
an iSCSI host and M stands for iscsi holdoff patch
which was recently MFC'd, but appeared later than the 11.1 was released.

Eugene.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

panic: vdrop: holdcnt 0

[Eugene M. Zheganin]

Hi,


today I eventyally got "panic: vdrop: holdcnt 0" on an iSCSI host, on an 
11.1. Since I don't see any decent information on this - I just wanted 
to ask - what this kind of panic generally mean ? And where do I go with 
this. The only PR I see is about 9.[, and the author there got multiple 
reproducing crashes, not just one.



Thanks.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

RE: [HEADS UP] - OFED/RDMA stack update

[Meny Yossefi]

Hi Navdeep, 

What's the current iWARP status on the project branch? 
If it's ready we'd like to merge it to FreeBSD11-STABLE immediately. 

-Meny


-Original Message-
From: Navdeep Parhar [mailto:npar...@gmail.com] On Behalf Of Navdeep Parhar
Sent: Tuesday, March 20, 2018 10:08 PM
To: Hans Petter Selasky ; Konstantin Belousov 
; 'freebsd-infinib...@freebsd.org' 
; freebsd-drivers 
; Meny Yossefi ; 
'FreeBSD-stable@FreeBSD.org' ; freebsd-arch 

Subject: Re: [HEADS UP] - OFED/RDMA stack update

On 03/17/2018 13:03, Hans Petter Selasky wrote:
> On 03/17/18 20:52, Navdeep Parhar wrote:
>> Hold your horses.  Do you have confirmation from the affected party 
>> that the shims are adequate for them?  I have been waiting for that 
>> before looking at this branch.
> 
> Hi Navdeep,
> 
> Mellanox has received an API list from at least one party, and has 
> taken the action to support all the required APIs.
> 
>> Is the iw_cxgbe breakage a simple merge conflict as previously 
>> discussed or do the shims require driver changes?
> 
> It is a merge conflict. The code already compiles in 12-current.

I tried backing out r329391 and r329017 in a local copy and then was able to 
merge r320418, r323082, and r326169 in that order without any conflicts.  But 
iw_cxgbe/cm.c still doesn't compile in the projects branch because it has some 
socket code that relies on some of glebius's changes available only in head (I 
checked with him and they aren't MFC'able).  I'm trying to figure out what to 
do about those.

And what about the cxgb breakage?  Is there any simple way to make an old style 
driver work with the new stack?  T3 iw_cxgb in head was retired before the ofed 
overhaul.

Regards,
Navdeep

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"