diff options
author | Robin H. Johnson <robbat2@gentoo.org> | 2018-01-04 08:14:18 -0800 |
---|---|---|
committer | Robin H. Johnson <robbat2@gentoo.org> | 2018-01-04 08:24:22 -0800 |
commit | fccaf0ae53dc43de3b79968ce6bdf169e9dd0ddd (patch) | |
tree | c04b6387519bed176a0f8d0a6a2d11991f92da49 /licenses/sgb2ns | |
parent | sys-kernel/gentoo-sources: genpatches-4.14-16 (diff) | |
download | gentoo-fccaf0ae53dc43de3b79968ce6bdf169e9dd0ddd.tar.gz gentoo-fccaf0ae53dc43de3b79968ce6bdf169e9dd0ddd.tar.bz2 gentoo-fccaf0ae53dc43de3b79968ce6bdf169e9dd0ddd.zip |
sys-block/tw_cli: special version for >=3.8 kernel
TL;DR: if you run 3ware cards on a 3.8 or newer kernel, you need to
upgrade the utility to correctly write card variables, as the old
version will sometimes segfault.
Tested on hardware models: 9750-4i, 9650SE-8LPML, 9690SA.
Per email:
> I've noticed recently that sys-block/tw_cli will segfault on modern
> systems when setting variables on a card (at least on a 9750-4i).
> ...
> when you go to run a battery capacity test, it'll complete the capacity
> test command, but segfault before it can update the timestamp on the
> card to record the last capacity test date. That causes the date to
> become "01-Jan-1970", and then dmesg will get flooded with "Battery
> capacity test overdue" messages. That's what prompted me to open a case
> with Broadcom, and then try to find some kind of workaround.
Reported-by: Joshua Kinard <kumba@gentoo.org>
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
Package-Manager: Portage-2.3.16, Repoman-2.3.6
RepoMan-Options: --force
Diffstat (limited to 'licenses/sgb2ns')
0 files changed, 0 insertions, 0 deletions