summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdlib/rand.c
diff options
context:
space:
mode:
authoryongari <yongari@FreeBSD.org>2012-04-25 02:46:13 +0000
committeryongari <yongari@FreeBSD.org>2012-04-25 02:46:13 +0000
commit1ecac70b9bf3981112c5133eb6a2f90566188c97 (patch)
tree429c1b4c2846250972be3e2109e83f8411ce706c /lib/libc/stdlib/rand.c
parent51624e0f68c22df8810cc6a81c39edd7c8c4ce2d (diff)
downloadFreeBSD-src-1ecac70b9bf3981112c5133eb6a2f90566188c97.zip
FreeBSD-src-1ecac70b9bf3981112c5133eb6a2f90566188c97.tar.gz
For Yukon II controllers that implement optional temperature sensor
and voltage sensor, TWSI is used to get sensor data. msk(4) does not monitor these sensors and interrupt for TWSI completion is disabled by default. However, due to unknown reason, the TWSI completion interrupt fires and it resulted in interrupt storm. To fix it, acknowledges the TWSI completion interrupt if driver see the event. Given that not all Yukon II controllers show the issue it could be a silicon bug which does not honor interrupt masking. Probably the right way to address the issue is disabling automatic TWSI cycle initiation against these sensors. It would be even better to implement reading voltage/temperature from the NIC but it requires access to National LM80 through TWSI and documentation to do that is not available yet(probably will never happen). Reported by: jhb Tested by: jhb MFC after: 2 weeks
Diffstat (limited to 'lib/libc/stdlib/rand.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud