[Bug 278993] fsck not checking disk if sysctl kern.boottrace.enabled=1 is set

2024-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278993

Warner Losh  changed:

   What|Removed |Added

 CC||i...@freebsd.org

--- Comment #4 from Warner Losh  ---
So part of the problem is that the boottrace stuff doesn't export any of the
variables.  What about _boot or rc_fast? It looks like rc_fast is reconstructed
whenver _boot is fast* in rc.subr and only set when _boot has been set to
'faststart'.

The fix is a bit of a hack.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 110146] [patch] [request] Allow arbitrary gdb(1) options to bypass kgdb

2024-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=110146

John Baldwin  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|Open|Closed

--- Comment #6 from John Baldwin  ---
kgdb in base has been removed.  For kgdb in ports, use gdb directly instead.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 279365] Incomplete syslog message on console after login timeout

2024-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279365

Bug ID: 279365
   Summary: Incomplete syslog message on console after login
timeout
   Product: Base System
   Version: 15.0-CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: j...@mit.edu

When login on the console times out an apparent race between respawning getty
and logging the failure results in an incomplete syslog message on the console.

This is the console:

FreeBSD/arm64 (striatus) (ttyu0)

login: invalid
Password:
Login incorrect
login: Login timed out after 300 seconds
May 28 10:56:38 striatus login[66089]
FreeBSD/arm64 (striatus) (ttyu0)

login: 


The full message is in /var/log/messages:

May 28 10:56:38 striatus login[66089]: 1 LOGIN FAILURE ON ttyu0

Possibly getty is interrupting a non-atomic write by syslog.  I know syslog is
capable of reporting the full message because I see it if I type ^D instead of
waiting for login to give up.

This is my console device:

uart0:  mem 0xe101-0xe1010fff irq 13 on simplebus0
uart0: console (115200,n,8,1)

Externally it appears as a type B USB socket, device ID 2e02:1000 (SoftIron
OverDrive 1000), version 1.02, full speed.  It is plugged into a Mac.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 278993] fsck not checking disk if sysctl kern.boottrace.enabled=1 is set

2024-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278993

--- Comment #3 from Oleksii Samorukov  ---
Proposed fix is at https://github.com/freebsd/freebsd-src/pull/1261

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 271826] FreeBSD is disastrously slow on a PowerMac G5, freezing at every command

2024-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271826

--- Comment #24 from Sergey Fedorov  ---
(In reply to Justin Hibbits from comment #20)

If someone could build the image to try (or if installing from a FireWire drive
works, then I can clone DVD image there and just replace the kernel, but I
still need the new kernel), I will definitely test it.

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 27760] pkg_add -r hangs when fetching via ftp

2024-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=27760

--- Comment #3 from commit-h...@freebsd.org ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/ports/commit/?id=600c83f389932163135592b08d80df4a7296eef8

commit 600c83f389932163135592b08d80df4a7296eef8
Author: Jochen Neumeister 
AuthorDate: 2024-05-28 08:10:31 +
Commit: Jochen Neumeister 
CommitDate: 2024-05-28 08:11:38 +

databases/mysql81-client: fix package without SASLCLIENT

fix package without SASLCLIENT

PR: 27760
Sponsored by:   Netzkommune GmbH

 databases/mysql81-client/Makefile  | 2 +-
 databases/mysql81-client/pkg-plist | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

-- 
You are receiving this mail because:
You are the assignee for the bug.


[Bug 266480] Panic "sleeping thread" with qlnxe driver

2024-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266480

Zhenlei Huang  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2780
   ||84

--- Comment #5 from Zhenlei Huang  ---
Fix in 278084 changed the hw_lock from mutex(9) to sx(9). That should fix this
issue.

```
diff --git a/sys/dev/qlnx/qlnxe/qlnx_os.h b/sys/dev/qlnx/qlnxe/qlnx_os.h
index 261283fb6eaf..6d717d0e70bf 100644
--- a/sys/dev/qlnx/qlnxe/qlnx_os.h
+++ b/sys/dev/qlnx/qlnxe/qlnx_os.h
@@ -130,8 +130,8 @@ MALLOC_DECLARE(M_QLNXBUF);
 /*
  * Locks
  */
-#define QLNX_LOCK(ha)  mtx_lock(&ha->hw_lock)
-#define QLNX_UNLOCK(ha)mtx_unlock(&ha->hw_lock)
+#define QLNX_LOCK(ha)  sx_xlock(&ha->hw_lock)
+#define QLNX_UNLOCK(ha)sx_xunlock(&ha->hw_lock)
```

-- 
You are receiving this mail because:
You are the assignee for the bug.