From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Duncan Sands <duncan.sands@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: speedtch driver, 2.6.14.2
Date: Fri, 13 Jan 2006 19:08:16 +0000 [thread overview]
Message-ID: <200601131908.16584.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <200601131315.55355.duncan.sands@free.fr>
On Friday 13 January 2006 12:15, Duncan Sands wrote:
> > 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
>
> Is this correlated with disk activity (heavy use of the pci bus)?
No, the machine is completely idle. However I switched to the CVS driver (it
does not work in isochronous mode still), and in bulk-mode it gives me a new
set of messages:
ATM dev 0: speedtch_read_status: MSG E failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG F failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG F failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG D failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG D failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG D failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG B failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG B failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG B failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG F failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG F failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG B failed
ATM dev 0: error -110 fetching device status
ATM dev 0: speedtch_read_status: MSG F failed
ATM dev 0: error -110 fetching device status
This seems to happen less often than with the kernel driver, however.
--
Cheers,
Alistair.
'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
prev parent reply other threads:[~2006-01-13 19:08 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
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 [this message]
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=200601131908.16584.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=duncan.sands@free.fr \
--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
all inboxes | Powered by JetHome®