[Bug 279576] WITHOUT_CLANG build option fails, possibly a race condition
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279576 Michael Dexter changed: What|Removed |Added Status|New |Closed Resolution|--- |Unable to Reproduce --- Comment #3 from Michael Dexter --- This might have been attributed to building 15-CURRENT on 14.0R and appears to be working with combinations of 15 on 15, and 15 on 14.1R. I will close this for now and keep testing. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277060] pax(1) hangs when copying directories with a trailing slash
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277060 Ganael LAPLANCHE changed: What|Removed |Added Version|14.0-RELEASE|CURRENT -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279224] [panic] Loading i915kms from drm-61-kmod crashes if kernel was compiled with VT_MAXWINDOWS or SC_NO_CUTPASTE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279224 Anton Saietskii changed: What|Removed |Added CC||vsasja...@gmail.com --- Comment #1 from Anton Saietskii --- (In reply to Andre Albsmeier from comment #0) How does crash look like? For me, it's like this (on 14.1-RELEASE amd64): 1. Screen goes black. 2. Screen turns on, displays some DRM-related messages. 3. Screen goes black again. 4. System reboots. Note: there's no panic visible and I have PANIC_REBOOT_WAIT_TIME=-1. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279224] [panic] Loading i915kms from drm-61-kmod crashes if kernel was compiled with VT_MAXWINDOWS or SC_NO_CUTPASTE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279224 --- Comment #2 from Anton Saietskii --- Commented VT_MAXWINDOWS, recompiled kernel -- boots fine now. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279662] net/bird2@netlink - broken multiple FIB support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279662 Olivier Cochard changed: What|Removed |Added Assignee|b...@freebsd.org|oliv...@freebsd.org CC||oliv...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279224] [panic] Loading i915kms from drm-61-kmod crashes if kernel was compiled with VT_MAXWINDOWS or SC_NO_CUTPASTE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279224 --- Comment #3 from Andre Albsmeier --- (In reply to Anton Saietskii from comment #1) > How does crash look like? 1. System boots. 2. When it loads i915kms.ko, screen goes black 3. goto 1. I can't see any messages but that doesn't mean that there are none. Maybe the LCD needs some time to switch resolution and the crash/reboot ist faster. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279224] [panic] Loading i915kms from drm-61-kmod crashes if kernel was compiled with VT_MAXWINDOWS or SC_NO_CUTPASTE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279224 --- Comment #4 from Anton Saietskii --- (In reply to Andre Albsmeier from comment #3) Looks pretty similar to mine, except your steps are less. It may be related due to my systems boots in UEFI, which in turn means it's already in high-resolution graphic mode before even loader starts. This may explain why I see some DRM messages -- time for switching is saved. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 228251] Touchpad non-functional on Dell Latitude 5580
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228251 --- Comment #9 from Ed Maste --- Four or five years later, Shawn or Trenton can you comment on the current state here? As Trenton mentioned in Comment #8 there was a lot of work in progress at the time of this report. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279683] ctld: inconsistent parsing "option" in traditional vs UCL mode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279683 Bug ID: 279683 Summary: ctld: inconsistent parsing "option" in traditional vs UCL mode 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: asom...@freebsd.org ctld.conf(5) says that both the portal-group context and the lun context may have an "option" section (note: it's singular). The YACC code for parsing the traditional config file also expects "option" (singular again). But the UCL parsing code expects "options" (plural). Curiously, the man page _does_ use "options" in the example UCL file, though it doesn't mention that spelling in the text. I think it best if both traditional and UCL mode use the same spelling. And since I'm guessing that traditional users still outnumber UCL users, we should standardize on "option". -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279661] ctld ignores several settings in UCL mode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279661 Alan Somers changed: What|Removed |Added Summary|ctld ignores offload in UCL |ctld ignores several |mode|settings in UCL mode --- Comment #2 from Alan Somers --- And from the lun context, uclparse.y ignores "ctl-lun" and "device-type"/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279684] ctld truncates LUN size to 4GiB on 32-bit platforms
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279684 Bug ID: 279684 Summary: ctld truncates LUN size to 4GiB on 32-bit platforms 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: asom...@freebsd.org The ctld.conf file allows specifying the size of a LUN. It's required for ramdisk-backed LUNs, and optional for block-backed LUNs. In traditional mode it's parsed as a uin64_t. In UCL mode, it's parsed as an int64_t. That's a little bit inconsistent, but not bad. The bad part is that it then gets truncated by being passed to lun_set_size, which takes its argument as a usize. That's a bug on 32-bit platforms. The solution is to always handle the size as a uint64_t, which is ultimately what the kernel expects. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279542] mandoc emits error after exiting pager
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279542 Ed Maste changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2235 ||16 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279622] Change Default bsdinstall(8) Partition Sizes for Auto (ZFS) Option
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279622 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|sysinst...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 15470] Proposed change to comments in /etc/namedb/named.conf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=15470 --- Comment #3 from Mark Linimon --- (In reply to commit-hook from comment #2) ^Triage: note that this commit was misfiled against PR https://bugs.freebsd.org/273207 . -- You are receiving this mail because: You are the assignee for the bug.
[Bug 228251] Touchpad non-functional on Dell Latitude 5580
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228251 --- Comment #10 from Trenton Schulz --- (In reply to Ed Maste from comment #9) I think this can safely be closed. I believe I was using the builtin trackpad with no changes by 12.2-RELEASE. Unfortunately, that laptop has been repurposed to non-FreeBSD things, so I can't check it anymore, but I believe it was working through at least 13.2-RELEASE and I don't think much has changed that would break it. I'm happy to have this closed if possible. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279686] [asmc] [patch] Add support for MacBookPro 11.4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279686 Bug ID: 279686 Summary: [asmc] [patch] Add support for MacBookPro 11.4 Product: Base System Version: 13.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: megaman...@gmail.com Created attachment 251403 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251403&action=edit asmc macbookpro11,4 support This patch adds support for asmc with the Macbookpro 11.4. SMCs were (mostly) taken from https://logi.wiki/index.php/SMC_Sensor_Codes. Three errors occur when running sysctl: asmc0: asmc_key_read for key F1Sf failed 10 times, giving up asmc0: asmc_key_read for key F0Sf failed 10 times, giving up asmc0: asmc_key_read for key F0Sf failed 10 times, giving up These correspond to: dev.asmc.0.fan.1.safespeed dev.asmc.0.fan.0.safespeed but cannot be disabled without severely altering the driver, so I've left them as-is. Keyboard backlight is working nicely, and fan and temp reporting is also working. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279690] Inbuilt keyboard capslock LED does not work past bootloader
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279690 Bug ID: 279690 Summary: Inbuilt keyboard capslock LED does not work past bootloader Product: Base System Version: 13.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: megaman...@gmail.com I am currently trying to get an inbuilt laptop keyboard to fully function using FreeBSD 13.3, on a MacBook Pro 11.4. In general everything has been successful, however I am having just one problem remaining to be fixed. When I boot into the laptop, the caps lock button works and when it is enabled, the LED turns on. This is true both during the entering of the full disk encryption, and during the bootloader dialogue. However, as soon as the booting process begins, the caps lock LED is switched off, and there is seemingly no way to turn it back on. I have tried using ioctl to set the LED on using KDSETLED, but despite the device believing that it is set, the actual LED is not on (caps lock does work, though). -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279690] Inbuilt keyboard capslock LED does not work past bootloader on a MacBook Pro 11.4
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279690 Mark Linimon changed: What|Removed |Added Summary|Inbuilt keyboard capslock |Inbuilt keyboard capslock |LED does not work past |LED does not work past |bootloader |bootloader on a MacBook Pro ||11.4 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 277783] libc fma() doesn't not return the correct zero sign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277783 --- Comment #10 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=e77ad954bb825983b4346b9cc646c9c910b1be24 commit e77ad954bb825983b4346b9cc646c9c910b1be24 Author: Ed Maste AuthorDate: 2024-06-12 01:34:02 + Commit: Ed Maste CommitDate: 2024-06-12 01:36:12 + Revert "libm: fma: correct zero sign with small inputs" This change introduced a test failure, so revert until that can be addressed. This reverts commit 888796ade2842486d3167067e8034254c38aadd3. PR: 277783 Reported by:rlibby Sponsored by: The FreeBSD Foundation lib/msun/src/s_fma.c | 4 +--- lib/msun/src/s_fmal.c | 4 +--- 2 files changed, 2 insertions(+), 6 deletions(-) -- You are receiving this mail because: You are the assignee for the bug.
