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: Tue, 29 Nov 2005 13:46:53 +0100 [thread overview]
Message-ID: <m3sltf1v0i.fsf@defiant.localdomain> (raw)
In-Reply-To: <200511291214.08104.duncan.sands@free.fr> (Duncan Sands's message of "Tue, 29 Nov 2005 12:14:07 +0100")
Hi,
Duncan Sands <duncan.sands@free.fr> writes:
>> 17:03:15 ATM dev 0: speedtch_check_status entered
>> 17:03:17 usb 1-1: events/0 timed out on ep0in len=0/4
>> 17:03:17 ATM dev 0: speedtch_read_status: MSG D failed
>> 17:03:17 ATM dev 0: error -110 fetching device status
>
> Is it always MSG D that fails?
I think so. Since yesterday I have 7 identical MSG D faults and nothing
else.
> Is failure of this message
> correlated with anything else, eg: heavy network use?
I don't think so. The ADSL was mostly idle last 24 hrs. Only inbound SMTP
mail and the Windows viruses etc. trying to attack something.
I can perform a test with inactive PPP (=no any flow) but I think it will
show up the same.
BTW: it's an old notebook PC, i440BX (PIIX4) based:
00:00.0 Host bridge: Intel 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:07.0 ISA bridge: Intel 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:0a.0 CardBus bridge: Texas Instruments PCI1225 (rev 01)
00:0a.1 CardBus bridge: Texas Instruments PCI1225 (rev 01)
00:0d.0 ESS Technology ES1983S Maestro-3i PCI Audio Accelerator
00:0d.1 ESS Technology ES1983S Maestro-3i PCI Modem Accelerator
01:00.0 VGA: Silicon Motion, Inc. SM720 Lynx3DM (rev b1)
02:00.0 Ethernet: DECchip 21142/43 (rev 41)
--
Krzysztof Halasa
next prev parent reply other threads:[~2005-11-29 12:46 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 [this message]
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=m3sltf1v0i.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®