public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Härdeman" <david@hardeman.nu>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sdhci: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter - disabling IRQ
Date: Sun, 3 Aug 2008 00:47:25 +0200	[thread overview]
Message-ID: <20080802224725.GA6574@hardeman.nu> (raw)
In-Reply-To: <20080719015531.6c8a1981@mjolnir.drzeus.cx>

On Sat, Jul 19, 2008 at 01:55:31AM +0200, Pierre Ossman wrote:
>On Fri, 11 Jul 2008 18:47:06 +0200 David Härdeman <david@hardeman.nu> wrote:
>> On Thu, Jul 10, 2008 at 08:34:57AM +0200, Pierre Ossman wrote:
>> >And can you give me a complete
>> >dmesg dump. The sdhci hardware might not be the culprit, but just a
>> >trigger in that it enables that interrupt line.
>> 
>> Attached below....and /proc/interrupts says:
>> 
>
>I see that you have an iwl4965. I got this precise problem when I
>toggled the rfkill switch on my laptop. It is fixed in 2.6.26 though.
>Could you try upgrading the kernel and see if it's the same bug?

Unfortunately the problem is still present with 2.6.26 (Debian package 
linux-image-2.6.26-1-amd64):

[  640.407901] irq 19: nobody cared (try booting with the "irqpoll" option)
[  640.407906] Pid: 0, comm: swapper Not tainted 2.6.26-1-amd64 #1
[  640.407908] 
[  640.407909] Call Trace:
[  640.407910]  <IRQ>  [<ffffffff8026c46b>] __report_bad_irq+0x30/0x72
[  640.407937]  [<ffffffff8026c6aa>] note_interrupt+0x1fd/0x23b
[  640.407945]  [<ffffffff8026cf33>] handle_fasteoi_irq+0xa5/0xc8
[  640.407951]  [<ffffffff8020f590>] do_IRQ+0x6d/0xd9
[  640.407956]  [<ffffffff8020c43d>] ret_from_intr+0x0/0x19
[  640.407958]  <EOI>  [<ffffffff8021e480>] hpet_legacy_next_event+0x0/0x34
[  640.407974]  [<ffffffffa002f46e>] :processor:acpi_idle_enter_simple+0x18d/0x1ff
[  640.407983]  [<ffffffff803a704c>] cpuidle_idle_call+0x7a/0xb2
[  640.407986]  [<ffffffff803a6fd2>] cpuidle_idle_call+0x0/0xb2
[  640.407989]  [<ffffffff8020ac79>] cpu_idle+0x89/0xb3
[  640.408003] 
[  640.408004] handlers:
[  640.408005] [<ffffffffa012e9ab>] (sdhci_irq+0x0/0x5de [sdhci])
[  640.408010] Disabling IRQ #19

-- 
David Härdeman

  reply	other threads:[~2008-08-02 23:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 18:16 sdhci: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter - disabling IRQ David Härdeman
2008-07-10  6:34 ` Pierre Ossman
2008-07-11 16:47   ` David Härdeman
2008-07-18 23:55     ` Pierre Ossman
2008-08-02 22:47       ` David Härdeman [this message]
2008-08-05  9:22         ` Pierre Ossman
2008-08-20  6:45           ` David Härdeman
2008-08-20 11:04             ` Pierre Ossman
2008-08-05  9:34         ` Eric Piel

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=20080802224725.GA6574@hardeman.nu \
    --to=david@hardeman.nu \
    --cc=drzeus-list@drzeus.cx \
    --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