mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Duncan Sands <duncan.sands@free.fr>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: speedtch driver, 2.6.14.2
Date: Thu, 24 Nov 2005 09:22:59 +0100	[thread overview]
Message-ID: <200511240923.01185.duncan.sands@free.fr> (raw)
In-Reply-To: <200511232125.25254.s0348365@sms.ed.ac.uk>

Hi Alistair,

> I recently switched from the userspace speedtouch driver to the in-kernel one. 
> However, on my rev 4.0 Speedtouch 330, I periodically get the message:
> 
> ATM dev 0: error -110 fetching device status

-110 means that it timed out.

> I suspect the source of this "error" is the warning message from speedtch:435:
> 
> 	ret = speedtch_read_status(instance);
> 	if (ret < 0) {
> 		atm_warn(usbatm, "error %d fetching device status\n", ret);
> 		instance->poll_delay = min(2 * instance->poll_delay, MAX_POLL_DELAY);
> 		return;
> 	}
> 
> Tell me if I'm wrong, but I suspect speedtch_check_status() is called 
> periodically to check line status. It may be the case that my modem does not 
> like having its status read when it is sending/receiving data (which it is 
> constantly doing).

Well, I have the same modem, and mine doesn't seem to mind!  So something is
strange.

> Unfortunately the message eventually fills the dmesg ring buffer. My current 
> workaround is to remove the atm_warn() call; everything works fine, but I'm 
> concerned that the modem will not automatically reconnect if the connection 
> drops as a result of the failure from speedtch_read_status().

You can test it by unplugging the phone line, then replugging it.

> Any suggestions for debugging this further? From a quick google I've noticed a 
> recent Fedora bugzilla entry mentioning this same problem.

I'll think about it.

All the best,

Duncan.

  reply	other threads:[~2005-11-24  8:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-23 21:25 Alistair John Strachan
2005-11-24  8:22 ` Duncan Sands [this message]
2005-11-24 17:01 ` Duncan Sands
2005-11-26 23:48   ` Alistair John Strachan
2005-11-27 22:58 ` Krzysztof Halasa
2005-11-28  8:29   ` Duncan Sands
2005-11-28 10:04     ` Krzysztof Halasa
2005-11-28 11:34       ` Duncan Sands
2005-11-28 17:18         ` Krzysztof Halasa
2005-11-29 11:14           ` Duncan Sands
2005-11-29 12:46             ` Krzysztof Halasa
2005-12-01  7:59               ` Duncan Sands
2005-12-01 15:17                 ` Krzysztof Halasa
2005-12-01 15:19                   ` Duncan Sands
2005-12-01 16:14                     ` Krzysztof Halasa
2005-12-02 16:46                   ` Duncan Sands
2005-11-28 11:44       ` Duncan Sands
2006-01-13 12:15 ` Duncan Sands
2006-01-13 13:33   ` Andrew Walrond
2006-01-13 19:08   ` Alistair John Strachan

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=200511240923.01185.duncan.sands@free.fr \
    --to=duncan.sands@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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

all inboxes | Powered by JetHome®