[Bug 271657] unzip doesn't know infozip (beta)'s -O and -I options
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271657 Mingye Wang changed: What|Removed |Added Status|New |Closed Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 281257] base llvm csetjmp C++ header file now generates an error
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281257 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|toolch...@freebsd.org Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[Bug 281291] zfs: panic: MSan: Uninitialized malloc memory from zfs_acl_chmod
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281291 Bug ID: 281291 Summary: zfs: panic: MSan: Uninitialized malloc memory from zfs_acl_chmod Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: asom...@freebsd.org I tried to run the ZFS test suite with a GENERIC-KMSAN kernel. The sys/cddl/zfs/tests/bootfs/bootfs_test:bootfs_005_neg test paniced like this: panic: MSan: Uninitialized malloc memory from zfs_acl_chmod+0x2cd cpuid = 6 time = 1725502132 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x99/frame 0xfe00b4c9c540 vpanic() at vpanic+0x56e/frame 0xfe00b4c9c6d0 panic() at panic+0x1dd/frame 0xfe00b4c9c7e0 __msan_warning() at __msan_warning+0x244/frame 0xfe00b4c9c930 lzjb_compress() at lzjb_compress+0x9f6/frame 0xfe00b4c9ca70 zio_compress_data() at zio_compress_data+0x388/frame 0xfe00b4c9cb40 zio_write_compress() at zio_write_compress+0x12bd/frame 0xfe00b4c9cca0 zio_execute() at zio_execute+0x4e0/frame 0xfe00b4c9cd30 taskqueue_run_locked() at taskqueue_run_locked+0x607/frame 0xfe00b4c9ce30 taskqueue_thread_loop() at taskqueue_thread_loop+0x29e/frame 0xfe00b4c9cea0 fork_exit() at fork_exit+0x1ee/frame 0xfe00b4c9cf30 fork_trampoline() at fork_trampoline+0xe/frame 0xfe00b4c9cf30 --- trap 0x5a5a5a5a, rip = 0x5a5a5a5a5a5a5a5a, rsp = 0x5a5a5a5a5a5a5a5a, rbp = 0x5a5a5a5a5a5a5a5a --- KDB: enter: panic -- You are receiving this mail because: You are the assignee for the bug.
[Bug 257960] mkimg: partition 1: No such file or directory when using a ":" in the file name
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257960 --- Comment #3 from Ed Maste --- manu it looks like this comes from 8f3c71c85e5f -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276985] crash in LinuxKPI/drm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276985 --- Comment #48 from Tomasz "CeDeROM" CEDRO --- That kinda strange discussion resulted in installing 14.1-RELEASE AMD64 on problematic setup. I did replace one drive (all SATA ports in use) and made UFS install so not touching ZFS on 6 other drives. It works and I can test whatever you like :-) The OS is 14.1-RELEASE (not -p3) releng/14.1-n267679-10e31f0946d8 GENERIC amd64. I have installed *dbg, test, src, and ports packages via installer. On a bare install I did `pkg install drm-515-kmod` (version is 5.15.160). `kldload amdgpu` results in freeze, hardware reset is required, no kernel panic, no reaction to user input, etc. After reset `kldload amdgpu` gives the same result system freeze. There are no firmware files in /boot/firmware, which may indicate missing dependency for gpu-firmware-kmod. There is no package for drm-61-kmod. I have uninstalled drm-515-kmod. What would you like me to do at this point? What I would do right now: 1. freebsd-update fetch install to upgrade base to -p3. 2. Replace installed /usr/ports with git clone pointing to main. 3. Replace installed /usr/src with git clone pointing to releng/14.1 4. Build and install drm-61-kmod from ports. 5. Check if gpu-firmware-kmod was installed as drm-61-kmod dependency and build + install fro ports if not. Waiting for testing instructions :-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276985] crash in LinuxKPI/drm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276985 --- Comment #49 from Alexander Vereeken --- (In reply to Tomasz "CeDeROM" CEDRO from comment #48) Installing drm-xxx-kmod via packages (pkg) have to be used with caution. FreeBSD is building packages with the last supported release, that means it builds for 14.0 packages until its EoL. For a kernel related package such as drm-xxx-kmod it can cause a panic because the kernel mismatches. In your position i would build drm-61-kmod from ports as you have described: Making sure that ports is up to date and that the kernel source (/usr/src) matches with your current running kernel and then compile drm-61-kmod. The GPU-firmware can be installed via pkg without any problems. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276985] crash in LinuxKPI/drm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276985 --- Comment #50 from Olivier Certner --- (In reply to Tomasz "CeDeROM" CEDRO from comment #48) Your procedure is fine. Please test drm-61-kmod first, but then drm-515-kmod as well if you have time. I concur with Alexander. I'm not even sure that official DRM binary packages for, let's say 14.1-RELEASE, are supposed to always work on, let's say, 14.1-RELEASE-p3. To avoid problems, or if you encounter a crash, the first thing is to compile those from source. That's why I'm asking you to also recompile drm-515-kmod: I suspect the module built from it on your machine will load correctly (provided it builds correctly, which might not be the case given feh@'s experience above) instead of the crash you are reporting for the binary package's module. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 281291] zfs: panic: MSan: Uninitialized malloc memory from zfs_acl_chmod
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281291 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org Keywords||crash -- You are receiving this mail because: You are the assignee for the bug.
[Bug 281218] Quectel LTE MODEM not working anymore
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281218 free...@jjabba.com changed: What|Removed |Added CC||free...@jjabba.com --- Comment #2 from free...@jjabba.com --- I'm experiencing the same issue. My setup runs on an embedded system from PC Engines. Hardware: APU6B4: 1 SFP, 3 LAN, quad core CPU, 4 GB RAM Modem: Simcom SIM7600G-H LTE, mini-pci Software OPNsense 24.7.3_1-amd64 FreeBSD 14.1-RELEASE-p3 OpenSSL 3.0.14 Here is my PPP log: 2024-09-03T00:22:06 Informational ppp [wan_link0] Link: reconnection attempt 8 in 2 seconds 2024-09-03T00:22:06 Informational ppp [wan_link0] LCP: Down event 2024-09-03T00:22:06 Informational ppp [wan_link0] Link: DOWN event 2024-09-03T00:22:06 Informational ppp [wan_link0] MODEM: chat script failed 2024-09-03T00:22:06 Informational ppp [wan_link0] CHAT: line 391: label "MomIdentGeneriicc" not found 2024-09-03T00:22:06 Informational ppp Label 'MomIdentGeneriicc' not found 2024-09-03T00:22:06 Informational ppp [wan_link0] Link: reconnection attempt 7 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 281218] Quectel LTE MODEM not working anymore
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281218 --- Comment #3 from free...@jjabba.com --- On the topic of the repeat strings in the AT command log (labeell and MomIdentGeneriicc): - expect or chat timing issues? Not unlike string buffers over serial interfaces with incorrect baud. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 262301] [ctl] Cannot "kldunload ctl"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262301 BB Lister changed: What|Removed |Added CC||bblis...@gmail.com --- Comment #1 from BB Lister --- This problem still exists in 14.1-RELEASE-p4 FreeBSD 14.1-RELEASE-p4 GENERIC amd64 and it causes a strange mallfunction because if the process misbehaves and I kill -9 then I cannot even start it. I receive the error that the shares already exist. # ctld -d ctld: obtaining previously configured CTL luns from the kernel ctld: CTL port 0 "camsim" wasn't managed by ctld; ctld: CTL port 1 "ioctl" wasn't managed by ctld; ctld: CTL port 2 "tpc" wasn't managed by ctld; ctld: found CTL lun 0 "iqn.2012-06.gr.X:target500,lun,0" ctld: found CTL lun 1 "iqn.2012-06.gr.X:iscsi2tb,lun,0" ctld: obtaining configuration from /etc/ctl.conf ctld: auth-group "default" not defined; going with defaults ctld: portal-group "default" not defined; going with defaults ctld: opening pidfile /var/run/ctld.pid ctld: modifying lun "iqn.2012-06.gr.XX:target500,lun,0", CTL lun 0 ctld: modifying lun "iqn.2012-06.gr.X:iscsi2tb,lun,0", CTL lun 1 ctld: adding port "pg0-iqn.2012-06.XX:target500" ctld: error returned from port creation request: target "iqn.2012-06.XX:target500" for portal group tag 257 already exists ctld: failed to update port pg0-iqn.2012-06.XX:target500 ctld: adding port "pg0-iqn.2012-06.:iscsi2tb" ctld: error returned from port creation request: target "iqn.2012-06.:iscsi2tb" for portal group tag 257 already exists ctld: failed to update port pg0-iqn.2012-06.XXx:iscsi2tb ctld: not listening on portal-group "default", not assigned to any target ctld: listening on 0.0.0.0, portal-group "pg0" ctld: listening on [::], portal-group "pg0" and it exists. no client can connect to this. Rebooting the machine is not an option. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 281279] nfscl: panic: MSan: Uninitialized stack memory in nfscl_cberrmap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281279 --- Comment #1 from Alan Somers --- This might be a false alarm. From inspection, I can't find any code paths that would result in the "struct stat" buffer being uninitialized. Plus, nfscl_cberrmap+0xb86 does not lie within any known function, according to kgdb. Unless I can produce a build where KMSAN can correctly determine the location of the offending function, this will be impossible to fix. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 281279] nfscl: panic: MSan: Uninitialized stack memory in nfscl_cberrmap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281279 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #2 from Mark Johnston --- (In reply to Alan Somers from comment #1) It's probably a real bug (I've fixed several issues like this in the past), but the origin info is not helpful. In that case, I usually sprinkle kmsan_check() calls in areas that seem to be relevant, to try and iteratively narrow the problem down to its root cause. I've hit KMSAN issues in NFS before and fixed all that I could find. Offset 28 corresponds to st_uid, which is a bit surprising. Can you describe your NFS setup a bit? Are you using v3 or v4? What exports flags do you have set? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280538] adduser man page references wrong log file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280538 Alexander Ziaee changed: What|Removed |Added Assignee|b...@freebsd.org|zi...@runbox.com Status|New |In Progress -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276985] crash in LinuxKPI/drm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276985 --- Comment #51 from Tomasz "CeDeROM" CEDRO --- Yes I know packages are built on prior relases and that does not match kernel for drm, vbox, etc. So let's build all from ports :-) Okay so initiali testing of drm-61-kmod: 1. `freebsd-update fetch install` gave me 14.1-RELEASE-p4. 2. `mv /usr/src /usr/src.pkg; git clone https://git.freebsd.org/src.git /usr/src; cd /usr/src; git checkout releng/14.1`. One question here how do I know this is exactly the commit used for -p4? `uname -a` does not show me the commit anymore. 3. `mv /usr/ports /usr/ports.pkg; git clone https://git.freebsd.org/ports.git /usr/ports` gave me the latest ports tree. 4. `cd /usr/ports/graphics/drm-61-kmod; make install; kldload amdgpu` results in instant kernel panic (cannot find firmware?). 5. reboot. 6. `cd /usr/ports/graphics/gpu-firmware-amd-kmod; make install; kldload amdgpu` also results in instant kernel panic (still no firmware?). 7. reboot.. see lots of UFS corruption.. haven't seen those for a while with ZFS.. and I really have bad memories with SU+J on UFS it did hide corruption.. well `fsck -fy /` :-) 8. See what gpu-firmware-amd-kmod installed.. only gpu-firmware-amd-kmod-aldebaran-20230625_2 ??? 8. `cd /usr/ports/graphics/gpu-firmware-kmod; make install; kldload amdgpu` yeah it loaded fine right now :-) 9. Will use some xorg + enlighenment wm and report back after a while. (So far) conclusions: 1. drm-61-kmod seems to work on 14.1-RELEASE-p5 :-) 2. drm packages / ports are missing dependency on gpu-firmware-kmod package :-) Thanks for your time :-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 281279] nfscl: panic: MSan: Uninitialized stack memory in nfscl_cberrmap
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281279 --- Comment #3 from Alan Somers --- (In reply to Mark Johnston from comment #2) My mount flags are nfsv4,rw,minorversion=2 My server's export flags are -maproot=root -network 192.168.0.0/23 The offending file is /usr/home/somers/.local/share/fish/fish_history , and the KMSAN alert is triggered when fish calls fstat on that file whenever I run any command. But curiously, simply "ls"ing the file is insufficient to trigger the alert. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276985] crash in LinuxKPI/drm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276985 --- Comment #52 from Tomasz "CeDeROM" CEDRO --- Also I noticed ugly (UEFI) pixelerated font on my desktop (with AMDGPU) on 14.1 which is strange I have this nice font on laptop with 14.1 that I write from right now o_O -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276985] crash in LinuxKPI/drm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276985 --- Comment #53 from Tomasz "CeDeROM" CEDRO --- Ouch the kernel panics corrupted the UFS and after `fsck -fy /` it was not fixed correctly Xorg packages got broken on filesystem level :\ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279308] mdmfs does not work as documented
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279308 --- Comment #6 from Michael Proto --- Applied the patch to 14.1p4, issue resolved: # ./mdmfs -M -S -o async -s 16m md1 /media # mount -v /dev/md1 on /media (ufs, asynchronous, local, writes: sync 2 async 0, reads: sync 3 async 0, fsid 033fda663af4f405, vnodes: count 2 ) # tunefs -p /dev/md1 tunefs: POSIX.1e ACLs: (-a)disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) disabled tunefs: soft update journaling: (-j) disabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) disabled tunefs: maximum blocks per file in a cylinder group: (-e) 4096 tunefs: average file size: (-f)16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: space to hold for metadata blocks: (-k)40 tunefs: optimization preference: (-o) time tunefs: volume label: (-L) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276985] crash in LinuxKPI/drm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276985 --- Comment #54 from Tomasz "CeDeROM" CEDRO --- The rest of packages are installed with pkg. Enlightenment WM works fine and smooth. Firefox works fine and smooth, video playback in 4K works fine. FreeCAD works fine and smooth. Blender works fine and smooth. KiCAD works fine and smooth. PrusaSlicer works fine and smooth. OBS works fine and seems to use VAAPI hardware encoder :-) What I think of is maybe also VBox with 3D acceleration.. but not really important here I only need USB passthrough (its easier than on bhyve where I had to put whole PCI-E USB controller just for that). gzdoom returns Bus Error (core dumped) on launch.. but it works on the laptop.. maybe a port problem (problem is at libfluidsynth.so.3 -> memset.c:119:26). Not really important here. OpenArena freezes the computer on launch when the screen resolution changes and intro movie is supposed to display. No reaction to Ctrl+Alt+F1. No reaction to Ctrl+Alt+Del. Machine needs a hardware reset. After that reset UFS is corrupted (two consecutive runs of `fsck -fy /` in a single mode finds and fixes some issues but that may as well result in hidden filesystem corruption as before). I am really scared of that fs corruption and it jumped right here from start with UFS (its really good to have ZFS now). Other than that OpenArena problem I can switch resolutions and refresh rates at Enlightenment WM on both screens with no problem while video playback in web browser and recording with obs using vaapi hw enc. I would have to work on this setup with my standard load which is quite heavy for several days to asses if its stable. So far it works well but I did not stress test it. Do you have any stress test scripts that I can run? Also I am using linuxlator with latest debian base to work with some Linux only stuff for work. Is there any risk that if Linux package would use DRM it could also freeze whole machine just like OpenArena? This desktop has fairly old AMD FX-8320 CPU and ASUS Sabertooth 990FX 2.0 mainboard with hardware serial port. Maybe I can set this serial port so it spits out the dmesg on a screen / compuer freeze so I can pinpoint the cause? Maybe some debug over serial port is it possible here on FreeBSD (I usually use JTAG/SWD for that but on smaller non amd64/x86 RTOS platforms but remote gdb should be similar right)? Summing up I am happy that drm-61-kmod is some alternative to drm-515-kmod on 14.1-RELEASE that caused problems last time I used 14 branch (14.0-RELEASE). Not sure about the long time stability but I would like to try 5.15 and even 5.10 here if that is okay? :-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276985] crash in LinuxKPI/drm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276985 --- Comment #55 from Tomasz "CeDeROM" CEDRO --- Just to confirm this OpenArena freeze does not occur on 14.1-RELEASE on laptop with Intel DRM, all works fine here. -- You are receiving this mail because: You are the assignee for the bug.
