Your message dated Mon, 27 Jul 2009 22:37:24 +0200
with message-id <20090727203724.ga20...@galadriel.inutil.org>
and subject line Re: Unbalanced enable for IRQ 16 seems to be solved by using
kernel 2.6.29
has caused the Debian Bug report #523503,
regarding kernel-image-2.6: Unbalanced enable for IRQ 16
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
523503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kernel-image-2.6
Version: linux-image
Severity: normal
Since two weeks I get a kernel oops message and dmesg shows the
following information:
------------------------ snip -----------------------------
[ 6.632957] Unbalanced enable for IRQ 16
[ 6.632999] ------------[ cut here ]------------
[ 6.633038] WARNING: at kernel/irq/manage.c:158 enable_irq+0x3a/0x56()
[ 6.633083] Modules linked in: usbhid hid ff_memless uhci_hcd(+) floppy
ohci1394(+) ahci(+) jmicron(+) ieee1394 libata r8169 ide_core scsi_mod dock
ehci_hcd thermal processor
fan thermal_sys
[ 6.633692] Pid: 783, comm: modprobe Not tainted 2.6.26-1-amd64 #1
[ 6.633731]
[ 6.633732] Call Trace:
[ 6.633805] [<ffffffff802349b8>] warn_on_slowpath+0x51/0x7a
[ 6.633844] [<ffffffff8023540d>] printk+0x4e/0x56
[ 6.633884] [<ffffffff8023cf9f>] try_to_del_timer_sync+0x51/0x5a
[ 6.633925] [<ffffffff8021a826>] lapic_next_event+0xf/0x13
[ 6.633964] [<ffffffff80428c7a>] schedule_timeout+0x92/0xad
[ 6.634004] [<ffffffff8023cc1c>] process_timeout+0x0/0x5
[ 6.634043] [<ffffffff80428c6d>] schedule_timeout+0x85/0xad
[ 6.634083] [<ffffffff802127e5>] native_read_tsc+0x8/0x18
[ 6.634123] [<ffffffff8023d0db>] msleep+0x14/0x1e
[ 6.634162] [<ffffffff8026c629>] enable_irq+0x3a/0x56
[ 6.634210] [<ffffffffa005f602>] :ide_core:ide_probe_port+0x4cf/0x4e1
[ 6.634258] [<ffffffffa005ff86>] :ide_core:ide_device_add_all+0x209/0x5e4
[ 6.634306] [<ffffffffa006038b>] :ide_core:ide_device_add+0x2a/0x2f
[ 6.634348] [<ffffffffa00cffff>] :ahci:ahci_init_one+0x125/0xa69
[ 6.634395] [<ffffffffa0061ace>] :ide_core:ide_setup_pci_device+0x3c/0x45
[ 6.634436] [<ffffffff8032858f>] pci_match_device+0x18/0xad
[ 6.634476] [<ffffffff80328759>] pci_device_probe+0xa9/0xf8
[ 6.634516] [<ffffffff80384fd4>] driver_probe_device+0xd0/0x14d
[ 6.634556] [<ffffffff80385097>] __driver_attach+0x46/0x6d
[ 6.634596] [<ffffffff80385051>] __driver_attach+0x0/0x6d
[ 6.634634] [<ffffffff80384777>] bus_for_each_dev+0x44/0x6f
[ 6.634674] [<ffffffff80384bad>] bus_add_driver+0xb4/0x203
[ 6.634714] [<ffffffff80231a39>] check_preempt_wakeup+0xbd/0xe9
[ 6.634754] [<ffffffff803852f3>] driver_register+0x8d/0x101
[ 6.634794] [<ffffffff803289bd>] __pci_register_driver+0x47/0x7a
[ 6.636952] [<ffffffff80255067>] sys_init_module+0x190e/0x1aa4
[ 6.636952] [<ffffffff80324c3d>] pci_bus_read_config_dword+0x0/0x82
[ 6.636952] [<ffffffff8020beca>] system_call_after_swapgs+0x8a/0x8f
[ 6.636952]
[ 6.636952] ---[ end trace efd39fbcde4bec5b ]---
------------------------ snap -----------------------------
This message appears not at every system boot and I cant detect some
misfunction until yet.
I dont have change the configuration but I update my system via
aptitude safe-upgrade every two days.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Version: 2.6.29-1
On Mon, Jul 27, 2009 at 02:09:34PM +0200, Axel Ludszuweit wrote:
> No, after using kernel 2.6.29 this behavoiur does not appear anymore.
Thanks, closing the bug, then.
Cheers,
Moritz
--- End Message ---
