linux-kernel - Re: sdhci: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48981EAB.8080302@tudelft.nl>
Date:	Tue, 05 Aug 2008 11:34:35 +0200
From:	Eric Piel <E.A.B.Piel@...elft.nl>
To:	Pierre Ossman <drzeus-list@...eus.cx>, linux-kernel@...r.kernel.org
Subject: Re: sdhci: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter
 -	disabling IRQ

David Härdeman schreef:
> 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@...deman.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
> 

Interesting, I have the same problem when I turn on my wifi and 
bluetooth (b43 + hci_usb). However, it's my firewire controller which is 
on IRQ 19. So, could it be one of those hardware components generate an 
interrupt on #19 when turned on?

irq 19: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Not tainted 2.6.26-git-eric #17

Call Trace:
  <IRQ>  [<ffffffff804ca0eb>] ? _spin_unlock_irqrestore+0x1b/0x40
  [<ffffffff80283926>] __report_bad_irq+0x26/0x80
  [<ffffffff80283c1f>] note_interrupt+0x29f/0x2d0
  [<ffffffff8028450d>] handle_fasteoi_irq+0xdd/0x100
  [<ffffffff8020ff1d>] do_IRQ+0x9d/0x130
  [<ffffffff8020cbdd>] ret_from_intr+0x0/0x19
  <EOI>  [<ffffffff80223c26>] ? native_irq_enable+0x6/0x10
  [<ffffffffa01206b1>] ? :processor:acpi_idle_enter_simple+0x1e9/0x265
  [<ffffffff80422ac9>] ? cpuidle_idle_call+0xb9/0x100
  [<ffffffff80422a10>] ? cpuidle_idle_call+0x0/0x100
  [<ffffffff8020a000>] ? default_idle+0x0/0x50
  [<ffffffff8020b57c>] ? cpu_idle+0x6c/0x100
  [<ffffffff804b8d00>] ? rest_init+0x70/0x80

handlers:
[<ffffffffa0161fd0>] (ohci_irq_handler+0x0/0x8d0 [ohci1394])
Disabling IRQ #19


See you,
Eric

View attachment "E_A_B_Piel.vcf" of type "text/x-vcard" (368 bytes)