linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: jt@hpl.hp.com
Cc: linux-kernel@vger.kernel.org, irda-users@lists.sourceforge.net
Subject: Re: 2.5.42: IrDA issues
Date: Mon, 21 Oct 2002 11:19:35 +0200	[thread overview]
Message-ID: <3DB3C6A7.5040007@oracle.com> (raw)
In-Reply-To: 20021014173421.GC10672@bougret.hpl.hp.com

Jean Tourrilhes wrote:
> On Sun, Oct 13, 2002 at 05:27:19AM -0800, ALESSANDRO.SUARDI wrote:
> 
>>I have a PPP over IrDA connection to my Nokia phone; under 2.4.20-preX I have no
>> problem keeping the link up, while in 2.5.4x it fails in a very short time like this:
>>
>>Oct 13 01:13:13 dolphin kernel: IrLAP, no activity on link!
>>Oct 13 01:13:11 dolphin kernel: NETDEV WATCHDOG: irda0: transmit timed out
>>Oct 13 01:13:11 dolphin kernel: irda0: transmit timed out
>>Oct 13 01:13:13 dolphin kernel: IrLAP, no activity on link!
>>Oct 13 01:13:13 dolphin kernel: NETDEV WATCHDOG: irda0: transmit timed out
>>Oct 13 01:13:13 dolphin kernel: irda0: transmit timed out
>>Oct 13 01:13:13 dolphin pppd[5378]: Modem hangup
>>Oct 13 01:13:13 dolphin pppd[5378]: Connection terminated.
>>Oct 13 01:13:13 dolphin pppd[5378]: Connect time 1.8 minutes.
>>Oct 13 01:13:13 dolphin pppd[5378]: Sent 19541 bytes, received 35933 bytes.
>>Oct 13 01:13:13 dolphin pppd[5378]: Exit.
>>
>>I also get the transmit timed out spam (why one with WATCHDOG and one without ?)
>> in 2.4.20-pre but the IrLAP line isn't there. And the GPRS link stays up...
>>
>>
>>Thanks in advance for any insight,
>>
>>--alessandro
> 
> 
> 	Please do yourself a favor and give me a proper bug report,
> including hardware, driver and irdadump.
> 

Will provide irdadump stuff soon[-ish], I'm wading through a backlog
  of, uhm, too much email. The short-form report really meant "is this
  a known issue ?"...

Anyway - the box is a Dell Latitude CPx750J with this:

[root@dolphin root]# findchip -v
Found SMC FDC37N958FR Controller at 0x3f0, DevID=0x01, Rev. 1
     SIR Base 0x3e8, FIR Base 0x290
     IRQ = 4, DMA = 3
     Enabled: yes, Suspended: no
     UART compatible: yes
     Half duplex delay = 3 us

So clearly I'm using smc-ircc.o.

(Of course I'll try and reproduce in 2.5.44 tonight or tomorrow).


Thanks,

--alessandro

  "everything dies, baby that's a fact
    but maybe everything that dies someday comes back"
        (Bruce Springsteen, "Atlantic City")


  reply	other threads:[~2002-10-21  9:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-13 13:27 2.5.42: IrDA issues ALESSANDRO.SUARDI
2002-10-14 17:34 ` Jean Tourrilhes
2002-10-21  9:19   ` Alessandro Suardi [this message]
2002-10-21 17:22     ` Jean Tourrilhes
  -- 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-11-02 20:36 ALESSANDRO.SUARDI
2002-11-04 21:11 ` 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=3DB3C6A7.5040007@oracle.com \
    --to=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).