Bug 575875
| Summary: | nut with USB TrippLite OMNIVIS1000 causes system lockup after powerfail | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Niels Mayer <NielsMayer> |
| Component: | nut | Assignee: | Michal Hlavinka <mhlavink> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | mhlavink, NielsMayer |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-06-04 07:42:56 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Niels Mayer
2010-03-22 15:51:05 UTC
Testing fixes in http://admin.fedoraproject.org/updates/nut-2.4.3-2.fc12 to see if fix "reduced size of buffer to maximum size supported by low-speed USB devices, which fixes some recent usbhid-ups problems" -- also relates to this bug. see also https://bugzilla.redhat.com/show_bug.cgi?id=575334 Thanks. I guess the other bug is not related, but let me know the result of testing. What's the result of testing? After running for a while without incident (2.6.32.10-90.fc12.x86_64 with nut-2.4.3-2.fc12.x86_64 nut-client-2.4.3-2.fc12.x86_64), I just ran a successful "pull the plug" test with the UPS powering the system: > Apr 9 16:19:03 gnulem upsmon[1734]: UPS tripplite@localhost on battery > Apr 9 16:19:03 gnulem wall[2455]: wall: user nut broadcasted 1 lines (36 chars) > ... > Apr 9 16:27:23 gnulem upsmon[1734]: UPS tripplite@localhost on line power > Apr 9 16:27:23 gnulem wall[2843]: wall: user nut broadcasted 1 lines (39 chars) I have yet to experience a lockup as described in my initial report. Since I installed the update 3/23, there have also been several small power glitches that have also NOT triggered the bug: > messages-20100328:9370:Mar 26 08:30:56 gnulem upsmon[1729]: UPS tripplite@localhost on battery > messages-20100328:9372:Mar 26 08:31:06 gnulem upsmon[1729]: UPS tripplite@localhost on line power > messages-20100404:1525:Mar 29 23:21:13 gnulem upsmon[1729]: UPS tripplite@localhost on battery > messages-20100404:1527:Mar 29 23:21:18 gnulem upsmon[1729]: UPS tripplite@localhost on line power IMHO, the same issue that caused a problem in the previous version of nut ( https://bugzilla.redhat.com/show_bug.cgi?id=575334 ) was also behind the problem I saw with the USB UPS device somehow causing the USB bus and X server to lockup after a power event, rendering keyboard/mouse input impossible. The fix -- "reduced size of buffer to maximum size supported by low-speed USB devices, which fixes some recent usbhid-ups problems" -- also fixes the problem here too, perhaps. (Then again, I also put the USB device that went on/offline during powerfail on the UPS, so there is less traffic on the USB bus anyways during the powerfail....) I'm leaving status in this "needinfo" request as "NEW" as I don't want to be accidentally closing bugs for you again. However, for me, using 2.4.3-2.fc12 version of 'nut', this issue is resolved. However, as F12 hasn't been updated with the new version of 'nut' this issue still exists in F12's latest: 2.4.3-1.fc12 . I hope my accidental closing of https://bugzilla.redhat.com/show_bug.cgi?id=575334 isn't the reason why F11's nut has the fix and F12's doesn't.... Thanks I'll leave this bug open for another week and when there are no other reporters, I'll close it.
> I hope my accidental closing of
> bug #575334 isn't the reason why F11's nut has the fix
> and F12's doesn't....
maybe, but id does not matter, update system should handle it anyway and if there is any problem with it then update system is buggy, which is definitely not your fault ;-)
I can see nut 2.4.3-3 in updates repo, so it's ok now. If you don't see it then it means mirror you are using is out of sync which should "fix" itself within a few hours.
> Thanks I'll leave this bug open for another week and when there are no other
reporters, I'll close it.
closing
I haven't seen this problem recur since the updates, so I agree this bug is closed. |