[Bug 228536] x11/nvidia-driver: 11.2-BETA3 - fails to operate correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228536 Ahmed changed: What|Removed |Added CC||ahmedsayeed1...@yahoo.com --- Comment #15

[Bug 228535] emulators/virtualbox-ose-kmod: 11.2-BETA3 - kldload vboxdrv leads to panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228535 Ahmed changed: What|Removed |Added CC||ahmedsayeed1...@yahoo.com --- Comment #21

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 Marek Zarychta changed: What|Removed |Added CC||stable@FreeBSD.org -- You are re

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 --- Comment #4 from Slawomir Wojciech Wojtczak --- Isn't the vt(4) 'the future' for terminal on FreeBSD? Maybe vidcontrol(1) should just be fixed to work on vt(4)? -- You are receiving this mail because: You are on the CC list for the bu

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 --- Comment #5 from Chris Hutchinson --- (In reply to Marek Zarychta from comment #3) > Unfortunately, sc(4) can be only enabled when you are not booting with EFI. Well. That may be true on your hardware. But all our servers, and all my per

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 Tomoaki AOKI changed: What|Removed |Added CC||junch...@dec.sakura.ne.jp --- Comme

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #7 from

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 Ed Maste changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 --- Comment #8 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=1f4442f71fa33a8ef6d3da808e32872fb23a5700 commit 1f4442f71fa33a8ef6d3da808e32872fb23a5700 Author:

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 --- Comment #9 from Ed Maste --- (In reply to Slawomir Wojciech Wojtczak from comment #2) | DESCRIPTION | The vidcontrol utility is used to set various | options for the syscons(4) or vt(4) console driver immediately after that: Only

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 Ed Maste changed: What|Removed |Added Status|New |In Progress -- You are receiving this

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 --- Comment #10 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=c71ae91f1976746b380a8aada8676d7ae084fdc5 commit c71ae91f1976746b380a8aada8676d7ae084fdc5 Author:

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 Ed Maste changed: What|Removed |Added Assignee|b...@freebsd.org|ema...@freebsd.org -- You are receivin

[Bug 263099] vidcontrol(1) -p and -P does not work

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263099 Ed Maste changed: What|Removed |Added CC|stable@FreeBSD.org | -- You are receiving this mail becaus

[Bug 193386] [panic] resource_list_alloc: resource entry is busy

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193386 Graham Perrin changed: What|Removed |Added Keywords||crash --- Comment #2 from Graham P

[Bug 229694] [zfs] unkillable "zpool scrub" in [tx->tx_sync_done_cv] state for damaged data

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229694 --- Comment #6 from Eugene Grosbein --- It is reproduceacble exactly same way under 13.2-PRERELEASE/amd64 with stock ZFS. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 271238] mpr (LSI SAS3816) driver not finding ses devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 Marek Zarychta changed: What|Removed |Added CC||stable@FreeBSD.org,

[Bug 271238] mpr (LSI SAS3816) driver not finding ses devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 --- Comment #2 from Peter Eriksson --- (In reply to Marek Zarychta from comment #1) Regarding the P440 - is it using the "ciss" driver? Then yes, that driver has well known bugs regarding discovering disks due to a couple of errors in the

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 Marek Zarychta changed: What|Removed |Added CC||stable@FreeBSD.org,

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #20 from Peter Eriksson --- See comment #12 a bit up here :-) -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 271238] mpr (LSI SAS3816) driver not finding ses devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 Warner Losh changed: What|Removed |Added CC||i...@freebsd.org --- Comment #3 from

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #22 from Peter Eriksson --- Yes, I'll try to test it later today. I'll get back with some results. - Peter -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #23 from Peter Eriksson --- First test on a server with two HP H241 HBA cards with just 5 disks (in two boxes) running FreeBSD 12.4 with the full ciss.c from Fabricator - works fine. Next I'll test it on another server with 14

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #24 from Peter Eriksson --- Result on the bigger server: Booted, but then I got a long list of CAM errors ending with a "ADAPTER HEARTBEAT FAILED". ... (da116:ciss2:32:56:0): CAM status: CCB request completed with an error (d

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #25 from Peter Eriksson --- Rebooted and tried with hw.ciss.nop_message_heartbeat=1, then logged in via ssh and ran an "sesutil show" (before zfs had started importing pools), then it panic:ed with: login: (da116:ciss2:32:56:0)

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #26 from Peter Eriksson --- On the third attempt I just let it keep trying, no "sesutil show". And then it eventually printed: (da116:ciss2:32:56:0): SCSI status: Check Condition (da116:ciss2:32:56:0): SCSI sense: ILLEGAL

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #27 from Marek Zarychta --- Thanks for taking an effort to test it again Peter. Without the patch you authored, the tests would end sooner with no panic and 40 instead of 140 drives seen. That's a large setup and the solution is

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #28 from Peter Eriksson --- Actually, with hw.ciss.nop_message_heartbeat="0" my first test ended with ciss2: ADAPTER HEARTBEAT FAILED and then things deadlocked. With: hw.ciss.nop_message_heartbeat="1" and if I d

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 Peter Eriksson changed: What|Removed |Added Version|12.1-RELEASE|12.4-RELEASE -- You are receivin

[Bug 270601] freebsd-hackers and freebsd-stable list archives: for some messages, URLs have changed

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270601 Graham Perrin changed: What|Removed |Added CC||hack...@freebsd.org,

[Bug 270601] freebsd-hackers and freebsd-stable list archives: for some messages, URLs have changed

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270601 --- Comment #3 from Graham Perrin --- (In reply to Graham Perrin from comment #2) Two more examples from the same period (January 2022). A)

[Bug 270601] freebsd-hackers and freebsd-stable list archives: for some messages, URLs have changed

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270601 Charlie Li changed: What|Removed |Added CC|hack...@freebsd.org,| |stable@FreeBSD.or

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 Graham Perrin changed: What|Removed |Added Keywords|patch | -- You are receiving this mail b

[Bug 271238] mpr (LSI SAS3816) driver not finding ses devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 mgro...@shrew.net changed: What|Removed |Added CC||mgro...@shrew.net --- Comment #

[Bug 278099] outdated version of zstd(1) is kept in the base

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278099 Marek Zarychta changed: What|Removed |Added CC||stable@FreeBSD.org -- You are re

[Bug 278099] outdated version of zstd(1) is kept in the base

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278099 Xin LI changed: What|Removed |Added CC||allanj...@freebsd.org,

[Bug 278099] outdated version of zstd(1) is kept in the base

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278099 --- Comment #2 from Marek Zarychta --- PR was submitted on April 1 and after this date, all suggestions but backdoor pronity are still legitimate. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 278099] outdated version of zstd(1) is kept in the base

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278099 --- Comment #3 from Alexander Motin --- (In reply to Xin LI from comment #1) ZFS intentionally keeps older versions of compressors (decompressors can be updated) to produce identical results when needed (L2ARC on system with uncompressed AR

[Bug 278099] outdated version of zstd(1) is kept in the base

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278099 Dag-Erling Smørgrav changed: What|Removed |Added CC||d...@freebsd.org --- Comment

[Bug 278099] outdated version of zstd(1) is kept in the base

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278099 --- Comment #5 from Marek Zarychta --- (In reply to Dag-Erling Smørgrav from comment #4) >“pronity” is not a word, and I don't think “prone” means what you think it >means: https://www.merriam-webster.com/dictionary/prone Maybe it's not a

[Bug 278099] outdated version of zstd(1) is kept in the base

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278099 --- Comment #6 from Xin LI --- (In reply to Alexander Motin from comment #3) For future reference in case someone wanted to give this a shot, the concerns at OpenZFS[1] was that different versions of zstd may [2] generate different output f

[Bug 278099] outdated version of zstd(1) is kept in the base

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278099 alex-freebsd-b...@alexburke.ca changed: What|Removed |Added CC||alex-freebsd-bugs@a

[Bug 278099] outdated version of zstd(1) is kept in the base

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278099 --- Comment #8 from Chris Hutchinson --- pronity: noun Proneness; propensity. It *is* a word. It's been in use since 1913. If you happen to have a copy of the Websters dictionary with a print/publishing date of 1913. You'll find it there.

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 Mark Linimon changed: What|Removed |Added Attachment #214328|0 |1 is patch|

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #33 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=b339ab1491055d89415f85b6d1a03423193178f9 commit b339ab1491055d89415f85b6d1a03423193178f9 Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #31 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=7c74337e2c3d2269d1559f4e5541c0a3f402d814 commit 7c74337e2c3d2269d1559f4e5541c0a3f402d814 Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #32 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=fd95966af50bab6229bc5e67fadc7ffd915f77f5 commit fd95966af50bab6229bc5e67fadc7ffd915f77f5 Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #30 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=45645518ea19ccb4761aee3a525aab2f323d37d4 commit 45645518ea19ccb4761aee3a525aab2f323d37d4 Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #36 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=d8b024673bbfb32259030db7e54f043f3e471abe commit d8b024673bbfb32259030db7e54f043f3e471abe Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #35 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=a35564358ac442d5d7a5c9c2dd0544f07b1963e7 commit a35564358ac442d5d7a5c9c2dd0544f07b1963e7 Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #40 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=f03e1a42e92eff76dcf474655b600db37b04ae2b commit f03e1a42e92eff76dcf474655b600db37b04ae2b Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #41 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=cafc839393db5c5d8000fd086118b3c7b47e95c2 commit cafc839393db5c5d8000fd086118b3c7b47e95c2 Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #34 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=cec58bba6425d4b9cf19a9ede9ca0dc00c1d48e3 commit cec58bba6425d4b9cf19a9ede9ca0dc00c1d48e3 Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #38 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=74575d14284fde2c7617ad14fd9a8bac897b4427 commit 74575d14284fde2c7617ad14fd9a8bac897b4427 Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #37 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=f373e6b866b9efafc66ccc5355e1ea0aeeedfb6a commit f373e6b866b9efafc66ccc5355e1ea0aeeedfb6a Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #39 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=77af8c6db25ff6154268eb17f54f082a7eb61ea0 commit 77af8c6db25ff6154268eb17f54f082a7eb61ea0 Author:

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #29 from Warner Losh --- OK. I've staged the rebased patch I broke it down into tiny bites in case there's problems. I've also noted my extreme reservations about making the cr == NULL panic just a printf. There's some race that

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #42 from Peter Eriksson --- (In reply to commit-hook from comment #33) > I've also noted my extreme reservations about making the cr == NULL > panic just a printf. There's some race that's causing it (I think > with where we se

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|i...@freebsd.org Flags

[Bug 271238] mpr (LSI SAS3816) driver not finding ses devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 Peter Eriksson changed: What|Removed |Added Version|12.4-RELEASE|13.4-RELEASE -- You are receivin

[Bug 271238] mpr (LSI SAS3816) driver not finding ses devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 --- Comment #5 from Peter Eriksson --- Still seening strange behaviour with the SAS3816 controller and mpr driver on FreeBSD 14.1-RELEASE-p5 Now all the SES controllers are detected and accessible, but instead it doesn't correctly detect a

[Bug 271238] mpr (LSI SAS3816) driver not finding ses devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 Peter Eriksson changed: What|Removed |Added Severity|Affects Only Me |Affects Some People -- You are r

[Bug 271238] mpr (LSI SAS3816) driver not finding ses devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 Peter Eriksson changed: What|Removed |Added Version|13.4-RELEASE|14.1-RELEASE -- You are receivin

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 --- Comment #15 from Peter Eriksson --- Btw, for someone else trying to read the output from "mprutil show cfgpage", it prints the bytes backwards... > # mprutil show cfgpage 0x15 0 1 > Page 0x15: Enclosure 0, Read-only > 0f 00 00

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 --- Comment #14 from Peter Eriksson --- (In reply to Rafe from comment #13) Yes, it's that mapping that fails. However I can't use "-1" since from the man page: "device. This feature is not recommended if the topology includes multiple

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 Rafe changed: What|Removed |Added CC||mondo.debater...@icloud.com --- Comment #13

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 --- Comment #9 from Peter Eriksson --- Created attachment 255468 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255468&action=edit Add hw.mpr.encl_min_slots loader.conf setting to override detected num_slots Please find enclosed

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 k...@denninger.net changed: What|Removed |Added CC||k...@denninger.net --- Comment

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 Michael Osipov changed: What|Removed |Added CC||micha...@freebsd.org --- Comment

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 --- Comment #12 from Peter Eriksson --- Correct, it's a workaround. Ideally it would have been constructed as some kind of blacklist so one could have different override values for different enclosures but that requires more work and this q

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 --- Comment #6 from Peter Eriksson --- Some more interresting details from the lastest boot. At boot all the disks are detected, however Partial output from "mpr show devices" > 00 101 5000cca2912db98d 00390017 SAS Target

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 --- Comment #7 from Peter Eriksson --- Created attachment 255443 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=255443&action=edit Boot, and various outputs from mprutil & sesutil Some log files from system boot and outputs from

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 Peter Eriksson changed: What|Removed |Added Summary|mpr (LSI SAS3816) driver|mpr (LSI SAS3816) driver

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 --- Comment #8 from Peter Eriksson --- Hmm. I added some debugging printf's to the mpr driver and rebooted. It says: > mpr0: mpr_mapping_initialize: Mapping table has a max of 2622 entries and DPM > has a max of 128 entries. > mpr0: _mapp

[Bug 283755] ports-mgmt/pkg: pkg-upgrade(8) - version comparison new kernel modules ("kmods") failure

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283755 Graham Perrin changed: What|Removed |Added CC||stable@FreeBSD.org -- You are rec

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 Peter Eriksson changed: What|Removed |Added Version|14.1-RELEASE|14.2-RELEASE -- You are receivin

[Bug 271238] mpr (LSI SAS3816) driver not finding all devices in HP D6020 enclosures

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271238 --- Comment #16 from Peter Eriksson --- Still the same problem in FreeBSD 14.2-RELEASE... (The patch solves the issue). -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 193386] [panic] resource_list_alloc: resource entry is busy

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193386 Mark Linimon changed: What|Removed |Added Resolution|--- |Overcome By Events Stat

[Bug 283755] ports-mgmt/pkg: pkg-upgrade(8) - version comparison new kernel modules ("kmods") failure

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283755 --- Comment #2 from Eric --- (in reply to comment #1) Thanks. With the suggested settings, it seems the following sequence of two commands is a practicle work-around at the moment: pkg upgrade -r FreeBSD pkg upgrade -r FreeBSD-kmods

[Bug 283755] ports-mgmt/pkg: pkg-upgrade(8) - version comparison new kernel modules ("kmods") failure

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283755 --- Comment #4 from Eric --- (in reply to comment #3 ) As shown in the attached debug out, it seems there is definitely a problem with version comparison: drm-61-kmod-6.1.92.1402000_3 is recognised but rejected. -- You are receiving t

[Bug 283755] ports-mgmt/pkg: pkg-upgrade(8) - version comparison new kernel modules ("kmods") failure

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283755 --- Comment #3 from Eric --- Created attachment 256383 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=256383&action=edit debug output from pkg upgrade drm-61-kmod -- You are receiving this mail because: You are on the CC list f

[Bug 283755] ports-mgmt/pkg: pkg-upgrade(8) - version comparison new kernel modules ("kmods") failure

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283755 Mark Millard changed: What|Removed |Added CC||marklmi26-f...@yahoo.com --- Commen

[Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 Mark Linimon changed: What|Removed |Added Status|Open|In Progress -- You are receiving t

[Bug 278099] outdated version of zstd(1) is kept in the base

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278099 --- Comment #9 from Marek Zarychta --- Zstandard (zstd) version 1.5.7 was released last week, introducing significant performance enhancements and bug fixes[1] We have zstd 1.5.2 in the base system. It was released 3+ years ago and there a