Bug 197443
Summary: | 2.6.17-1.2139_FC5 breaks newhidups for my usb attached ups | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bruno Wolff III <bruno> |
Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | davej, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-07-04 16:40:12 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
Bruno Wolff III
2006-07-01 17:07:31 UTC
I tried out kernel-2.6.17-1.2339.fc6 and it also has the same problem. I was able to get newhidups to work with kernel-smp-2.6.17-1.2139_FC5 eventaully. So I am pretty sure the problem is my fault and not a bug. I suspect that I wasn't getting back to a clean spot when doing some of my tests and so I wasn't testing the conditions I thought I was and thought some combinations of kernel and nut were working when they weren't (because of the test version of nut, not the kernel) and in other cases that they weren't working (with the supported version of nut) when they were. So I am going to resolve this as "not a bug". Sorry for the noise. This is just FYI, but I think I figured out how I managed to get confused. It seems as if when newhidups is started (at least for the supported 2.0.3 version), it leaves something running even if it is uninstalled and the ups service is restarted. So I think the order I did things was this: Got nut 2.0.3 running on 2.6.16. Installed nut 2.1 from nut development, but didn't reboot and things were still working. Upgraded to 2.6.17 kernel at which point things stopped working. Tried switching back to nut-2.0.3, still broken because I didn't reboot. Switched back to 2.6.16 and then things were working again (because of the reboot, not the downgrade). One more FYI update on this. I did get nut 2.1 to work on 2.6.17 by having the daemons run as root. I think what the sticky status might be, is access to the usb device. The nut development rpm may not have provided that access to user 'nut', while the fedora rpm did. That seems like it would be something that would stay until a reboot. This is the last followup to this. I did find there was udev rules file installed by the FC nut rpm that wasn't installed by the one from nut development, and this was the source of my problems. Now that I have that file in place everything is working as expected. |