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: <6FACEDE1-72B7-45DE-ADDF-5FCD4F6E90B8@gmail.com>
Date:	Wed, 17 Sep 2008 15:18:45 -0700
From:	"Justin P. Mattock" <justinmattock@...il.com>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Chris Snook <csnook@...hat.com>,
	April Tsui <aprilla@...il.com>,
	David Brownell <dbrownell@...rs.sourceforge.net>,
	Linux-usb <linux-usb@...r.kernel.org>
Subject: Re: [19.666764] Disabling IRQ #23

 From what I remember this started around 2.6.27-rc1(I.g. Seeing this  
message during bootup), with having issues With ift-load probably  
around 2.6.26-rc1(should of done an upgrade then,but never got around  
to it), as for this being a regression? I guess; if this was happening  
with 2.6.26 and other previous kernels.
  As for my situation I've rebooted again a few times with
Not receiving this message. As for the issue being fixed? Not sure,  
one side of me says yes it is due to not having the kernel report any  
problems, but then there's the side that agrees with what you had  
said. maybe the problem doesn't happen with different user-space  
tools, doesn't mean the kernels problem is fixed.

justin P. Mattock

On Sep 17, 2008, at 2:48 PM, Bjorn Helgaas <bjorn.helgaas@...com> wrote:

> On Wednesday 17 September 2008 11:13:55 am Justin Mattock wrote:
>> I've seeing something interesting at the moment
>> with this. I've upgraded isight-firmware-tools to the latest,
>> and instead of using udev I'm using hal. I've done numerous
>> reboots, and am not receiving this message. I think it might have  
>> been
>> something to do with ift-load. If I don't see this message after a  
>> few more days
>> of rebooting, and cold starts I think we can close this.
>
> Maybe the problem doesn't happen with different user-space
> tools, but that doesn't mean the kernel problem is fixed.
>
> And we still don't know whether this is really a regression
> or not.
>
> Bjorn
--
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/