From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Chris Snook <csnook@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [19.666764] Disabling IRQ #23
Date: Tue, 9 Sep 2008 16:56:52 -0700 [thread overview]
Message-ID: <92D1B39E-9EF1-4D8F-B2C0-B1D2716AC4A9@gmail.com> (raw)
In-Reply-To: <48C706B3.4070409@redhat.com>
The only proprietary modules
Atheros and Fglrx. Which confuses me, due to the message giving
Info on USB. As for the login,
On a MacBook I need uhci
To use the keyboard. When this
Goes off I can type, but results
In the letter duplicating itself I.g.
Typing the letter * results in **
As for using ssh, no.
I guess as a workaround I can try and change my login name and password
With double letters so I can grab a copy of dmesg
justin P. Mattock
On Sep 9, 2008, at 4:28 PM, Chris Snook <csnook@redhat.com> wrote:
> 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
next prev parent reply other threads:[~2008-09-09 23:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 19:08 Justin Mattock
2008-09-09 23:28 ` Chris Snook
2008-09-09 23:56 ` Justin P. Mattock [this message]
2008-09-10 19:06 Justin Mattock
2008-09-10 19:36 ` Yinghai Lu
2008-09-10 19:39 ` Justin Mattock
2008-09-17 15:04 ` Bjorn Helgaas
2008-09-17 17:13 ` Justin Mattock
2008-09-17 21:48 ` Bjorn Helgaas
2008-09-17 22:18 ` Justin P. Mattock
2008-09-18 0:14 ` Justin Mattock
2008-09-18 4:44 ` Justin Mattock
2008-09-18 9:09 ` David Brownell
2008-09-18 16:57 ` Justin Mattock
2008-09-18 21:56 ` April Tsui
2008-09-18 22:23 ` Alan Stern
2008-09-19 0:32 ` Justin Mattock
2008-09-19 16:08 ` Alan Stern
2008-09-19 16:41 ` Justin Mattock
2008-09-19 17:05 ` Alan Stern
2008-09-19 18:18 ` Justin Mattock
2008-09-19 21:20 ` Justin Mattock
2008-09-20 0:56 ` David Brownell
2008-09-20 1:19 ` Justin Mattock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92D1B39E-9EF1-4D8F-B2C0-B1D2716AC4A9@gmail.com \
--to=justinmattock@gmail.com \
--cc=csnook@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®