mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Justin Mattock" <justinmattock@gmail.com>
To: "Alan Stern" <stern@rowland.harvard.edu>
Cc: "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>,
	"David Brownell" <dbrownell@users.sourceforge.net>,
	Linux-usb <linux-usb@vger.kernel.org>
Subject: Re: [19.666764] Disabling IRQ #23
Date: Thu, 18 Sep 2008 17:32:26 -0700	[thread overview]
Message-ID: <dd18b0c30809181732t48b41806nadb60829a4fbdd67@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0809181818200.17483-100000@iolanthe.rowland.org>

On Thu, Sep 18, 2008 at 3:23 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Wed, 17 Sep 2008, Justin Mattock wrote:
>
>> Hello,
>> after a bit of
>> searching I located a patch for something
>> that might be similar to this issue:(cant seem to locate the
>> linux-kernel thread).
>> http://www.gossamer-threads.com/lists/linux/kernel/966076
>> I've applied the patches just to see what would happen,
>> As for now I have not seen the Disable irq #23 yet,
>> (usually after a recompile of the kernel, upon reboot this message will appear,
>> this time it didn't). But you never know I'll run the system for a few days
>> and see if it pops up.
>
> You are concentrating on the symptom instead of the problem.  The
> symptom is that "Disabling IRQ #23" message -- don't worry about it.
>
> The underlying problem is the "ehci_hcd 0000:00:1d.7: HC died;
> cleaning up" message -- it should _never_ appear.  If you have a
> reliable way of provoking it then something needs to be fixed.
>
> Alan Stern
>
>

The reliable way of provoking this message is
when uvcvideo is loading(not the module, but the tools involved with
the communication of loading the firmware and module).
i.g. when using the udev approach with isight-firware-tools
I will receive this, but if I use the hal approach
this message does not appear. Now with using the udev approach
I did try this patch:(not knowing what it really was doing),
http://www.gossamer-threads.com/lists/linux/kernel/966076
And it seems this message has not appeared. From looking at the
situation after running this patch irregardless if it was intended for this
or not, I'm wondering if isight-firware-tools is the main issue with this
rather than the kernel.


-- 
Justin P. Mattock

  reply	other threads:[~2008-09-19  0:32 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 [this message]
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
  -- 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=dd18b0c30809181732t48b41806nadb60829a4fbdd67@mail.gmail.com \
    --to=justinmattock@gmail.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=csnook@redhat.com \
    --cc=dbrownell@users.sourceforge.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®