https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246279
--- Comment #42 from Peter Eriksson <p...@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 on the CC list for the bug.
