Processed: affects 886474

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # See #886512 and #886510
> affects 886474 + nvidia-legacy-304xx-kernel-dkms broadcom-sta-dkms dkms
Bug #886474 [linux-headers-4.14.0-3-amd64] linux-headers-4.14.0-3-amd64: 
missing dependency on libelf-dev
Bug #886510 [linux-headers-4.14.0-3-amd64] Cannot generate ORC metadata for 
CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel
Added indication that 886474 affects nvidia-legacy-304xx-kernel-dkms, 
broadcom-sta-dkms, and dkms
Added indication that 886510 affects nvidia-legacy-304xx-kernel-dkms, 
broadcom-sta-dkms, and dkms
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
886474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886474
886510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#886510: OK now I installed libelf-dev, but...

[積丹尼 Dan Jacobson]

OK now I did,

# aptitude install libelf-dev
The following NEW packages will be installed:
  libelf-dev
The following packages will be REMOVED:
  linux-headers-4.14.0-1-amd64{pu}  linux-headers-4.14.0-1-common{pu} (D: 
linux-headers-4.14.0-1-amd64)

And now the error is gone,

# aptitude reinstall linux-image-4.14.0-3-amd64
The following packages will be REINSTALLED:
  linux-image-4.14.0-3-amd64
Preparing to unpack .../linux-image-4.14.0-3-amd64_4.14.12-2_amd64.deb ...
Unpacking linux-image-4.14.0-3-amd64 (4.14.12-2) over (4.14.12-2) ...
Setting up linux-image-4.14.0-3-amd64 (4.14.12-2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.14.0-3-amd64

But I didn't see and nvidia-legacy-304xx-kernel-dkms related messages...
so maybe I have wiped that component out in the process, ruining the
whole purpose?

Processed: Re: Bug#886510: Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 linux-headers-4.14.0-3-amd64
Bug #886510 [nvidia-legacy-304xx-kernel-dkms] Cannot generate ORC metadata for 
CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel
Bug reassigned from package 'nvidia-legacy-304xx-kernel-dkms' to 
'linux-headers-4.14.0-3-amd64'.
No longer marked as found in versions 
nvidia-graphics-drivers-legacy-304xx/304.137-3.
Ignoring request to alter fixed versions of bug #886510 to the same values 
previously set
> forcemerge 886474 -1
Bug #886474 [linux-headers-4.14.0-3-amd64] linux-headers-4.14.0-3-amd64: 
missing dependency on libelf-dev
Bug #886510 [linux-headers-4.14.0-3-amd64] Cannot generate ORC metadata for 
CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel
Severity set to 'grave' from 'normal'
Marked as found in versions linux/4.14.12-2.
Merged 886474 886510

-- 
886474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886474
886510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 886474 is grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 886474 grave
Bug #886474 [linux-headers-4.14.0-3-amd64] linux-headers-4.14.0-3-amd64: 
missing dependency on libelf-dev
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
886474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

linux_3.2.96-3_multi.changes REJECTED

[Debian FTP Masters]

linux_3.2.96-3.dsc: Refers to non-existing file 'linux_3.2.96.orig.tar.xz'
Perhaps you need to include the file in your upload?



===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.

Processed: retitle 883425 to linux-image 4.14.x: stale Android device entries in Thunar after USB disconnection

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 883425 linux-image 4.14.x: stale Android device entries in Thunar 
> after USB disconnection
Bug #883425 [linux-image-4.14.0-3-amd64] linux-image 14.4: stale Android device 
entries in Thunar after USB disconnection
Changed Bug title to 'linux-image 4.14.x: stale Android device entries in 
Thunar after USB disconnection' from 'linux-image 14.4: stale Android device 
entries in Thunar after USB disconnection'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
883425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#886417: linux-source-4.9: Kernel sources do not compile

[Robert Senger]

Package: linux-source-4.9
Followup-For: Bug #886417

I am also using a custom config, trying to build a kernel for a old AMD Geode
i386 machine (inside a i386 systemd-nspawn container running on a amd64
machine).




-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-source-4.9 depends on:
ii  binutils  2.28-5
ii  xz-utils  5.2.2-1.2+b1

Versions of packages linux-source-4.9 recommends:
ii  bc1.06.95-9+b3
ii  gcc   4:6.3.0-4
ii  libc6-dev [libc-dev]  2.24-11+deb9u1
ii  make  4.1-9.1

Versions of packages linux-source-4.9 suggests:
pn  libncurses-dev | ncurses-dev  
pn  libqt4-dev
ii  pkg-config0.29-4+b1
#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 4.9.65-1-geode Kernel Configuration
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf32-i386"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_MMU=y
CONFIG_ARCH_MMAP_RND_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_BITS_MAX=16
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_DEBUG_RODATA=y
CONFIG_PGTABLE_LEVELS=2
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
CONFIG_THREAD_INFO_IN_TASK=y

#
# General setup
#
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
CONFIG_KERNEL_XZ=y
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_FHANDLE=y
CONFIG_USELIB=y
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_GENERIC_MSI_IRQ=y
CONFIG_GENERIC_MSI_IRQ_DOMAIN=y
# CONFIG_IRQ_DOMAIN_DEBUG is not set
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_IRQ_TIME_ACCOUNTING is not set
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y

#
# RCU Subsystem
#
CONFIG_TINY_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
# CONFIG_TASKS_RCU is not set
# CONFIG_RCU_STALL_COMMON is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_RCU_EXPEDITE_BOOT is not set
CONFIG_BUILD_BIN2C=y
CONFIG_IKCONFIG=m
# CONFIG_IKCONFIG_PROC is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_NMI_LOG_BUF_SHIFT=13
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
# CONFIG_MEMCG_SWAP_ENABLED is not set
CONFIG_BLK_CGROUP=y
# CONFIG_DEBUG_BLK_CGROUP is not set
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_CFS_BANDWIDTH is not set
# CONFIG_RT_GROUP_SCHED is not set
# CONFIG_CGROUP_PIDS is not set
CONFIG_CGROUP_FREEZER=y
# CONFIG_CGROUP_HUGETLB is not set
CONFIG_CPUSETS=y

Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as Xen guest in HVM mode

[frm]

> -Oorspronkelijk bericht-
> Van: Hans van Kranenburg [mailto:h...@knorrie.org]
> Verzonden: zondag 7 januari 2018 00:27
> Aan: frm ; 886...@bugs.debian.org
> Onderwerp: Re: Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as
> Xen guest in HVM mode
> 
> Hi,
> 
> Please reply-all and not only to me.
> 
> On 01/07/2018 12:07 AM, frm wrote:
> >> The first step here is to collect more information. Things that are
> >> or are not working with Xen setups can be difficult to track down,
> >> since it can be related to any combination of anything like hardware,
> hypervisor, dom0, domU etc...
> >>
> >> From your description I guess that changing domU from
> >> linux-image-4.9.0-3-amd64 to linux-image-4.9.0-5-amd64 while all
> >> other things remain the same caused the issue. Is that right?
> > Yes. If I revert back to 4.9.0-3-amd64 at the guest, I can boot in hvm mode.
> 
> Ok, great.
> 
> >> I see you're using Debian Release: 8.10, which might imply Xen 4.4
> >> and the jessie kernel for the dom0.
> >>
> >> As seen from the dom0, can you please reply with `uname -a`, `xen
> >> info` and `lspci -v` output.
> > uname -a
> > Linux nuc1 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19)
> > x86_64 GNU/Linux
> 
> So that's a stretch kernel package for the dom0.
> 
> How did you end up reporting this from a Jessie system?
I am on stretch

> 
> > xen info
> > host   : nuc1
> > release: 4.9.0-3-amd64
> > version: #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19)
> > machine: x86_64
> > nr_cpus: 4
> > max_cpu_id : 3
> > nr_nodes   : 1
> > cores_per_socket   : 2
> > threads_per_core   : 2
> > cpu_mhz: 1895
> > hw_caps:
> b7ebfbff:77faf3bf:2c100800:0021:0001:27ab::0100
> > virt_caps  : hvm hvm_directio
> > total_memory   : 16309
> > free_memory: 366
> > sharing_freed_memory   : 0
> > sharing_used_memory: 0
> > outstanding_claims : 0
> > free_cpus  : 0
> > xen_major  : 4
> > xen_minor  : 8
> > xen_extra  : .1
> > xen_version: 4.8.1
> > xen_caps   : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-
> 3.0-x86_32p hvm-3.0-x86_64
> > xen_scheduler  : credit
> > xen_pagesize   : 4096
> > platform_params: virt_start=0x8000
> > xen_changeset  :
> > xen_commandline: loglvl=all noreboot dom0_mem=3328M
> max=3328M dom0_max_vcpus=4 dom0_vcpus_pin gnttab_max_frames=256
> > cc_compiler: gcc (Debian 6.3.0-18) 6.3.0 20170516
> > cc_compile_by  : ian.jackson
> > cc_compile_domain  : eu.citrix.com
> > cc_compile_date: Thu Sep  7 18:24:26 UTC 2017
> > build_id   : bc5b60fc44b11ff01ffbaea6cbc8cf9d
> > xend_config_format : 4
> 
> Ok, xen 4.8
> 
> > lspci -v
> > 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev
> 09)
> > Subsystem: Intel Corporation Haswell-ULT DRAM Controller
> > Flags: bus master, fast devsel, latency 0
> > Capabilities: [e0] Vendor Specific Information: Len=0c 
> >
> > 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT
> Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
> > Subsystem: Intel Corporation Haswell-ULT Integrated Graphics
> Controller
> > Flags: bus master, fast devsel, latency 0, IRQ 77
> > Memory at f780 (64-bit, non-prefetchable) [size=4M]
> > Memory at e000 (64-bit, prefetchable) [size=256M]
> > I/O ports at f000 [size=64]
> > [virtual] Expansion ROM at 000c [disabled] [size=128K]
> > Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
> > Capabilities: [d0] Power Management version 2
> > Capabilities: [a4] PCI Advanced Features
> > Kernel driver in use: i915
> > Kernel modules: i915
> >
> > 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller
> (rev 09)
> > Subsystem: Intel Corporation Haswell-ULT HD Audio Controller
> > Flags: bus master, fast devsel, latency 0, IRQ 78
> > Memory at f7c34000 (64-bit, non-prefetchable) [size=16K]
> > Capabilities: [50] Power Management version 2
> > Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit-
> > Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
> > Kernel driver in use: snd_hda_intel
> > Kernel modules: snd_hda_intel
> >
> > 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
> (prog-if 30 [XHCI])
> > Subsystem: Intel Corporation 8 Series USB xHCI HC
> > Flags: medium devsel, IRQ 73
> > Memory at f7c2 (64-bit, non-prefetchable) [size=64K]
> > Capabilities: [70] Power Management version 2
> > Capabilities: 

Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as Xen guest in HVM mode

[Hans van Kranenburg]

Hi,

Please reply-all and not only to me.

On 01/07/2018 12:07 AM, frm wrote:
>> The first step here is to collect more information. Things that are or are 
>> not
>> working with Xen setups can be difficult to track down, since it can be 
>> related
>> to any combination of anything like hardware, hypervisor, dom0, domU etc...
>>
>> From your description I guess that changing domU from
>> linux-image-4.9.0-3-amd64 to linux-image-4.9.0-5-amd64 while all other
>> things remain the same caused the issue. Is that right?
> Yes. If I revert back to 4.9.0-3-amd64 at the guest, I can boot in hvm mode.

Ok, great.

>> I see you're using Debian Release: 8.10, which might imply Xen 4.4 and the
>> jessie kernel for the dom0.
>>
>> As seen from the dom0, can you please reply with `uname -a`, `xen info` and
>> `lspci -v` output.
> uname -a
> Linux nuc1 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 
> GNU/Linux

So that's a stretch kernel package for the dom0.

How did you end up reporting this from a Jessie system?

> xen info
> host   : nuc1
> release: 4.9.0-3-amd64
> version: #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19)
> machine: x86_64
> nr_cpus: 4
> max_cpu_id : 3
> nr_nodes   : 1
> cores_per_socket   : 2
> threads_per_core   : 2
> cpu_mhz: 1895
> hw_caps: 
> b7ebfbff:77faf3bf:2c100800:0021:0001:27ab::0100
> virt_caps  : hvm hvm_directio
> total_memory   : 16309
> free_memory: 366
> sharing_freed_memory   : 0
> sharing_used_memory: 0
> outstanding_claims : 0
> free_cpus  : 0
> xen_major  : 4
> xen_minor  : 8
> xen_extra  : .1
> xen_version: 4.8.1
> xen_caps   : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
> hvm-3.0-x86_32p hvm-3.0-x86_64
> xen_scheduler  : credit
> xen_pagesize   : 4096
> platform_params: virt_start=0x8000
> xen_changeset  :
> xen_commandline: loglvl=all noreboot dom0_mem=3328M max=3328M 
> dom0_max_vcpus=4 dom0_vcpus_pin gnttab_max_frames=256
> cc_compiler: gcc (Debian 6.3.0-18) 6.3.0 20170516
> cc_compile_by  : ian.jackson
> cc_compile_domain  : eu.citrix.com
> cc_compile_date: Thu Sep  7 18:24:26 UTC 2017
> build_id   : bc5b60fc44b11ff01ffbaea6cbc8cf9d
> xend_config_format : 4

Ok, xen 4.8

> lspci -v
> 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
> Subsystem: Intel Corporation Haswell-ULT DRAM Controller
> Flags: bus master, fast devsel, latency 0
> Capabilities: [e0] Vendor Specific Information: Len=0c 
> 
> 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
> Graphics Controller (rev 09) (prog-if 00 [VGA controller])
> Subsystem: Intel Corporation Haswell-ULT Integrated Graphics 
> Controller
> Flags: bus master, fast devsel, latency 0, IRQ 77
> Memory at f780 (64-bit, non-prefetchable) [size=4M]
> Memory at e000 (64-bit, prefetchable) [size=256M]
> I/O ports at f000 [size=64]
> [virtual] Expansion ROM at 000c [disabled] [size=128K]
> Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
> Capabilities: [d0] Power Management version 2
> Capabilities: [a4] PCI Advanced Features
> Kernel driver in use: i915
> Kernel modules: i915
> 
> 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
> 09)
> Subsystem: Intel Corporation Haswell-ULT HD Audio Controller
> Flags: bus master, fast devsel, latency 0, IRQ 78
> Memory at f7c34000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [50] Power Management version 2
> Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit-
> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
> Kernel driver in use: snd_hda_intel
> Kernel modules: snd_hda_intel
> 
> 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 
> (prog-if 30 [XHCI])
> Subsystem: Intel Corporation 8 Series USB xHCI HC
> Flags: medium devsel, IRQ 73
> Memory at f7c2 (64-bit, non-prefetchable) [size=64K]
> Capabilities: [70] Power Management version 2
> Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
> Kernel driver in use: xhci_hcd
> Kernel modules: xhci_pci
> 
> 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
> Subsystem: Intel Corporation 8 Series HECI
> Flags: bus master, fast devsel, latency 0, IRQ 75
> Memory at f7c3e000 (64-bit, non-prefetchable) [size=32]
> Capabilities: [50] Power Management version 3
> Capabilities: [8c] MSI: Enable+ Count=1/1 

Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as Xen guest in HVM mode

[Hans van Kranenburg]

Hi jgfrm,

On 01/06/2018 06:41 PM, jgfrm wrote:
> Package: linux-image-4.9.0-5-amd64
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> Upgrade of linux-image-4.9.0-3-amd64 to linux-image-4.9.0-5-amd64
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> Disable hvm guest boot in hypervisor
> 
>* What was the outcome of this action?
> Guest boots in pv mode
>* What outcome did you expect instead?
> Use hvm mode in guest config file, such that guest boots in hvm mode
> 
> *** End of the template - remove these template lines ***
> 
> 
> -- System Information:
> Debian Release: 8.10
>   APT prefers oldstable
>   APT policy: (500, 'oldstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 

The first step here is to collect more information. Things that are or
are not working with Xen setups can be difficult to track down, since it
can be related to any combination of anything like hardware, hypervisor,
dom0, domU etc...

>From your description I guess that changing domU from
linux-image-4.9.0-3-amd64 to linux-image-4.9.0-5-amd64 while all other
things remain the same caused the issue. Is that right?



I see you're using Debian Release: 8.10, which might imply Xen 4.4 and
the jessie kernel for the dom0.

As seen from the dom0, can you please reply with `uname -a`, `xen info`
and `lspci -v` output.

Since the domU is running linux-image-4.9.0-5-amd64 that can only mean
it's the kernel update just done, which is version 4.9.65-3+deb9u2

When reporting kernel versions, note that the package name and the
actual version can be different. So please always include the real
package version, like 4.9.65-3 or whatever in case of
linux-image-4.9.0-4-amd64.

Anything you could do yourself to narrow down the issue would help.

With enough information, someone else might be able to reproduce the
same situation and confirm the issue.

Hans van Kranenburg

Bug#884638: Any word/progress?

[John Eikenberry]

Any word on this? I'm currently stuck deciding between having a usable computer
or an insecure one while waiting for the meltdown fix to make it into
backports.

-- 

John Eikenberry
[ j...@zhar.net - http://zhar.net ]
[ PGP public key @ http://zhar.net/jae_at_zhar_net.gpg ]

"Perfection is attained, not when no more can be added, but when no more
 can be removed." -- Antoine de Saint-Exupery


signature.asc
Description: PGP signature

Bug#886504: firmware-misc-nonfree: Please include Intel GPU firmware supporting 'HuC' (HEVC decoding) and 'GuC' (improved workload scheduling)

[a . marmodoro]

Package: firmware-misc-nonfree
Version: 20161130-3
Severity: wishlist

Dear Maintainer,
In addition to the already provided '/lib/firmware/i915/skl_dmc_ver1_26.bin' 
firmware file 
for the Intel 'Skylake' integrated GPU architecture, please consider including 
also the 2
additional 'HuC' and 'GuC' packages, respectively claimed to assist with HEVC 
media operations
and parallel workload scheduling.

The compressed firmware files are available from:

https://01.org/sites/default/files/downloads/intelr-graphics-linux/sklhucver01071398.tar_0.bz2

https://01.org/sites/default/files/downloads/intelr-graphics-linux/sklgucver933.tar_0.bz2

... and more generally, it would appear very desireable to try and include 
within this Debian
package further firmwares from:

https://01.org/linuxgraphics/downloads

One may perhaps consider collecting such content within a separate 
'firmware-intel-graphics'
new package, to keep things neat.

Thank you very much,
--
Alberto.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.10 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ii  initramfs-tools  0.130

-- no debconf information

Processed: reassign 883425 to linux-image-4.14.0-3-amd64

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 883425 linux-image-4.14.0-3-amd64 4.14.12-2
Bug #883425 [src:linux] linux-image 14.4: stale Android device entries in 
Thunar after USB disconnection
Bug reassigned from package 'src:linux' to 'linux-image-4.14.0-3-amd64'.
No longer marked as found in versions linux/4.14.2-1.
Ignoring request to alter fixed versions of bug #883425 to the same values 
previously set
Bug #883425 [linux-image-4.14.0-3-amd64] linux-image 14.4: stale Android device 
entries in Thunar after USB disconnection
Marked as found in versions linux/4.14.12-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
883425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 883425 to linux-image 14.4: stale Android device entries in Thunar after USB disconnection

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 883425 linux-image 14.4: stale Android device entries in Thunar after 
> USB disconnection
Bug #883425 [src:linux] linux-image-4.14.0-1-amd64: stale Android device 
entries in Thunar after USB disconnection
Changed Bug title to 'linux-image 14.4: stale Android device entries in Thunar 
after USB disconnection' from 'linux-image-4.14.0-1-amd64: stale Android device 
entries in Thunar after USB disconnection'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
883425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#883425: linux-image-4.14.0-1-amd64: stale Android device entries in Thunar after USB disconnection

[Ben Caradoc-Davies]

Still present in linux-image-4.14.0-3-amd64 4.14.12-2.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed: reassign 886491 to src:linux

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 886491 src:linux 4.9.65-3+deb9u2
Bug #886491 [linux-image-4.9.0-5-amd64] linux-image-4.9.0-5-amd64: Does not 
boot as Xen guest in HVM mode
Bug reassigned from package 'linux-image-4.9.0-5-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #886491 to the same values 
previously set
Ignoring request to alter fixed versions of bug #886491 to the same values 
previously set
Bug #886491 [src:linux] linux-image-4.9.0-5-amd64: Does not boot as Xen guest 
in HVM mode
Marked as found in versions linux/4.9.65-3+deb9u2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
886491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

[LJ]

> Try also booting without 'quiet' and with 'debug earlyprintk'.

Happy to try, but not sure how to do that - do I edit
/boot/config-4.9.0-5-686-pae ?  Couldn't see "QUIET" in there?

> If you manage to get a kernel log (using a
> serial port or maybe netconsole if it's not too early in the boot) it'd
> help I guess.

The box has a serial port, but not sure I've got anything to plug into it!
I might have an old Debian box somewhere... :)

Thanks,
LJ

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

[Yves-Alexis Perez]

On Sat, 2018-01-06 at 18:04 +, LJ wrote:
> > Looking at the lspci output you have a Xeon E3 from the 1200 series, but
> > you
> > could provide your full /proc/cpuinfo?
> 
> Hi, sure...

Thanks
> 
> root@sam:~# cat /proc/cpuinfo
> processor   : 0
> vendor_id   : GenuineIntel
> cpu family  : 6
> model   : 60
> model name  : Intel(R) Celeron(R) CPU G1840 @ 2.80GHz

So definitely not a Xeon E3, but Haswell generation.

> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb
> rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc
> aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
> sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer
> xsave rdrand lahf_lm abm tpr_shadow vnmi flexpriority ept vpid fsgsbase
> tsc_adjust erms invpcid xsaveopt dtherm arat pln pts

So with pcid/invpcid.

Right now I'm unsure what to do. If you manage to get a kernel log (using a
serial port or maybe netconsole if it's not too early in the boot) it'd help I
guess.

Try also booting without 'quiet' and with 'debug earlyprintk'.

If you have the possibility to build a 4.9.75 kernel and try booting it might
help (at one point I might have a Debian build for you but that's not the case
right now).

Regards,
-- 
Yves-Alexis

signature.asc
Description: This is a digitally signed message part

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

[LJ]

> Looking at the lspci output you have a Xeon E3 from the 1200 series, but
> you
> could provide your full /proc/cpuinfo?

Hi, sure...

root@sam:~# cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : Intel(R) Celeron(R) CPU G1840 @ 2.80GHz
stepping: 3
microcode   : 0x22
cpu MHz : 1097.680
cache size  : 2048 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer
xsave rdrand lahf_lm abm tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust erms invpcid xsaveopt dtherm arat pln pts
bugs:
bogomips: 5587.41
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : Intel(R) Celeron(R) CPU G1840 @ 2.80GHz
stepping: 3
microcode   : 0x22
cpu MHz : 1199.877
cache size  : 2048 KB
physical id : 0
siblings: 2
core id : 1
cpu cores   : 2
apicid  : 2
initial apicid  : 2
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer
xsave rdrand lahf_lm abm tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust erms invpcid xsaveopt dtherm arat pln pts
bugs:
bogomips: 5587.41
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

Thanks,
LJ

Bug#886491: linux-image-4.9.0-5-amd64: Does not boot as Xen guest in HVM mode

[jgfrm]

Package: linux-image-4.9.0-5-amd64
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Upgrade of linux-image-4.9.0-3-amd64 to linux-image-4.9.0-5-amd64

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Disable hvm guest boot in hypervisor

   * What was the outcome of this action?
Guest boots in pv mode
   * What outcome did you expect instead?
Use hvm mode in guest config file, such that guest boots in hvm mode

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 8.10
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#886440: linux: Support to build linux-libc-dev for the upcoming riscv64 architecture

[Manuel A. Fernandez Montecelo]

2018-01-06 18:15 GMT+01:00 Ben Hutchings :
> On Sat, 2018-01-06 at 01:09 +0100, Manuel A. Fernandez Montecelo wrote:
>> Source: linux
>> Version: 4.15~rc5-1~exp1
>> Severity: wishlist
>> Tags: patch
>> User: debian-ri...@lists.debian.org
>> Usertags: riscv64
>>
>> Hello,
>>
>> The 4.15 kernel comes with initial support for RISC-V.
>>
>> Enabling support to build linux-libc-dev is one of the first steps to 
>> bootstrap
>> the architecture, so please consider enabling it.
>>
>> If there's anything wrong or missing, please let me know.
>
> You've missed out several steps:
>
> 1. Add the architecture definition to dpkg/unstable.
> 2. Backport that addition to dpkg/stable.
> 3. Get the stable update installed on ftp-master.
>
> dak will reject uploads that mention an architecture that the local
> dpkg doesn't recognise.

It's requested, but not done:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822914

Didn't know about dak, thanks for the notice.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

[Yves-Alexis Perez]

On Sat, 2018-01-06 at 15:46 +, LJ wrote:
> Booting in recovery mode the final lines are:
> 
> [   0.058600] x86: Booting SMP configuration:
> [   0.058632]  node  #0, CPUs:  :1
> 
> The cursor is flashing after the "#1" and the system hangs at that point.
> 
> I have video and a screenshot of boot if that helps.

Looking at the lspci output you have a Xeon E3 from the 1200 series, but you
could provide your full /proc/cpuinfo?

You're running the system in 32bit mode, which KAISER/KPTI doesn't touch (so
meltdown is *not* fixed), so I guess it comes from the preparation patches for
 KAISER rather than KAISER itself.

Regards,
-- 
Yves-Alexis

signature.asc
Description: This is a digitally signed message part

Bug#886440: linux: Support to build linux-libc-dev for the upcoming riscv64 architecture

[Ben Hutchings]

On Sat, 2018-01-06 at 01:09 +0100, Manuel A. Fernandez Montecelo wrote:
> Source: linux
> Version: 4.15~rc5-1~exp1
> Severity: wishlist
> Tags: patch
> User: debian-ri...@lists.debian.org
> Usertags: riscv64
> 
> Hello,
> 
> The 4.15 kernel comes with initial support for RISC-V.
> 
> Enabling support to build linux-libc-dev is one of the first steps to 
> bootstrap
> the architecture, so please consider enabling it.
> 
> If there's anything wrong or missing, please let me know.

You've missed out several steps:

1. Add the architecture definition to dpkg/unstable.
2. Backport that addition to dpkg/stable.
3. Get the stable update installed on ftp-master.

dak will reject uploads that mention an architecture that the local
dpkg doesn't recognise.

Ben.

-- 
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.



signature.asc
Description: This is a digitally signed message part

Processed: tagging 886485, affects 886485

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 886485 - security
Bug #886485 [src:linux] linux-image-4.9.0-5-686-pae: Hangs on boot at " 
node  #0, CPUs:#1"
Removed tag(s) security.
> affects 886485 + security.debian.org
Bug #886485 [src:linux] linux-image-4.9.0-5-686-pae: Hangs on boot at " 
node  #0, CPUs:#1"
Added indication that 886485 affects security.debian.org
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
886485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: additional info

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found #884001 linux/4.9.65-3+deb9u2
Bug #884001 [src:linux] linux-image-4.9.0-4-amd64: Severe graphics corruption 
on intel graphics after kernel upgrade
Marked as found in versions linux/4.9.65-3+deb9u2.
> fixed #884001 linux/4.14.7-1~bpo9+1
Bug #884001 [src:linux] linux-image-4.9.0-4-amd64: Severe graphics corruption 
on intel graphics after kernel upgrade
Marked as fixed in versions linux/4.14.7-1~bpo9+1.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
884001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

[LJ]

Package: src:linux
Version: 4.9.65-3+deb9u2
Severity: critical
Tags: security
Justification: breaks the whole system

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Updated the system as requested in Debian Security Advisory DSA-4078-1

Booting in recovery mode the final lines are:

[   0.058600] x86: Booting SMP configuration:
[   0.058632]  node  #0, CPUs:  :1

The cursor is flashing after the "#1" and the system hangs at that point.

I have video and a screenshot of boot if that helps.

Thanks,
LJ


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM 
Controller [8086:0c00] (rev 06)
Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM 
Controller [1458:5000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: hsw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 
00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF 
Not Supported ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [90] Subsystem: Gigabyte Technology Co., Ltd 8 
Series/C220 Series Chipset Family PCI Express Root Port [1458:5001]
Capabilities: [a0] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
Family PCI Express Root Port #3 [8086:8c14] (rev d5) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
 

Processed: notfound 884569 in 4.9.51-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 884569 4.9.51-1
Bug #884569 {Done: Ryan Thoryk } [linux-image-4.9.0-4-amd64] 
Unknown Symbol error when loading Tun driver
No longer marked as found in versions linux/4.9.51-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 xen-hypervisor-4.8-amd64
Bug #880554 [linux-image-4.9.0-4-amd64] xen domu freezes with kernel 
linux-image-4.9.0-4-amd64
Bug reassigned from package 'linux-image-4.9.0-4-amd64' to 
'xen-hypervisor-4.8-amd64'.
No longer marked as found in versions linux/4.9.51-1.
Ignoring request to alter fixed versions of bug #880554 to the same values 
previously set

-- 
880554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Yves-Alexis Perez]

control: reassign -1 xen-hypervisor-4.8-amd64

On Sat, 2018-01-06 at 15:23 +0100, Valentin Vidic wrote:
> On Sat, Jan 06, 2018 at 03:08:26PM +0100, Yves-Alexis Perez wrote:
> > According to that link, the fix seems to be configuration rather than
> > code.
> > Does this mean this bug against the kernel should be closed?
> 
> Yes, the problem seems to be in the Xen hypervisor and not the Linux
> kernel itself.  The default value for the gnttab_max_frames parameter
> needs to be increased to avoid domU disk IO hangs, for example:
> 
>   GRUB_CMDLINE_XEN="dom0_mem=10240M gnttab_max_frames=256"
> 
> So either close the bug or reassign it to xen-hypervisor package so
> they can increase the default value for this parameter in the
> hypervisor code.
> 
Ok, I'll reassign and let the Xen maintainers handle that (maybe in a stable
update).

@Xen maintainers: see the complete bug log for more information, but basically
it seems that a domu freezes happens with the “new” multi-queue xen blk
driver, and the fix is to increase a configuration value. Valentin suggests
adding that to the default.

Regards,
-- 
Yves-Alexis

signature.asc
Description: This is a digitally signed message part

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Valentin Vidic]

On Sat, Jan 06, 2018 at 03:08:26PM +0100, Yves-Alexis Perez wrote:
> According to that link, the fix seems to be configuration rather than code.
> Does this mean this bug against the kernel should be closed?

Yes, the problem seems to be in the Xen hypervisor and not the Linux
kernel itself.  The default value for the gnttab_max_frames parameter
needs to be increased to avoid domU disk IO hangs, for example:

  GRUB_CMDLINE_XEN="dom0_mem=10240M gnttab_max_frames=256"

So either close the bug or reassign it to xen-hypervisor package so
they can increase the default value for this parameter in the
hypervisor code.

-- 
Valentin

Bug#886474: linux-headers-4.14.0-3-amd64: missing dependency on libelf-dev

[Sebastian Ramacher]

Package: linux-headers-4.14.0-3-amd64
Version: 4.14.12-2
Severity: important

(I am not sure if this is the correct package, so please reassign as you see
fit.)

Since the upgrade to 4.14.12-2 the virtualbox and nvidia kernel modules
(#886470) fail to build with:
| make: Entering directory '/usr/src/linux-headers-4.14.0-3-amd64'
| /usr/src/linux-headers-4.14.0-3-common/Makefile:947: *** "Cannot generate ORC 
metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel".  Stop.

After installing libelf-dev as suggested, this part succeeds and the build
continues. Please add libelf-dev to the dependencies.

Cheers

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (650, 'unstable-debug'), (650, 'buildd-unstable'), (650, 
'unstable'), (601, 'testing'), (600, 'experimental-debug'), (600, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-headers-4.14.0-3-amd64 depends on:
ii  linux-compiler-gcc-7-x86   4.14.12-2
ii  linux-headers-4.14.0-3-common  4.14.12-2
ii  linux-kbuild-4.14  4.14.12-2

linux-headers-4.14.0-3-amd64 recommends no packages.

linux-headers-4.14.0-3-amd64 suggests no packages.

-- no debconf information

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Yves-Alexis Perez]

On Fri, 2017-11-17 at 07:39 +0100, Valentin Vidic wrote:
> Hi,
> 
> The problem seems to be caused by the new multi-queue xen blk driver
> and I was advised by the Xen devs to increase the gnttab_max_frames=256
> parameter for the hypervisor.  This has solved the blocking issue
> for me and it has been running without problems for a few months now.

I'm not really fluent in Xen, but does this relate to the kernel in dom0 or
one of the domU then? 
> 
> I/O to LUNs hang / stall under high load when using xen-blkfront
> https://www.novell.com/support/kb/doc.php?id=7018590

According to that link, the fix seems to be configuration rather than code.
Does this mean this bug against the kernel should be closed?

Regards,
-- 
Yves-Alexis

signature.asc
Description: This is a digitally signed message part

linux_4.9.65-3+deb9u2~bpo8+1_amd64.changes ACCEPTED into jessie-backports->backports-policy, jessie-backports

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 05 Jan 2017 10:58:41 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-0.bpo.5 linux-doc-4.9 
linux-manual-4.9 linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev 
linux-perf-4.9 libusbip-dev usbip hyperv-daemons 
linux-headers-4.9.0-0.bpo.5-common linux-headers-4.9.0-0.bpo.5-common-rt 
linux-libc-dev linux-headers-4.9.0-0.bpo.5-all 
linux-headers-4.9.0-0.bpo.5-all-alpha 
kernel-image-4.9.0-0.bpo.5-alpha-generic-di 
nic-modules-4.9.0-0.bpo.5-alpha-generic-di 
nic-wireless-modules-4.9.0-0.bpo.5-alpha-generic-di 
nic-shared-modules-4.9.0-0.bpo.5-alpha-generic-di 
serial-modules-4.9.0-0.bpo.5-alpha-generic-di 
usb-serial-modules-4.9.0-0.bpo.5-alpha-generic-di 
ppp-modules-4.9.0-0.bpo.5-alpha-generic-di 
pata-modules-4.9.0-0.bpo.5-alpha-generic-di 
cdrom-core-modules-4.9.0-0.bpo.5-alpha-generic-di 
scsi-core-modules-4.9.0-0.bpo.5-alpha-generic-di 
scsi-modules-4.9.0-0.bpo.5-alpha-generic-di 
loop-modules-4.9.0-0.bpo.5-alpha-generic-di 
btrfs-modules-4.9.0-0.bpo.5-alpha-generic-di
 ext4-modules-4.9.0-0.bpo.5-alpha-generic-di 
isofs-modules-4.9.0-0.bpo.5-alpha-generic-di 
jfs-modules-4.9.0-0.bpo.5-alpha-generic-di 
xfs-modules-4.9.0-0.bpo.5-alpha-generic-di 
fat-modules-4.9.0-0.bpo.5-alpha-generic-di 
md-modules-4.9.0-0.bpo.5-alpha-generic-di 
multipath-modules-4.9.0-0.bpo.5-alpha-generic-di 
usb-modules-4.9.0-0.bpo.5-alpha-generic-di 
usb-storage-modules-4.9.0-0.bpo.5-alpha-generic-di 
fb-modules-4.9.0-0.bpo.5-alpha-generic-di 
input-modules-4.9.0-0.bpo.5-alpha-generic-di 
event-modules-4.9.0-0.bpo.5-alpha-generic-di 
mouse-modules-4.9.0-0.bpo.5-alpha-generic-di 
nic-pcmcia-modules-4.9.0-0.bpo.5-alpha-generic-di 
pcmcia-modules-4.9.0-0.bpo.5-alpha-generic-di 
nic-usb-modules-4.9.0-0.bpo.5-alpha-generic-di 
sata-modules-4.9.0-0.bpo.5-alpha-generic-di 
crc-modules-4.9.0-0.bpo.5-alpha-generic-di 
crypto-modules-4.9.0-0.bpo.5-alpha-generic-di 
crypto-dm-modules-4.9.0-0.bpo.5-alpha-generic-di 
ata-modules-4.9.0-0.bpo.5-alpha-generic-di
 nbd-modules-4.9.0-0.bpo.5-alpha-generic-di 
squashfs-modules-4.9.0-0.bpo.5-alpha-generic-di 
virtio-modules-4.9.0-0.bpo.5-alpha-generic-di 
zlib-modules-4.9.0-0.bpo.5-alpha-generic-di 
fuse-modules-4.9.0-0.bpo.5-alpha-generic-di 
srm-modules-4.9.0-0.bpo.5-alpha-generic-di 
linux-image-4.9.0-0.bpo.5-alpha-generic 
linux-headers-4.9.0-0.bpo.5-alpha-generic linux-image-4.9.0-0.bpo.5-alpha-smp 
linux-headers-4.9.0-0.bpo.5-alpha-smp linux-headers-4.9.0-0.bpo.5-all-amd64 
kernel-image-4.9.0-0.bpo.5-amd64-di nic-modules-4.9.0-0.bpo.5-amd64-di 
nic-wireless-modules-4.9.0-0.bpo.5-amd64-di 
nic-shared-modules-4.9.0-0.bpo.5-amd64-di serial-modules-4.9.0-0.bpo.5-amd64-di 
usb-serial-modules-4.9.0-0.bpo.5-amd64-di ppp-modules-4.9.0-0.bpo.5-amd64-di 
pata-modules-4.9.0-0.bpo.5-amd64-di cdrom-core-modules-4.9.0-0.bpo.5-amd64-di 
firewire-core-modules-4.9.0-0.bpo.5-amd64-di 
scsi-core-modules-4.9.0-0.bpo.5-amd64-di scsi-modules-4.9.0-0.bpo.5-amd64-di 
loop-modules-4.9.0-0.bpo.5-amd64-di
 btrfs-modules-4.9.0-0.bpo.5-amd64-di ext4-modules-4.9.0-0.bpo.5-amd64-di 
isofs-modules-4.9.0-0.bpo.5-amd64-di jfs-modules-4.9.0-0.bpo.5-amd64-di 
ntfs-modules-4.9.0-0.bpo.5-amd64-di xfs-modules-4.9.0-0.bpo.5-amd64-di 
fat-modules-4.9.0-0.bpo.5-amd64-di md-modules-4.9.0-0.bpo.5-amd64-di 
multipath-modules-4.9.0-0.bpo.5-amd64-di usb-modules-4.9.0-0.bpo.5-amd64-di 
usb-storage-modules-4.9.0-0.bpo.5-amd64-di 
pcmcia-storage-modules-4.9.0-0.bpo.5-amd64-di fb-modules-4.9.0-0.bpo.5-amd64-di 
input-modules-4.9.0-0.bpo.5-amd64-di event-modules-4.9.0-0.bpo.5-amd64-di 
mouse-modules-4.9.0-0.bpo.5-amd64-di nic-pcmcia-modules-4.9.0-0.bpo.5-amd64-di 
pcmcia-modules-4.9.0-0.bpo.5-amd64-di nic-usb-modules-4.9.0-0.bpo.5-amd64-di 
sata-modules-4.9.0-0.bpo.5-amd64-di acpi-modules-4.9.0-0.bpo.5-amd64-di 
i2c-modules-4.9.0-0.bpo.5-amd64-di crc-modules-4.9.0-0.bpo.5-amd64-di 
crypto-modules-4.9.0-0.bpo.5-amd64-di crypto-dm-modules-4.9.0-0.bpo.5-amd64-di 
efi-modules-4.9.0-0.bpo.5-amd64-di
 ata-modules-4.9.0-0.bpo.5-amd64-di mmc-core-modules-4.9.0-0.bpo.5-amd64-di 
mmc-modules-4.9.0-0.bpo.5-amd64-di nbd-modules-4.9.0-0.bpo.5-amd64-di 
squashfs-modules-4.9.0-0.bpo.5-amd64-di speakup-modules-4.9.0-0.bpo.5-amd64-di 
virtio-modules-4.9.0-0.bpo.5-amd64-di uinput-modules-4.9.0-0.bpo.5-amd64-di 
sound-modules-4.9.0-0.bpo.5-amd64-di hyperv-modules-4.9.0-0.bpo.5-amd64-di 
udf-modules-4.9.0-0.bpo.5-amd64-di fuse-modules-4.9.0-0.bpo.5-amd64-di 
linux-image-4.9.0-0.bpo.5-amd64 linux-headers-4.9.0-0.bpo.5-amd64 
linux-image-4.9.0-0.bpo.5-amd64-dbg linux-image-4.9.0-0.bpo.5-rt-amd64 
linux-headers-4.9.0-0.bpo.5-rt-amd64 linux-image-4.9.0-0.bpo.5-rt-amd64-dbg 
linux-headers-4.9.0-0.bpo.5-all-arm64 kernel-image-4.9.0-0.bpo.5-arm64-di 
nic-modules-4.9.0-0.bpo.5-arm64-di nic-wireless-modules-4.9.0-0.bpo.5-arm64-di 
nic-shared-modules-4.9.0-0.bpo.5-arm64-di ppp-modules-4.9.0-0.bpo.5-arm64-di 
cdrom-core-modules-4.9.0-0.bpo.5-arm64-di 

Processed: found 886366 in 4.14.12-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 886366 4.14.12-1
Bug #886366 {Done: Salvatore Bonaccorso } [src:linux] 
linux-headers-4.15.0-rc5-amd64: missing tools/objtool in /lib/modules/foo/build 
breaks DKMS modules builds
Ignoring request to alter found versions of bug #886366 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
886366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

linux_4.14.12-2_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 06 Jan 2018 09:08:42 +0100
Source: linux
Binary: linux-source-4.14 linux-support-4.14.0-3 linux-doc-4.14 
linux-kbuild-4.14 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.14 
usbip hyperv-daemons lockdep liblockdep4.14 liblockdep-dev 
linux-headers-4.14.0-3-common linux-headers-4.14.0-3-common-rt linux-libc-dev 
linux-headers-4.14.0-3-all linux-headers-4.14.0-3-all-alpha 
kernel-image-4.14.0-3-alpha-generic-di nic-modules-4.14.0-3-alpha-generic-di 
nic-wireless-modules-4.14.0-3-alpha-generic-di 
nic-shared-modules-4.14.0-3-alpha-generic-di 
serial-modules-4.14.0-3-alpha-generic-di 
usb-serial-modules-4.14.0-3-alpha-generic-di 
ppp-modules-4.14.0-3-alpha-generic-di pata-modules-4.14.0-3-alpha-generic-di 
cdrom-core-modules-4.14.0-3-alpha-generic-di 
scsi-core-modules-4.14.0-3-alpha-generic-di 
scsi-modules-4.14.0-3-alpha-generic-di loop-modules-4.14.0-3-alpha-generic-di 
btrfs-modules-4.14.0-3-alpha-generic-di ext4-modules-4.14.0-3-alpha-generic-di 
isofs-modules-4.14.0-3-alpha-generic-di
 jfs-modules-4.14.0-3-alpha-generic-di xfs-modules-4.14.0-3-alpha-generic-di 
fat-modules-4.14.0-3-alpha-generic-di md-modules-4.14.0-3-alpha-generic-di 
multipath-modules-4.14.0-3-alpha-generic-di 
usb-modules-4.14.0-3-alpha-generic-di 
usb-storage-modules-4.14.0-3-alpha-generic-di 
input-modules-4.14.0-3-alpha-generic-di event-modules-4.14.0-3-alpha-generic-di 
mouse-modules-4.14.0-3-alpha-generic-di 
nic-pcmcia-modules-4.14.0-3-alpha-generic-di 
pcmcia-modules-4.14.0-3-alpha-generic-di 
nic-usb-modules-4.14.0-3-alpha-generic-di 
sata-modules-4.14.0-3-alpha-generic-di i2c-modules-4.14.0-3-alpha-generic-di 
crc-modules-4.14.0-3-alpha-generic-di crypto-modules-4.14.0-3-alpha-generic-di 
crypto-dm-modules-4.14.0-3-alpha-generic-di 
ata-modules-4.14.0-3-alpha-generic-di nbd-modules-4.14.0-3-alpha-generic-di 
squashfs-modules-4.14.0-3-alpha-generic-di 
virtio-modules-4.14.0-3-alpha-generic-di zlib-modules-4.14.0-3-alpha-generic-di 
fuse-modules-4.14.0-3-alpha-generic-di
 srm-modules-4.14.0-3-alpha-generic-di linux-image-4.14.0-3-alpha-generic 
linux-headers-4.14.0-3-alpha-generic linux-image-4.14.0-3-alpha-generic-dbg 
linux-image-4.14.0-3-alpha-smp linux-headers-4.14.0-3-alpha-smp 
linux-image-4.14.0-3-alpha-smp-dbg linux-headers-4.14.0-3-all-amd64 
kernel-image-4.14.0-3-amd64-di nic-modules-4.14.0-3-amd64-di 
nic-wireless-modules-4.14.0-3-amd64-di nic-shared-modules-4.14.0-3-amd64-di 
serial-modules-4.14.0-3-amd64-di usb-serial-modules-4.14.0-3-amd64-di 
ppp-modules-4.14.0-3-amd64-di pata-modules-4.14.0-3-amd64-di 
cdrom-core-modules-4.14.0-3-amd64-di firewire-core-modules-4.14.0-3-amd64-di 
scsi-core-modules-4.14.0-3-amd64-di scsi-modules-4.14.0-3-amd64-di 
loop-modules-4.14.0-3-amd64-di btrfs-modules-4.14.0-3-amd64-di 
ext4-modules-4.14.0-3-amd64-di isofs-modules-4.14.0-3-amd64-di 
jfs-modules-4.14.0-3-amd64-di ntfs-modules-4.14.0-3-amd64-di 
xfs-modules-4.14.0-3-amd64-di fat-modules-4.14.0-3-amd64-di 
md-modules-4.14.0-3-amd64-di
 multipath-modules-4.14.0-3-amd64-di usb-modules-4.14.0-3-amd64-di 
usb-storage-modules-4.14.0-3-amd64-di pcmcia-storage-modules-4.14.0-3-amd64-di 
fb-modules-4.14.0-3-amd64-di input-modules-4.14.0-3-amd64-di 
event-modules-4.14.0-3-amd64-di mouse-modules-4.14.0-3-amd64-di 
nic-pcmcia-modules-4.14.0-3-amd64-di pcmcia-modules-4.14.0-3-amd64-di 
nic-usb-modules-4.14.0-3-amd64-di sata-modules-4.14.0-3-amd64-di 
acpi-modules-4.14.0-3-amd64-di i2c-modules-4.14.0-3-amd64-di 
crc-modules-4.14.0-3-amd64-di crypto-modules-4.14.0-3-amd64-di 
crypto-dm-modules-4.14.0-3-amd64-di efi-modules-4.14.0-3-amd64-di 
ata-modules-4.14.0-3-amd64-di mmc-core-modules-4.14.0-3-amd64-di 
mmc-modules-4.14.0-3-amd64-di nbd-modules-4.14.0-3-amd64-di 
squashfs-modules-4.14.0-3-amd64-di speakup-modules-4.14.0-3-amd64-di 
virtio-modules-4.14.0-3-amd64-di uinput-modules-4.14.0-3-amd64-di 
sound-modules-4.14.0-3-amd64-di hyperv-modules-4.14.0-3-amd64-di 
udf-modules-4.14.0-3-amd64-di fuse-modules-4.14.0-3-amd64-di
 linux-image-4.14.0-3-amd64 linux-headers-4.14.0-3-amd64 
linux-image-4.14.0-3-amd64-dbg linux-image-4.14.0-3-rt-amd64 
linux-headers-4.14.0-3-rt-amd64 linux-image-4.14.0-3-rt-amd64-dbg 
linux-headers-4.14.0-3-all-arm64 kernel-image-4.14.0-3-arm64-di 
nic-modules-4.14.0-3-arm64-di nic-wireless-modules-4.14.0-3-arm64-di 
nic-shared-modules-4.14.0-3-arm64-di ppp-modules-4.14.0-3-arm64-di 
cdrom-core-modules-4.14.0-3-arm64-di scsi-core-modules-4.14.0-3-arm64-di 
scsi-modules-4.14.0-3-arm64-di loop-modules-4.14.0-3-arm64-di 
btrfs-modules-4.14.0-3-arm64-di ext4-modules-4.14.0-3-arm64-di 
isofs-modules-4.14.0-3-arm64-di jfs-modules-4.14.0-3-arm64-di 
xfs-modules-4.14.0-3-arm64-di fat-modules-4.14.0-3-arm64-di 
md-modules-4.14.0-3-arm64-di multipath-modules-4.14.0-3-arm64-di 
usb-modules-4.14.0-3-arm64-di usb-storage-modules-4.14.0-3-arm64-di 
fb-modules-4.14.0-3-arm64-di input-modules-4.14.0-3-arm64-di 

linux-latest_89_allonly.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 06 Jan 2018 00:20:59 +0100
Source: linux-latest
Binary: linux-source linux-doc linux-perf linux-image-alpha-generic 
linux-headers-alpha-generic linux-image-alpha-generic-dbg linux-image-alpha-smp 
linux-headers-alpha-smp linux-image-alpha-smp-dbg linux-image-amd64 
linux-headers-amd64 linux-image-amd64-dbg linux-image-rt-amd64 
linux-headers-rt-amd64 linux-image-rt-amd64-dbg linux-image-arm64 
linux-headers-arm64 linux-image-arm64-dbg linux-image-marvell 
linux-headers-marvell linux-image-marvell-dbg linux-image-armmp 
linux-headers-armmp linux-image-armmp-dbg linux-image-armmp-lpae 
linux-headers-armmp-lpae linux-image-armmp-lpae-dbg linux-image-parisc 
linux-headers-parisc linux-image-parisc-dbg linux-image-parisc64-smp 
linux-headers-parisc64-smp linux-image-parisc64-smp-dbg linux-image-686 
linux-headers-686 linux-image-686-dbg linux-image-686-pae linux-headers-686-pae 
linux-image-686-pae-dbg linux-image-rt-686-pae linux-headers-rt-686-pae 
linux-image-rt-686-pae-dbg linux-image-m68k linux-headers-m68k 
linux-image-m68k-dbg
 linux-image-4kc-malta linux-headers-4kc-malta linux-image-4kc-malta-dbg 
linux-image-5kc-malta linux-headers-5kc-malta linux-image-5kc-malta-dbg 
linux-image-octeon linux-headers-octeon linux-image-octeon-dbg 
linux-image-loongson-3 linux-headers-loongson-3 linux-image-loongson-3-dbg 
linux-image-mips64r6 linux-headers-mips64r6 linux-image-mips64r6-dbg 
linux-image-mips64r6el linux-headers-mips64r6el linux-image-mips64r6el-dbg 
linux-image-mips32r6 linux-headers-mips32r6 linux-image-mips32r6-dbg 
linux-image-mips32r6el linux-headers-mips32r6el linux-image-mips32r6el-dbg 
linux-image-powerpc linux-headers-powerpc linux-image-powerpc-dbg 
linux-image-powerpc-smp linux-headers-powerpc-smp linux-image-powerpc-smp-dbg 
linux-image-powerpc64 linux-headers-powerpc64 linux-image-powerpc64-dbg 
linux-image-powerpcspe linux-headers-powerpcspe linux-image-powerpcspe-dbg 
linux-image-powerpc64le linux-headers-powerpc64le linux-image-powerpc64le-dbg 
linux-image-s390x linux-headers-s390x
 linux-image-s390x-dbg linux-image-sh7751r linux-headers-sh7751r 
linux-image-sh7751r-dbg linux-image-sh7785lcr linux-headers-sh7785lcr 
linux-image-sh7785lcr-dbg linux-image-sparc64 linux-headers-sparc64 
linux-image-sparc64-dbg linux-image-sparc64-smp linux-headers-sparc64-smp
 linux-image-sparc64-smp-dbg
Architecture: all source
Version: 89
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Description: 
 linux-doc  - Linux kernel specific documentation (meta-package)
 linux-headers-4kc-malta - Header files for Linux 4kc-malta configuration 
(meta-package)
 linux-headers-5kc-malta - Header files for Linux 5kc-malta configuration 
(meta-package)
 linux-headers-686 - Header files for Linux 686 configuration (meta-package)
 linux-headers-686-pae - Header files for Linux 686-pae configuration 
(meta-package)
 linux-headers-alpha-generic - Header files for Linux alpha-generic 
configuration (meta-package)
 linux-headers-alpha-smp - Header files for Linux alpha-smp configuration 
(meta-package)
 linux-headers-amd64 - Header files for Linux amd64 configuration (meta-package)
 linux-headers-arm64 - Header files for Linux arm64 configuration (meta-package)
 linux-headers-armmp - Header files for Linux armmp configuration (meta-package)
 linux-headers-armmp-lpae - Header files for Linux armmp-lpae configuration 
(meta-package)
 linux-headers-loongson-3 - Header files for Linux loongson-3 configuration 
(meta-package)
 linux-headers-m68k - Header files for Linux m68k configuration (meta-package)
 linux-headers-marvell - Header files for Linux marvell configuration 
(meta-package)
 linux-headers-mips32r6 - Header files for Linux mips32r6 configuration 
(meta-package)
 linux-headers-mips32r6el - Header files for Linux mips32r6el configuration 
(meta-package)
 linux-headers-mips64r6 - Header files for Linux mips64r6 configuration 
(meta-package)
 linux-headers-mips64r6el - Header files for Linux mips64r6el configuration 
(meta-package)
 linux-headers-octeon - Header files for Linux octeon configuration 
(meta-package)
 linux-headers-parisc - Header files for Linux parisc configuration 
(meta-package)
 linux-headers-parisc64-smp - Header files for Linux parisc64-smp configuration 
(meta-package)
 linux-headers-powerpc - Header files for Linux powerpc configuration 
(meta-package)
 linux-headers-powerpc-smp - Header files for Linux powerpc-smp configuration 
(meta-package)
 linux-headers-powerpc64 - Header files for Linux powerpc64 configuration 
(meta-package)
 linux-headers-powerpc64le - Header files for Linux powerpc64le configuration 
(meta-package)
 linux-headers-powerpcspe - Header files for Linux powerpcspe configuration 
(meta-package)
 linux-headers-rt-686-pae - Header files for Linux rt-686-pae configuration 
(meta-package)
 

Bug#886366: marked as done (linux-headers-4.15.0-rc5-amd64: missing tools/objtool in /lib/modules/foo/build breaks DKMS modules builds)

[Debian Bug Tracking System]

Your message dated Sat, 06 Jan 2018 09:05:48 +
with message-id 
and subject line Bug#886366: fixed in linux 4.14.12-2
has caused the Debian Bug report #886366,
regarding linux-headers-4.15.0-rc5-amd64: missing tools/objtool in 
/lib/modules/foo/build breaks DKMS modules builds
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.)


-- 
886366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.15~rc5-1~exp1
Severity: important

Dear Maintainer,

The new tools/ directory is currently symlinked from linux-kbuild-4.15
into linux-headers-common-4.15.0-rc5 (directory: /usr/src/linux-
headers-4.15.0-rc5-common/tools ) but not into linux-headers-4.15.0-
rc5-amd64 like scripts/ is.

This means objtool is available under /lib/modules/4.15.0-rc5-
amd64/source but not under /lib/modules/4.15.0-rc5-amd64/build which
means kernel modules builds via DKMS fail with:

/bin/sh: 1: ./tools/objtool/objtool: not found

Manually adding the symlink fixes the problem.

If this is indeed the right thing to do, I guess the dh_link that was
added for the -common stanza in debian/rules.real in commit
392435021b7fbec should also be added for the _$(ARCH one):

--- a/debian/rules.real
+++ b/debian/rules.real
@@ -348,6 +348,7 @@ install-headers_$(ARCH)_$(FEATURESET)_$(FLAVOUR): 
$(STAMPS_DIR)/build_$(ARCH)_$(
@echo ' @:' >> $(DIR)/Makefile
 
dh_link /usr/lib/$(PACKAGE_NAME_KBUILD)/scripts $(BASE_DIR)/scripts
+   dh_link /usr/lib/$(PACKAGE_NAME_KBUILD)/tools $(BASE_DIR)/tools
 
mkdir -p $(PACKAGE_DIR)/lib/modules/$(REAL_VERSION)
ln -s /usr/src/$(PACKAGE_NAME) 
$(PACKAGE_DIR)/lib/modules/$(REAL_VERSION)/build


Kind regards,
Luca Boccassi

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.14.12-2

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 886...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 06 Jan 2018 09:08:42 +0100
Source: linux
Binary: linux-source-4.14 linux-support-4.14.0-3 linux-doc-4.14 
linux-kbuild-4.14 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.14 
usbip hyperv-daemons lockdep liblockdep4.14 liblockdep-dev 
linux-headers-4.14.0-3-common linux-headers-4.14.0-3-common-rt linux-libc-dev 
linux-headers-4.14.0-3-all linux-headers-4.14.0-3-all-alpha 
kernel-image-4.14.0-3-alpha-generic-di nic-modules-4.14.0-3-alpha-generic-di 
nic-wireless-modules-4.14.0-3-alpha-generic-di 
nic-shared-modules-4.14.0-3-alpha-generic-di 
serial-modules-4.14.0-3-alpha-generic-di 
usb-serial-modules-4.14.0-3-alpha-generic-di 
ppp-modules-4.14.0-3-alpha-generic-di pata-modules-4.14.0-3-alpha-generic-di 
cdrom-core-modules-4.14.0-3-alpha-generic-di 
scsi-core-modules-4.14.0-3-alpha-generic-di 
scsi-modules-4.14.0-3-alpha-generic-di loop-modules-4.14.0-3-alpha-generic-di 
btrfs-modules-4.14.0-3-alpha-generic-di ext4-modules-4.14.0-3-alpha-generic-di 
isofs-modules-4.14.0-3-alpha-generic-di
 jfs-modules-4.14.0-3-alpha-generic-di xfs-modules-4.14.0-3-alpha-generic-di 
fat-modules-4.14.0-3-alpha-generic-di md-modules-4.14.0-3-alpha-generic-di 
multipath-modules-4.14.0-3-alpha-generic-di 
usb-modules-4.14.0-3-alpha-generic-di 
usb-storage-modules-4.14.0-3-alpha-generic-di 
input-modules-4.14.0-3-alpha-generic-di event-modules-4.14.0-3-alpha-generic-di 
mouse-modules-4.14.0-3-alpha-generic-di 
nic-pcmcia-modules-4.14.0-3-alpha-generic-di 
pcmcia-modules-4.14.0-3-alpha-generic-di 
nic-usb-modules-4.14.0-3-alpha-generic-di 
sata-modules-4.14.0-3-alpha-generic-di i2c-modules-4.14.0-3-alpha-generic-di 
crc-modules-4.14.0-3-alpha-generic-di crypto-modules-4.14.0-3-alpha-generic-di 
crypto-dm-modules-4.14.0-3-alpha-generic-di 
ata-modules-4.14.0-3-alpha-generic-di nbd-modules-4.14.0-3-alpha-generic-di 

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 886366 linux/4.14.12-1
Bug #886366 [src:linux] linux-headers-4.15.0-rc5-amd64: missing tools/objtool 
in /lib/modules/foo/build breaks DKMS modules builds
Marked as found in versions linux/4.14.12-1.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
886366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processing of linux-latest_89_allonly.changes

[Debian FTP Masters]

linux-latest_89_allonly.changes uploaded successfully to localhost
along with the files:
  linux-latest_89.dsc
  linux-latest_89.tar.xz
  linux-doc_4.14+89_all.deb
  linux-perf_4.14+89_all.deb
  linux-source_4.14+89_all.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Processing of linux_4.14.12-2_source.changes

[Debian FTP Masters]

linux_4.14.12-2_source.changes uploaded successfully to localhost
along with the files:
  linux_4.14.12-2.dsc
  linux_4.14.12-2.debian.tar.xz
  linux_4.14.12-2_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#886366: [src:linux]

[Antonio Russo]

Control: found linux/4.14.12-1

+1 for this also shows up in 4.14. It blocks building spl, and therefore
blocks migration for zfs users.

This also looks to have been reported a few months ago:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833500