From: Brad Hards <bhards@bigpond.net.au>
To: "Michael Duane" <Mike.Duane@digeo.com>, <linux-kernel@vger.kernel.org>
Subject: Re: CDCether.c
Date: Thu, 19 Sep 2002 16:20:57 +1000 [thread overview]
Message-ID: <200209191620.58022.bhards@bigpond.net.au> (raw)
In-Reply-To: <4C568C6A13479744AA1EA3E97EEEB3231B7DDC@schumi.digeo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 19 Sep 2002 09:49, Michael Duane wrote:
> Who is the maintainer of CDCEther.c? I am having a problem
> with packets getting "wedged" somewhere on the way out
> and need to know if others have reported this problem.
Others have reported probems that normally look something like "it works fine
for some minutes to days, and then all connectivity stops, till I reboot or
re-insert the module", but I can't duplicate. Does this match your problem?
There are some races, but I can't explain the problem from them. I do need to
fix the races, but I only do this when I have some spare time (after work,
SO, and some other hobbies).
> I'm running the 2.4.17 kernel and using a Broadcom DOCSIS
> modem based around a 3345.
Most people have reported the problem with Via UHCI chipsets, and usb-uhci
driver. Does this match your configuration?
You might care to upgrade the kernel too.
Brad
- --
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9iWzJW6pHgIdAuOMRAvXrAJ9JfDSnx25dKI7yXvQC2XjNEydS+wCgpKMe
kSP0H8AB5Sj8Ebo6SGAPVNs=
=RTI4
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-09-19 6:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 23:49 CDCether.c Michael Duane
2002-09-19 0:15 ` CDCether.c Greg KH
2002-09-19 6:20 ` Brad Hards [this message]
2002-09-19 15:22 CDCether.c Michael Duane
2002-09-19 21:11 ` CDCether.c Brad Hards
2002-09-19 17:09 CDCether.c Michael Duane
2002-09-24 21:30 CDCether.c Michael Duane
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=200209191620.58022.bhards@bigpond.net.au \
--to=bhards@bigpond.net.au \
--cc=Mike.Duane@digeo.com \
--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;
as well as URLs for NNTP newsgroup(s).