All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Udo A. Steinberg" <reality@delusion.de>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: USB device not accepting new address
Date: Thu, 06 Sep 2001 02:38:50 +0200	[thread overview]
Message-ID: <3B96C59A.2EC7C768@delusion.de> (raw)
In-Reply-To: <mailman.999666181.21742.linux-kernel2news@redhat.com> <200109051619.f85GJEo07592@devserv.devel.redhat.com> <3B967EDD.5A81F2DD@delusion.de> <20010905160940.B11067@devserv.devel.redhat.com>

Pete Zaitcev wrote:

> Interesting. I just dealt with a bug which is most definitely
> a hardware problem, and the owner swore that "it worked with
> 2.4.3-12 perfectly" (it was the last errata that we shipped).
> The thing (a Kaweth compatible Ethernet) was found NOT to work
> on earlier kernels reliably either. Such things do happen:
> something stops working just in time.
> What regressions did you do? Did you run 2.4.7-ac _after_
> it broke?

I've just tried all -ac1 kernels from 2.4.5-ac1 to 2.4.9-ac1
and the problem exists with all of them. So it would appear that
it didn't work reliably with earlier kernels either. I find it
interesting however, that it is much harder to trigger in
earlier kernels and that it doesn't happen every time.

-Udo.

  parent reply	other threads:[~2001-09-06  0:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.999666181.21742.linux-kernel2news@redhat.com>
2001-09-05 16:19 ` USB device not accepting new address Pete Zaitcev
2001-09-05 19:37   ` Udo A. Steinberg
     [not found]     ` <20010905160940.B11067@devserv.devel.redhat.com>
2001-09-06  0:38       ` Udo A. Steinberg [this message]
2001-09-10 21:10         ` Len Sorensen
2001-09-05  4:44 Udo A. Steinberg
2001-09-05 15:58 ` Greg KH
     [not found]   ` <3B967E59.F4400CCE@delusion.de>
2001-09-05 20:12     ` Udo A. Steinberg

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=3B96C59A.2EC7C768@delusion.de \
    --to=reality@delusion.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.