From nobody Mon Aug 14 03:44:14 2023 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RPKyj02qRz4Tvg1 for ; Mon, 14 Aug 2023 03:44:29 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RPKyh581kz3FCy for ; Mon, 14 Aug 2023 03:44:28 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x102e.google.com with SMTP id 98e67ed59e1d1-26b41112708so1040228a91.3 for ; Sun, 13 Aug 2023 20:44:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; t=1691984667; x=1692589467; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=FvQ4dprH7EMStJL9isHR+vY2gyhC6JY9tlVyLmvy/EU=; b=SNikjMSl9R4R3fRPIhX2c1zMIaBHdViwPkTognK0nP2Sy/XvuAQINrSZS7UNguzEA+ /JPlPOiXpIRN/A7Z3MCvu9iOHwhI3IK+NuMUSnV8CXwIiu+ndNUXEN7JCMP/jMf+LfVf ktEbFDu4Dre8N/RDQCbmYSLH9OpzpecA/4L/U= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691984667; x=1692589467; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=FvQ4dprH7EMStJL9isHR+vY2gyhC6JY9tlVyLmvy/EU=; b=AjNX1davbTOt3XrO99elAW71DGP95bcxOydPblfv/1JogX9JMp6iRkTfxpMtdiuTeF l9BcRouWkPzFYkWWS9n1Fn7ak1jLk9wU1X+jSxyrOfAUw+Px9ZEHDs/BIvqY7cxh9vDa USjNed34DjORiS4t5Mzpi9wbgCJjBjJG0a/mqawzQkfQD6Z0sD5gp+AItKGebT1kE9kP TQuy+iBFDSG75dR4nb6qGFUIcbI8RR5wH59dXbAoj1OY6QtS3jA934HEWdaF7NI7ttBy S8KDMZVhkr1mE0W6s7VSYg/GuOVBku0TMA8GDynEPkb8sFFHLnq1g/ipqrrw/Qf5s0Lg KSAg== X-Gm-Message-State: AOJu0YzD2kgIzevD2pMJ5oUDALbyKp+csEJ6h4L31VLcnhEVbMS6qMek vUWgGdnU8vQWKv9STpB7x+8g9O6f4+pqtpAPfyix9G6y1t/Ly8w8 X-Google-Smtp-Source: AGHT+IFLbB6PCG7l8O8xb6hLWx+Kb/FLi+pklcA7sV9z1c9hvnrmbobesX5TxPsf7fwCvaCpMsL9MBnFBgLw/1ngztk= X-Received: by 2002:a17:90a:9501:b0:269:32d2:5ac4 with SMTP id t1-20020a17090a950100b0026932d25ac4mr7572966pjo.25.1691984666754; Sun, 13 Aug 2023 20:44:26 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <20230814015504.GB87066@eureka.lemis.com> In-Reply-To: <20230814015504.GB87066@eureka.lemis.com> From: Kevin Bowling Date: Sun, 13 Aug 2023 20:44:14 -0700 Message-ID: Subject: Re: Potential show-stopper in em driver? To: "Greg 'groggy' Lehey" Cc: current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4RPKyh581kz3FCy X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] On Sun, Aug 13, 2023 at 6:55=E2=80=AFPM Greg 'groggy' Lehey wrote: > > I've spent the last couple of days chasing random hangs on my -CURRENT > box. It seems to be related to the Ethernet driver (em). I've been > trying without much success to chase it down, and I'd be grateful. > The box is headless, and all communication is via the net, which > doesn't make it any easier. I've tried a verbose boot, but nothing of > interest shows up. Typically it happens during the nightly backups, > which are over NFS: > > Aug 13 21:06:46 dereel kernel: <<<66>n>nffs server s6>neurekfs server a= eureka:/dum:p: /ndoump: tnot responding > Aug 13 21:06:46 dereel kernel: > Aug 13 21:06:46 dereel kernel: responding > Aug 13 21:06:46 dereel kernel: > Aug 13 21:06:46 dereel kernel: server eureka:/dump:n not responding > > And if you haven't seen those garbled messages before, admire. > They've been there for a long time, and they have nothing to do with > the problem. More to the point, there are no other error messages. > > I've run three kernels on this box over the last few weeks: > > 1. FreeBSD dereel 14.0-CURRENT FreeBSD 14.0-CURRENT amd64 1400093 #10 mai= n-n264292-7f9318a022ef: Mon Jul 24 17:13:32 AEST 2023 grog@dereel:/usr/= obj/eureka/home/src/FreeBSD/git/main/amd64.amd64/sys/GENERIC amd64 > > This works with no problems. > > 2. FreeBSD 14.0-CURRENT amd64 1400094 #11 main-n264653-517e0978db1f: Thu = Aug 10 14:17:13 AEST 2023 grog@dereel:/usr/obj/eureka/home/src/FreeBSD/git/= main/amd64.amd64/sys/GENERIC > > 3. FreeBSD dereel 14.0-ALPHA1 FreeBSD 14.0-ALPHA1 amd64 1400094 #12 main-= n264693-b231322dbe95: Sat Aug 12 14:31:44 AEST 2023 grog@dereel:/usr/ob= j/eureka/home/src/FreeBSD/git/main/amd64.amd64/sys/GENERIC amd64 > > Both of these exhibit the problem. > > Note that we're now ALPHA1, so it's a good idea to get to the bottom > of it. The box is an ThinkCentre M93p. I'm attaching a verbose boot > log, though I don't expect anybody to find something of use there. > I'm also currently building a new world in case something has happened > since Saturday. The verbose boot didn't make it in the email. 'dmesg | grep em' would be a good enough start. Can you post 'sysctl dev.em.' from the machine after a lockup? Since you don't seem to have OOB access you may have to get creative with cron or something. > Greg > -- > Sent from my desktop computer. > See complete headers for address and phone numbers. > This message is digitally signed. If your Microsoft mail program > reports problems, please read http://lemis.com/broken-MUA.php