mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Justin Mattock" <justinmattock@gmail.com>
To: "David Brownell" <david-b@pacbell.net>
Cc: "Alan Stern" <stern@rowland.harvard.edu>,
	"Bjorn Helgaas" <bjorn.helgaas@hp.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Yinghai Lu" <yhlu.kernel@gmail.com>,
	"Chris Snook" <csnook@redhat.com>,
	Linux-usb <linux-usb@vger.kernel.org>
Subject: Re: [19.666764] Disabling IRQ #23
Date: Fri, 19 Sep 2008 18:19:08 -0700	[thread overview]
Message-ID: <dd18b0c30809191819m39c4dfcbu22979daed9e94912@mail.gmail.com> (raw)
In-Reply-To: <200809191756.18661.david-b@pacbell.net>

On Fri, Sep 19, 2008 at 5:56 PM, David Brownell <david-b@pacbell.net> wrote:
> In
>
>  http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-02-usb.current/
>
> the patch
>
>  usb-fix-ehci-periodic-transfers.patch
>
> seems like it should resolve the root cause of this, and
>
>  usb-ehci-fix-some-ehci-hangs-and-crashes.patch
>
> would cover symptoms which probably caused the "Disabling..." message.
> Both patches were in that LKML thread you referenced.
>

Cool, I did apply that patch and the periodic patch as well,
after doing so the system did not report any disable irq #23
message., but after running these two for a few days without
any issues I reverted. Then looking more into my situation,
I think ehci_hcd was getting confused with one usb device being
created by udev, and then a few seconds later another device with the
same numbers
created by hal(if thats how those two work), causing ehci_hcd to freak out.
in any case; applying the patch you had mentioned, as well
as the periodic patch did make ehci_hcd accept the two(if thats what
was happening).

regards;

-- 
Justin P. Mattock

  reply	other threads:[~2008-09-20  1:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 19:06 Justin Mattock
2008-09-10 19:36 ` Yinghai Lu
2008-09-10 19:39   ` Justin Mattock
2008-09-17 15:04 ` Bjorn Helgaas
2008-09-17 17:13   ` Justin Mattock
2008-09-17 21:48     ` Bjorn Helgaas
2008-09-17 22:18       ` Justin P. Mattock
2008-09-18  0:14         ` Justin Mattock
2008-09-18  4:44           ` Justin Mattock
2008-09-18  9:09             ` David Brownell
2008-09-18 16:57               ` Justin Mattock
2008-09-18 21:56                 ` April Tsui
2008-09-18 22:23             ` Alan Stern
2008-09-19  0:32               ` Justin Mattock
2008-09-19 16:08                 ` Alan Stern
2008-09-19 16:41                   ` Justin Mattock
2008-09-19 17:05                     ` Alan Stern
2008-09-19 18:18                       ` Justin Mattock
2008-09-19 21:20                         ` Justin Mattock
2008-09-20  0:56                           ` David Brownell
2008-09-20  1:19                             ` Justin Mattock [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-09-09 19:08 Justin Mattock
2008-09-09 23:28 ` Chris Snook
2008-09-09 23:56   ` Justin P. Mattock

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=dd18b0c30809191819m39c4dfcbu22979daed9e94912@mail.gmail.com \
    --to=justinmattock@gmail.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=csnook@redhat.com \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=yhlu.kernel@gmail.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 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®