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]
Date:	Fri, 19 Sep 2008 16:13:21 -0700
From:	"Chris Li" <lkml@...isli.org>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: irq 19: nobody cared

On Fri, Sep 19, 2008 at 3:38 PM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
>
> It could also be an IRQ being routed wrongly or an incorrect BIOS table
> so that the kernel is looking for the IRQ in the wrong place.
>
> Does booting with the irqpoll option help ?

Yes, booting with irqpoll option does helps with the latest kernel.
There is not such message appear any more. However I do want
the kernel fix this problem. The very same problem prevent me from
installing a FC8 live CD on this slim tower. In that FC8 kernel,
irqpoll does not help. BTW, it was working fine on FC7 kernel.
Upgrade to FC8 complete ruined it.

There are other user dell slim tower user report the same
problem on the Internet. One of the work around mention on the
internet is to change BIOS setting for SATA from "IDE"
mode to "RAID" mode. That tip complete destroy my partition
but  does not work for me any way. FC9 is better, at least
I am able to install with irqpoll.

I was hoping some one else already complain this on the lkml
and get it fixed. Guess not. So I am going my part then.

>> usb 4-2: new full speed USB device using uhci_hcd and address 2
>> irq 19: nobody cared (try booting with the "irqpoll" option)
>
> And does this last one (the irq19) occur immediately when you plug in a
> USB device ?

No,  the USB device is already (cold) plug to the system before the
kernel was booted. That new device message should be the first time the
USB driver detect the those USB device. I just load the kernel and
I did not hotplug any thing. It is the USB keyboard and mouse I think.

Any thing I can do to help to identify the problem?

Chris
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ