[Bug 280965] Typo in comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280965 Li-Wen Hsu changed: What|Removed |Added CC||lw...@freebsd.org Assignee|b...@freebsd.org|lw...@freebsd.org Status|New |In Progress -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280910] [PATCH] Fix crash for "tail -F"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280910 --- Comment #2 from commit-h...@freebsd.org --- A commit in branch stable/14 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=cf4a34bbc7dfee43e9983a847ecf0fa0ed1d258d commit cf4a34bbc7dfee43e9983a847ecf0fa0ed1d258d Author: Andre Albsmeier AuthorDate: 2024-08-19 07:54:24 + Commit: Konstantin Belousov CommitDate: 2024-08-21 10:32:49 + tail -F: fix crash PR: 280910 (cherry picked from commit 308399a179a49b7b858c725de10177fdb0502fd2) usr.bin/tail/forward.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280910] [PATCH] Fix crash for "tail -F"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280910 --- Comment #3 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=8dfa4e5b6ce2e22ef92c0ec13aa001994774c23f commit 8dfa4e5b6ce2e22ef92c0ec13aa001994774c23f Author: Andre Albsmeier AuthorDate: 2024-08-19 07:54:24 + Commit: Konstantin Belousov CommitDate: 2024-08-21 10:34:06 + tail -F: fix crash PR: 280910 (cherry picked from commit 308399a179a49b7b858c725de10177fdb0502fd2) usr.bin/tail/forward.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 264757] fetch: Show correct port number in -vv output
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264757 Dag-Erling Smørgrav changed: What|Removed |Added Resolution|--- |Works As Intended Status|Open|Closed --- Comment #4 from Dag-Erling Smørgrav --- I disagree. It's not the URL parser's place to decide default ports. And as your own example shows, `fetch -vv` correctly displays the port it connects to regardless. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280972] hms(4): Broken fresh after 13d00a43cba4c35fcc9e0ab567baf530126a6348
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280972 Bug ID: 280972 Summary: hms(4): Broken fresh after 13d00a43cba4c35fcc9e0ab567baf530126a6348 Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: mik...@freebsd.org My touchpad doesn't work anymore after https://github.com/freebsd/freebsd-src/commit/13d00a43cba4c35fcc9e0ab567baf530126a6348 It works fine if I revert this commit. This is a Dell Precision 3520 iichid0: at addr 0x2c irq 51 on iicbus7 hidbus0: on iichid0 hms0: on hidbus0 hms0: 3 buttons and [XYWH] coordinates ID=1 Not sure if it's the same problem as bug #280290, creating a new one. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280972] hms(4): Broken after 13d00a43cba4c35fcc9e0ab567baf530126a6348
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280972 Mikael Urankar changed: What|Removed |Added Summary|hms(4): Broken fresh after |hms(4): Broken after |13d00a43cba4c35fcc9e0ab567b |13d00a43cba4c35fcc9e0ab567b |af530126a6348 |af530126a6348 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280972] hms(4): Broken after 13d00a43cba4c35fcc9e0ab567baf530126a6348
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280972 Mikael Urankar changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
[Bug 269523] net/samba413: libc error with samba
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269523 Mateusz Piotrowski <0...@freebsd.org> changed: What|Removed |Added Version|CURRENT |Latest Assignee|b...@freebsd.org|sa...@freebsd.org Status|New |Open Product|Base System |Ports & Packages Component|bin |Individual Port(s) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280972] hms(4): Broken after 13d00a43cba4c35fcc9e0ab567baf530126a6348
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280972 Emmanuel Vadot changed: What|Removed |Added Status|New |Open --- Comment #1 from Emmanuel Vadot --- Can you share a verbose dmesg with and without this commit ? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280972] hms(4): Broken after 13d00a43cba4c35fcc9e0ab567baf530126a6348
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280972 --- Comment #2 from Mikael Urankar --- Created attachment 252985 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=252985&action=edit bad -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280972] hms(4): Broken after 13d00a43cba4c35fcc9e0ab567baf530126a6348
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280972 --- Comment #3 from Mikael Urankar --- Created attachment 252986 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=252986&action=edit good -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280978] Kernel panics with vfs.nfsd.enable_locallocks=1 and nfs clients doing hdf5 file operations
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280978 Bug ID: 280978 Summary: Kernel panics with vfs.nfsd.enable_locallocks=1 and nfs clients doing hdf5 file operations Product: Base System Version: 15.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: matthew.l.dai...@dartmouth.edu With vfs.nfsd.enable_locallocks=1, kernel panics or hung nfs server (more rarely) can be induced from Linux nfs clients doing hdf5 file operations. In testing, this has also sometimes resulted in irrecoverable zpool corruption due to (I assume) memory corruption. In testing on hardware and VMs, we have induced these failures usually within a few hours, but sometimes within several days to a week. We have replicated this on 13.0 through 15.0-CURRENT (20240725-82283cad12a4-271360). With this sysctl set to 0 (default), we are unable to replicate the issue, even after several weeks of 24/7 hdf5 file operations. Below is a backtrace from a recent panic on a test VM. Based on a suggestion from a colleague, we are currently running a test with a VM on 15.0-CURRENT (20240725-82283cad12a4-271360) with a single CPU, just to see if this has any effect. Thanks and please let me know what other information I can provide. #0 __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57 #1 doadump (textdump=textdump@entry=0) at /usr/src/sys/kern/kern_shutdown.c:404 #2 0x8049e0fa in db_dump (dummy=, dummy2=, dummy3=, dummy4=) at /usr/src/sys/ddb/db_command.c:596 #3 0x8049deed in db_command (last_cmdp=, cmd_table=, dopager=true) at /usr/src/sys/ddb/db_command.c:508 #4 0x8049dbad in db_command_loop () at /usr/src/sys/ddb/db_command.c:555 #5 0x804a15f6 in db_trap (type=, code=) at /usr/src/sys/ddb/db_main.c:267 #6 0x80b9c49f in kdb_trap (type=type@entry=3, code=code@entry=0, tf=tf@entry=0xfe00da2dfce0) at /usr/src/sys/kern/subr_kdb.c:790 #7 0x81068479 in trap (frame=0xfe00da2dfce0) at /usr/src/sys/amd64/amd64/trap.c:606 #8 #9 kdb_enter (why=, msg=) at /usr/src/sys/kern/subr_kdb.c:556 #10 0x80b4cd40 in vpanic (fmt=0x811db2b0 "%s", ap=ap@entry=0xfe00da2dff10) at /usr/src/sys/kern/kern_shutdown.c:967 #11 0x80b4cbc3 in panic ( fmt=0x81b98380 "N\235\024\201\377\377\377\377") at /usr/src/sys/kern/kern_shutdown.c:892 #12 0x81068edb in trap_fatal (frame=0xfe00da2e0010, eva=7) at /usr/src/sys/amd64/amd64/trap.c:950 #13 0x81068f80 in trap_pfault (frame=, usermode=false, signo=0x0, ucode=) at /usr/src/sys/amd64/amd64/trap.c:758 #14 #15 0x80a42cc7 in nfsrv_freelockowner ( stp=stp@entry=0xf8000459a600, vp=vp@entry=0x0, cansleep=cansleep@entry=0, p=p@entry=0xf8002716d740) at /usr/src/sys/fs/nfsserver/nfs_nfsdstate.c:1637 #16 0x80a45865 in nfsrv_freestateid (nd=nd@entry=0xfe00da2e0428, stateidp=stateidp@entry=0xfe00da2e0180, p=p@entry=0xf8002716d740) at /usr/src/sys/fs/nfsserver/nfs_nfsdstate.c:6651 #17 0x80a558b1 in nfsrvd_freestateid (nd=0xfe00da2e0428, isdgram=, vp=, exp=) at /usr/src/sys/fs/nfsserver/nfs_nfsdserv.c:4775 #18 0x80a35ecf in nfsrvd_compound (nd=0xfe00da2e0428, isdgram=0, tag=, taglen=0, minorvers=) at /usr/src/sys/fs/nfsserver/nfs_nfsdsocket.c:1338 #19 nfsrvd_dorpc (nd=nd@entry=0xfe00da2e0428, isdgram=isdgram@entry=0, tag=, taglen=0, minorvers=) at /usr/src/sys/fs/nfsserver/nfs_nfsdsocket.c:633 #20 0x80a4b608 in nfs_proc (nd=0xfe00da2e0428, xid=, xprt=0xf8000a8a6400, rpp=) at /usr/src/sys/fs/nfsserver/nfs_nfsdkrpc.c:474 #21 nfssvc_program (rqst=0xf80027e51800, xprt=0xf8000a8a6400) at /usr/src/sys/fs/nfsserver/nfs_nfsdkrpc.c:358 #22 0x80e62dd0 in svc_executereq (rqstp=0xf80027e51800) at /usr/src/sys/rpc/svc.c:1053 #23 svc_run_internal (grp=grp@entry=0xf80003201100, ismaster=ismaster@entry=1) at /usr/src/sys/rpc/svc.c:1329 #24 0x80e6220f in svc_run (pool=0xf80003201000) at /usr/src/sys/rpc/svc.c:1408 #25 0x80a4bd73 in nfsrvd_nfsd (td=td@entry=0xf8002716d740, args=args@entry=0xfe00da2e09a0) at /usr/src/sys/fs/nfsserver/nfs_nfsdkrpc.c:641 #26 0x80a66ada in nfssvc_nfsd (td=0xf8002716d740, uap=) at /usr/src/sys/fs/nfsserver/nfs_nfsdport.c:3877 #27 0x80dcc11c in sys_nfssvc (td=, uap=) at /usr/src/sys/nfs/nfs_nfssvc.c:107 #28 0x81069888 in syscallenter (td=0xf8002716d740) at /usr/src/sys/amd64/amd64/../../kern/subr_syscall.c:189 #29 amd64_syscall (td=0xf8002716d740, traced=0) at /usr/src/sys/amd64/amd64/trap.c:1192 #30 #31 0x2687a11d1eda in ?? () Backtrace stopped:
[Bug 280978] Kernel panics with vfs.nfsd.enable_locallocks=1 and nfs clients doing hdf5 file operations
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280978 Matthew L. Dailey changed: What|Removed |Added Attachment #252988|text/markdown |text/plain mime type|| --- Comment #1 from Matthew L. Dailey --- Created attachment 252988 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=252988&action=edit Steps to reproduce panics Attached are instructions on how to set up a server and client and steps to reproduce the panics. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280817] With DMAR enabled, my laptop panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280817 --- Comment #23 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=45543d3424d46f84a5399879e190fc359dcefbd4 commit 45543d3424d46f84a5399879e190fc359dcefbd4 Author: Konstantin Belousov AuthorDate: 2024-08-20 14:41:33 + Commit: Konstantin Belousov CommitDate: 2024-08-21 15:23:07 + DMAR: clear dmar_devs[unit] if attach failed This should stop attempts to use a unit which was not completely initialized, but referenced by ACPI DMAR table during scoped devices operions. PR: 280817 Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D46382 sys/x86/iommu/intel_drv.c | 11 +++ 1 file changed, 11 insertions(+) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280910] [PATCH] Fix crash for "tail -F"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280910 --- Comment #4 from commit-h...@freebsd.org --- A commit in branch releng/13.4 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=9b945635c147feb4ac6ebf84bd19e149e9a10227 commit 9b945635c147feb4ac6ebf84bd19e149e9a10227 Author: Andre Albsmeier AuthorDate: 2024-08-19 07:54:24 + Commit: Konstantin Belousov CommitDate: 2024-08-21 15:59:21 + tail -F: fix crash PR: 280910 Approved by:re (cperciva) (cherry picked from commit 308399a179a49b7b858c725de10177fdb0502fd2) (cherry picked from commit 8dfa4e5b6ce2e22ef92c0ec13aa001994774c23f) usr.bin/tail/forward.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280801] /bin/df -l reports remote (fuse) filesystems as local
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280801 --- Comment #3 from khw...@gmail.com --- (In reply to Ed Maste from comment #2) Linux does do it. so there should be a way to do so. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280801] /bin/df -l reports remote (fuse) filesystems as local
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280801 --- Comment #4 from Alan Somers --- There's nothing in the fuse protocol that indicates that. Furthermore, our VFS doesn't even track that on a per-mountpoint basis, only on a per-file system basis. So our choices are to consider all fusefs mounts as remote or to consider them all as local. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280801] /bin/df -l reports remote (fuse) filesystems as local
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280801 --- Comment #5 from Alan Somers --- Curious about the OP's comment, I checked the source code for GNU df. It doesn't have a good way to tell if a file system is remote, either. Instead, it just guesses based on the file system's type name. It's got a hard-coded list of a few file systems like "smbfs" and "cifs", and it also considers anything with a ":" in its name to be remote. So, not very good. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 280946] Realtek RTS522A recognized at boot but not when plugging a card.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280946 --- Comment #2 from Lorenzo Torres --- So, I tried putting my ThinkPad in the inverted_list in the sys/dev/rtsx/rtsx.c because apparently the boot option for it wasn't working and by inverting it works just the opposite way so this is not the issue. -- You are receiving this mail because: You are the assignee for the bug.
