From: Krzysztof Halasa <khc@pm.waw.pl>
To: Duncan Sands <duncan.sands@free.fr>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: speedtch driver, 2.6.14.2
Date: Thu, 01 Dec 2005 16:17:51 +0100 [thread overview]
Message-ID: <m3u0ds7so0.fsf@defiant.localdomain> (raw)
In-Reply-To: <200512010859.19905.duncan.sands@free.fr> (Duncan Sands's message of "Thu, 1 Dec 2005 08:59:19 +0100")
Duncan Sands <duncan.sands@free.fr> writes:
>> ... Since yesterday I have 7 identical MSG D faults and nothing
>> else.
>
> Does increasing the value of CTRL_TIMEOUT help?
I've increased it to 4 seconds, no change. It looks like the response
(or request) is lost somewhere.
The answer is always the same second:
Dec 1 15:20:32 defiant kernel: ATM dev 0: speedtch_check_status entered
Dec 1 15:20:32 defiant kernel: ATM dev 0: speedtch_check_status: line state 20
Dec 1 15:20:37 defiant kernel: ATM dev 0: speedtch_check_status entered
Dec 1 15:20:37 defiant kernel: ATM dev 0: speedtch_check_status: line state 20
Dec 1 15:20:42 defiant kernel: ATM dev 0: speedtch_check_status entered
Dec 1 15:20:42 defiant kernel: ATM dev 0: speedtch_check_status: line state 20
... or it doesn't come at all:
Dec 1 15:20:47 defiant kernel: ATM dev 0: speedtch_check_status entered
Dec 1 15:20:51 defiant kernel: usb 1-1: events/0 timed out on ep0in len=0/4
Dec 1 15:20:51 defiant kernel: ATM dev 0: speedtch_read_status: MSG D failed
Dec 1 15:20:51 defiant kernel: ATM dev 0: error -110 fetching device status
Do the speedtouches have some means (firmware) for debugging or logging?
We would need to see what does the ADSL receive and what does it think
about it.
--
Krzysztof Halasa
next prev parent reply other threads:[~2005-12-01 15:17 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
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 [this message]
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=m3u0ds7so0.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=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®