Bug 164051 - "Unhandled event" in hidups driver
Summary: "Unhandled event" in hidups driver
Keywords:
Status: CLOSED DUPLICATE of bug 160700
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-23 11:44 UTC by Matthew Saltzman
Modified: 2015-01-04 22:21 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-11-05 06:29:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matthew Saltzman 2005-07-23 11:44:03 UTC
Description of problem:

When unning nut with the hidups driver, I get entries in /var/log/messages every
5 seconds, as follows:

Jul 17 04:02:52 yankee hidups[2046]: Ignoring x86 page event 0xff860060 (8)
Jul 17 04:02:56 yankee last message repeated 2 times
Jul 17 04:02:56 yankee hidups[2046]: Unhandled event: 0x8500d1 (1)
Jul 17 04:02:56 yankee hidups[2046]: Unhandled event: 0x850043 (0)
Jul 17 04:02:56 yankee hidups[2046]: Unhandled event: 0x85004b (0)
Jul 17 04:02:56 yankee hidups[2046]: Unhandled event: 0x840065 (0)
Jul 17 04:02:56 yankee hidups[2046]: Ignoring x86 page event 0xff860060 (8)
Jul 17 04:03:01 yankee last message repeated 3 times



Version-Release number of selected component (if applicable):
nut-2.0.1-1

How reproducible:
Always

Steps to Reproduce:
1. Configure nut for UPS that uses hidups.
2. Start the ups service.
3. Watch /var/log/messages.
  
Actual results:
The log entries above appear every 5 seconds.

Expected results:
The occasional status message.

Additional info:
Tested on three different machines with three different APC UPS's using the same
USB driver.  This is a regression from FC3, where everything worked fine.

Comment 1 Than Ngo 2005-08-25 17:03:11 UTC
It seems a problem in usb driver. There's no difference in hidups between 
2.0.0 and 2.0.1! 
 
do you still see the warnings if you start nut-2.0.1-1 on FC3 system? 

Comment 2 Matthew Saltzman 2005-08-25 18:36:32 UTC
I don't have an FC3 system to test anymore, but I did not see this problem when
I was running FC3 with whatever nut version was included.

Comment 3 Matthew Saltzman 2005-09-24 12:25:49 UTC
Just noticed, this looks like a dup of #160700.

Comment 4 Dave Jones 2005-09-30 06:29:42 UTC
Mass update to all FC4 bugs:

An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (2.6.13.2). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.

Please retest with this update, and update this bug if necessary.

Thanks.


Comment 5 Matthew Saltzman 2005-09-30 13:27:06 UTC
This bug is not--repeat, not--fixed in kernel-2.6.13-1.1526_FC4.

Comment 6 Dave Jones 2005-11-05 06:29:22 UTC

*** This bug has been marked as a duplicate of 160700 ***


Note You need to log in before you can comment on or make changes to this bug.