linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Kagan <rkagan@mail.ru>
To: linux-kernel@vger.kernel.org
Cc: Serge Tchesmeli <zztchesmeli@echo.fr>,
	Duncan Sands <duncan.sands@math.u-psud.fr>
Subject: Re: 2.6.10 and speedtouch usb
Date: Wed, 29 Dec 2004 19:18:33 +0300	[thread overview]
Message-ID: <20041229161829.GA9076@panda.itep.ru> (raw)
In-Reply-To: <200412271108.47578.zztchesmeli@echo.fr>

On Wed, Dec 29, 2004 at 04:04:21PM +0000, Serge Tchesmeli wrote:
> i have try the new kernel 2.6.10, compil with exactly the same option from my 
> 2.6.9 (i have copied the .config) but i notice a high load on my machine, and 
> i see that was syslogd.
> So, i look at my log and see:
> 
> Dec 26 19:40:44 gateway last message repeated 137 times
> Dec 26 19:40:46 gateway kernel: usb 2-1: events/0 timed out on ep0in
> Dec 26 19:40:46 gateway kernel: SpeedTouch: Error -110 fetching device status
> Dec 26 19:40:46 gateway kernel: usb 2-1: modem_run timed out on ep0in
> Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd 
> modem_run rqt 192 rq 18 len 8 ret -110
> Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: process 5296 (modem_run) did 
> not claim interface 0 before use
> Dec 26 19:40:49 gateway last message repeated 413 times
> Dec 26 19:40:51 gateway kernel: usb 2-1: events/0 timed out on ep0in
> Dec 26 19:40:51 gateway kernel: SpeedTouch: Error -110 fetching device status
> Dec 26 19:40:51 gateway kernel: usb 2-1: modem_run timed out on ep0in
> Dec 26 19:40:51 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd 
> modem_run rqt 192 rq 18 len 8 ret -110
> Dec 26 19:40:51 gateway kernel: usb 2-1: usbfs: process 5296 (modem_run) did 
> not claim interface 0 before use
> Dec 26 19:40:59 gateway last message repeated 1105 times
> 
> The speedtouch modem work, connection is etablished and work well.

It looks like the line status monitoring implemented in the driver in
2.6.10 interferes with that in modem_run.  Unless you have a reason to
keep using modem_run, you can let it go and use the line status
monitoring and firmware loading facilities provided by the driver
itself.  Just follow Andrew's advice.

  Roman.

  parent reply	other threads:[~2004-12-29 16:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-27 10:08 2.6.10 and speedtouch usb Serge Tchesmeli
2004-12-27 13:25 ` Andrew Benton
2004-12-27 13:33   ` Serge Tchesmeli
2004-12-27 15:48     ` Andrew Benton
2004-12-27 16:03       ` Serge Tchesmeli
2004-12-29  9:11 ` Duncan Sands
2004-12-29 16:18 ` Roman Kagan [this message]
2004-12-30 12:00   ` Duncan Sands
2004-12-30 16:48     ` Serge Tchesmeli
2005-01-03 11:17     ` Serge Tchesmeli

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=20041229161829.GA9076@panda.itep.ru \
    --to=rkagan@mail.ru \
    --cc=duncan.sands@math.u-psud.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zztchesmeli@echo.fr \
    /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).