Prev: use of setjmp/longjmp in x86 emulator.
Next: block: don't access jiffies when initialising io_context
From: Justin Piszcz on 1 Mar 2010 04:50
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.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: use of setjmp/longjmp in x86 emulator.
Next: block: don't access jiffies when initialising io_context