I have a usb infrared remote receiver (Windows media center variety) which
works correctly at boot, but stops working sometime later.
Kernel gives:
[ 1101.490321] irq 21: nobody cared (try booting with the "irqpoll" option)
[ 1101.490328] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P O 3.13.0-rc8 #1
[
Alan Stern writes:
>
> On Thu, 23 Jan 2014, Josh Bendavid wrote:
>
> > Hi Alan,
> >
> > Requested output below. For the trace at the bottom, most of the output
> > just corresponds to me pressing buttons on the IR remote before it dies. I
> > don'
Alan Stern writes:
>
> On Thu, 23 Jan 2014, Josh Bendavid wrote:
>
> > Hi Alan,
> > Is it understood why/how this always happens when the interrupt counter for
> > this device reaches exactly 21? I would have assumed that this was a
> > software count
> These messages have no connection with the patch. What you should see,
> just once not long after you boot up or start using the device, is
> about 200 messages mentioning IRQ counts and register values (from the
> ohci_info call in the patch).
>
> Did the "nobody cared" error occur while you
Alan Stern writes:
>
> On Mon, 3 Feb 2014, Josh Bendavid wrote:
>
> > The output you're in fact looking for is attached below (ending with the
> > "nobody cared" error).
> >
> > [ 1121.572119] ohci-pci :00:06.0: IRQ 199900 status 24 enable 8
Alan Stern writes:
>
> The dmesg output is normal. And yes, lack of any error does indicate
> that something is wrong with your controller.
>
> I don't think this problem can be fixed by a simple workaround. I've
> been considering adding an I/O watchdog to ohci-hcd, because it ought
> to h
> If the problem was indeed caused by software, there's a good chance you
> can track it down by doing a bisection search. That's a time-consuming
> procedure but it doesn't require much intellectual effort.
>
> Have you verified that the controller still works okay under a 3.5
> kernel (to rule
