All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Guterl <mguterl@gmail.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net,
	"Luis Miguel  Garcý Mancebo" <ktech@wanadoo.es>,
	"Greg KH" <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>,
	akpm@osdl.org
Subject: Re: [linux-usb-devel] Re: USB troubles in rc2
Date: Sat, 7 Aug 2004 23:19:07 -0400	[thread overview]
Message-ID: <944a03770408072019362f4a33@mail.gmail.com> (raw)
In-Reply-To: <200408071051.23047.david-b@pacbell.net>

What if Alan's assumptions that it is in ACPI and not USB are correct?
 Personally I don't know enough to handle really any of the tasks you
suggested.  I figured the fact that reverting bk-acpi.patch and
bk-usb.patch would throw up some kind of red flag, that something in
there was maybe messed up and merged in.

On Sat, 7 Aug 2004 10:51:23 -0700, David Brownell <david-b@pacbell.net> wrote:
> On Thursday 05 August 2004 10:05, Michael Guterl wrote:
> > Thanks for the reply David, but where exactly does this leave me and
> > the others experiencing this problem?  Is there any more information I
> > can provide that might help?  Any possible solutions, patches, etc?
> 
> It leaves you (and others) with the problem partially isolated, so that
> someone with time to track it down will have that much less work to do.
> 
> The most effective solutions involve someone who has the problem
> actually stepping up and debugging the whole thing, then providing
> a patch fixing the problem.
> 
> A second-best would be collaboration between someone who has
> the time (not me!) and someone who has the problem (you?) to
> remotely debug the problem.
> 
> A third-best would be for someone (you?) to find out exactly which patch
> caused the problem -- a binary search of the USB patches, luckily it's
> made easier by the fact that it could only be a change in HID, usbcore,
> or some HCD.  (And most likely IMO it's usbcore.)  Then that patch can
> either be further debugged, or reverted.
> 
> - Dave
> 
> 
> > On Thu, 5 Aug 2004 08:34:27 -0700, David Brownell <david-b@pacbell.net>
> wrote:
> > > ....
> 
> 
> > >
> > > The dmesg output shows this is a HID failure.  It's likely connected
> > > with some changes in the unlink logic, since that's what returns
> > > the "-ENOENT" status.  The usb_kill_urb() changes added a new
> > > URB state as I recall, maybe that's part of the issue here... since
> > > that routine replaced the previous "synchronous unlink" logic.
> > >
> > > - Dave
> > >
> > >
> >
>

  parent reply	other threads:[~2004-08-08  3:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 19:00 USB troubles in rc2 Luis Miguel García Mancebo
2004-08-03  0:26 ` Greg KH
2004-08-03  2:08   ` Michael Guterl
2004-08-03  6:49     ` Trever L. Adams
2004-08-03  8:46   ` Luis Miguel García Mancebo
2004-08-03 13:57     ` Greg KH
2004-08-03 23:04       ` Luis Miguel García Mancebo
2004-08-04 20:32         ` Michael Guterl
2004-08-05  1:20           ` [linux-usb-devel] " David Brownell
2004-08-05  3:57             ` Michael Guterl
2004-08-05 15:34               ` David Brownell
2004-08-05 17:05                 ` Michael Guterl
2004-08-07 17:51                   ` David Brownell
2004-08-07 22:01                     ` Wes Janzen
2004-08-08  3:19                     ` Michael Guterl [this message]
2004-08-08  4:20                       ` Alan Stern
2004-08-08 13:29                         ` Michael Guterl
2004-08-10 17:16                           ` Michael Guterl
2004-08-10 18:54                             ` Alan Stern
2004-08-10 19:41                               ` Michael Guterl
2004-08-05 18:08                 ` Kevin O'Shea
2004-08-05 18:50                   ` Michael Guterl
2004-08-06 14:23               ` Alan Stern
2004-08-05  3:59             ` Michael Guterl

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=944a03770408072019362f4a33@mail.gmail.com \
    --to=mguterl@gmail.com \
    --cc=akpm@osdl.org \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=ktech@wanadoo.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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.