[Bug 265569] [panic] Fatal trap 9: general protection fault while in kernel mode arc_reap

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265569 --- Comment #1 from Charlie Stanley --- I was doing some more debugging and the call chain looks sane until the slab address is computed. The slab pointer seems to be at an odd offset, and when I dereference it, the data looks like garbage

[Bug 265569] [panic] Fatal trap 9: general protection fault while in kernel mode arc_reap

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265569 Bug ID: 265569 Summary: [panic] Fatal trap 9: general protection fault while in kernel mode arc_reap Product: Base System Version: 13.1-RELEASE Hardware: amd64

[Bug 263300] FreeBSD administration: update the organization.dot organisational chart

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263300 Graham Perrin changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 265517] Unattended install FreeBSD 13.1 ZFS+UEFI fails: "cannot unmount '/mnt': pool or dataset busy"

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265517 Graham Perrin changed: What|Removed |Added CC||grahamper...@gmail.com --- Comment

[Bug 265533] uchcom: baud rate is not correct for CH34x

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265533 --- Comment #4 from Tomoyuki Sakurai --- tested other CH340 chips. works fine with CH340G (115200). -- You are receiving this mail because: You are the assignee for the bug.

[Bug 265533] uchcom: baud rate is not correct for CH34x

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265533 Tomoyuki Sakurai changed: What|Removed |Added URL||https://github.com/nospam20

[Bug 265549] Vultr Q35 hangs while booting during virtio-random initialization

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265549 Bob Grant changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 265549] Vultr Q35 hangs while booting during virtio-random initialization

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265549 --- Comment #4 from Bob Grant --- Created attachment 235607 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=235607&action=edit CPU graph for 1 vCPU VM hanging for 16 hrs This is the CPU utilization as shown by the vultr dashboard

[Bug 265549] Vultr Q35 hangs while booting during virtio-random initialization

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265549 --- Comment #3 from Bob Grant --- Ok, I had a test boot of FreeBSD 13.1 STABLE that was booted 15 hours ago and is still hung at the same place on a 1 vCPU system. Thus the hang is more than just something that will resolve in an hour or t

[Bug 265549] Vultr Q35 hangs while booting during virtio-random initialization

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265549 --- Comment #2 from Bob Grant --- I read in one related thread about the virtio-random spinning 100% cpu. All my hangs took place on a 1 vCPU VM. I just tested on a 2 vCPU VM and the system boots successfully. I'm going to test a 1vCPU

[Bug 265484] Adding INVARIANTS to GENERIC 13.1 kernel causes panic in mrsas

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265484 --- Comment #2 from Warner Losh --- (In reply to Mark Johnston from comment #1) I've forwarded this to them and see if they are still the right point of contact. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 264600] openssh: sshd spamming logs: error: Fssh_kex_exchange_identification: Connection closed by remote host

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264600 neroz...@gmail.com changed: What|Removed |Added CC||neroz...@gmail.com --- Comment

[Bug 265403] dtrace: invalid probe specifier

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265403 Mark Johnston changed: What|Removed |Added Assignee|b...@freebsd.org|ma...@freebsd.org

[Bug 265484] Adding INVARIANTS to GENERIC 13.1 kernel causes panic in mrsas

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265484 Mark Johnston changed: What|Removed |Added CC||i...@freebsd.org,

[Bug 265548] small correction in sys/conf/newvers.sh

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265548 --- Comment #2 from ghislain --- (In reply to Li-Wen Hsu from comment #1) Thanks for the clarification and sorry for the false alert. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 265533] uchcom: baud rate is not correct for CH34x

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265533 --- Comment #3 from Tomoyuki Sakurai --- checked all the failed boards on Fedora. none worked. it is likely that they are malfunctioning not because of issues in device driver. at least, the patch saved some. -- You are receiving this mai

[Bug 265533] uchcom: baud rate is not correct for CH34x

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265533 --- Comment #2 from Tomoyuki Sakurai --- "always work" is bit too early to say. although success rate is far better than before, i am seeing failures. -- You are receiving this mail because: You are the assignee for the bug.