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

Bug#701577: marked as done (BUG)

Your message dated Sun, 29 May 2016 21:24:52 +0100
with message-id ca00d8ed-41ed-45fb-a6ac-9ac4f4bd113e@decadent.org.uk
and subject line Closing bugs assigned to linux-2.6 package
has caused the Debian Bug report #701577,
regarding BUG
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.)


-- 
701577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701577
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-source-2.6.32
Version: 2.6.32-48
 
When CONFIG_AMD_NB is not set, compiling fails with:
 
amd_bus.c:(.init.text+0x148a): undefined reference to `amd_get_mmconfig_range'.
 
The patchfix:
 
--- arch/x86/pci/Makefile-orig  2013-02-24 12:46:05.000000000 +0100
+++ arch/x86/pci/Makefile       2013-02-24 12:51:05.000000000 +0100
@@ -14,4 +14,4 @@
 obj-$(CONFIG_X86_NUMAQ)                += numaq_32.o
 
 obj-y                          += common.o early.o
-obj-y                          += amd_bus.o
+obj-$(CONFIG_AMD_NB)           += amd_bus.o

--- End Message ---
--- Begin Message --- 
Version: 3.4.1-1~experimental.1+rm

Debian 6.0 Long Term Support has ended, and the 'linux-2.6' source
package will no longer be updated.  This bug was reassigned to the
'linux' source package earlier today, but I am now closing it on the
assumption that it does not affect the kernel versions in newer Debian
releases.

If you can still reproduce this bug in a newer release, please reopen
the bug report and reassign it to 'src:linux' and the affected version
of the package.  You can find the package version for the running
kernel by running:

    uname -v

or the versions of all installed kernel packages by running:

    dpkg -l 'linux-image-[34]*' | grep ^.i

and looking at the third column.

I apologise that we weren't able to provide a specific resolution for
this bug.

Ben.

-- 
Ben Hutchings - Debian developer, member of Linux kernel and LTS teams

--- End Message ---
Reply to: