From nobody Wed Mar 01 03:19:58 2023 X-Original-To: freebsd-stable@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 4PRKHH5YY4z3vHv5 for ; Wed, 1 Mar 2023 03:20:11 +0000 (UTC) (envelope-from rnhurt@gmail.com) Received: from mail-oa1-x2a.google.com (mail-oa1-x2a.google.com [IPv6:2001:4860:4864:20::2a]) (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 4PRKHH3g9cz3MV1 for ; Wed, 1 Mar 2023 03:20:11 +0000 (UTC) (envelope-from rnhurt@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x2a.google.com with SMTP id 586e51a60fabf-172afa7bee2so13113892fac.6 for ; Tue, 28 Feb 2023 19:20:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1677640810; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5a/SeYs8jf27hsEqQykoJlc3B9MxThaoimIvpw5cUgs=; b=aoNNEJ0YNnRd5EhGYtXts/Mz8f1W7sMByaKv/Y1vzltL+erAO+O9ATJ7EdApU8A4wm ujJc8TkAnTo1X6eBdlI0Jc354uV0gk33ylu1ucnODfDYkAq6rJrIjLEUjHu8ZvPzgCW+ Xh4/ABsuPjpxpu2dA2etK9yAoCoJdSrpGnQUNbFsvNR2FuLtggKJrZBiuNOUGpWlv1MW IGIBsuquIOEhCCocBSZgOKEyTqBUZB4cyy6Gg5fM2hXy0WlR6bPU34dewZR1C4gviuUs 1hdRGRdzwhAEo7W6CX726CQCobDqRe7sMMvrd7VnXmRwj/ehRrAtyK3g5tsKvWOVr5it E+pA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677640810; h=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=5a/SeYs8jf27hsEqQykoJlc3B9MxThaoimIvpw5cUgs=; b=dD7Nm4vDdnB/JPmRURJ9F/myjsvwJSo6N023zW+pkMyc4s6sMD/gQxtrNbp0B6XLN3 seBkSaej7hblCTnw9d2fja3ZrE1oFUBPpjAdkUiSXET8D8/HsYYRryhGSeKqz8sj29jK BKxvPJ88p0IUWcfwpV+bnyJ2J86SRD83oXBFtx5AOJEhgCSMv70DffvXq92WdGe5Wi6T jAfB4hopxXgB05LOHyJa7xQRGF/N4L/aZ+1WWAUd5i54d1jyzGxWDLe9HT0Nljm8YuDE zkl4oC3AsuafmgL3Lgeegmv58Sgfw4nq36m/P53eiL2n4+WgLCaTbMxr+XOJi2hlAj9x n8Mg== X-Gm-Message-State: AO0yUKXoEa5Z9a93LPNzwsVYnLTM413B7ObrXW9fzBCR2NwRKFKE/7hC dUfWsTQo0/BJtmIJ3JhoNbsRnA9O72nFpd3fuxuWYY4= X-Google-Smtp-Source: AK7set8Eq+8yVjjEg15IiSZ7yBTK2nTiBCDO6ThJNzXlvRBJJMbmqkQkZRBY8byE+8MzHIkkhiO49Yeiqq+Dk7U8i/A= X-Received: by 2002:a05:6870:d99:b0:172:5ef0:4288 with SMTP id mj25-20020a0568700d9900b001725ef04288mr2131163oab.3.1677640809815; Tue, 28 Feb 2023 19:20:09 -0800 (PST) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <82564799-2ab9-f19f-0fa8-a069325c0e7a@grosbein.net> In-Reply-To: <82564799-2ab9-f19f-0fa8-a069325c0e7a@grosbein.net> From: Richard Hurt Date: Tue, 28 Feb 2023 22:19:58 -0500 Message-ID: Subject: Re: OPNSense (FreeBSD 13.1-p6) kernel panic To: Eugene Grosbein Cc: freebsd-stable@freebsd.org Content-Type: multipart/alternative; boundary="00000000000087a4fa05f5ce30d5" X-Rspamd-Queue-Id: 4PRKHH3g9cz3MV1 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000087a4fa05f5ce30d5 Content-Type: text/plain; charset="UTF-8" Yes, that was exactly the problem. Sorry for wasting everyone's time. -- Richard On Tue, Feb 28, 2023 at 9:29 AM Eugene Grosbein wrote: > 28.02.2023 19:25, Richard Hurt wrote: > > > After a recent OPNSense update my HD activity light was staying on and > the CPU meter on the OPNSense dashboard was reading 100%. After looking > for anything obvious and turning off all the services I could, the CPU was > still pegged and the HD light was still on constantly. So I rebooted the > machine; it never came back online. > > > > After I attached a monitor to the machine I saw that it had a kernel > panic. While unusual I didn't think too much of it however rebooting the > machine didn't resolve the issue. So, I removed all the cards, memory, > etc. to see if I could get a clean boot. Nothing helped and I continued to > get a kernel panic. > > > > I thought it might be a corrupted hard drive or something so I > disconnected the drive and booted off a USB thumb drive with a fresh copy > of OPNSense v23.1 installed on it. The system booted just fine and ran the > live version. So I turned the machine off, reconnected the drive, rebooted > and installed v23.1 on the HD. The install worked perfectly and the > machine rebooted. Once again, I got the kernel panic. > > > > My next thought was that maybe the HD was "bad". I replaced the HD and > again installed a fresh copy of v23.1. Again, the kernel panic showed up. > Arrggghhh! > > > > I'm running Memtest86 v6.10 right now and it has passed 4 times, so I > don't think it's memory related. I've replaced the HD so that's (probably) > not the problem. It seems to work fine when booting from the USB flash > drive (it's just slooooow) so the CPU seems to be OK. > > > > After the kernel panic the machine is locked up completely. Nothing > works. The keyboard doesn't do anything, the capslock key doesn't, light > up and the floppy drive light is stuck on. > > > > I've not been able to get a text output of the panic but here is a > screenshot I took from my phone: https://imgur.com/a/aaXwkVK I posted > about this first on the OPNSense forum ( > https://forum.opnsense.org/index.php?topic=32728.msg158386#msg158386) but > they said that this mailing list was probably the better option. > > > > Equipment: > > * Acer Aspire AST180-UA380B > > * AMD Athlon 3800+ > > * 3GB RAM > > * 1TB SATA drive > > > > Thanx > > Richard > > The problem seems to be known and specific to OPNSense that change some > default FreeBSD settings > unconditionally, no matter if hardware's compatible with non-default > setting or not: > > https://github.com/opnsense/core/issues/3177 > > > > --00000000000087a4fa05f5ce30d5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes, that was exactly the problem.=C2=A0 Sorry for wasting= everyone's time.
<= br>
--
Richard
<= br>
On Tue,= Feb 28, 2023 at 9:29 AM Eugene Grosbein <eugen@grosbein.net> wrote:
28.02.2023 19:25, Richard Hurt wrote:

> After a recent OPNSense update my HD activity light was staying on and= the CPU meter on the OPNSense dashboard was reading 100%.=C2=A0 After look= ing for anything obvious and turning off all the services I could, the CPU = was still pegged and the HD light was still on constantly.=C2=A0 So I reboo= ted the machine; it never came back online.
>
> After I attached a monitor to the machine I saw that it had a kernel p= anic.=C2=A0 While unusual I didn't think too much of it however rebooti= ng the machine didn't resolve the issue.=C2=A0 So, I removed all the ca= rds, memory, etc. to see if I could get a clean boot.=C2=A0 Nothing helped = and I continued to get a kernel panic.
>
> I thought it might be a corrupted hard drive or something so I disconn= ected the drive and booted off a USB thumb drive with a fresh copy of OPNSe= nse v23.1 installed on it.=C2=A0 The system booted just fine and ran the li= ve version.=C2=A0 So I turned the machine off, reconnected the drive, reboo= ted and installed v23.1 on the HD.=C2=A0 The install worked perfectly and t= he machine rebooted.=C2=A0 Once again, I got the kernel panic.
>
> My next thought was that maybe the HD was "bad".=C2=A0 I rep= laced the HD and again installed a fresh copy of v23.1.=C2=A0 Again, the ke= rnel panic showed up.=C2=A0 Arrggghhh!
>
> I'm running Memtest86 v6.10 right now and it has passed 4 times, s= o I don't think it's memory related.=C2=A0 I've replaced the HD= so that's (probably) not the problem.=C2=A0 It seems to work fine when= booting from the USB flash drive (it's just slooooow) so the CPU seems= to be OK.
>
> After the kernel panic the machine is locked up completely.=C2=A0 Noth= ing works.=C2=A0 The keyboard doesn't do anything, the capslock key doe= sn't, light up and the floppy drive light is stuck on.
>
> I've not been able to get a text output of the panic but here is a= screenshot I took from my phone: https://imgur.com/a/aaXwkVK=C2=A0 I= posted about this first on the OPNSense forum (https://forum.opnsense.org/index.php?topic=3D32728.msg158= 386#msg158386) but they said that this mailing list was probably the be= tter option.
>
> Equipment:
> * Acer Aspire AST180-UA380B
> * AMD Athlon 3800+
> * 3GB RAM
> * 1TB SATA drive
>
> Thanx
> Richard

The problem seems to be known and specific to OPNSense that change some def= ault FreeBSD settings
unconditionally, no matter if hardware's compatible with non-default se= tting or not:

https://github.com/opnsense/core/issues/3177



--00000000000087a4fa05f5ce30d5--