From owner-freebsd-current@freebsd.org Sat Jul 20 17:08:40 2019 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 37733C2B9B; Sat, 20 Jul 2019 17:08:40 +0000 (UTC) (envelope-from pkelsey@gmail.com) Received: from mail-io1-f49.google.com (mail-io1-f49.google.com [209.85.166.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A4F488F4B; Sat, 20 Jul 2019 17:08:39 +0000 (UTC) (envelope-from pkelsey@gmail.com) Received: by mail-io1-f49.google.com with SMTP id e20so34656278iob.9; Sat, 20 Jul 2019 10:08:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qwftr7hfAoPOc7UkDypV8VZ/E91Lm1eNDERdVKv3z+s=; b=O8eamPKdMczPcGKP0rdjwb2mBm4icndLorUJmKFLR+h1rPVDhplKCtZITcditw9rVN paV98KUt7u+YdnjG6Z9pDq0B/UmLs+kioukmghBoe0H10BjdQJV5CKJ+X879aYQNvxkM I5dZpij9DIHpmd1ylM1Tc8i50mEG7o5ZxBd1vPiao3XR0sWcqPfryAN2fF8Sgl360kbq j3VmVy+rW6WSGSQzpm+C7ua+kxuzzNcXjt0Xbn4zJLxytVA3NDRBON1v4UDxvcdE2V71 HlWh2Y1i+VP2XWHk5ZPD6VQ3gCaC+GWiNkgwS19pJOFK4qhHaJIeDfCEqwHYNlTCsLbt 5Xfw== X-Gm-Message-State: APjAAAVPJpxPbUTepA7E3ihUvJaJYnFj74zvRV8wDh22Vj5CQx28AoLV +XA/9vQZfXcoKJx26dIj7+jjLCCTu83h9uS2IlAbGEIW X-Google-Smtp-Source: APXvYqz6p5R6RvuZkpPtJ2KRUp57i0OsyvH7L6v4Mo7ls6F0s/B4aw4HArW7jm8c1rzFcLrqMLv3S04tYTytCOTQvyg= X-Received: by 2002:a02:ad15:: with SMTP id s21mr64118056jan.47.1563642512862; Sat, 20 Jul 2019 10:08:32 -0700 (PDT) MIME-Version: 1.0 References: <9c509f7b-8294-d2fe-ea3e-f10fd51f5736@FreeBSD.org> In-Reply-To: <9c509f7b-8294-d2fe-ea3e-f10fd51f5736@FreeBSD.org> From: Patrick Kelsey Date: Sat, 20 Jul 2019 13:08:21 -0400 Message-ID: Subject: Re: vmx0: watchdog timeout on queue 2, no interrupts on BSP To: Andriy Gapon Cc: freebsd-net@freebsd.org, FreeBSD Current X-Rspamd-Queue-Id: 8A4F488F4B X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of pkelsey@gmail.com designates 209.85.166.49 as permitted sender) smtp.mailfrom=pkelsey@gmail.com X-Spamd-Result: default: False [-5.51 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.88)[-0.877,0]; FORGED_SENDER(0.30)[pkelsey@freebsd.org,pkelsey@gmail.com]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[pkelsey@freebsd.org,pkelsey@gmail.com]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MIME_TRACE(0.00)[0:+,1:+]; DMARC_NA(0.00)[freebsd.org]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[49.166.85.209.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.62)[ip: (-7.18), ipnet: 209.85.128.0/17(-3.44), asn: 15169(-2.43), country: US(-0.05)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2019 17:08:40 -0000 On Fri, Jul 19, 2019 at 10:07 AM Andriy Gapon wrote: > > Recently we experienced a strange problem. > We noticed a lot of these messages in the logs: > vmx0: watchdog timeout on queue 2 > (always queue 2) > Also, we noticed that connections to some end points did not work at all > while others worked without problems. I assume that that was because > specific flows got assigned to that queue 2. > > Further investigation has shown that none of interrupts assigned to the > BSP has ever fired (since boot, of course). That included vmx0:rx2 and > vmx0:tx2. But also interrupts for other drivers as well. > > Trying to get more information I rebooted the system and the problem > disappeared. > > Has anyone seen anything like that? > Any thoughts on possible causes? > Any suggestions what to check if/when the problem reoccurs? > > Thanks! > > If you are running head at or after r347221 or stable/12 at or after r349112, then this could be due to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239118 (see Comment 4 - short story is that an iflib change has broken the vmx driver). -Patrick