linux-kernel - Re: irq 19: nobody cared

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:	Mon, 22 Sep 2008 18:32:10 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Chris Li" <lkml@...isli.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: irq 19: nobody cared

On Mon, Sep 22, 2008 at 4:30 PM, Chris Li <lkml@...isli.org> wrote:
> On Sat, Sep 20, 2008 at 4:21 PM, Chris Li <lkml@...isli.org> wrote:
>>> can you boot with pci=routeirq ?
>>
>> See attached dmesg.
>
> Ping?
>
> Any other suggestions? In the week end I try to patch the SATA driver
> and USB driver.
>
> I add some debug print from UHCI interrupt handler. So the interrupt
> start to hammer as soon as the first UHCI hook to IRQ 19. The UHCI
> status bit is clean.
>
> I also try to disable SATA interrupt at early PCI scan. It does not
> help either.
>
> So I guess seems like wrong irq routing. How do I find out which
> device is injecting the interrupt?
>

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