mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* 2.6.33: Intel DP55KG - USB still not fixed: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110
@ 2010-03-01  9:49 Justin Piszcz
  2010-03-01 15:38 ` Alan Stern
  0 siblings, 1 reply; 2+ messages in thread
From: Justin Piszcz @ 2010-03-01  9:49 UTC (permalink / raw)
  To: linux-kernel, linux-usb

Hi,

Feb 28 19:39:10 p34 kernel: [274199.684428] usb 2-1.7: usbfs: USBDEVFS_CONTROL
failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110

I know the DP55KG has USB problems (still, apparently) but was curious 
what the (above) error means?

In addition, this occurs when the CPU is maxed out, this still occurs
(many interrupts/from a backup etc), someone at Intel needs to run
nut with a UPS and then run some heavy CPU-bound processes and they will
see the same problem.

Feb 28 22:08:44 p34 upsd[13131]: Data for UPS [apc] is stale - check driver
Feb 28 22:08:48 p34 upsd[13131]: UPS [apc] data is no longer stale
Feb 28 22:58:43 p34 upsd[13131]: Data for UPS [apc] is stale - check driver
Feb 28 22:58:45 p34 upsd[13131]: UPS [apc] data is no longer stale

Justin.



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: 2.6.33: Intel DP55KG - USB still not fixed: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110
  2010-03-01  9:49 2.6.33: Intel DP55KG - USB still not fixed: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 Justin Piszcz
@ 2010-03-01 15:38 ` Alan Stern
  0 siblings, 0 replies; 2+ messages in thread
From: Alan Stern @ 2010-03-01 15:38 UTC (permalink / raw)
  To: Justin Piszcz; +Cc: linux-kernel, linux-usb

On Mon, 1 Mar 2010, Justin Piszcz wrote:

> Hi,
> 
> Feb 28 19:39:10 p34 kernel: [274199.684428] usb 2-1.7: usbfs: USBDEVFS_CONTROL
> failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110
> 
> I know the DP55KG has USB problems (still, apparently) but was curious 
> what the (above) error means?

It means that the usbhid-ups program submitted a USB control transfer
request via usbfs, and the device did not reply within the specified
timeout period.

Alan Stern


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-03-01 15:38 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-03-01  9:49 2.6.33: Intel DP55KG - USB still not fixed: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 Justin Piszcz
2010-03-01 15:38 ` Alan Stern

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®