From: Wojciech Zareba <wojtekz@comp.waw.pl>
To: linux-ide@vger.kernel.org
Subject: Re: PROBLEM: WARNING: at kernel/irq/manage.c:158 enable_irq() during boot
Date: Tue, 11 Dec 2007 14:00:30 +0100 [thread overview]
Message-ID: <475E89EE.70501@comp.waw.pl> (raw)
In-Reply-To: <475D085F.9010307@gmail.com>
Hello,
Tejun Heo pisze:
> (cc'ing Bartlomiej)
> Hello,
>
> wojtekz@comp.waw.pl wrote:
>> Dec 6 11:58:23 titanium kernel: WARNING: at kernel/irq/manage.c:158 enable_irq()
>> Dec 6 11:58:23 titanium kernel: [<c014b5c3>] enable_irq+0x6e/0xa2
>> Dec 6 11:58:23 titanium kernel: [<f887b783>] probe_hwif+0x6d8/0x7c7 [ide_core]
>> Dec 6 11:58:23 titanium kernel: [<f887c0be>] probe_hwif_init_with_fixup+0xc/0x80 [ide_core]
>> Dec 6 11:58:23 titanium kernel: [<c0190007>] elf_core_dump+0x627/0xb60
>> Dec 6 11:58:23 titanium kernel: [<f887df7b>] ide_setup_pci_device+0x6f/0x9c [ide_core]
>> Dec 6 11:58:23 titanium kernel: [<f883b1a7>] pdc202new_init_one+0xf/0x10 [pdc202xx_new]
>> Dec 6 11:58:23 titanium kernel: [<c01d94de>] pci_device_probe+0x36/0x55
>> Dec 6 11:58:23 titanium kernel: [<c021f8cb>] driver_probe_device+0xc8/0x14b
>> Dec 6 11:58:23 titanium kernel: [<c021fa37>] __driver_attach+0x52/0x87
>> Dec 6 11:58:23 titanium kernel: [<c021eecc>] bus_for_each_dev+0x35/0x57
>> Dec 6 11:58:23 titanium kernel: [<c021f748>] driver_attach+0x16/0x18
>> Dec 6 11:58:23 titanium kernel: [<c021f9e5>] __driver_attach+0x0/0x87
>> Dec 6 11:58:23 titanium kernel: [<c021f1a8>] bus_add_driver+0x6d/0x153
>> Dec 6 11:58:23 titanium kernel: [<c01d961d>] __pci_register_driver+0x4b/0x77
>> Dec 6 11:58:23 titanium kernel: [<c0143a39>] sys_init_module+0x1525/0x15fb
>> Dec 6 11:58:23 titanium kernel: [<f8879af9>] ide_config_drive_speed+0x0/0x314 [ide_core]
>> Dec 6 11:58:23 titanium kernel: [<c0103f9e>] syscall_call+0x7/0xb
>> Dec 6 11:58:23 titanium kernel: [<c02b0000>] wireless_nlevent_process+0x15/0x31
>> Dec 6 11:58:23 titanium kernel: =======================
>
> That means IRQ is being enabled more times than it should be. Can you
> please give a shot at 2.6.24-rc4 and see whether the problem is still there?
>
It seems to be no more of this warning in the 2.6.24-rc4 kernel. But my feeling
is that overall system performance is much poorer... pity. Maybe I should change
something in the .config file?
Regards
Wojciech
next prev parent reply other threads:[~2007-12-11 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 12:10 PROBLEM: WARNING: at kernel/irq/manage.c:158 enable_irq() during boot wojtekz
2007-12-10 9:35 ` Tejun Heo
2007-12-11 13:00 ` Wojciech Zareba [this message]
2007-12-11 23:39 ` Tejun Heo
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=475E89EE.70501@comp.waw.pl \
--to=wojtekz@comp.waw.pl \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).