Date: Sun, 30 Jun 2024 05:38:07 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 280037] KTLS with Intel QAT may trigger kernel panics Message-ID: <bug-280037-7501-NrRXqW7BCm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280037-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-280037-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280037 --- Comment #10 from ss3bsd <3226388001@jcom.home.ne.jp> --- To be clear, Panic #1: reproducible with a clean kernel. I was aware of that "kldunload qat" might trigger panic at 13.x too. Panic #2: log was acquired for a dirty kernel. It is intermittent and so far is difficult to intentionally reproduce. I= may not be able to offer another log with clean kernel. Therefore, at this moment I cannot assure that my patch is not affecting anything. What I can tell is that 13.x was stably running with KTLS and QAT, and I had not experienced this before upgrading to 14.1 even with the same = kind of private patch. Panic #3: reproducible with a clean kernel. I did not try to switch dev.qat_ocf.0.enable=3D0 when the host was runni= ng 13.x. I cannot tell whether it is common for 14.1 and 13.x. (may be not exi= st in 13.x?) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280037-7501-NrRXqW7BCm>