Processed: bug 918103 is forwarded to https://marc.info/?l=linux-netdev=154635529809577=2

[Debian Bug Tracking System]

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

> forwarded 918103 https://marc.info/?l=linux-netdev=154635529809577=2
Bug #918103 [src:linux] ipv6: Consider sk_bound_dev_if when binding a socket to 
an address
Changed Bug forwarded-to-address to 
'https://marc.info/?l=linux-netdev=154635529809577=2' from 
'https://marc.info/?l=linux-netdev'.
> thanks
Stopping processing here.

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

Processed: bug 918103 is forwarded to https://marc.info/?l=linux-netdev

[Debian Bug Tracking System]

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

> forwarded 918103 https://marc.info/?l=linux-netdev
Bug #918103 [src:linux] ipv6: Consider sk_bound_dev_if when binding a socket to 
an address
Set Bug forwarded-to-address to 'https://marc.info/?l=linux-netdev'.
> thanks
Stopping processing here.

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

Bug#918097: initramfs-tools-core: Error while building DKMS modules when kernel has all its modules built in

[Mikhail Morfikov]

Package: initramfs-tools-core
Version: 0.132
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

I wanted to build a custom kernel using the linux-source package from the
Debian repository. I haven't changed much, the only thing I wanted to do is to
build in all the modules my machine needs and remove all the others. Such
kernels don't have modules in *.ko files and it looks like mkinitramfs has some
issues with that.

Basically, the problem is in the /usr/share/initramfs-tools/hook-functions
script file with the following line:

find "${DESTDIR}/lib/modules/${version}/kernel" -name '*.ko*'

Since none of the modules listed above in the file were copied to the temp
destination folder, the kernel/ subdir doesn't exist and hence the above
command returns error. The initramfs image is building fine, but DKMS packages
return something similar to the following:

# dpkg --configure -a
Setting up sysdig-dkms (0.24.1-1) ...
Removing old sysdig-0.24.1 DKMS files...

-  Uninstall Beginning 
Module:  sysdig
Version: 0.24.1
Kernel:  4.19.13-amd64-morficzny (x86_64)
- -

Status: Before uninstall, this module version was ACTIVE on this kernel.

sysdig-probe.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.19.13-amd64-morficzny/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod...

DKMS: uninstall completed.

- --
Deleting module version: 0.24.1
completely from the DKMS tree.
- --
Done.
Loading new sysdig-0.24.1 DKMS files...
Building for 4.19.13-amd64-morficzny 4.20.0-amd64-morficzny
Building initial module for 4.19.13-amd64-morficzny
Error! Bad return status for module build on kernel: 4.19.13-amd64-morficzny
(x86_64)
Consult /var/lib/dkms/sysdig/0.24.1/build/make.log for more information.
dpkg: error processing package sysdig-dkms (--configure):
 installed sysdig-dkms package post-installation script subprocess returned
error exit status 10
Errors were encountered while processing:
 sysdig-dkms

I changed my kernel config a little bit:

# egrep \=m /boot/config-4.19.13-amd64-morficzny
CONFIG_BTRFS_FS=m
CONFIG_XOR_BLOCKS=m
CONFIG_RAID6_PQ=m

And after rebuilding the kernel when I want to created the initramfs image I
can see the the kernel/ subdir:

# tree
/var/tmp/mkinitramfs_p7rDVj/usr/lib/modules/4.19.13-amd64-morficzny/kernel/
/var/tmp/mkinitramfs_p7rDVj/usr/lib/modules/4.19.13-amd64-morficzny/kernel/
├── crypto
│   └── xor.ko
├── fs
│   └── btrfs
│   └── btrfs.ko
└── lib
└── raid6
└── raid6_pq.ko

5 directories, 3 files

Will this qualify as bug or should I fix this in some way myself since it's not
the Debian distribution's kernel?



- -- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (130, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages initramfs-tools-core depends on:
ii  coreutils8.30-1
ii  cpio 2.12+dfsg-6
ii  e2fsprogs1.44.5-1
ii  klibc-utils  2.0.4-14
ii  kmod 25-2
ii  udev 240-2

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.27.2-3

Versions of packages initramfs-tools-core suggests:
ii  bash-completion  1:2.8-5




-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE5JPPWm5C7TFDUMqpzQRoEHcbZSAFAlwt2AAACgkQzQRoEHcb
ZSDrjg//X6cMtoFjEw3BOAg+1EpKTQ1/yfJSAW611NgsgfvvPurncPx5X3XtQ0sH
/I47mXSB4ds3/KuGIJb96SXgOChBqvfdS/7ajirGL11Ou4Ujfmb9CC0sOpUe3uba
OKNdB+QiwHMDlfKdvDMk0LXN4i7fx9hCUukAkhE1s9xbqCk+veTmHpnv5BomIoX/
AqfdmeN2Y08MDdd5K8S/g1/4fVg9QUSE8+9dP9r1Bw7nqdp4EpSj7ZSKtifSayRb
k+AENOn0nMoXQP9zTYbzIv8k3LvB6+rTBf67ST1uMGGIljuf78VveJqMvJfBgS8P
8VNDdx8O5J2U2Dn9S4j4NOiKJLkQIBELyR+hTF4AQrPJ8BHquPvvCbUyVLL9SV4S
Wz8gylSP9uWwYlEjN/9vfFtMhZIiJ5Maloow4SKYgjw6+5w7BDtpp/f35Vji2+cc
9JKf+xTVuMRmMQn43NAj6a+JcUv6i9n9wy9C9HsC2qt6NnVdTx2+YGdx+vqwAz/0
QewOxkeuHgqLrRD4aUSkrZ4Z2vcfW+5ccXiej0+QsMyHt1gWgMU3DbZcNdpK/k2+
JioqBC2aLN37FfQzAhB/KDFwJ1XmJCqi1GKdk431Z/urtAFlPB/X08aDRUf/QfVq
wwD8hUwzLB3hSHqGDmKCuY0Z/y/uz1tW7B79tPgZIiIneX3loIY=
=G9Xp
-END PGP SIGNATURE-

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

[Ralf Jung]

Package: linux-image-4.18.0-0.bpo.3-amd64
Version: 4.18.20-2~bpo9+1
Severity: normal
Tags: upstream

Dear Maintainer,

I reported an upstream bug at 
 that got a patch 
submitted with .
It would be great to have this patch applied to the next Debian kernel update.

Kind regards,
Ralf

Bug#918097: initramfs-tools-core: Error while building DKMS modules when kernel has all its modules built in

[Mikhail Morfikov]

It looks like the DKMS error was because of my mistake and not the initramfs
one -- the ARCH=x86_64 env variable caused the issue, so just ignore the info 
about 
DKMS.



signature.asc
Description: OpenPGP digital signature

Processed: reassign 918103 to src:linux

[Debian Bug Tracking System]

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

> reassign 918103 src:linux 4.18.20-2
Bug #918103 [linux-image-4.18.0-0.bpo.3-amd64] ipv6: Consider sk_bound_dev_if 
when binding a socket to an address
Bug reassigned from package 'linux-image-4.18.0-0.bpo.3-amd64' to 'src:linux'.
No longer marked as found in versions linux/4.18.20-2~bpo9+1.
Ignoring request to alter fixed versions of bug #918103 to the same values 
previously set
Bug #918103 [src:linux] ipv6: Consider sk_bound_dev_if when binding a socket to 
an address
Marked as found in versions linux/4.18.20-2.
> thanks
Stopping processing here.

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

Processed: closing 914491

[Debian Bug Tracking System]

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

> close 914491 4.19.5-1~exp1
Bug #914491 [src:linux] linux-image-4.18.0-3-amd64: Please revert the STIBP 
patch from 4.18.20
Marked as fixed in versions linux/4.19.5-1~exp1.
Bug #914491 [src:linux] linux-image-4.18.0-3-amd64: Please revert the STIBP 
patch from 4.18.20
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#918188: linux: FTBFS on arm64

[Salvatore Bonaccorso]

Source: linux
Version: 4.9.144-1
Severity: serious
Justification: FTBFS

For tracking the issue:

4.9.144-1 FTBFS on arm64:

>   LD  vmlinux.o
>   MODPOST vmlinux.o
>   GEN .version
>   CHK include/generated/compile.h
>   UPD include/generated/compile.h
>   CC  init/version.o
>   LD  init/built-in.o
> ./drivers/firmware/efi/libstub/lib.a(arm64-stub.stub.o): In function 
> `handle_kernel_image':
> ./debian/build/build_arm64_none_arm64/./drivers/firmware/efi/libstub/arm64-stub.c:63:
>  undefined reference to `__efistub__GLOBAL_OFFSET_TABLE_'
> ld: ./drivers/firmware/efi/libstub/lib.a(arm64-stub.stub.o): relocation 
> R_AARCH64_ADR_PREL_PG_HI21 against external symbol 
> `__efistub__GLOBAL_OFFSET_TABLE_' can not be used when making a shared 
> object; recompile with -fPIC
> /<>/Makefile:1010: recipe for target 'vmlinux' failed
> make[5]: *** [vmlinux] Error 1
> Makefile:152: recipe for target 'sub-make' failed
> make[4]: *** [sub-make] Error 2
> Makefile:24: recipe for target '__sub-make' failed
> make[3]: *** [__sub-make] Error 2
> make[3]: Leaving directory 
> '/<>/debian/build/build_arm64_none_arm64'
> debian/rules.real:190: recipe for target 
> 'debian/stamps/build_arm64_none_arm64' failed
> make[2]: *** [debian/stamps/build_arm64_none_arm64] Error 2
> make[2]: Leaving directory '/<>'
> debian/rules.gen:400: recipe for target 'build-arch_arm64_none_arm64_real' 
> failed
> make[1]: *** [build-arch_arm64_none_arm64_real] Error 2
> make[1]: Leaving directory '/<>'
> debian/rules:41: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 2
> dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

https://buildd.debian.org/status/fetch.php?pkg=linux=arm64=4.9.144-1=1546572157=0

(different issue than #914556).

Regards,
Salvatore

Processed: reassign 918107 to src:linux

[Debian Bug Tracking System]

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

> reassign 918107 src:linux 4.19.12-1
Bug #918107 [linux-image-4.19.0-1-amd64] Random boot failure using VMware 
Paravirtual Adapter
Bug reassigned from package 'linux-image-4.19.0-1-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/4.19.12+1.
Ignoring request to alter fixed versions of bug #918107 to the same values 
previously set
Bug #918107 [src:linux] Random boot failure using VMware Paravirtual Adapter
Marked as found in versions linux/4.19.12-1.
> thanks
Stopping processing here.

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

Processed: reassign 918114 to src:linux

[Debian Bug Tracking System]

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

> reassign 918114 src:linux 4.18.20-2
Bug #918114 [linux-image-armmp] linux-image-armmp: please add 
CONFIG_SENSORS_LM75=m
Bug reassigned from package 'linux-image-armmp' to 'src:linux'.
No longer marked as found in versions linux-latest/100~bpo9+1.
Ignoring request to alter fixed versions of bug #918114 to the same values 
previously set
Bug #918114 [src:linux] linux-image-armmp: please add CONFIG_SENSORS_LM75=m
Marked as found in versions linux/4.18.20-2.
> thanks
Stopping processing here.

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

Bug#918036: linux: uptime after reboot wrong (kvm-clock related?)

[Salvatore Bonaccorso]

Hi Thorsten,

On Wed, Jan 02, 2019 at 05:39:39PM +0100, Salvatore Bonaccorso wrote:
> Hi Thorsten,
> 
> On Wed, Jan 02, 2019 at 04:08:23PM +, Thorsten Glaser wrote:
> > Package: src:linux
> > Version: 4.19.13-1
> > Severity: normal
> > 
> > I???ve just rebooted this VM and get:
> > 
> > root@ci-busyapps:~ # uptime
> >  16:06:57 up 58 days, 21:22,  1 user,  load average: 0.62, 0.98, 0.46
> > 
> > In syslog, I see this:
> > 
> > Jan  2 15:55:01 ci-busyapps CRON[3287]: (root) CMD (command -v debian-sa1 > 
> > /dev/null && debian-sa1 1 1)
> > Jan  2 15:56:11 ci-busyapps postfix/anvil[3005]: statistics: max connection 
> > rate 1/60s for (smtp:172.26.1.40) at Jan  2 15:52:51
> > Jan  2 15:56:11 ci-busyapps postfix/anvil[3005]: statistics: max connection 
> > count 1 for (smtp:172.26.1.40) at Jan  2 15:52:51
> > Jan  2 15:56:11 ci-busyapps postfix/anvil[3005]: statistics: max cache size 
> > 1 at Jan  2 15:52:51
> > Jan  2 15:57:20 ci-busyapps sensord: sensord stopped
> > Jan  2 15:58:05 ci-busyapps dhclient[1031]: DHCPREQUEST of 172.26.1.40 on 
> > eth0 to 172.26.100.2 port 67
> > Jan  2 15:58:05 ci-busyapps dhclient[1031]: DHCPACK of 172.26.1.40 from 
> > 172.26.100.2
> > Jan  2 15:58:05 ci-busyapps dhclient[1031]: bound to 172.26.1.40 -- renewal 
> > in 19447 seconds.
> > Jan  2 15:59:04 ci-busyapps shutdown[7314]: shutting down for system reboot
> > Jan  2 15:59:05 ci-busyapps init: Switching to runlevel: 6
> > Jan  2 15:59:09 ci-busyapps jenkins: jenkins: client (pid 1579) exited with 
> > 143 status 
> > Jan  2 15:59:10 ci-busyapps ntpd[1608]: ntp engine exiting
> > Jan  2 15:59:10 ci-busyapps ntpd[1607]: Terminating
> > Jan  2 15:59:10 ci-busyapps postfix/master[22032]: terminating on signal 15
> > Jan  2 15:59:18 ci-busyapps syslogd: exiting on signal 15
> > Jan  2 16:00:47 ci-busyapps syslogd (GNU inetutils 1.9.4): restart
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] Linux version 
> > 4.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 8.2.0 (Debian 
> > 8.2.0-13)) #1 SMP Debian 4.19.13-1 (2018-12-30)
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] Command line: 
> > BOOT_IMAGE=/boot/vmlinuz-4.19.0-1-amd64 
> > root=/dev/mapper/vg--ci--busyapps-lv--root ro net.ifnames=0 kaslr nomodeset
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] x86/fpu: x87 FPU will 
> > use FXSAVE
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] BIOS-provided physical 
> > RAM map:
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] BIOS-e820: [mem 
> > 0x-0x0009fbff] usable
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] BIOS-e820: [mem 
> > 0x0009fc00-0x0009] reserved
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] BIOS-e820: [mem 
> > 0x000f-0x000f] reserved
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] BIOS-e820: [mem 
> > 0x0010-0xdfffdfff] usable
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] BIOS-e820: [mem 
> > 0xdfffe000-0xdfff] reserved
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] BIOS-e820: [mem 
> > 0xfeffc000-0xfeff] reserved
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] BIOS-e820: [mem 
> > 0xfffc-0x] reserved
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] BIOS-e820: [mem 
> > 0x0001-0x00021fff] usable
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] NX (Execute Disable) 
> > protection: active
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] SMBIOS 2.4 present.
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] DMI: Bochs Bochs, BIOS 
> > Bochs 01/01/2011
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] Hypervisor detected: KVM
> > Jan  2 16:00:47 ci-busyapps vmunix: [0.00] kvm-clock: Using msrs 
> > 4b564d01 and 4b564d00
> > Jan  2 16:00:47 ci-busyapps vmunix: [5087690.332663] kvm-clock: cpu 0, msr 
> > 3ffd7001, primary cpu clock
> > Jan  2 16:00:47 ci-busyapps vmunix: [5087690.332663] clocksource: 
> > kvm-clock: mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 
> > 881590591483 ns
> > Jan  2 16:00:47 ci-busyapps vmunix: [5087690.332665] tsc: Detected 3064.488 
> > MHz processor
> 
> As a datapoint: This sounds familiar in the sense that it was reported
> earlier https://lore.kernel.org/lkml/20181106054212.GA31768@nautica/ .

There was now a followup on this, and if you can I think it's best if
you can followup there.

https://lore.kernel.org/lkml/ca+ck2bc70pnl0wimb0xt99j4nnfi8w3zuuhgak-jspuop9j...@mail.gmail.com/

Regards,
Salvatore

p.s.: my earlier reply to you seem to have been rejected and never
  reached you, hope this one does now.

Bug#918036: [PATCH v15 23/26] sched: early boot clock (was Re: Bug#918036: linux: uptime after reboot wrong (kvm-clock related?))

[Thorsten Glaser]

Hi Salvatore,

>p.s.: my earlier reply to you seem to have been rejected and never
>  reached you, hope this one does now.

if you sent from Googlemail, it may reach me in the next weeks or
never *shrug* they don’t play nice with greylisting. The -submitter
or @d.o works, though. I’m following up from my $dayjob address as
the issue occurred there (which is also Googlemail, unfortunately).

>There was now a followup on this, and if you can I think it's best if
>you can followup there.
>
>https://lore.kernel.org/lkml/ca+ck2bc70pnl0wimb0xt99j4nnfi8w3zuuhgak-jspuop9j...@mail.gmail.com/

OK, doing now:


Pavel Tatashin wrote:

>Could you please send the config file and qemu arguments that were
>used to reproduce this problem.

This is from a libvirt-managed system. The arguments as shown by
“ps axwww” are:

qemu-system-x86_64 -enable-kvm -name ci-busyapps -S -machine 
pc-1.1,accel=kvm,usb=off -m 8192 -realtime mlock=off -smp 
2,sockets=2,cores=1,threads=1 -uuid 09536d92-dd73-8993-78fb-e0c885acf763 
-no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/ci-busyapps.monitor,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive 
file=/dev/vms/ci-busyapps,format=raw,if=none,id=drive-virtio-disk0,cache=none,aio=native
 -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:05:6e:fd,bus=pci.0,addr=0x3 
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-device usb-tablet,id=input0 -vnc 127.0.0.1:0 -device 
cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on

I’ve attached the kernel configuration; this is a stock Debian
unstable/amd64 system, just upgraded. After upgrading the guest,
I merely issued a “reboot” in the guest and did not stop/start
qemu.

The host is Debian jessie/amd64 (Linux 3.16.0-7-amd64 / 3.16.59-1)
in case that matters.

Thanks,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Processed: affects 918188

[Debian Bug Tracking System]

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

> affects 918188 + release.debian.org
Bug #918188 [src:linux] linux: FTBFS on arm64
Added indication that 918188 affects release.debian.org
> thanks
Stopping processing here.

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

Bug#918114: linux-image-armmp: please add CONFIG_SENSORS_LM75=m

[Reco]

Package: linux-image-armmp
Version: 4.18+100~bpo9+1
Severity: wishlist

Dear Maintainer,

Please enable building lm75.ko as a module, there's a hardware (Helios4 NAS), 
which runs Debian kernel and userland without a hitch, but lm75 is required for 
monitoring CPU temperature.

Sincerely yours, Reco


-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 4.18.0-0.bpo.3-armmp (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (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-image-armmp depends on:
ii  linux-image-4.18.0-0.bpo.3-armmp  4.18.20-2~bpo9+1

linux-image-armmp recommends no packages.

linux-image-armmp suggests no packages.

-- no debconf information

Processed: [bts-link] source package initramfs-tools

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package initramfs-tools
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #917524 (http://bugs.debian.org/917524)
> # Bug title: initramfs-tools: Upgrade from initramfs-tools package fails
> #  * https://github.com/systemd/systemd/issues/11255
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 917524 + fixed-upstream
Bug #917524 [initramfs-tools-core] initramfs-tools: Upgrade from 
initramfs-tools package fails
Added tag(s) fixed-upstream.
> usertags 917524 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: bug 917524 is not forwarded, tagging 917524

[Debian Bug Tracking System]

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

> notforwarded 917524
Bug #917524 [initramfs-tools-core] initramfs-tools: Upgrade from 
initramfs-tools package fails
Unset Bug forwarded-to-address
> tags 917524 - fixed-upstream
Bug #917524 [initramfs-tools-core] initramfs-tools: Upgrade from 
initramfs-tools package fails
Removed tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#918113: linux-image-4.19.0-1-amd64: Fails to initalize DisplayPort displays with rx560

[Mark Brown]

On Thu, Jan 03, 2019 at 01:49:49PM +, Mark Brown wrote:

> Even with only one monitor connected the system is unable to do anything
> useful with the display, it has trouble setting up a valid clock
> configuration though there is no oops:
> 
> Dec 29 17:57:14 debutante kernel: [3.561312] amdgpu :01:00.0: 
> firmware: direct-loading firmware amdgpu/polaris11_k_smc.bin
> Dec 29 17:57:14 debutante kernel: [3.622018] EXT4-fs (sdb1): mounted 
> filesystem with ordered data mode. Opts: errors=remount-ro
> Dec 29 18:14:17 debutante kernel: [3.482651] amdgpu: [powerplay] Failed 
> to retrieve minimum clocks.
> Dec 29 18:14:17 debutante kernel: [3.482652] amdgpu: [powerplay] Error in 
> phm_get_clock_info 

I've confirmed that this part of the issue is fixed with the 4.20
packages in experimental, the problems with a dual monitor setup oopsing
and generally failing to work that were the main focus of the report
remain.


signature.asc
Description: PGP signature

[bts-link] source package src:linux

[debian-bts-link]

#
# bts-link upstream status pull for source package src:linux
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #887045 (http://bugs.debian.org/887045)
# Bug title: iwlwifi: TX_STATUS_FAIL_DEST_PS at iwlwifi/mvm/tx.c:1363 using 
hostapd
#  * http://bugzilla.kernel.org/show_bug.cgi?id=199967
#  * remote status changed: (?) -> CLOSED
#  * remote resolution changed: (?) -> CODE-FIX
#  * closed upstream
tags 887045 + fixed-upstream
usertags 887045 + status-CLOSED resolution-CODE-FIX

thanks

[bts-link] source package initramfs-tools

[debian-bts-link]

#
# bts-link upstream status pull for source package initramfs-tools
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #917524 (http://bugs.debian.org/917524)
# Bug title: initramfs-tools: Upgrade from initramfs-tools package fails
#  * https://github.com/systemd/systemd/issues/11255
#  * remote status changed: (?) -> closed
#  * closed upstream
tags 917524 + fixed-upstream
usertags 917524 + status-closed

thanks

Processed: [bts-link] source package src:linux

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:linux
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #887045 (http://bugs.debian.org/887045)
> # Bug title: iwlwifi: TX_STATUS_FAIL_DEST_PS at iwlwifi/mvm/tx.c:1363 using 
> hostapd
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=199967
> #  * remote status changed: (?) -> CLOSED
> #  * remote resolution changed: (?) -> CODE-FIX
> #  * closed upstream
> tags 887045 + fixed-upstream
Bug #887045 [src:linux] iwlwifi: TX_STATUS_FAIL_DEST_PS at 
iwlwifi/mvm/tx.c:1363 using hostapd
Added tag(s) fixed-upstream.
> usertags 887045 + status-CLOSED resolution-CODE-FIX
There were no usertags set.
Usertags are now: resolution-CODE-FIX status-CLOSED.
> thanks
Stopping processing here.

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

Re: Bug#917941: Installation Buster on HP 17-by Notebook

[Cyril Brulebois]

Hi Bernhard,

Bernhard  (2019-01-03):
> Thanks for your response.
> In my installer image, the firmware-realtek.deb is available.
> 
> I'm not sure, if the WLAN ethernet adapter is supported from current kernel 
> 4.19.
> It would be great, if the WLAN ethernet adapter can be supported in Debian 10 
> "buster".
> 
> Attached, there is the syslog.

[This mail didn't reach debian-boot@ due to the attachment's size, sorry
for not having suggested compression in the first place.]

Looking at the syslog, the nic-wireless udeb is loaded successfully and
no interfaces show up, so I've spent some more time digging around, and
found that some linux forks have merged out of tree drivers, including
the separate rtl8821ce module, e.g. at [1], which isn't in mainline yet
as of v4.20+):
| kibi@armor:~/hack/linux.git$ git log endless/master -- 
drivers/net/wireless/rtl8821ce
| commit 3966567041ddd2d355a28ad980a3b5d68b36f975
| Author: Daniel Drake 
| Date:   Tue Nov 6 11:34:48 2018 +0800
| 
| rtl8821ce: fix build for Linux-4.19
| 
| commit 856fff46ec4d60c2c3e4c6aba3c6442fd703e948
| Author: Chris Chiu 
| Date:   Mon Aug 28 13:21:22 2017 +0800
| 
| rtl8821ce: integrate and fix build
| 
| https://phabricator.endlessm.com/T18646
| 
| commit 2102de7420ecb9136471cd5bf29ad7165a560614
| Author: Chris Chiu 
| Date:   Mon Aug 28 13:14:23 2017 +0800
| 
| Import rtl8821ce wifi driver
| 
| From Realtek official release 
rtl8821CE_WiFi_linux_v5.2.5_23431.20170824_COEX20170310-1212.tar.gz
| 
| https://phabricator.endlessm.com/T18646

 1. https://github.com/endlessm/linux/tree/master/drivers/net/wireless/rtl8821ce

So I guess there's not much we can do on the debian-installer side, we
would need to get this module merged into our linux source package to
make use of it, and I don't think the kernel team would add random out
of tree modules. ISTR backporting drivers is something that happens, so
we might get this module supported in a later 4.19.x release, once it
reaches mainline and someone backports it?

Cc'ing kernel team to make sure I'm not entirely wrong here. Maybe also
steal this bug away from installation-reports and have it retitled “no
support for rtl8821ce” or something similar?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#918096: linux-image-4.19.0-1-amd64: disk and keyboard do not work - unusable even in recovery mode

[Vincent Lefevre]

Note: I have the same issue with the 4.9 kernel from stable, which
I have just installed, so that initrd.img-4.9.0-8-amd64 is recent
(this might matter).

See also bug 917607 (I get the same error), reported against udev.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#918009: firmware-amd-graphics: please add amdgpu firmware for kaveri

[Trek]

Version: 20180825+dfsg-1

I confirm the problem, it leads to a crash of the amdgpu module if the
4.19 kernel is booted with amdgpu.cik_support=1 radeon.cik_support=0

for further informations see

https://bugs.freedesktop.org/show_bug.cgi?id=107855

comment 2 for the kernel messages and comment 4 for a simple workaround

however the correct solution is to include the amdgpu firmware, as the
radeon firmware seems to be no more updated

ciao!

Bug#918106: linux-image-4.9.0-8-amd64: segfault with logrotate

[marc Revival]

Package: src:linux
Version: 4.9.130-2
Severity: important

Dear Maintainer,


   * What led up to the situation?

A  logrotate in the cron is rotating all the logs daily of a rsyslog (> 2 TB)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
i try a fsck and safe-upgrade or full upgrade with no results on the
segfault.

   * What was the outcome of this action?
Nothing better
   * What outcome did you expect instead?
No segfault and a logrotate that end with
a positiv result.

Thanks

-- Package-specific info:
** Version:
Linux version 4.9.0-8-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.130-2 (2018-10-27)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-8-amd64 root=/dev/mapper/VG0-slash ro quiet

** Not tainted

** Kernel log:
[3.096359] PM: Image not found (code -22)
[3.096362] PM: Hibernation image not present or could not be loaded.
[3.174896] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: 
(null)
[3.962764] ip_tables: (C) 2000-2006 Netfilter Core Team
[4.146857] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[4.147329] systemd[1]: Detected virtualization vmware.
[4.147393] systemd[1]: Detected architecture x86-64.
[4.148555] random: crng init done
[4.148596] random: 7 urandom warning(s) missed due to ratelimiting
[4.183538] systemd[1]: Set hostname to .
[5.27] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[5.444570] systemd[1]: Listening on Journal Socket.
[5.444625] systemd[1]: Listening on udev Kernel Socket.
[5.444686] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[5.444709] systemd[1]: Reached target Remote File Systems.
[5.444757] systemd[1]: Listening on Journal Socket (/dev/log).
[5.763542] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro
[6.221680] vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16
[6.223181] vmw_vmci :00:07.7: Using capabilities 0xc
[6.236827] Guest personality initialized and is active
[6.238885] VMCI host device registered (name=vmci, major=10, minor=58)
[6.238925] Initialized host personality
[6.310305] NET: Registered protocol family 40
[7.935252] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[7.935262] ACPI: Power Button [PWRF]
[7.951039] ACPI: AC Adapter [ACAD] (on-line)
[8.131446] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[8.131473] sr 1:0:0:0: Attached scsi generic sg0 type 5
[8.131628] sd 2:0:0:0: Attached scsi generic sg1 type 0
[8.131734] sd 2:0:1:0: Attached scsi generic sg2 type 0
[8.131839] sd 2:0:2:0: Attached scsi generic sg3 type 0
[8.131937] sd 2:0:3:0: Attached scsi generic sg4 type 0
[8.181580] [drm] Initialized
[8.182287] input: PC Speaker as /devices/platform/pcspkr/input/input5
[8.198738] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 
10737418240 ms ovfl timer
[8.198742] RAPL PMU: hw unit of domain pp0-core 2^-0 Joules
[8.198745] RAPL PMU: hw unit of domain package 2^-0 Joules
[8.198748] RAPL PMU: hw unit of domain dram 2^-0 Joules
[8.321344] [drm] DMA map mode: Using physical TTM page addresses.
[8.321594] [drm] Capabilities:
[8.321600] [drm]   Rect copy.
[8.321602] [drm]   Cursor.
[8.321603] [drm]   Cursor bypass.
[8.321605] [drm]   Cursor bypass 2.
[8.321606] [drm]   8bit emulation.
[8.321607] [drm]   Alpha cursor.
[8.321609] [drm]   Extended Fifo.
[8.321610] [drm]   Multimon.
[8.321612] [drm]   Pitchlock.
[8.321613] [drm]   Irq mask.
[8.321614] [drm]   Display Topology.
[8.321616] [drm]   GMR.
[8.321617] [drm]   Traces.
[8.321619] [drm]   GMR2.
[8.321620] [drm]   Screen Object 2.
[8.321622] [drm]   Command Buffers.
[8.321623] [drm]   Command Buffers 2.
[8.321625] [drm]   Guest Backed Resources.
[8.321627] [drm] Max GMR ids is 64
[8.321629] [drm] Max number of GMR pages is 65536
[8.321631] [drm] Max dedicated hypervisor surface memory is 0 kiB
[8.321633] [drm] Maximum display memory size is 4096 kiB
[8.321636] [drm] VRAM at 0xe800 size is 4096 kiB
[8.321638] [drm] MMIO at 0xfe00 size is 256 kiB
[8.321641] [drm] global init.
[8.321763] [TTM] Zone  kernel: Available graphics memory: 8209152 kiB
[8.321766] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[8.321768] [TTM] Initializing pool allocator
[8.321775] [TTM] Initializing DMA pool allocator
[8.322075] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[8.322082] [drm] No driver support for vblank timestamp query.
[8.322624] [drm] Screen Target Display device initialized
[8.322708] [drm] width 640
[8.322726] [drm] 

Bug#918107: Random boot failure using VMware Paravirtual Adapter

[Thomas Kotzian]

Package: linux-image-4.19.0-1-amd64
Version: 4.19.12-1

Random boot failures on VMware when VM uses the Paravirtual Adapter. I drop 
into a busybox shell after the first line from the kernel. No disk found. 
Normally the 2nd line mentions the disk - this line doesn’t appear on failing 
boots - no disk is accessible. Rebooting sometimes works.

Kernel 4.18.0-3-amd64 work all the time. 4.19.3-1 is also broken.

LSI SCSI controller works fine on every reboot.

I have looked through the changelog of 4.19.12. it mentions code re-arrangement 
in pv_scsi driver - maybe something broke there?

Bug#918113: linux-image-4.19.0-1-amd64: Fails to initalize DisplayPort displays with rx560

[Mark Brown]

Package: src:linux
Version: 4.19.13-1
Severity: important

As covered in the kernel log below the amdgpu driver fails to initialize
a multi-monitor DisplayPort chain connected to a and AMD RX560
(Polaris11), rendering the system unusable in desktop configurations.
There is an oops earlier in the kernel output:

Jan  3 12:44:01 debutante kernel: [7.630953] WARNING: CPU: 2 PID: 69 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:2293 
core_link_enable_stream+0x4b3/0xb90 [am
dgpu]
Jan  3 12:44:01 debutante kernel: [7.630954] Modules linked in: fuse 
binfmt_misc nls_ascii nls_cp437 vfat fat intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp amdk
fd kvm_intel kvm irqbypass crct10dif_pclmul amdgpu crc32_pclmul 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic i915 chash 
gpu_sched ghash_clmulni_intel snd_hda_
intel ttm snd_hda_codec intel_cstate cp210x mei_me snd_hda_core sr_mod cdrom 
drm_kms_helper snd_hwdep iTCO_wdt efi_pstore intel_uncore snd_pcm usbserial 
intel_rapl_perf cdc_acm
 joydev efivars sg evdev pcspkr mei parport_serial iTCO_vendor_support 
snd_timer drm snd i2c_algo_bit soundcore video pcc_cpufreq button ipmi_devintf 
ipmi_msghandler loop nfsd 
parport_pc auth_rpcgss ppdev nfs_acl lp lockd parport grace sunrpc efivarfs 
ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 fscrypto btrfs
Jan  3 12:44:01 debutante kernel: [7.630978]  zstd_decompress zstd_compress 
xxhash raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor usb_storage
 raid6_pq libcrc32c raid1 raid0 multipath linear md_mod hid_generic usbhid hid 
sd_mod crc32c_intel ahci libahci xhci_pci libata aesni_intel xhci_hcd ehci_pci 
realtek ehci_hcd a
es_x86_64 i2c_i801 scsi_mod crypto_simd r8169 cryptd usbcore glue_helper libphy 
natsemi lpc_ich usb_common thermal fan
Jan  3 12:44:01 debutante kernel: [7.630993] CPU: 2 PID: 69 Comm: 
kworker/2:1 Tainted: P   OE 4.19.0-1-amd64 #1 Debian 4.19.12-1
Jan  3 12:44:01 debutante kernel: [7.630994] Hardware name: Gigabyte 
Technology Co., Ltd. H87-HD3/H87-HD3, BIOS F3 05/09/2013
Jan  3 12:44:01 debutante kernel: [7.631002] Workqueue: events_long 
drm_dp_mst_link_probe_work [drm_kms_helper]
Jan  3 12:44:01 debutante kernel: [7.631043] RIP: 
0010:core_link_enable_stream+0x4b3/0xb90 [amdgpu]
Jan  3 12:44:01 debutante kernel: [7.631044] Code: ff 48 89 ef be 01 00 00 
00 e8 b9 86 00 00 4c 89 ef 48 89 de e8 fe df ff ff bf c8 00 00 00 89 c5 e8 62 
67 26 fb e9 ea fd ff ff <0f> 0b e9 de fe ff ff 48 8b 82 50 02 00 00 48 8b 40 50 
48 8b 40 30
Jan  3 12:44:01 debutante kernel: [7.631045] RSP: 0018:a57081dd7668 
EFLAGS: 00010246
Jan  3 12:44:01 debutante kernel: [7.631046] RAX:  RBX: 
901ca62a4188 RCX: 
Jan  3 12:44:01 debutante kernel: [7.631046] RDX: 0005 RSI: 
c2349588 RDI: 0004
Jan  3 12:44:01 debutante kernel: [7.631047] RBP: 901cb7dede00 R08: 
0005 R09: 
Jan  3 12:44:01 debutante kernel: [7.631047] R10:  R11: 
a57081dd75c0 R12: 901ca89ed000
Jan  3 12:44:01 debutante kernel: [7.631048] R13: 901cb7dedf90 R14: 
901cb77f0400 R15: 0006
Jan  3 12:44:01 debutante kernel: [7.631048] FS:  () 
GS:901cbe08() knlGS:
Jan  3 12:44:01 debutante kernel: [7.631049] CS:  0010 DS:  ES:  
CR0: 80050033
Jan  3 12:44:01 debutante kernel: [7.631050] CR2: 7f586f069e20 CR3: 
4f20a002 CR4: 001606e0
Jan  3 12:44:01 debutante kernel: [7.631050] Call Trace:
Jan  3 12:44:01 debutante kernel: [7.631095]  ? 
dce110_stream_encoder_update_dp_info_packets+0x14c/0x200 [amdgpu]
Jan  3 12:44:01 debutante kernel: [7.631133]  
dce110_apply_ctx_to_hw+0x63f/0x650 [amdgpu]
Jan  3 12:44:01 debutante kernel: [7.631171]  dc_commit_state+0x2c6/0x520 
[amdgpu]
Jan  3 12:44:01 debutante kernel: [7.631207]  ? 
set_freesync_on_streams.part.6+0x4d/0x250 [amdgpu]
Jan  3 12:44:01 debutante kernel: [7.631241]  ? 
mod_freesync_set_user_enable+0x11f/0x150 [amdgpu]
Jan  3 12:44:01 debutante kernel: [7.631277]  
amdgpu_dm_atomic_commit_tail+0x388/0xdb0 [amdgpu]
Jan  3 12:44:01 debutante kernel: [7.631280]  ? _cond_resched+0x15/0x30
Jan  3 12:44:01 debutante kernel: [7.631282]  ? 
wait_for_completion_timeout+0x3b/0x1a0
Jan  3 12:44:01 debutante kernel: [7.631318]  ? 
amdgpu_dm_atomic_commit_tail+0xdb0/0xdb0 [amdgpu]
Jan  3 12:44:01 debutante kernel: [7.631325]  commit_tail+0x3d/0x70 
[drm_kms_helper]
Jan  3 12:44:01 debutante kernel: [7.631329]  
drm_atomic_helper_commit+0xb4/0x120 [drm_kms_helper]
Jan  3 12:44:01 debutante kernel: [7.631333]  
restore_fbdev_mode_atomic+0x170/0x1d0 [drm_kms_helper]
Jan  3 12:44:01 debutante kernel: [7.631337]  
drm_fb_helper_restore_fbdev_mode_unlocked+0x45/0x90 [drm_kms_helper]
Jan  3 12:44:01 debutante kernel: 

Processed: reassign 918106 to logrotate

[Debian Bug Tracking System]

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

> reassign 918106 logrotate
Bug #918106 [src:linux] linux-image-4.9.0-8-amd64: segfault with logrotate
Bug reassigned from package 'src:linux' to 'logrotate'.
No longer marked as found in versions linux/4.9.130-2.
Ignoring request to alter fixed versions of bug #918106 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#918140: linux-image-4.19.0-1-amd64: Samsung PM951 SSD in Dell XPS 15 9550 goes read-only

[Tyler Schwend]

Package: src:linux
Version: 4.19.12-1
Severity: critical
Tags: upstream
Justification: breaks the whole system

Dear Maintainer,

Submitting a bug report wherein after a kernel upgrade my laptop's SSD will,
during use or idle, go into read-only mode after minutes or hours of uptime. It
seems this is related to NVME/APSTE features (which I don't understand). Below
are some similar reports for other models:

https://groups.google.com/forum/#!searchin/linux.debian.bugs.dist/apst$20samsung|sort:date/linux.debian.bugs.dist/1AAKPI7rfQA/450TYup-
AQAJ

https://bbs.archlinux.org/viewtopic.php?id=232692

https://askubuntu.com/questions/905710/ext4-fs-error-after-
ubuntu-17-04-upgrade/906105#906105

I had been running an older kernel (because I previously noticed this and
associated it with a kernel upgrade) but over time forgot why I was using an
old kernel. Some docker work required me to update my kernel again, the problem
returned, and I was reminded of why I kept running the old kernel.

I believe that linux-image-4.17.0-3-amd64 works fine for me (possibly now that
I have disabled APSTE) but linux-image-4.19.0-1-amd64 does not. I don't know
what version of kernel I was running previously, but I will boot back to
4.17.03 and use that for a time, and then update the bug report.


   * What led up to the situation?
- Upgrading from an older 4.x kernel. I think 4.17 is fine, but will have to
run for a while to be sure.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
- No fixes found except for running older kernel.
- Disabling APSTE with nvme_core.default_ps_max_latency_us=0 provides no
relief, though it is reported as disabled by NVME tool.
- There are no firmware updates available for this drive.



-- Package-specific info:
** Version:
Linux version 4.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 
8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-1-amd64 root=/dev/mapper/func--platform--vg-root ro 
quiet nvme_core.default_ps_max_latency_us=0

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[3.661043] Bluetooth: L2CAP socket layer initialized
[3.661055] Bluetooth: SCO socket layer initialized
[3.666339] usbcore: registered new interface driver btusb
[3.690698] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[3.690699] Bluetooth: BNEP filters: protocol multicast
[3.690702] Bluetooth: BNEP socket layer initialized
[3.713324] input: HDA Intel PCH Headphone Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input20
[3.713365] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
[3.713400] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
[3.713450] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
[3.713507] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
[3.715654] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25
[3.736832] input: Logitech Unifying Device. Wireless PID:2011 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000A/input/input26
[3.737036] input: Logitech Unifying Device. Wireless PID:2011 Consumer 
Control as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000A/input/input27
[3.737096] input: Logitech Unifying Device. Wireless PID:2011 System 
Control as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000A/input/input28
[3.737154] hid-generic 0003:046D:2011.000A: input,hidraw7: USB HID v1.11 
Keyboard [Logitech Unifying Device. Wireless PID:2011] on usb-:00:14.0-2.3:4
[3.738701] input: Logitech Unifying Device. Wireless PID:4055 Mouse as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:4055.000B/input/input32
[3.738766] hid-generic 0003:046D:4055.000B: input,hidraw8: USB HID v1.11 
Mouse [Logitech Unifying Device. Wireless PID:4055] on usb-:00:14.0-2.3:1
[3.752683] input: Logitech K520 as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3:1.2/0003:046D:C52B.0008/0003:046D:2011.000C/input/input36
[3.781508] Bluetooth: hci0: BCM: chip id 102
[3.782508] Bluetooth: hci0: BCM: features 0x2f
[3.798526] Bluetooth: hci0: func-platform
[3.799513] Bluetooth: hci0: BCM (001.001.005) build 0422
[3.801782] bluetooth hci0: firmware: direct-loading firmware 
brcm/BCM-0a5c-6410.hcd
[3.847890] logitech-hidpp-device 0003:046D:2011.000C: input,hidraw9: USB 
HID v1.11 Keyboard [Logitech K520] on usb-:00:14.0-2.3:2
[3.854718] input: Logitech K520 as 

Bug#918142: linux-image-4.19.0-1-amd64: Can no longer disable the touchscreen module

[lauren]

Package: src:linux
Version: 4.19.12-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
upgraded to kernel 4.19 as part of regular debian apt update

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
i added "blacklist hid_multitouch" to /etc/modprobe.d/blacklist.conf

   * What was the outcome of this action?
no effect - the touchscreen is still active

   * What outcome did you expect instead?
that the touchscreen was not active

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


-- Package-specific info:
** Version:
Linux version 4.19.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 
8.2.0 (Debian 8.2.0-13)) #1 SMP Debian 4.19.12-1 (2018-12-22)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-1-amd64 
root=UUID=9b57622f-6800-4162-a7df-46de6f9934ba ro quiet

** Not tainted

** Kernel log:
[ 6296.343484] ACPI: EC: EC stopped
[ 6296.343485] PM: Saving platform NVS memory
[ 6296.343537] Disabling non-boot CPUs ...
[ 6296.360186] IRQ 46: no longer affine to CPU1
[ 6296.361961] smpboot: CPU 1 is now offline
[ 6296.384158] IRQ 47: no longer affine to CPU2
[ 6296.385177] smpboot: CPU 2 is now offline
[ 6296.407964] IRQ 23: no longer affine to CPU3
[ 6296.407971] IRQ 42: no longer affine to CPU3
[ 6296.408991] smpboot: CPU 3 is now offline
[ 6296.414128] ACPI: Low-level resume complete
[ 6296.414175] ACPI: EC: EC started
[ 6296.414176] PM: Restoring platform NVS memory
[ 6296.414563] Enabling non-boot CPUs ...
[ 6296.414601] x86: Booting SMP configuration:
[ 6296.414602] smpboot: Booting Node 0 Processor 1 APIC 0x1
[ 6296.415112]  cache: parent cpu1 should not be sleeping
[ 6296.415333] CPU1 is up
[ 6296.415357] smpboot: Booting Node 0 Processor 2 APIC 0x2
[ 6296.415799]  cache: parent cpu2 should not be sleeping
[ 6296.415975] CPU2 is up
[ 6296.415997] smpboot: Booting Node 0 Processor 3 APIC 0x3
[ 6296.416437]  cache: parent cpu3 should not be sleeping
[ 6296.416618] CPU3 is up
[ 6296.420122] ACPI: Waking up from system sleep state S3
[ 6296.428828] ACPI: EC: interrupt unblocked
[ 6296.479402] usb usb1: root hub lost power or was reset
[ 6296.479409] usb usb2: root hub lost power or was reset
[ 6296.479463] ACPI: EC: event unblocked
[ 6296.482240] sd 0:0:0:0: [sda] Starting disk
[ 6296.725465] usb 3-1: reset high-speed USB device number 2 using ehci-pci
[ 6296.796875] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 6296.833457] usb 1-7: reset full-speed USB device number 4 using xhci_hcd
[ 6296.885816] psmouse serio1: synaptics: queried max coordinates: x [..5112], 
y [..3834]
[ 6296.915388] psmouse serio1: synaptics: queried min coordinates: x [1024..], 
y [1024..]
[ 6297.029537] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 6297.029541] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
[ 6297.029544] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered 
out
[ 6297.029642] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
[ 6297.032193] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
[ 6297.032198] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
[ 6297.032201] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered 
out
[ 6297.032262] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
[ 6297.033747] ata1.00: configured for UDMA/133
[ 6297.109557] usb 1-6: reset full-speed USB device number 3 using xhci_hcd
[ 6297.177507] usb 3-1.5: reset full-speed USB device number 3 using ehci-pci
[ 6297.385614] usb 1-8: reset high-speed USB device number 5 using xhci_hcd
[ 6297.661569] usb 1-1: reset high-speed USB device number 2 using xhci_hcd
[ 6297.812178] acpi LNXPOWER:02: Turning OFF
[ 6297.812595] OOM killer enabled.
[ 6297.812598] Restarting tasks ... done.
[ 6297.859330] PM: suspend exit
[ 6298.009230] e1000e: enp0s25 NIC Link is Down
[ 6298.096772] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[ 6298.313640] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
[ 6298.318509] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 6298.325015] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 6298.330253] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 6298.507043] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 6299.989373] Bluetooth: hci0: command 0xfc05 tx timeout
[ 6299.989377] Bluetooth: hci0: Reading Intel version information failed (-110)
[ 6301.781300] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 6302.997758] Bluetooth: hci0: setting interface failed (110)
[ 6304.864724] wlp3s0: authenticate with e8:de:27:65:86:8e
[ 6304.868640] wlp3s0: send auth to e8:de:27:65:86:8e (try 1/3)
[ 6304.877870] wlp3s0: authenticated
[ 6304.881192] wlp3s0: associate with e8:de:27:65:86:8e (try 1/3)
[ 6304.885080] wlp3s0: RX AssocResp from e8:de:27:65:86:8e (capab=0x431 

Bug#918142: linux-image-4.19.0-1-amd64: Can no longer disable the touchscreen module

[Ben Hutchings]

Control: tag -1 moreinfo

On Thu, 2019-01-03 at 20:19 +0100, lauren wrote:
> Package: src:linux
> Version: 4.19.12-1
> Severity: normal
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>   upgraded to kernel 4.19 as part of regular debian apt update
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>   i added "blacklist hid_multitouch" to /etc/modprobe.d/blacklist.conf
> 
>* What was the outcome of this action?
>   no effect - the touchscreen is still active
> 
>* What outcome did you expect instead?
>   that the touchscreen was not active
[...]

The kernel doesn't load modules itself; that's controlled by systemd,
initramfs-tools, etc.

If you only recently updated the modprobe configuration, try running
"update-initramfs -u" and then rebooting.  Does that fix the problem?

Ben.

-- 
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer




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

Processed: Re: Bug#918142: linux-image-4.19.0-1-amd64: Can no longer disable the touchscreen module

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #918142 [src:linux] linux-image-4.19.0-1-amd64: Can no longer disable the 
touchscreen module
Added tag(s) moreinfo.

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

Bug#918156: linux-image-4.18.0-0.bpo.3-armmp: please enable support for Ti WL1838 Bluetooth

[Josua Mayer]

Package: src:linux
Version: 4.18.20-2~bpo9+1
Severity: wishlist
Tags: patch

Dear Maintainer,

Please enable support for above mentioned bluetooth chip.
It is used in SolidRun Ltd. i.MX6 MicroSOMs since revision 1.5,
thereby applying to all Hummingboards and Cuboxes with a recent SoM.

I enabled the necessary options and tested with a local build of 4.20 from
the debian kernel source tree, and am attaching the diff.

Yours sincerely
Josua Mayer


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

** Model information
Hardware: Freescale i.MX6 Quad/DualLite (Device Tree)
Revision: 
Device Tree model: SolidRun HummingBoard2 Dual/Quad (1.5som+emmc)

** PCI devices:
00:00.0 PCI bridge [0604]: Synopsys, Inc. Device [16c3:abcd] (rev 01) (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-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: dwc3_haps


** USB devices:
Bus 002 Device 002: ID 04b4:6570 Cypress Semiconductor Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)

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

Versions of packages linux-image-4.18.0-0.bpo.3-armmp depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod23-2
ii  linux-base  4.5

Versions of packages linux-image-4.18.0-0.bpo.3-armmp recommends:
ii  apparmor 2.11.0-3+deb9u2
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2.3

Versions of packages linux-image-4.18.0-0.bpo.3-armmp suggests:
pn  debian-kernel-handbook  
pn  linux-doc-4.18  

Versions of packages linux-image-4.18.0-0.bpo.3-armmp is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
ii  firmware-misc-nonfree 20180825+dfsg-1~bpo9+1
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
ii  firmware-ti-connectivity  20161130-4
pn  xen-hypervisor

-- no debconf information
>From 38737c0c24a8d7c23b46cd0a28e8dcf932ce06e1 Mon Sep 17 00:00:00 2001
From: Josua Mayer 
Date: Thu, 3 Jan 2019 20:59:05 +0100
Subject: [PATCH] armmp: enable BT_HCIUART_LL

This allows using the wl1837-st bluetooth chip on the SolidRun i.MX6 SoMs
Revision 1.5.

Signed-off-by: Josua Mayer 
---
 debian/config/armhf/config | 4 
 1 file changed, 4 insertions(+)

diff --git a/debian/config/armhf/config b/debian/config/armhf/config
index 48d26fea8269..e390fe168b42 100644
--- a/debian/config/armhf/config
+++ b/debian/config/armhf/config
@@ -179,6 +179,10 @@ CONFIG_DMA_CMA=y
 ##
 ## file: drivers/bluetooth/Kconfig
 ##
+CONFIG_BT_HCIUART=m
+CONFIG_BT_HCIUART_3WIRE=y
+CONFIG_BT_HCIUART_LL=y
+CONFIG_BT_HCIUART_SERDEV=y
 CONFIG_BT_WILINK=m
 
 ##
-- 
2.20.1

Bug#918156: some omitted details

[Josua Mayer]

I forgot to mention some important bits:
1. this is for armmp flavour only
2. the options I chose enable some more by default that I did not list
3. maybe all HCIUART drivers should be enabled, just like on x86?

linux_4.9.144-1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 30 Dec 2018 23:27:02 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-8 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-8-common 
linux-headers-4.9.0-8-common-rt linux-libc-dev linux-headers-4.9.0-8-all 
linux-headers-4.9.0-8-all-alpha kernel-image-4.9.0-8-alpha-generic-di 
nic-modules-4.9.0-8-alpha-generic-di 
nic-wireless-modules-4.9.0-8-alpha-generic-di 
nic-shared-modules-4.9.0-8-alpha-generic-di 
serial-modules-4.9.0-8-alpha-generic-di 
usb-serial-modules-4.9.0-8-alpha-generic-di 
ppp-modules-4.9.0-8-alpha-generic-di pata-modules-4.9.0-8-alpha-generic-di 
cdrom-core-modules-4.9.0-8-alpha-generic-di 
scsi-core-modules-4.9.0-8-alpha-generic-di 
scsi-modules-4.9.0-8-alpha-generic-di loop-modules-4.9.0-8-alpha-generic-di 
btrfs-modules-4.9.0-8-alpha-generic-di ext4-modules-4.9.0-8-alpha-generic-di 
isofs-modules-4.9.0-8-alpha-generic-di jfs-modules-4.9.0-8-alpha-generic-di
 xfs-modules-4.9.0-8-alpha-generic-di fat-modules-4.9.0-8-alpha-generic-di 
md-modules-4.9.0-8-alpha-generic-di multipath-modules-4.9.0-8-alpha-generic-di 
usb-modules-4.9.0-8-alpha-generic-di 
usb-storage-modules-4.9.0-8-alpha-generic-di 
fb-modules-4.9.0-8-alpha-generic-di input-modules-4.9.0-8-alpha-generic-di 
event-modules-4.9.0-8-alpha-generic-di mouse-modules-4.9.0-8-alpha-generic-di 
nic-pcmcia-modules-4.9.0-8-alpha-generic-di 
pcmcia-modules-4.9.0-8-alpha-generic-di 
nic-usb-modules-4.9.0-8-alpha-generic-di sata-modules-4.9.0-8-alpha-generic-di 
crc-modules-4.9.0-8-alpha-generic-di crypto-modules-4.9.0-8-alpha-generic-di 
crypto-dm-modules-4.9.0-8-alpha-generic-di ata-modules-4.9.0-8-alpha-generic-di 
nbd-modules-4.9.0-8-alpha-generic-di squashfs-modules-4.9.0-8-alpha-generic-di 
virtio-modules-4.9.0-8-alpha-generic-di zlib-modules-4.9.0-8-alpha-generic-di 
fuse-modules-4.9.0-8-alpha-generic-di srm-modules-4.9.0-8-alpha-generic-di 
linux-image-4.9.0-8-alpha-generic
 linux-headers-4.9.0-8-alpha-generic linux-image-4.9.0-8-alpha-generic-dbg 
linux-image-4.9.0-8-alpha-smp linux-headers-4.9.0-8-alpha-smp 
linux-image-4.9.0-8-alpha-smp-dbg linux-headers-4.9.0-8-all-amd64 
kernel-image-4.9.0-8-amd64-di nic-modules-4.9.0-8-amd64-di 
nic-wireless-modules-4.9.0-8-amd64-di nic-shared-modules-4.9.0-8-amd64-di 
serial-modules-4.9.0-8-amd64-di usb-serial-modules-4.9.0-8-amd64-di 
ppp-modules-4.9.0-8-amd64-di pata-modules-4.9.0-8-amd64-di 
cdrom-core-modules-4.9.0-8-amd64-di firewire-core-modules-4.9.0-8-amd64-di 
scsi-core-modules-4.9.0-8-amd64-di scsi-modules-4.9.0-8-amd64-di 
loop-modules-4.9.0-8-amd64-di btrfs-modules-4.9.0-8-amd64-di 
ext4-modules-4.9.0-8-amd64-di isofs-modules-4.9.0-8-amd64-di 
jfs-modules-4.9.0-8-amd64-di ntfs-modules-4.9.0-8-amd64-di 
xfs-modules-4.9.0-8-amd64-di fat-modules-4.9.0-8-amd64-di 
md-modules-4.9.0-8-amd64-di multipath-modules-4.9.0-8-amd64-di 
usb-modules-4.9.0-8-amd64-di usb-storage-modules-4.9.0-8-amd64-di
 pcmcia-storage-modules-4.9.0-8-amd64-di fb-modules-4.9.0-8-amd64-di 
input-modules-4.9.0-8-amd64-di event-modules-4.9.0-8-amd64-di 
mouse-modules-4.9.0-8-amd64-di nic-pcmcia-modules-4.9.0-8-amd64-di 
pcmcia-modules-4.9.0-8-amd64-di nic-usb-modules-4.9.0-8-amd64-di 
sata-modules-4.9.0-8-amd64-di acpi-modules-4.9.0-8-amd64-di 
i2c-modules-4.9.0-8-amd64-di crc-modules-4.9.0-8-amd64-di 
crypto-modules-4.9.0-8-amd64-di crypto-dm-modules-4.9.0-8-amd64-di 
efi-modules-4.9.0-8-amd64-di ata-modules-4.9.0-8-amd64-di 
mmc-core-modules-4.9.0-8-amd64-di mmc-modules-4.9.0-8-amd64-di 
nbd-modules-4.9.0-8-amd64-di squashfs-modules-4.9.0-8-amd64-di 
speakup-modules-4.9.0-8-amd64-di virtio-modules-4.9.0-8-amd64-di 
uinput-modules-4.9.0-8-amd64-di sound-modules-4.9.0-8-amd64-di 
hyperv-modules-4.9.0-8-amd64-di udf-modules-4.9.0-8-amd64-di 
fuse-modules-4.9.0-8-amd64-di linux-image-4.9.0-8-amd64 
linux-headers-4.9.0-8-amd64 linux-image-4.9.0-8-amd64-dbg 
linux-image-4.9.0-8-rt-amd64
 linux-headers-4.9.0-8-rt-amd64 linux-image-4.9.0-8-rt-amd64-dbg 
linux-headers-4.9.0-8-all-arm64 kernel-image-4.9.0-8-arm64-di 
nic-modules-4.9.0-8-arm64-di nic-wireless-modules-4.9.0-8-arm64-di 
nic-shared-modules-4.9.0-8-arm64-di ppp-modules-4.9.0-8-arm64-di 
cdrom-core-modules-4.9.0-8-arm64-di scsi-core-modules-4.9.0-8-arm64-di 
scsi-modules-4.9.0-8-arm64-di loop-modules-4.9.0-8-arm64-di 
btrfs-modules-4.9.0-8-arm64-di ext4-modules-4.9.0-8-arm64-di 
isofs-modules-4.9.0-8-arm64-di jfs-modules-4.9.0-8-arm64-di 
xfs-modules-4.9.0-8-arm64-di fat-modules-4.9.0-8-arm64-di 
md-modules-4.9.0-8-arm64-di multipath-modules-4.9.0-8-arm64-di 
usb-modules-4.9.0-8-arm64-di usb-storage-modules-4.9.0-8-arm64-di 
fb-modules-4.9.0-8-arm64-di input-modules-4.9.0-8-arm64-di 
event-modules-4.9.0-8-arm64-di nic-usb-modules-4.9.0-8-arm64-di 
sata-modules-4.9.0-8-arm64-di i2c-modules-4.9.0-8-arm64-di 
crc-modules-4.9.0-8-arm64-di 

Bug#914556: marked as done (linux: FTBFS on arm64: changed ABI)

[Debian Bug Tracking System]

Your message dated Thu, 03 Jan 2019 21:47:17 +
with message-id 
and subject line Bug#914556: fixed in linux 4.9.144-1
has caused the Debian Bug report #914556,
regarding linux: FTBFS on arm64: changed ABI
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.)


-- 
914556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.9.135-1
Severity: serious
Justification: FTBFS
Control: affects -1 release.debian.org

For tracking the issue:

4.9.135-1 FTBFS on arm64 due to changed ABI:

https://buildd.debian.org/status/fetch.php?pkg=linux=arm64=4.9.135-1=1543036173=0

Relevant part:

hnae_ae_register module: 
drivers/net/ethernet/hisilicon/hns/hnae, version: 0xdf635812 -> 0xbdde09c7, 
export: EXPORT_SYMBOL
hnae_ae_unregister   module: 
drivers/net/ethernet/hisilicon/hns/hnae, version: 0xe679c9fd -> 0x1c9eb41e, 
export: EXPORT_SYMBOL
hnae_get_handle  module: 
drivers/net/ethernet/hisilicon/hns/hnae, version: 0xafb4a8fd -> 0x29ae7935, 
export: EXPORT_SYMBOL
hnae_put_handle  module: 
drivers/net/ethernet/hisilicon/hns/hnae, version: 0x899f69bb -> 0x43a26da5, 
export: EXPORT_SYMBOL
hnae_reinit_handle   module: 
drivers/net/ethernet/hisilicon/hns/hnae, version: 0x767c1c31 -> 0xbc41182f, 
export: EXPORT_SYMBOL

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.144-1

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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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: Sun, 30 Dec 2018 23:27:02 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-8 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-8-common 
linux-headers-4.9.0-8-common-rt linux-libc-dev linux-headers-4.9.0-8-all 
linux-headers-4.9.0-8-all-alpha kernel-image-4.9.0-8-alpha-generic-di 
nic-modules-4.9.0-8-alpha-generic-di 
nic-wireless-modules-4.9.0-8-alpha-generic-di 
nic-shared-modules-4.9.0-8-alpha-generic-di 
serial-modules-4.9.0-8-alpha-generic-di 
usb-serial-modules-4.9.0-8-alpha-generic-di 
ppp-modules-4.9.0-8-alpha-generic-di pata-modules-4.9.0-8-alpha-generic-di 
cdrom-core-modules-4.9.0-8-alpha-generic-di 
scsi-core-modules-4.9.0-8-alpha-generic-di 
scsi-modules-4.9.0-8-alpha-generic-di loop-modules-4.9.0-8-alpha-generic-di 
btrfs-modules-4.9.0-8-alpha-generic-di ext4-modules-4.9.0-8-alpha-generic-di 
isofs-modules-4.9.0-8-alpha-generic-di jfs-modules-4.9.0-8-alpha-generic-di
 xfs-modules-4.9.0-8-alpha-generic-di fat-modules-4.9.0-8-alpha-generic-di 
md-modules-4.9.0-8-alpha-generic-di multipath-modules-4.9.0-8-alpha-generic-di 
usb-modules-4.9.0-8-alpha-generic-di 
usb-storage-modules-4.9.0-8-alpha-generic-di 
fb-modules-4.9.0-8-alpha-generic-di input-modules-4.9.0-8-alpha-generic-di 
event-modules-4.9.0-8-alpha-generic-di mouse-modules-4.9.0-8-alpha-generic-di 
nic-pcmcia-modules-4.9.0-8-alpha-generic-di 
pcmcia-modules-4.9.0-8-alpha-generic-di 
nic-usb-modules-4.9.0-8-alpha-generic-di sata-modules-4.9.0-8-alpha-generic-di 
crc-modules-4.9.0-8-alpha-generic-di crypto-modules-4.9.0-8-alpha-generic-di 
crypto-dm-modules-4.9.0-8-alpha-generic-di ata-modules-4.9.0-8-alpha-generic-di 
nbd-modules-4.9.0-8-alpha-generic-di squashfs-modules-4.9.0-8-alpha-generic-di 
virtio-modules-4.9.0-8-alpha-generic-di zlib-modules-4.9.0-8-alpha-generic-di 
fuse-modules-4.9.0-8-alpha-generic-di srm-modules-4.9.0-8-alpha-generic-di 
linux-image-4.9.0-8-alpha-generic
 linux-headers-4.9.0-8-alpha-generic linux-image-4.9.0-8-alpha-generic-dbg 
linux-image-4.9.0-8-alpha-smp linux-headers-4.9.0-8-alpha-smp 
linux-image-4.9.0-8-alpha-smp-dbg linux-headers-4.9.0-8-all-amd64 
kernel-image-4.9.0-8-amd64-di 

Bug#915229: marked as done (src:linux: Updated driver needed for Amazon ENA ethernet)

[Debian Bug Tracking System]

Your message dated Thu, 03 Jan 2019 21:47:17 +
with message-id 
and subject line Bug#915229: fixed in linux 4.9.144-1
has caused the Debian Bug report #915229,
regarding src:linux: Updated driver needed for Amazon ENA ethernet
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.)


-- 
915229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Severity: important

ENA is an ethernet adaptor used on Amazon EC2 cloud instances. Version 2.0.2 of
the ENA driver was added to the mainline kernel as of version 4.20. This
version includes fixes for various bugs, some of which result in kernel panics,
and is needed in order to enable access to features available on newer
hardware. It is also needed in order to support the recently announced
arm64-based instances.

I have opened https://salsa.debian.org/kernel-team/linux/merge_requests/77 to
backport ENA 2.0.2 to 4.19 for buster.

I have a WIP branch for stretch's 4.9 kernel at
https://salsa.debian.org/noahm/linux/tree/stretch+ena2 This requires a bit more
effort as 4.9 contains a much older version of the driver.

Thanks
noah
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.144-1

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 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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: Sun, 30 Dec 2018 23:27:02 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-8 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-8-common 
linux-headers-4.9.0-8-common-rt linux-libc-dev linux-headers-4.9.0-8-all 
linux-headers-4.9.0-8-all-alpha kernel-image-4.9.0-8-alpha-generic-di 
nic-modules-4.9.0-8-alpha-generic-di 
nic-wireless-modules-4.9.0-8-alpha-generic-di 
nic-shared-modules-4.9.0-8-alpha-generic-di 
serial-modules-4.9.0-8-alpha-generic-di 
usb-serial-modules-4.9.0-8-alpha-generic-di 
ppp-modules-4.9.0-8-alpha-generic-di pata-modules-4.9.0-8-alpha-generic-di 
cdrom-core-modules-4.9.0-8-alpha-generic-di 
scsi-core-modules-4.9.0-8-alpha-generic-di 
scsi-modules-4.9.0-8-alpha-generic-di loop-modules-4.9.0-8-alpha-generic-di 
btrfs-modules-4.9.0-8-alpha-generic-di ext4-modules-4.9.0-8-alpha-generic-di 
isofs-modules-4.9.0-8-alpha-generic-di jfs-modules-4.9.0-8-alpha-generic-di
 xfs-modules-4.9.0-8-alpha-generic-di fat-modules-4.9.0-8-alpha-generic-di 
md-modules-4.9.0-8-alpha-generic-di multipath-modules-4.9.0-8-alpha-generic-di 
usb-modules-4.9.0-8-alpha-generic-di 
usb-storage-modules-4.9.0-8-alpha-generic-di 
fb-modules-4.9.0-8-alpha-generic-di input-modules-4.9.0-8-alpha-generic-di 
event-modules-4.9.0-8-alpha-generic-di mouse-modules-4.9.0-8-alpha-generic-di 
nic-pcmcia-modules-4.9.0-8-alpha-generic-di 
pcmcia-modules-4.9.0-8-alpha-generic-di 
nic-usb-modules-4.9.0-8-alpha-generic-di sata-modules-4.9.0-8-alpha-generic-di 
crc-modules-4.9.0-8-alpha-generic-di crypto-modules-4.9.0-8-alpha-generic-di 
crypto-dm-modules-4.9.0-8-alpha-generic-di ata-modules-4.9.0-8-alpha-generic-di 
nbd-modules-4.9.0-8-alpha-generic-di squashfs-modules-4.9.0-8-alpha-generic-di 
virtio-modules-4.9.0-8-alpha-generic-di zlib-modules-4.9.0-8-alpha-generic-di 
fuse-modules-4.9.0-8-alpha-generic-di srm-modules-4.9.0-8-alpha-generic-di 
linux-image-4.9.0-8-alpha-generic
 linux-headers-4.9.0-8-alpha-generic linux-image-4.9.0-8-alpha-generic-dbg 
linux-image-4.9.0-8-alpha-smp linux-headers-4.9.0-8-alpha-smp 
linux-image-4.9.0-8-alpha-smp-dbg linux-headers-4.9.0-8-all-amd64 
kernel-image-4.9.0-8-amd64-di nic-modules-4.9.0-8-amd64-di 
nic-wireless-modules-4.9.0-8-amd64-di nic-shared-modules-4.9.0-8-amd64-di 
serial-modules-4.9.0-8-amd64-di usb-serial-modules-4.9.0-8-amd64-di 
ppp-modules-4.9.0-8-amd64-di pata-modules-4.9.0-8-amd64-di 
cdrom-core-modules-4.9.0-8-amd64-di firewire-core-modules-4.9.0-8-amd64-di 

Bug#915231: marked as done (src:linux: Enable PCI_HOTPLUG for arm64)

[Debian Bug Tracking System]

Your message dated Thu, 03 Jan 2019 21:47:17 +
with message-id 
and subject line Bug#915231: fixed in linux 4.9.144-1
has caused the Debian Bug report #915231,
regarding src:linux: Enable PCI_HOTPLUG for arm64
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.)


-- 
915231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.9.130-2
Severity: wishlist
Tags: stretch

Amazon recently announced arm64-based EC2 instances. These instances rely on
PCI_HOTPLUG functionality to support attach/detach of resources such as
ethernet interfaces and block devices. PCI_HOTPLUG is enabled for arm64 in
buster and sid, but not stretch. Please enable PCI_HOTPLUG for arm64 in order
to support EC2 on arm64.

Thanks
noah
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.144-1

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 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (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: Sun, 30 Dec 2018 23:27:02 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-8 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-8-common 
linux-headers-4.9.0-8-common-rt linux-libc-dev linux-headers-4.9.0-8-all 
linux-headers-4.9.0-8-all-alpha kernel-image-4.9.0-8-alpha-generic-di 
nic-modules-4.9.0-8-alpha-generic-di 
nic-wireless-modules-4.9.0-8-alpha-generic-di 
nic-shared-modules-4.9.0-8-alpha-generic-di 
serial-modules-4.9.0-8-alpha-generic-di 
usb-serial-modules-4.9.0-8-alpha-generic-di 
ppp-modules-4.9.0-8-alpha-generic-di pata-modules-4.9.0-8-alpha-generic-di 
cdrom-core-modules-4.9.0-8-alpha-generic-di 
scsi-core-modules-4.9.0-8-alpha-generic-di 
scsi-modules-4.9.0-8-alpha-generic-di loop-modules-4.9.0-8-alpha-generic-di 
btrfs-modules-4.9.0-8-alpha-generic-di ext4-modules-4.9.0-8-alpha-generic-di 
isofs-modules-4.9.0-8-alpha-generic-di jfs-modules-4.9.0-8-alpha-generic-di
 xfs-modules-4.9.0-8-alpha-generic-di fat-modules-4.9.0-8-alpha-generic-di 
md-modules-4.9.0-8-alpha-generic-di multipath-modules-4.9.0-8-alpha-generic-di 
usb-modules-4.9.0-8-alpha-generic-di 
usb-storage-modules-4.9.0-8-alpha-generic-di 
fb-modules-4.9.0-8-alpha-generic-di input-modules-4.9.0-8-alpha-generic-di 
event-modules-4.9.0-8-alpha-generic-di mouse-modules-4.9.0-8-alpha-generic-di 
nic-pcmcia-modules-4.9.0-8-alpha-generic-di 
pcmcia-modules-4.9.0-8-alpha-generic-di 
nic-usb-modules-4.9.0-8-alpha-generic-di sata-modules-4.9.0-8-alpha-generic-di 
crc-modules-4.9.0-8-alpha-generic-di crypto-modules-4.9.0-8-alpha-generic-di 
crypto-dm-modules-4.9.0-8-alpha-generic-di ata-modules-4.9.0-8-alpha-generic-di 
nbd-modules-4.9.0-8-alpha-generic-di squashfs-modules-4.9.0-8-alpha-generic-di 
virtio-modules-4.9.0-8-alpha-generic-di zlib-modules-4.9.0-8-alpha-generic-di 
fuse-modules-4.9.0-8-alpha-generic-di srm-modules-4.9.0-8-alpha-generic-di 
linux-image-4.9.0-8-alpha-generic
 linux-headers-4.9.0-8-alpha-generic linux-image-4.9.0-8-alpha-generic-dbg 
linux-image-4.9.0-8-alpha-smp linux-headers-4.9.0-8-alpha-smp 
linux-image-4.9.0-8-alpha-smp-dbg linux-headers-4.9.0-8-all-amd64 
kernel-image-4.9.0-8-amd64-di nic-modules-4.9.0-8-amd64-di 
nic-wireless-modules-4.9.0-8-amd64-di nic-shared-modules-4.9.0-8-amd64-di 
serial-modules-4.9.0-8-amd64-di usb-serial-modules-4.9.0-8-amd64-di 
ppp-modules-4.9.0-8-amd64-di pata-modules-4.9.0-8-amd64-di 
cdrom-core-modules-4.9.0-8-amd64-di firewire-core-modules-4.9.0-8-amd64-di 
scsi-core-modules-4.9.0-8-amd64-di scsi-modules-4.9.0-8-amd64-di 
loop-modules-4.9.0-8-amd64-di btrfs-modules-4.9.0-8-amd64-di 
ext4-modules-4.9.0-8-amd64-di isofs-modules-4.9.0-8-amd64-di 
jfs-modules-4.9.0-8-amd64-di ntfs-modules-4.9.0-8-amd64-di 
xfs-modules-4.9.0-8-amd64-di fat-modules-4.9.0-8-amd64-di 
md-modules-4.9.0-8-amd64-di