linux-kernel - Re: Regression in 2.6.27: "irq 18: nobody cared" on Toshiba Satellite A100

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]

Message-id: <48FB6321.7030501@superonline.com>
Date:	Sun, 19 Oct 2008 12:41:05 -0400
From:	"M. Vefa Bicakci" <bicave@...eronline.com>
To:	Sven-Thorsten Dietrich <sdietrich@...ell.com>
Cc:	Olaf Dabrunz <odabrunz@...e.de>, Stefan Assmann <sassmann@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: Regression in 2.6.27: "irq 18: nobody cared" on Toshiba Satellite
 A100

Sven-Thorsten Dietrich wrote:
> On Sun, 2008-10-19 at 10:06 -0400, M. Vefa Bicakci wrote:
>> Hello,
>>
>> As you might guess from the subject line, since I started to use 2.6.27-rcX
>> series, I began to get "irq 18: nobody cared" messages in dmesg. Currently I am
>> using 2.6.27.2 with Sidux on this laptop, which is a Toshiba Satellite A100.
>> I have reproduced this problem with vanilla and sidux's kernels.
>>
> 
> Can you provide the contents of /proc/interrupts? 

My computer is currently in the "nobody cared" state. Here are the current
contents of /proc/interrupts:

--- 8< ---
           CPU0       CPU1       
  0:   45249492      60399   IO-APIC-edge      timer
  1:      25451          0   IO-APIC-edge      i8042
  8:          1          0   IO-APIC-edge      rtc0
  9:      36514          0   IO-APIC-fasteoi   acpi
 12:    1147983       2103   IO-APIC-edge      i8042
 14:     170245          0   IO-APIC-edge      ata_piix
 15:     558085        819   IO-APIC-edge      ata_piix
 16:        508          0   IO-APIC-fasteoi   uhci_hcd:usb5, i915@pci:0000:00:02.0
 17:       1353          0   IO-APIC-fasteoi   firewire_ohci
 18:     300158          1   IO-APIC-fasteoi   uhci_hcd:usb4, tifm_7xx1, yenta
 19:          0          0   IO-APIC-fasteoi   uhci_hcd:usb3
 20:      26606          2   IO-APIC-fasteoi   eth0
 22:    3206279          1   IO-APIC-fasteoi   HDA Intel
 23:          3          0   IO-APIC-fasteoi   uhci_hcd:usb1, ehci_hcd:usb2
220:    2105545          0   PCI-MSI-edge      iwl3945
NMI:          0          0   Non-maskable interrupts
LOC:    5971997   27874747   Local timer interrupts
RES:     938710    1791498   Rescheduling interrupts
CAL:     138135     180813   function call interrupts
TLB:      48455      64413   TLB shootdowns
TRM:          0          0   Thermal event interrupts
SPU:          0          0   Spurious interrupts
ERR:          0
MIS:          0
--- >8 ---

> If you can reproduce the keyboard issue, it would be helpful to have the
> above a few seconds before and after the device failure.

The keyboard issue happens every time I get the "nobody cared" message.

Unfortunately, this regression requires me to wait a long time before it shows itself.
As I mentioned in my original e-mail, the "nobody cared" message appears at 3:00
or 5:00 in the morning. However, I can write a cron job which saves the contents
of /proc/interrupts every minute or so. If this would be helpful, please let me know.

>> Note 2: Another interesting thing which might be relevant is the following
>> message which appears in dmesg some time after I boot:
>>
>> --- 8< ---
>> hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
>> --- >8 ---
>>
> 
> Is this card using IRQ 18?

It seems to use IRQ 22. I thought that there might be a connection, but it looks
like it isn't relevant.

> Thanks,
> Sven

Thank you; I appreciate your help.

Regards,

M. Vefa Bicakci

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