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]

Date:	Tue, 09 Sep 2008 19:28:51 -0400
From:	Chris Snook <csnook@...hat.com>
To:	Justin Mattock <justinmattock@...il.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	April Tsui <aprilla@...il.com>
Subject: Re: [19.666764] Disabling IRQ #23

Justin Mattock wrote:
> I've been noticing this message appear
> every "X" amount of boot's(maybe ten or so);
> 
> [19.656768] irq 23: nobody cared (try booting with the "irqpoll" option)
> [19.666039] Pid: 0, comm: swapper Tainted: P          2.6.27-rc5-00363-ga002d93
> [19.666764]  [<c0151774>] __report_bad_irq+0x2e/0x6f
> [19.666764]  [<c015199b>] note_interrupt+0x1e6/0x217
> [19.666764]  [<c0150d73>] ? handle_IRQ_event+0x2a/0x5a
> [19.666764]  [<c0151f4c>] handle_fastoei_irq+0x91/0xb6
> [19.666764]  [<c0104ff2>] do_IRQ+ox6c/0x86
> [19.666764]  [<c0103a6f>] common_interrupt+0x23/0x28
> [19.666764]  [<f886099a>] ? acpi_idle_enter_simple+0x19c/0x20e [processor]
> [19.666764]  [<c02ec323>] cpuidle_idle_call+ox5e/0x8b
> [19.666764]  [<c0101d42>] cpu_idle+0xda/0xfa
> [19.666764]  [<c038fde6>] rest_init+0x4e/0x50
> [19.666764]  =======================
> [19.666764] handlers:
> [19.666764] [<c02cca2b>] (usb_hcd_irq+0x0/0x79)
> [19.666764] [<c02cca2b>] (usb_hcd_irq+0x0/0x79)
> [19.666764] Disabling IRQ #23
> 
> normally upon booting leaving me unable
> to login.
> 

What's the proprietary module that's tainting it?  Ideally we'd like to see it 
reproduced on an untainted kernel, but depending on what it is, it may not matter.

When you say you're not able to log in, is that because the keyboard is 
unresponsive?  It appears to be affecting USB, so I'd be curious to know if you 
can ssh into the box, or log in with a PS/2 keyboard.  Of course, some PS/2 
ports are connected via USB under the hood, so the keyboard might not tell us much.

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