[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#426264: marked as done (linux-image-2.6.18-4-686-bigmem: Kernel BUG: Unbalanced enable for IRQ nnn)

Your message dated Mon, 29 Dec 2008 14:00:21 +0100
with message-id <20081229130021.GA3926@galadriel.inutil.org>
and subject line Re: linux-image-2.6.18-4-686-bigmem: Kernel BUG: Unbalanced enable for IRQ nnn
has caused the Debian Bug report #426264,
regarding linux-image-2.6.18-4-686-bigmem: Kernel BUG: Unbalanced enable for IRQ nnn
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 owner@bugs.debian.org
immediately.)


-- 
426264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426264
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-4-686-bigmem
Version: 2.6.18.dfsg.1-12
Severity: normal

*** Please type your report below this line ***
Hi,

during the boot process sometimes the kernel reports the following message:

hde: HL-DT-ST DVDRAM GSA-H10N, ATAPI CD/DVD-ROM drive
Unbalanced enable for IRQ 177
BUG: warning at kernel/irq/manage.c:118/enable_irq()
 [<c013e6b1>] enable_irq+0x54/0x87
 [<f88638ae>] probe_hwif+0x556/0x627 [ide_core]
 [<c0210dfc>] __driver_attach+0x0/0x5d
 [<f8864195>] probe_hwif_init_with_fixup+0xb/0x63 [ide_core]
 [<f8865f61>] ide_setup_pci_device+0x3c/0x6d [ide_core]
 [<f8bc911e>] generic_init_one+0x92/0xa0 [generic]
 [<c01c121c>] pci_device_probe+0x36/0x57
 [<c0210d5d>] driver_probe_device+0x42/0x8b
 [<c0210e34>] __driver_attach+0x38/0x5d
 [<c021087e>] bus_for_each_dev+0x33/0x55
 [<c0210cc7>] driver_attach+0x11/0x13
 [<c0210dfc>] __driver_attach+0x0/0x5d
 [<c0210597>] bus_add_driver+0x64/0xfd
 [<c01c1358>] __pci_register_driver+0x47/0x63
 [<c0135fa5>] sys_init_module+0x16c3/0x1846
 [<c0160e08>] cp_new_stat64+0xfd/0x10f
 [<c0102c77>] syscall_call+0x7/0xb
ide2 at 0xbc00-0xbc07,0xb882 on irq 177

The problem does not occur at every boot and the system seems working well even after
reporting this warning.

I've an ASUS P5B motherboard with a JMicron 363 IDE controller.

Should you need further information about my hardware, please do not hesitate to
contact me.

Kind Regards,

Pietro Pizzo

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.18-4-686-bigmem depends on:
ii  coreutils                     5.97-5.3   The GNU core utilities
ii  debconf [debconf-2.0]         1.5.13     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.87b      tools for generating an initramfs
ii  module-init-tools             3.3-pre4-2 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.18-4-686-bigmem recommends:
ii  libc6-i686                  2.3.6.ds1-13 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.18-4-686-bigmem/postinst/depmod-error-initrd-2.6.18-4-686-bigmem: false
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-4-686-bigmem/postinst/bootloader-test-error-2.6.18-4-686-bigmem:
  linux-image-2.6.18-4-686-bigmem/preinst/abort-overwrite-2.6.18-4-686-bigmem:
  linux-image-2.6.18-4-686-bigmem/preinst/bootloader-initrd-2.6.18-4-686-bigmem: true
  linux-image-2.6.18-4-686-bigmem/postinst/depmod-error-2.6.18-4-686-bigmem: false
  linux-image-2.6.18-4-686-bigmem/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-4-686-bigmem/postinst/bootloader-error-2.6.18-4-686-bigmem:
  linux-image-2.6.18-4-686-bigmem/postinst/create-kimage-link-2.6.18-4-686-bigmem: true
  linux-image-2.6.18-4-686-bigmem/prerm/would-invalidate-boot-loader-2.6.18-4-686-bigmem: true
  linux-image-2.6.18-4-686-bigmem/preinst/overwriting-modules-2.6.18-4-686-bigmem: true
  linux-image-2.6.18-4-686-bigmem/postinst/old-system-map-link-2.6.18-4-686-bigmem: true
  linux-image-2.6.18-4-686-bigmem/preinst/initrd-2.6.18-4-686-bigmem:
  linux-image-2.6.18-4-686-bigmem/postinst/old-initrd-link-2.6.18-4-686-bigmem: true
  linux-image-2.6.18-4-686-bigmem/postinst/kimage-is-a-directory:
  linux-image-2.6.18-4-686-bigmem/preinst/abort-install-2.6.18-4-686-bigmem:
  linux-image-2.6.18-4-686-bigmem/prerm/removing-running-kernel-2.6.18-4-686-bigmem: true
  linux-image-2.6.18-4-686-bigmem/preinst/failed-to-move-modules-2.6.18-4-686-bigmem:
  linux-image-2.6.18-4-686-bigmem/postinst/old-dir-initrd-link-2.6.18-4-686-bigmem: true
  linux-image-2.6.18-4-686-bigmem/preinst/already-running-this-2.6.18-4-686-bigmem:
  linux-image-2.6.18-4-686-bigmem/preinst/lilo-initrd-2.6.18-4-686-bigmem: true
  linux-image-2.6.18-4-686-bigmem/preinst/elilo-initrd-2.6.18-4-686-bigmem: true

--- End Message ---
--- Begin Message --- 
Version: 2.6.26-1

On Mon, Dec 29, 2008 at 08:01:23AM +0100, Pietro Pizzo wrote:
> On Mon Dec 29 07:50:56 CET 2008, Moritz Muehlenhoff wrote:
>> Does this error still occur with more recent kernel versions?
>>
>> If you're running Etch, could you try to reproduce this bug
>> with the 2.6.24 based kernel added in 4.0r4?
>> http://packages.qa.debian.org/l/linux-2.6.24.html
>>
>> Cheers,
>>         Moritz
>
> I'm still running testing (Lenny) distribution at the moment and it's  
> now long time the bug didn't occur any more.
>
> I think it got fixed sometime in the past, when Lenny moved to a newer  
> kernel. I don't remember exactly which kernel version resolved the  
> problem, but the current testing kernel (2.6.26-1 at the time of  
> writing) doesn't suffer this bug.
>
> I've no time to reproduce the bug on a Etch distribution, but you can  
> reasonably close this bug on Lenny.
>
> Cheers and thanks for your support (even after 1.5 yrs!)

Thanks, closing the bug then.

Cheers,
        Moritz

--- End Message ---
Reply to: