https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #18 from cos ---
After calling `sysrc xdm_enable=NO` and rebooting, `acpiconf -s 3` worked both
once and twice.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #17 from cos ---
I am quite confident the old 14.1 works. This laptop is my daily driver, so
there were a couple of weeks of trouble-free suspend-resume. I am also still
able to consistently reproduce the correct behaviour with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #16 from cos ---
Created attachment 251764
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251764&action=edit
procstat -kka, 14.1-RELEASE-p1 (kernel 14.0-p6) 02-stuck; acpiconf failed
--
You are receiving this mail b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #15 from cos ---
Created attachment 251763
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251763&action=edit
procstat -kka, 14.1-RELEASE-p1 (kernel 14.0-p6) 01-post only resume
--
You are receiving this mail because
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #14 from cos ---
Created attachment 251762
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251762&action=edit
procstat -kka, 14.1-RELEASE-p1 (kernel 14.0-p6) 00-just booted
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #13 from cos ---
Created attachment 251761
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251761&action=edit
procstat -kka, 14.1-RELEASE (kernel 14.0-p6) 02-post second resume
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #12 from cos ---
Created attachment 251760
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251760&action=edit
procstat -kka, 14.1-RELEASE (kernel 14.0-p6) 01-post first resume
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #11 from cos ---
Created attachment 251759
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251759&action=edit
procstat -kka, 14.1-RELEASE (kernel 14.0-p6) 00-just booted
--
You are receiving this mail because:
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #10 from cos ---
Created attachment 251758
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251758&action=edit
kldstat, 14.1-RELEASE-p1 (kernel 14.0-p6)
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #9 from cos ---
Created attachment 251757
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251757&action=edit
kldstat, 14.1-RELEASE (kernel 14.0-p6)
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
cos changed:
What|Removed |Added
Attachment #251755|dmesg, 14.1-RELEASE |dmesg, 14.1-RELEASE (kernel
descripti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #8 from cos ---
Created attachment 251756
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251756&action=edit
dmesg, 14.1-RELEASE-p1 (kernel 14.0-p6)
--
You are receiving this mail because:
You are the assignee for th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #7 from cos ---
Created attachment 251755
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251755&action=edit
dmesg, 14.1-RELEASE
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279773
Warner Losh changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279774
Warner Losh changed:
What|Removed |Added
Assignee|b...@freebsd.org|i...@freebsd.org
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279792
Warner Losh changed:
What|Removed |Added
Assignee|b...@freebsd.org|i...@freebsd.org
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279872
Mark Johnston changed:
What|Removed |Added
Status|New |Closed
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279892
Warner Losh changed:
What|Removed |Added
Assignee|b...@freebsd.org|i...@freebsd.org
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280039
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #6 from Warner Losh ---
Also, procstat -kka would be helpful to see if maybe a thread is getting stuck
now that wasn't before.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #5 from Warner Losh ---
It would also be good to know the network drivers involved. Can you attach a
complete dmesg before/after the update?
Does kldstat show differences?
--
You are receiving this mail because:
You are the as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #4 from Warner Losh ---
Also, would you be able to build a new kernel?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280024
Warner Losh changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
Warner Losh changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #3 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280039
Bug ID: 280039
Summary: bluetooth socket security filter incomplete
initialization
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #2 from cos ---
I naively attempted `for _s in $( service -l ); do echo $_s; service $_s stop &
sleep 2; done` when in the broken state but, unlike when calling `halt`, it did
not lead to suspend.
--
You are receiving this mai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
--- Comment #1 from cos ---
*** Bug 280029 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280029
cos changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280037
--- Comment #7 from ss3bsd <3226388...@jcom.home.ne.jp> ---
(kgdb) frame 14
#14 0x80c83fb0 in crypto_dispatch_one
(crp=crp@entry=0xfe014b081c38, hint=0) at
/usr/src/sys/opencrypto/crypto.c:1432
1432result = cr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280037
--- Comment #6 from Mark Johnston ---
(In reply to ss3bsd from comment #4)
Thank you. Could we also see
(kgdb) frame 14
(kgdb) p/x *crp->crp_buf.cb_uio
output?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163978
Mitchell Horne changed:
What|Removed |Added
CC||mho...@freebsd.org
St
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280031
Mark Linimon changed:
What|Removed |Added
Keywords||regression
Assignee|b...@
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198395
Mitchell Horne changed:
What|Removed |Added
Resolution|--- |Overcome By Events
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280037
--- Comment #5 from ss3bsd <3226388...@jcom.home.ne.jp> ---
> Also, is the second panic reproducible? Does it happen as soon as a KTLS
> session starts, or does it take some time to trigger the crash?
I upgraded from 13.3 to 14.1 on 6/19
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280037
--- Comment #4 from ss3bsd <3226388...@jcom.home.ne.jp> ---
(kgdb) frame 14
#14 0x80c83fb0 in crypto_dispatch_one
(crp=crp@entry=0xfe014b081c38, hint=0) at
/usr/src/sys/opencrypto/crypto.c:1432
1432result = cr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280037
--- Comment #3 from Mark Johnston ---
(In reply to ss3bsd from comment #2)
Please try running the following commands:
(kgdb) frame 14
(kgdb) p/x *crp
and share the output.
Also, is the second panic reproducible? Does it happen as soon a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280037
--- Comment #2 from ss3bsd <3226388...@jcom.home.ne.jp> ---
Hello.
Is this what you need?
I'm not familiar with kernel debugging.
#14 0x80c83fb0 in crypto_dispatch_one
(crp=crp@entry=0xfe014b081c38, hint=0) at
/usr/src/sys/ope
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280037
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280037
Bug ID: 280037
Summary: KTLS with Intel QAT may trigger kernel panics
Product: Base System
Version: 14.1-RELEASE
Hardware: Any
OS: Any
Status: New
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280036
Bug ID: 280036
Summary: Data corruption over if_ovpn (OpenVPN DCO) observed
Product: Base System
Version: 14.1-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280031
--- Comment #2 from bnd...@outlook.com ---
Downgraded to 13.3, pkg installed instantly.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280031
--- Comment #1 from bnd...@outlook.com ---
Ran:
certctl rehash
Now getting slightly different errors:
pkg: error:0268:rsa routines::bad signature
Verifying signature with trusted certificate pkg.freebsd.org.2013102301...
failed
Signa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280031
Bug ID: 280031
Summary: Cannot install `pkg` due to 404 on pkg.freebsd.org
Product: Base System
Version: 14.1-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280029
Bug ID: 280029
Summary: S3 suspend of Thinkpad x270 stopped working after
freebsd-update to 14.1-RELEASE-p1
Product: Base System
Version: 14.1-RELEASE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280028
Bug ID: 280028
Summary: S3 suspend of Thinkpad x270 stopped working after
freebsd-update to 14.1-RELEASE-p1
Product: Base System
Version: 14.1-RELEASE
Hardware: amd64
46 matches
Mail list logo