From: Pete Zaitcev <zaitcev@redhat.com>
To: nettings@folkwang-hochschule.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.17 usbnet usb.c: USB device not accepting new address
Date: Mon, 7 Jan 2002 16:41:03 -0500 [thread overview]
Message-ID: <200201072141.g07Lf3102857@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1010437020.13415.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.1010437020.13415.linux-kernel2news@redhat.com>
> kernel: usb.c: USB device not accepting new address=6 (error=-110)
And your /proc/interrupts is ... ?
-- Pete
next parent reply other threads:[~2002-01-07 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1010437020.13415.linux-kernel2news@redhat.com>
2002-01-07 21:41 ` Pete Zaitcev [this message]
2002-01-07 21:44 ` 2.4.17 usbnet usb.c: USB device not accepting new address Johannes Erdfelt
2002-01-07 22:12 ` Jörn Nettingsmeier
2002-01-07 22:14 ` Johannes Erdfelt
2002-01-07 20:54 Jörn Nettingsmeier
2002-01-07 21:07 ` Jörn Nettingsmeier
2002-01-07 21:15 ` Johannes Erdfelt
2002-01-07 21:59 ` Jörn Nettingsmeier
2002-01-08 8:29 ` Sebastian Heidl
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=200201072141.g07Lf3102857@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nettings@folkwang-hochschule.de \
/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