aboutsummaryrefslogtreecommitdiff
path: root/tools/regression/p1003_1b
diff options
context:
space:
mode:
authorprateek sethi <prateekrootkey@gmail.com>2024-10-13 18:38:54 +0000
committerWarner Losh <imp@FreeBSD.org>2024-10-13 21:38:01 +0000
commitc0e0e530ced057502f51d7a6086857305e08fae0 (patch)
tree81a03ddc5a21657c1eb6e1528eb14f469f2de6e8 /tools/regression/p1003_1b
parentf50a0944d034519c300be1cd1c9518d259a17337 (diff)
downloadsrc-c0e0e530ced057502f51d7a6086857305e08fae0.tar.gz
src-c0e0e530ced057502f51d7a6086857305e08fae0.zip
mps/mpr: Add workaround for firmware not responding to IOC_FACTS or IOC_INIT
Sometimes, especially with older firmware, mps(4) would have trouble initializing the card in one of these two steps. Add in a retry after a short delay. Sean Bruno and Stephen McConnell thought this was OK in the bug discussions, but never committed it. Steve indicated the delay might not be necessary, but the OP clearly needed to make it longer to make things work. I've kept the delay, and added the suggested comment. Ported the iocfacts part to mpr as well, since we see similar errors about once every month or two over a few thousand controllers at work. We've not seen it with IOC_INIT as far back as I can query the error log database, so I didn't port that forward. We'll see if this helps, but won't know for sure until next year (so I'm committing it now since it won't hurt and might help). We usually see this failure in connection with complicated recovery operations with a drive that's failing, though, at least in the last year's worth of failures. It's not clear this is the same as OP or not. PR: 212841 Sponsored by: Netflix Co-authored-by: imp
Diffstat (limited to 'tools/regression/p1003_1b')
0 files changed, 0 insertions, 0 deletions