Date: Mon, 14 Aug 2023 12:47:03 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: "Greg 'groggy' Lehey" <grog@FreeBSD.org> Cc: current@FreeBSD.org, Kevin Bowling <kbowling@FreeBSD.org> Subject: Re: Potential show-stopper in em driver? Message-ID: <20230814124703.3875a7ba266cdf079525eb82@dec.sakura.ne.jp> In-Reply-To: <20230814015504.GB87066@eureka.lemis.com> References: <20230814015504.GB87066@eureka.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 14 Aug 2023 11:55:04 +1000 "Greg 'groggy' Lehey" <grog@FreeBSD.org> 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 aeureka:/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 main-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/obj/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. > > 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 Does commit f1b5488f7bba7f25a57750f87cbcbccbd5b9d16b [1] related? How does it go if disabling TSO as documeted on the commit message? CC'ing kbowling@, who committed all (I could find on cgit) e1000/em-related bits between the timeframe of 1. and 2. [1] https://cgit.freebsd.org/src/commit/?id=f1b5488f7bba7f25a57750f87cbcbccbd5b9d16b -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230814124703.3875a7ba266cdf079525eb82>