From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: "ALESSANDRO.SUARDI" <ALESSANDRO.SUARDI@oracle.com>
Cc: linux-kernel@vger.kernel.org, irda-users@lists.sourceforge.net
Subject: Re: 2.5.42: IrDA issues
Date: Mon, 4 Nov 2002 13:11:58 -0800 [thread overview]
Message-ID: <20021104211158.GA8382@bougret.hpl.hp.com> (raw)
In-Reply-To: <7312677.1036269363155.JavaMail.nobody@web55.us.oracle.com>
On Sat, Nov 02, 2002 at 12:36:03PM -0800, ALESSANDRO.SUARDI wrote:
>
> while a substantially lower amount of spam under 2.4 tells me
>
> Nov 2 21:28:31 dolphin kernel: NETDEV WATCHDOG: irda0: transmit timed out
> Nov 2 21:28:31 dolphin kernel: irda0: transmit timed out
> Nov 2 21:28:38 dolphin kernel: NETDEV WATCHDOG: irda0: transmit timed out
> Nov 2 21:28:38 dolphin kernel: irda0: transmit timed out
> Nov 2 21:29:05 dolphin kernel: NETDEV WATCHDOG: irda0: transmit timed out
> Nov 2 21:29:05 dolphin kernel: irda0: transmit timed out
Yep, I have the same problem when I try irport. It seems that
somehow we drop/miss a Tx-done interrupt (UART_IIR_THRI). I tried to
investigate that but came empty handed.
I looked a the new smsc-ircc2 driver, and I suspect that what
you see is another manifestation of the exact same problem.
> Thanks for now & ciao,
>
> --alessandro
Have fun...
Jean
next prev parent reply other threads:[~2002-11-04 21:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 20:36 2.5.42: IrDA issues ALESSANDRO.SUARDI
2002-11-04 21:11 ` Jean Tourrilhes [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-23 21:38 ALESSANDRO.SUARDI
2002-10-23 21:55 ` Jean Tourrilhes
2002-10-24 9:14 ` Alessandro Suardi
2002-10-24 16:49 ` Jean Tourrilhes
2002-10-23 22:06 ` Martin Diehl
2002-10-13 13:27 ALESSANDRO.SUARDI
2002-10-14 17:34 ` Jean Tourrilhes
2002-10-21 9:19 ` Alessandro Suardi
2002-10-21 17:22 ` Jean Tourrilhes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021104211158.GA8382@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=ALESSANDRO.SUARDI@oracle.com \
--cc=irda-users@lists.sourceforge.net \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).