[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070107005150.GE22817@gamma.logic.tuwien.ac.at>
Date: Sun, 7 Jan 2007 01:51:50 +0100
From: Andreas Leitgeb <avl@...ic.at>
To: netdev@...r.kernel.org
Subject: IrDA spams logfiles - since 2.6.19
I'm not on this list, so please keep me CC'ed on this thread.
Since 2.6.19 I've got a problem with my Tekram IRmate 410U
usb-irda-dongle. Until 2.6.18.3 (the latest I had before 2.6.19*)
it worked just fine. 2.6.19.1 had another change in irda-usb
but that didn't solve the problem.
As soon as I load the irda-usb module with the device plugged,
I get lots of messages of following kind into the logs:
irda_usb_hard_xmit(), Insuficient skb headroom.
(the "Insuficient"-typo is original)
about 7 in a second, then a 2-secs pause. Repeating
until the irda-usb module is removed again.
I then looked up the kernel-source for that particular
typo'ed word, and added some info to the log:
drivers/net/irda/irda-usb.c:448:
if (skb_headroom(skb) < self->header_length) {
IRDA_DEBUG(0, "%s(), Insuficient skb headroom. %d / %d \n",
__FUNCTION__, skb_headroom(skb) , self->header_length);
...
Which came out as:
irda_usb_hard_xmit(), Insuficient skb headroom. 0 / 1
Thus, while self->header_length == USB_IRDA_HEADER,
I didn't yet understand the meaning of fields
->data and ->head of the skb.
I don't know, if the warning itself is right or wrong,
because other than the spamming of logs, transferring
data over irda appears to work just fine.
(I've got timestamps turned on, so usual repeat-compression
by syslogd doesn't take effect.)
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists