Alexander Hoogerhuis wrote :
> Feb 27 06:25:02 lapper kernel: irda0: transmit timed out
> Feb 27 06:25:07 lapper kernel: NETDEV WATCHDOG: irda0: transmit timed out
> Feb 27 06:25:07 lapper kernel: irda0: transmit timed out
> Feb 27 06:25:09 lapper kernel: NETDEV WATCHDOG: irda0: transmit timed out
> Feb 27 06:25:09 lapper kernel: irda0: transmit timed out
> Feb 27 06:25:31 lapper kernel: NETDEV WATCHDOG: irda0: transmit timed out
> Feb 27 06:25:31 lapper kernel: irda0: transmit timed out
> Feb 27 06:25:34 lapper kernel: NETDEV WATCHDOG: irda0: transmit timed out
> Feb 27 06:25:34 lapper kernel: irda0: transmit timed out
>
> Anyone have idea why my machine keeps spewing out the above messages
> most of the time? Doesn't matter if anything is in front of the IR eye
> or not, they come along even if IR us being used.
>
> I'm running on 2.4.19-pre1-ac1 (and have had this since I got IR
> working in the early 2.4.18-pre-series). Hardware is using the
> smc-ircc driver and irport.
I don't use smc-ircc and irport, but usually those messages
are a good indication of irq troubles. Check /proc/interrupt.
The other possibility is a bug in the driver. For example,
most driver doesn't work through a suspend/resume.
Jean
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
