Date: Thu, 17 Oct 2024 08:27:21 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 246279] ciss device driver not allowing more than 48 drives to be detected by the CAM layer Message-ID: <bug-246279-227-aZGnOXh7oF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-246279-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279 --- Comment #42 from Peter Eriksson <pen@lysator.liu.se> --- (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 set the shutdown flag racing another thread that's setting it w/o > ciss_mtx held). Ideally, someone would chase that to ground who had the hardware and > the time to do so, but I do not. Perhaps we should make that panic / printf fix selectable via a sysctl knob? I agree that there is a bug somewhere since with the change to printf() I sometimes see a never-ending loop with errors instead. However, that takes longer to "develop" than the panic-reboot so it still makes it a bit more usable... It typically occurs with bad disks though, so another fix is to remove the bad disks :-) -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246279-227-aZGnOXh7oF>