[Bug 251248] Broadcom (LSI) 9300-8e mpr driver does not show all paths
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251248 --- Comment #4 from Dmitry Popovich --- Created attachment 219807 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219807&action=edit sesutil output -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251248] Broadcom (LSI) 9300-8e mpr driver does not show all paths
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251248 --- Comment #3 from Dmitry Popovich --- Created attachment 219806 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219806&action=edit mprutil output -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251248] Broadcom (LSI) 9300-8e mpr driver does not show all paths
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251248 --- Comment #2 from Dmitry Popovich --- Created attachment 219805 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219805&action=edit geom output -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251248] Broadcom (LSI) 9300-8e mpr driver does not show all paths
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251248 --- Comment #1 from Dmitry Popovich --- Created attachment 219804 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219804&action=edit dmesg output -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251248] Broadcom (LSI) 9300-8e mpr driver does not show all paths
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251248 Bug ID: 251248 Summary: Broadcom (LSI) 9300-8e mpr driver does not show all paths Product: Base System Version: 12.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: d...@mvdnet.org Created attachment 219803 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219803&action=edit logs mpr driver does not show all paths to dual-port disks. Tested on 2 LSI 9300-8e connected to HP D2700 （SAS2) disk external enclosure with 12 HDDs on HP DL360p Gen9 and HP D3700 (SAS3) disk enclosure with 10 SSDs and Supermicro X10SRH-CLN4F, FreeBSD 12.1 and 12.2 Same hardware setup works perfectly on Linux. mps driver (LSI 9207-8e) also works fine in FreeBSD I attached dmesg.log, geom, mprutil and sesutil output as you can see from geom output it can see only 1 device with 2 paths -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251227] setpgid sometimes returns ESRCH instead of EACCES
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251227 --- Comment #5 from Mahmoud Al-Qudsi --- Thanks for bringing my attention to the approach taken by sh - it made me realize what I'd missed. So you're right, there's no broken job control here. This is a real issue: > [..] prevents a subsequent process in the same job from getting access to a > shell that was assigned over to the newly minted pgrp that now contains only > zombies but it doesn't apply to FreeBSD, which is why sh can get away with ignoring any setpgid failures. (Interestingly, tcsh handles this situation by swapping pgrps in the middle of a single job invocation.) It turns out that while FreeBSD does not consider zombie processes as valid targets of a setpgid(2) call, it *does* keep their pgrp around and permits other processes to join the pgrp even if it only contains zombies. While the original issue persists and setpgid(zombie_pid, zombie_pid) calls fail with ESRCH instead of the expected EACCES, as you say, this is trivially handled if you have any degree of confidence that you are specifying a target process that is or was a valid child pid from the same session... and (more tenuously) assuming you know this is the behavior on at least some of the platforms you are targeting. It's not the end of the world by any means, but I would argue that the consideration of zombie child processes should be an everywhere or nowhere at all type of thing (and this is where my assumption of broken job control came from). e.g. Linux considers zombie processes in setpgid calls (only to determine the error code) and lets new processes join pgrps that contain only zombies, whereas some kernels (e.g. WSLv1 up until recently) don't consider zombies at all and reclaim pgrps as soon as the last process in it exits (before it's reaped). That aside, I'm assuming we can all agree it would be great for the man pages to clarify the behavior when it comes to zombie procs. Are you open to a patch? Thanks! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 231027] [META] FreeBSD-Foundation sponsored issues for FreeBSD 13-CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027 Bug 231027 depends on bug 217736, which changed state. Bug 217736 Summary: addr2line incorrectly resolves filename/lineno/function https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217736 What|Removed |Added Status|In Progress |Closed Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242039] eBox 3352DX3-AP (Vortex86DX3) crashes on 12.1 release
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242039 Andrius V changed: What|Removed |Added CC||vezh...@gmail.com --- Comment #1 from Andrius V --- The issue still persists on 12.2-RELEASE, however I have a bit more information. System successfully boots without SMP. The crash seemingly happens on second CPU (core) initialization (panic message prints cpuid = 1, time = 1). Just for information, CPU itself does not support PAE (flags from /proc/cpuinfo: fpu pse tsc msr cx8 apic sep pge cmov mmx fxsr sse cpuid). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233225] libssl.so.8 not found by pkg
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233225 kynes.l...@gmail.com changed: What|Removed |Added CC||kynes.l...@gmail.com --- Comment #14 from kynes.l...@gmail.com --- 'pkg bootstrap -f' worked for me then 'pkg update|upgrade' -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251025] efivar cannot write to EFI variables which have a '-' in their name
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251025 Warner Losh changed: What|Removed |Added Assignee|b...@freebsd.org|i...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242212] usr.sbin/mergemaster/mergemaster.sh: There is no logic to handle symbolic links
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242212 --- Comment #10 from commit-h...@freebsd.org --- A commit references this bug: Author: imp Date: Wed Nov 18 19:22:24 UTC 2020 New revision: 367810 URL: https://svnweb.freebsd.org/changeset/base/367810 Log: mergemaster: handle symbolic links during update. /etc/os-release is now a symbolic link to a generated file. Make mergemaster cope with symbolic links generically. I'm no longer a big mergemaster user, so this has only been lightly tested by me, though Kimura-san has ran it through its paces. Submitted by: Yasushiro KIMURA-san PR: 242212 MFC After: 2 weeks Changes: head/usr.sbin/mergemaster/mergemaster.sh -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242212] usr.sbin/mergemaster/mergemaster.sh: There is no logic to handle symbolic links
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242212 --- Comment #9 from Warner Losh --- I've committed r367810 which should fix this. I'll try to remember to MFC in 2 weeks. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251025] efivar cannot write to EFI variables which have a '-' in their name
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251025 prob...@puredarwin.org changed: What|Removed |Added Summary|efivar cannot write to EFI |efivar cannot write to EFI |variables which have a ':' |variables which have a '-' |in their name |in their name --- Comment #4 from prob...@puredarwin.org --- Confirm, thuis -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250667] Frequent Kernel panic for spin lock on TrueNAS (FreeBSD 12.2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250667 Alexander Motin changed: What|Removed |Added CC||m...@freebsd.org --- Comment #8 from Alexander Motin --- Seb, I've built TrueNAS 12.0-RELEASE kernel with the Mark's patch: https://people.freebsd.org/~mav/kernel.tgz You may create boot environment just in case, unpack the archive into /boot and reboot. Let us know whether it help. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251227] setpgid sometimes returns ESRCH instead of EACCES
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251227 --- Comment #4 from Conrad Meyer --- Thanks for the additional context, Mahmoud! I guess I'm confused on why this is a problem. Can fish just ignore ESRCH in this context on FreeBSD? Certainly half a dozen other shells run on FreeBSD and implement some form of job control. E.g., /bin/sh ignores the return value of setpgid() entirely. I don't see any requirement in POSIX around FreeBSD's ESRCH behavior (I looked at it briefly yesterday, too). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251112] Compiling C++ with asan fails by default because libclang_rt.asan-x86_64.so uses symbol pthread_attr_get_np but doesn't link to libpthread.so
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251112 --- Comment #5 from Andrew Stitcher --- (In reply to Konstantin Belousov from comment #4) I'm not sure I really understand what you mean about linking with libpthread.so changing the behaviour of libc.so. Most of the FreeBSD pthread calls are already in libc (or at least don't need to explicitly link with -lpthread according to the manpage). So I expected that libc is already multithreaded and linking in pthread is only used for the _np (non portable/posix) pthread calls. Looking at the clang source code pthread_attr_get_np is used to get the stack parameters (pthread_getattr_np is #defined to pthread_attr_get_np): pthread_attr_t attr; pthread_attr_init(&attr); CHECK_EQ(pthread_getattr_np(pthread_self(), &attr), 0); my_pthread_attr_getstack(&attr, &stackaddr, &stacksize); pthread_attr_destroy(&attr); I'm not sure how relevant this is to what you're interested in, but the symbol is used to call a function. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241831] freebsd-update from 11.3 to 12.1 causes error messages "Directory not empty"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241831 Doug Poland changed: What|Removed |Added CC||d...@polands.org --- Comment #4 from Doug Poland --- Same on 11.4 to 12.2 amd64 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 250667] Frequent Kernel panic for spin lock on TrueNAS (FreeBSD 12.2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250667 --- Comment #7 from Mark Johnston --- By coincidence, syzkaller found a bug which manifests with exactly the same panic. I posted a patch for it here: https://reviews.freebsd.org/D27266 I'm not sure if this is what you're hitting, but it seems plausible if you have a lot of CPU load on the system. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251216] fetch(1) not able to fetch file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251216 verma...@interia.pl changed: What|Removed |Added Status|Open|Closed Resolution|--- |Not A Bug --- Comment #9 from verma...@interia.pl --- I am sorry. I had an alias for fetch with -A ... % which fetch fetch: aliased to fetch -ApRr --no-verify-peer --no-verify-hostname My bad. Sorry for your lost time. Regards. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251216] fetch(1) not able to fetch file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251216 and...@tao11.riddles.org.uk changed: What|Removed |Added CC||and...@tao11.riddles.org.uk --- Comment #8 from and...@tao11.riddles.org.uk --- (In reply to vermaden from comment #5) (I am the "someone on IRC" previously mentioned) As far as I can tell, it's impossible to get this verbose output: > requesting https://github.com/amir/sctd/archive/0.2.0.tar.gz > fetch: https://github.com/amir/sctd/archive/0.2.0.tar.gz: Moved Temporarily unless the -A flag is somehow becoming set in libfetch. Without that flag, that code path would always lead through code that outputs this: > 302 redirect to https://codeload.github.com/amir/sctd/tar.gz/0.2.0 What if you run it in a clean environment with env -i? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 251237] 12.2 EFI console resolution regression
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251237 Bug ID: 251237 Summary: 12.2 EFI console resolution regression Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: freebsd-b...@morgandavis.net Booting UEFI into 12.1 provided a native resolution text console with hundreds of columns and dozens of rows of crisp text on a 17" monitor. Perfect for tmux with lots of panes. I don't recall having to do anything special to get this -- just booting via EFI gave this benefit over legacy BIOS boot. After upgrading the system from 12.1 to 12.2-RELEASE, the system no longer boots up with that high resolution text console. I'm now stuck with the 80x25 fuzzy and giant text display. "vidcontrol -i mode" returns no entries at all so I can't even force a specific video display mode. Does 12.2 have new hardware requirements for EFI version/compatibility or video text console resolutions? Hoping this is a regression that can be fixed. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Приглашаем к публикации [РИНЦ]
___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
