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

Bug#576408: marked as done (linux-image-2.6.32-4-amd64: ACPI conflict)

Your message dated Thu, 6 Jun 2013 00:13:24 +0200
with message-id <20130605221323.GD5444@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #576408,
regarding linux-image-2.6.32-4-amd64: ACPI conflict
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.)


-- 
576408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576408
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.32-4-amd64
Version: ACPI conflict
Severity: normal

When starting up I see this ACPI conflict being reported:

[    3.958046] i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[    3.958050] ACPI: I/O resource 0000:00:1f.3 [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f]
[    3.958122] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

/proc/ioports reveals:

0400-041f : 0000:00:1f.3
04d0-04d1 : pnp 00:08

This is on an Asus P5Q-E mobo. As I didn't tweak anything, I thought I'd
better report it. If I can provide any more information, please let me
know.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: