From nobody Tue Feb 28 12:25:33 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 4PQxRG64dqz3vPR5 for ; Tue, 28 Feb 2023 12:25:46 +0000 (UTC) (envelope-from rnhurt@gmail.com) Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) (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 4PQxRF5V0lz4286 for ; Tue, 28 Feb 2023 12:25:45 +0000 (UTC) (envelope-from rnhurt@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=T4TYG1rH; spf=pass (mx1.freebsd.org: domain of rnhurt@gmail.com designates 2607:f8b0:4864:20::32d as permitted sender) smtp.mailfrom=rnhurt@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ot1-x32d.google.com with SMTP id cc12-20020a05683061cc00b00693daa9016fso5442977otb.2 for ; Tue, 28 Feb 2023 04:25:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=yLXOVer+7Yhnn9yUv/76K/zpC10RMstufdLYbfAdja8=; b=T4TYG1rH+yf44ogWZbtkuhKoJp9aIZZ5eZfyCR6bmIFuGI44ufp5SbUr1VilJPAOXS DqfSHbDC+yE3j0z1Hk0k5W8UQxPllepQtwiyYkRAp3lTMb0W8vgmqqAkg2CI4lcJbnTP fujrCJB+N+rYZJB7XSnyz/uFTsAowaZJPKB03W1iaFSaUe9NRjEmGbL2EX6p0OMZtlJi oVk8cphDzUmsBetw26I15iOpd0dpf50wt6/F0La8jarveWgEINUcvYILH6Byo+4zKxbf BSBrxRwFhwNvGl6iE6pN5Q6mCuJg4mV52601RSvzorc0g1WTj40KV3tf3qTsUSYLpvU/ gp1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=yLXOVer+7Yhnn9yUv/76K/zpC10RMstufdLYbfAdja8=; b=NbxTbBno52fqPIVjVcVysbM7fjvKT/epwtbmTnfRxOukmep8WbQsH7reUca7EhgIxB DfuLL3tfSxG7Wlv24rdx62h5EYeoor2+qQWOetLknYmRczb9xZST4ibFcJbGNeB6QaSE m5i7MTZMZcOrIJwpoK4o1Efe6gELpryVAQGjFYNuuZsa54NDOFaMkiWDoS5+MJFkG349 JijJ3pzMhXQYaHpLLGlT7729VL68NYBC67gzJdjBPsISW8W0l4Y9cZMK3/bQwdhHgNWC HZf2yCthBQdlsGTs4EU7kE0I6eRmEBZW/8PCffFWL9CKEH2HNlFFkPetI+0ztFDFCFJC o5gw== X-Gm-Message-State: AO0yUKUFd5s8T5VJOdmrFwD+AuWjzdUSbUvBR/G4WsHWfsElVxof2c+h h1Str08YsaVMoxcUogbtKlWbvtJ16ELmk5gvpkudwAlh3w== X-Google-Smtp-Source: AK7set/AGS6RlfRjUviaSUd5QAtZfhmwaIQWSPbNOhUJF/LpHSWk4Be9izS39UwfS/p6bid3pJ84F44nZfLtrxNEgg4= X-Received: by 2002:a9d:609b:0:b0:690:e6d9:4842 with SMTP id m27-20020a9d609b000000b00690e6d94842mr901815otj.0.1677587144245; Tue, 28 Feb 2023 04:25:44 -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 From: Richard Hurt Date: Tue, 28 Feb 2023 07:25:33 -0500 Message-ID: Subject: OPNSense (FreeBSD 13.1-p6) kernel panic To: freebsd-stable@freebsd.org Content-Type: multipart/alternative; boundary="000000000000d0078405f5c1b174" X-Spamd-Result: default: False [-3.95 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.95)[-0.953]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::32d:from]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_FROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4PQxRF5V0lz4286 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --000000000000d0078405f5c1b174 Content-Type: text/plain; charset="UTF-8" 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 --000000000000d0078405f5c1b174 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
After a recent OPNSense update my HD activ= ity light was staying on and the CPU=20 meter on the OPNSense dashboard was reading 100%.=C2=A0 After looking for= =20 anything obvious and turning off all the services I could, the CPU was=20 still pegged and the HD light was still on constantly.=C2=A0 So I rebooted= =20 the machine; it never came back online.

After I attached a=20 monitor to the machine I saw that it had a kernel panic.=C2=A0 While=20 unusual I didn't think too much of it however rebooting the machine=20 didn't resolve the issue.=C2=A0 So, I removed all the cards, memory, et= c. to=20 see if I could get a clean boot.=C2=A0 Nothing helped and I continued to ge= t 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=20 drive with a fresh copy of OPNSense v23.1 installed on it.=C2=A0 The system= booted=20 just fine and ran the live version.=C2=A0 So I turned the machine off,=20 reconnected the drive, rebooted and installed v23.1 on the HD.=C2=A0 The=20 install worked perfectly and the machine rebooted.=C2=A0 Once again, I got= =20 the kernel panic.

My next thought was that maybe the HD was=20 "bad".=C2=A0 I replaced the HD and again installed a fresh copy o= f v23.1.=C2=A0=20 Again, the kernel panic showed up.=C2=A0 Arrggghhh!=C2=A0

I'm r= unning=20 Memtest86 v6.10 right now and it has passed 4 times, so I don't=20 think it's memory related.=C2=A0 I've replaced the HD so that's= (probably)=20 not the problem.=C2=A0 It seems to work fine when booting from the USB flas= h drive (it's just slooooow) so the CPU seems to be OK.=C2=A0

After th= e=20 kernel panic the machine is locked up completely.=C2=A0 Nothing works.=C2= =A0 The=20 keyboard doesn't do anything, the capslock key doesn't, light up an= d 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 too= k 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.msg158386#msg158386) but they said that this mailing list was probably the better option.
=
--000000000000d0078405f5c1b174--