linux-kernel - Re: [19.666764] Disabling IRQ #23

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <dd18b0c30809181732t48b41806nadb60829a4fbdd67@mail.gmail.com>
Date:	Thu, 18 Sep 2008 17:32:26 -0700
From:	"Justin Mattock" <justinmattock@...il.com>
To:	"Alan Stern" <stern@...land.harvard.edu>
Cc:	"Bjorn Helgaas" <bjorn.helgaas@...com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Yinghai Lu" <yhlu.kernel@...il.com>,
	"Chris Snook" <csnook@...hat.com>,
	"David Brownell" <dbrownell@...rs.sourceforge.net>,
	Linux-usb <linux-usb@...r.kernel.org>
Subject: Re: [19.666764] Disabling IRQ #23

On Thu, Sep 18, 2008 at 3:23 PM, Alan Stern <stern@...land.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/