linux_5.2.9-1_source.changes ACCEPTED into unstable

2019-08-18 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Aug 2019 22:54:21 +0100
Source: linux
Architecture: source
Version: 5.2.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 908712 925766 931707 933963 934091 934304 934309 934378 934824 934848
Changes:
 linux (5.2.9-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.8
 - scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
 - libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
 - libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
 - ALSA: usb-audio: Sanity checks for each pipe and EP types
 - ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
 - HID: wacom: fix bit shift for Cintiq Companion 2
 - HID: Add quirk for HP X1200 PIXART OEM mouse
 - atm: iphase: Fix Spectre v1 vulnerability (CVE-2017-5753)
 - bnx2x: Disable multi-cos feature.
 - drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case (Closes: #908712)
 - ife: error out when nla attributes are empty
 - ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
 - ip6_tunnel: fix possible use-after-free on xmit
 - ipip: validate header length in ipip_tunnel_xmit
 - [armhf,arm64] mvpp2: fix panic on module removal
 - [armhf,arm64] mvpp2: refactor MTU change code
 - net: bridge: delete local fdb on device init failure
 - net: bridge: mcast: don't delete permanent entries when fast leave is
   enabled
 - net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
 - net: fix ifindex collision during namespace removal
 - net/mlx5e: always initialize frag->last_in_page
 - net/mlx5: Use reversed order when unregister devices
 - net: phy: fixed_phy: print gpio error only if gpio node is present
 - net: phy: mscc: initialize stats array
 - net: sched: Fix a possible null-pointer dereference in dequeue_func()
 - net sched: update vlan action for batched events operations
 - net: sched: use temporary variable for actions indexes
 - net/smc: do not schedule tx_work in SMC_CLOSED state
 - [armhf,arm64] net: stmmac: Use netif_tx_napi_add() for TX polling
   function
 - tipc: compat: allow tipc commands without arguments
 - tipc: fix unitilized skb list crash
 - tun: mark small packets as owned by the tap sock
 - net/mlx5: Fix modify_cq_in alignment
 - net/mlx5e: Prevent encap flow counter update async to user query
 - r8169: don't use MSI before RTL8168d
 - net: fix bpf_xdp_adjust_head regression for generic-XDP
 - [x86] hv_sock: Fix hang when a connection is closed
 - net: phy: fix race in genphy_update_link
 - net/smc: avoid fallback in case of non-blocking connect
 - rocker: fix memory leaks of fib_work on two error return paths
 - net/mlx5: Add missing RDMA_RX capabilities
 - net/mlx5e: Fix matching of speed to PRM link modes
 - compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
 - [x86] drm/i915/vbt: Fix VBT parsing for the PSR section
 - Revert "mac80211: set NETIF_F_LLTX when using intermediate tx queues"
 - [armhf,arm64] spi: bcm2835: Fix 3-wire mode if DMA is enabled
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.9
 - Revert "PCI: Add missing link delays required by the PCIe spec"
 - [arm64] iio: cros_ec_accel_legacy: Fix incorrect channel setting
 - [x86] iio: imu: mpu6050: add missing available scan masks
 - [x86] crypto: ccp - Fix oops by properly managing allocated structures
 - [x86] crypto: ccp - Add support for valid authsize values less than 16
 - [x86] crypto: ccp - Ignore tag length when decrypting GCM ciphertext
 - driver core: platform: return -ENXIO for missing GpioInt
 - usb: usbfs: fix double-free of usb memory upon submiturb error
 - Revert "USB: rio500: simplify locking"
 - usb: iowarrior: fix deadlock on disconnect
 - sound: fix a memory leak bug
 - [arm64,mips/octeon] mmc: cavium: Set the correct dma max segment size for
   mmc_host
 - [arm64,mips/octeon] mmc: cavium: Add the missing dma unmap when the dma
   has finished.
 - loop: set PF_MEMALLOC_NOIO for the worker thread
 - bdev: Fixup error handling in blkdev_get() (Closes: #934378)
 - Input: usbtouchscreen - initialize PM mutex before using it
 - Input: elantech - enable SMBus on new (2018+) systems
 - [x86] Input: synaptics - enable RMI mode for HP Spectre X360
 - [x86] mm: Check for pfn instead of page in vmalloc_sync_one()
 - [x86] mm: Sync also unmappings in vmalloc_sync_all()
 - mm/vmalloc: Sync unmappings in __purge_vmap_area_lazy()
 - [s390x] perf annotate: Fix s390 gap between kernel end and module start
 - perf db-export: Fix thread__exec_comm()
 - [s390x] perf record: Fix module size on s390
 - [x86] purgatory: 

Bug#934378: marked as done (linux-image-5.2.0-2-amd64: linux-5.2.0-2 : Unable to mount CDROM)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#934378: fixed in linux 5.2.9-1
has caused the Debian Bug report #934378,
regarding linux-image-5.2.0-2-amd64: linux-5.2.0-2 : Unable to mount CDROM
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.)


-- 
934378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.2.7-1
Severity: normal
File: linux-image-5.2.0-2-amd64

Dear Maintainer,

With 5.2.0-2 (based on Upstream VANILLA 5.2.7), unable to mount CDROM by 
returning EBUSY with mount() system call.
With 5.2.0-1 (based on Upstream VANILLA 5.2.6), enable to mount CDROM.
This issue also happen at Upstream VANILLA 5.2.7 and 5.2.8.
See below log.
Regards,
Ohta.

---
Log:
~$ LC_ALL=C strace sudo mount /cdrom
execve("/usr/bin/sudo", ["sudo", "mount", "/cdrom"], 0x7ffdffb852e0 /* 68 vars 
*/) = 0
access("/etc/suid-debug", F_OK) = -1 ENOENT (No such file or directory)
brk(NULL)   = 0x558f257ff000
fcntl(0, F_GETFD)   = 0
fcntl(1, F_GETFD)   = 0
fcntl(2, F_GETFD)   = 0
access("/etc/suid-debug", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/sudo/tls/x86_64/x86_64/libaudit.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/sudo/tls/x86_64/x86_64", 0x7ffda774d260) = -1 ENOENT (No such 
file or directory)
openat(AT_FDCWD, "/usr/lib/sudo/tls/x86_64/libaudit.so.1", O_RDONLY|O_CLOEXEC) 
= -1 ENOENT (No such file or directory)
stat("/usr/lib/sudo/tls/x86_64", 0x7ffda774d260) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/usr/lib/sudo/tls/x86_64/libaudit.so.1", O_RDONLY|O_CLOEXEC) 
= -1 ENOENT (No such file or directory)
stat("/usr/lib/sudo/tls/x86_64", 0x7ffda774d260) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/usr/lib/sudo/tls/libaudit.so.1", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
stat("/usr/lib/sudo/tls", 0x7ffda774d260) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/usr/lib/sudo/x86_64/x86_64/libaudit.so.1", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
stat("/usr/lib/sudo/x86_64/x86_64", 0x7ffda774d260) = -1 ENOENT (No such file 
or directory)
openat(AT_FDCWD, "/usr/lib/sudo/x86_64/libaudit.so.1", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
stat("/usr/lib/sudo/x86_64", 0x7ffda774d260) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/usr/lib/sudo/x86_64/libaudit.so.1", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
stat("/usr/lib/sudo/x86_64", 0x7ffda774d260) = -1 ENOENT (No such file or 
directory)
openat(AT_FDCWD, "/usr/lib/sudo/libaudit.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT 
(No such file or directory)
stat("/usr/lib/sudo", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=594037, ...}) = 0
mmap(NULL, 594037, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f835ded1000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libaudit.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\3205\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=128944, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f835decf000
mmap(NULL, 172200, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f835dea4000
mprotect(0x7f835dea7000, 114688, PROT_NONE) = 0
mmap(0x7f835dea7000, 28672, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7f835dea7000
mmap(0x7f835deae000, 81920, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0xa000) = 0x7f835deae000
mmap(0x7f835dec3000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e000) = 0x7f835dec3000
mmap(0x7f835dec5000, 37032, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f835dec5000
close(3)= 0
openat(AT_FDCWD, "/usr/lib/sudo/libselinux.so.1", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libselinux.so.1", O_RDONLY|O_CLOEXEC) = 
3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\20|\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=167624, ...}) = 0
mmap(NULL, 179184, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f835de78000

Bug#934309: marked as done (linux-image-5.2.0-1-amd64-unsigned: suggesting INTEL_IOMMU_DEFAULT_ON)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#934309: fixed in linux 5.2.9-1
has caused the Debian Bug report #934309,
regarding linux-image-5.2.0-1-amd64-unsigned: suggesting INTEL_IOMMU_DEFAULT_ON
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.)


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

Dear Maintainer,

Without hardware IOMMU, heavy IO traffic sometimes causes
"swiotlb buffer is full" from kernel/dma/swiotlb.c.
Then an error is returned to a device driver calling dma_map_sg()
or something similar. Some device drivers (e.g. ehci-pci.c) do
not handle failures from dma_map_*() functions, and failures
of assigning DMA memories often lead undesirable behaviors.
Enablement of hardware IOMMU reduces possiblity of "swiotlb buffer is full".

I'd like to request to consider INTEL_IOMMU_DEFAULT_ON.
AMD IOMMU seems to be enabled by default, btw.

Best regards,
Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.2.0-1-amd64 (debian-kernel@lists.debian.org) (gcc
version 8.3.0 (Debian 8.3.0-19)) #1 SMP Debian 5.2.6-1 (2019-08-05)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.2.0-1-amd64
root=UUID=12f1110c-5548-452b-ba7e-b995b8aa7f45 ro i915.fastboot=1
swiotlb=noforce iommu=force,merge,nopanic,nopt intel_iommu=on
cgoup_no_v1=all systemd.unified_cgroup_hierarchy=1
systemd.show_status=1

** Tainted: E (8192)
 * Unsigned module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Panasonic Corporation
product_name: CFSZ6-1L
product_version: 001
chassis_vendor: Panasonic Corporation
chassis_version: 001
bios_vendor: American Megatrends Inc.
bios_version: V1.11L10
board_vendor: Panasonic Corporation
board_name: CFSZ6-1L
board_version: 1

** Loaded modules:
ctr(E)
ccm(E)
cmac(E)
cpufreq_powersave(E)
cpufreq_userspace(E)
cpufreq_conservative(E)
bnep(E)
intel_rapl(E)
x86_pkg_temp_thermal(E)
intel_powerclamp(E)
coretemp(E)
kvm_intel(E)
kvm(E)
irqbypass(E)
crct10dif_pclmul(E)
crc32_pclmul(E)
ghash_clmulni_intel(E)
nls_ascii(E)
nls_cp437(E)
vfat(E)
fat(E)
arc4(E)
snd_hda_codec_hdmi(E)
snd_soc_skl(E)
snd_soc_skl_ipc(E)
snd_soc_sst_ipc(E)
cdc_mbim(E)
snd_hda_codec_realtek(E)
btusb(E)
snd_soc_sst_dsp(E)
btrtl(E)
btbcm(E)
snd_hda_codec_generic(E)
cdc_wdm(E)
btintel(E)
snd_hda_ext_core(E)
ledtrig_audio(E)
snd_soc_acpi_intel_match(E)
snd_soc_acpi(E)
snd_soc_core(E)
qcserial(E)
bluetooth(E)
usb_wwan(E)
cdc_ncm(E)
snd_compress(E)
efi_pstore(E)
aesni_intel(E)
usbnet(E)
mii(E)
snd_hda_intel(E)
usbserial(E)
aes_x86_64(E)
crypto_simd(E)
cryptd(E)
glue_helper(E)
intel_cstate(E)
uvcvideo(E)
iwlmvm(E)
snd_hda_codec(E)
videobuf2_vmalloc(E)
videobuf2_memops(E)
intel_uncore(E)
videobuf2_v4l2(E)
mac80211(E)
iTCO_wdt(E)
intel_rapl_perf(E)
videobuf2_common(E)
snd_hda_core(E)
serio_raw(E)
iTCO_vendor_support(E)
snd_hwdep(E)
videodev(E)
watchdog(E)
drbg(E)
iwlwifi(E)
media(E)
snd_pcm(E)
efivars(E)
pcspkr(E)
snd_timer(E)
ansi_cprng(E)
snd(E)
soundcore(E)
cfg80211(E)
tpm_crb(E)
ecdh_generic(E)
ecc(E)
rfkill(E)
sg(E)
mei_me(E)
processor_thermal_device(E)
mei(E)
intel_soc_dts_iosf(E)
intel_pch_thermal(E)
battery(E)
acpi_als(E)
kfifo_buf(E)
industrialio(E)
int3403_thermal(E)
int340x_thermal_zone(E)
tpm_tis(E)
tpm_tis_core(E)
panasonic_laptop(E)
int3406_thermal(E)
tpm(E)
sparse_keymap(E)
rng_core(E)
int3400_thermal(E)
acpi_pad(E)
acpi_thermal_rel(E)
ac(E)
pcc_cpufreq(E)
evdev(E)
joydev(E)
parport_pc(E)
ppdev(E)
lp(E)
parport(E)
efivarfs(E)
ip_tables(E)
x_tables(E)
autofs4(E)
ext4(E)
crc16(E)
mbcache(E)
jbd2(E)
crc32c_generic(E)
sr_mod(E)
cdrom(E)
sd_mod(E)
ahci(E)
libahci(E)
crc32c_intel(E)
i915(E)
psmouse(E)
sdhci_pci(E)
xhci_pci(E)
i2c_algo_bit(E)
cqhci(E)
xhci_hcd(E)
libata(E)
drm_kms_helper(E)
e1000e(E)
scsi_mod(E)
i2c_i801(E)
sdhci(E)
mmc_core(E)
usbcore(E)
drm(E)
usb_common(E)
fan(E)
video(E)
button(E)

** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host

Bug#934848: marked as done (linux-image-4.19.0-5-amd64: The Cavium PTP device driver is always loaded)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:13 +
with message-id 
and subject line Bug#934848: fixed in linux 5.2.9-1
has caused the Debian Bug report #934848,
regarding linux-image-4.19.0-5-amd64: The Cavium PTP device driver is always 
loaded
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.)


-- 
934848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.37-5+deb10u2
Severity: normal

Dear Maintainer,

The Cavium PTP coprocess as PTP clock driver is rarely if ever
present on x86 systems, yet the Debian kernel config has it enabled.
Noticed this as driver in /sys/bus/pci/drivers on a standard x86 server.

The fix is simple, since this is a PCI device and can be built as
a module, just change the kernel config to build as module.
CONFIG_CAVIUM_PTP=m

-- Package-specific info:
** Version:
Linux version 4.19.0-5-amd64 (debian-kernel@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 
root=UUID=ae541fd6-fbff-48ce-ba8b-57840d9992d0 ro quiet

** Not tainted

** Kernel log:
[   14.102093] sd 1:0:0:0: Attached scsi generic sg2 type 0
[   14.102134] sr 8:0:0:0: Attached scsi generic sg3 type 5
[   14.102998] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   14.120054] input: PC Speaker as /devices/platform/pcspkr/input/input8
[   14.139416] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 655360 ms 
ovfl timer
[   14.139418] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[   14.139419] RAPL PMU: hw unit of domain package 2^-14 Joules
[   14.139420] RAPL PMU: hw unit of domain dram 2^-16 Joules
[   14.152308] EFI Variables Facility v0.08 2004-May-17
[   14.159835] pstore: Registered efi as persistent store backend
[   14.160040] systemd-journald[420]: Received request to flush runtime journal 
from PID 1
[   14.171072] Loading iSCSI transport class v2.0-870.
[   14.172013] checking generic (fa00 50) vs hw (fa00 100)
[   14.172014] fb: switching to astdrmfb from EFI VGA
[   14.172050] Console: switching to colour dummy device 80x25
[   14.172494] [drm] Using P2A bridge for configuration
[   14.172497] [drm] AST 2400 detected
[   14.172507] [drm] Analog VGA only
[   14.172521] [drm] dram MCLK=408 Mhz type=1 bus_width=16 size=0100
[   14.173232] snd_hda_intel :00:1b.0: enabling device (0140 -> 0142)
[   14.173335] [TTM] Zone  kernel: Available graphics memory: 16408614 kiB
[   14.173336] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[   14.173337] [TTM] Initializing pool allocator
[   14.173339] [TTM] Initializing DMA pool allocator
[   14.177685] fbcon: astdrmfb (fb0) is primary device
[   14.198073] Console: switching to colour frame buffer device 128x48
[   14.216339] ast :0a:00.0: fb0: astdrmfb frame buffer device
[   14.227981] iscsi: registered transport (iser)
[   14.254552] [drm] Initialized ast 0.1.0 20120228 for :0a:00.0 on minor 0
[   14.254794] snd_hda_codec_realtek hdaudioC0D0: ALC1150: SKU not ready 
0x
[   14.255267] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC1150: 
line_outs=3 (0x14/0x15/0x16/0x0/0x0) type:line
[   14.255268] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   14.255269] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x1b/0x0/0x0/0x0/0x0)
[   14.255269] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   14.255270] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[   14.255270] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   14.255271] snd_hda_codec_realtek hdaudioC0D0:  Front Mic=0x19
[   14.255272] snd_hda_codec_realtek hdaudioC0D0:  Rear Mic=0x18
[   14.255273] snd_hda_codec_realtek hdaudioC0D0:  Line=0x1a
[   14.266764] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card0/input9
[   14.275334] input: HDA Intel PCH Front Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input10
[   14.275396] input: HDA Intel PCH Rear Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input11
[   14.275468] input: HDA Intel PCH Line as 
/devices/pci:00/:00:1b.0/sound/card0/input12
[   14.275511] input: HDA Intel PCH Line Out Front as 
/devices/pci:00/:00:1b.0/sound/card0/input13
[   14.275578] input: HDA Intel PCH Line Out Surround as 
/devices/pci:00/:00:1b.0/sound/card0/input14
[   14.275636] input: HDA Intel PCH Line Out CLFE as 
/devices/pci:00/:00:1b.0/sound/card0/input15
[   14.275688] input: 

Bug#934824: marked as done (bug script doesn't grok missing /e/n/i)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:13 +
with message-id 
and subject line Bug#934824: fixed in linux 5.2.9-1
has caused the Debian Bug report #934824,
regarding bug script doesn't grok missing /e/n/i
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.)


-- 
934824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.2.7-1
Severity: normal
File: /usr/share/bug/linux-image-5.2.0-2-amd64/script

Hi,

I have long purged ifupdown from my system, there is no
/etc/network/interfaces. The bug script doesn't handle this situation:

Please select tags: (one at a time) [none]
Gathering additional data, this may take a while...
Use sudo to read the kernel log? y
[sudo] password for mh:
Include network configuration and status from this computer? y
/usr/share/bug/linux-image-5.2.0-2-amd64/include-network: line 7: 
/etc/network/interfaces: No such file or directory
The package bug script /usr/share/bug/linux-image-5.2.0-2-amd64/script exited 
with an error status (return code = 256). Do you still want to file a report? 
[y|N|q|?]?

The script should catch this situation and continue its work.

Greetings
Marc

-- Package-specific info:
** Version:
Linux version 5.2.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 
(Debian 8.3.0-19)) #1 SMP Debian 5.2.7-1 (2019-08-07)

** Command line:
BOOT_IMAGE=/vmlinuz-5.2.0-2-amd64 root=/dev/mapper/dropbtr0 ro 
rootflags=subvol=drop-root quiet splash

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 20F5S5X100
product_version: ThinkPad X260
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: R02ET63W (1.36 )
board_vendor: LENOVO
board_name: 20F5S5X100
board_version: 0B98417 WIN

** Loaded modules:
hid_generic
usbhid
hid
tun
ctr
ccm
rfcomm
cpufreq_userspace
cpufreq_powersave
cpufreq_conservative
cdc_mbim
cdc_wdm
cdc_ncm
cmac
bnep
fuse
cdc_ether
option
usbnet
mii
usb_wwan
usbserial
btusb
btrtl
btbcm
btintel
bluetooth
drbg
ansi_cprng
ecdh_generic
ecc
bridge
stp
llc
dummy
ip6t_REJECT
nf_reject_ipv6
arc4
ip6_tables
nft_chain_nat
xt_MASQUERADE
nf_nat
msr
xt_TCPMSS
intel_rapl
snd_soc_skl
snd_hda_codec_hdmi
iwlmvm
snd_soc_skl_ipc
snd_soc_sst_ipc
snd_soc_sst_dsp
nft_counter
snd_hda_ext_core
x86_pkg_temp_thermal
intel_powerclamp
snd_soc_acpi_intel_match
snd_soc_acpi
mac80211
kvm_intel
snd_hda_codec_realtek
ipt_REJECT
nf_reject_ipv4
snd_soc_core
snd_hda_codec_generic
mei_wdt
xt_tcpudp
snd_compress
kvm
snd_hda_intel
iwlwifi
xt_conntrack
snd_hda_codec
irqbypass
joydev
nf_conntrack
nf_defrag_ipv6
intel_cstate
iTCO_wdt
nf_defrag_ipv4
cfg80211
rtsx_pci_ms
iTCO_vendor_support
intel_uncore
snd_hda_core
sg
intel_rapl_perf
wmi_bmof
watchdog
nft_compat
snd_hwdep
memstick
serio_raw
tpm_tis
thinkpad_acpi
snd_pcm
mei_me
tpm_tis_core
snd_timer
nvram
mei
ledtrig_audio
intel_pch_thermal
tpm
snd
pcc_cpufreq
soundcore
rng_core
nf_tables
rfkill
ac
battery
evdev
nfnetlink
tcp_bbr
sch_fq
nfsd
coretemp
loop
parport_pc
auth_rpcgss
ppdev
lp
nfs_acl
lockd
parport
grace
sunrpc
ip_tables
x_tables
autofs4
btrfs
zstd_decompress
zstd_compress
ext4
crc16
mbcache
jbd2
algif_skcipher
af_alg
dm_crypt
dm_mod
uas
usb_storage
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
crc32c_generic
raid1
raid0
multipath
linear
md_mod
sd_mod
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
i915
rtsx_pci_sdmmc
mmc_core
aesni_intel
i2c_algo_bit
drm_kms_helper
aes_x86_64
crypto_simd
cryptd
glue_helper
psmouse
ahci
xhci_pci
drm
libahci
xhci_hcd
libata
e1000e
i2c_i801
usbcore
scsi_mod
rtsx_pci
mfd_core
usb_common
wmi
video
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th 
Gen Core Processor Host Bridge/DRAM Registers [8086:1904] (rev 08)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Host Bridge/DRAM Registers [17aa:504a]
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: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Skylake GT2 [HD 
Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:504a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- 

Bug#934335: marked as done (BUG: kernel NULL pointer dereference)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#934304: fixed in linux 5.2.9-1
has caused the Debian Bug report #934304,
regarding BUG: kernel NULL pointer dereference
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.)


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

Hi!

With the new 5.2.0 kernel I did try to run powertop and got this:

modprobe cpufreq_stats failed

Taking a look at dmesg it's possible to see:

=
[   24.916656] BUG: kernel NULL pointer dereference, address: 
[   24.916663] #PF: supervisor instruction fetch in kernel mode
[   24.916665] #PF: error_code(0x0010) - not-present page
[   24.916668] PGD 0 P4D 0 
[   24.916673] Oops: 0010 [#2] SMP PTI
[   24.916678] CPU: 3 PID: 15482 Comm: powertop Tainted: G  D   
5.2.0-2-amd64 #1 Debian 5.2.7-1
[   24.916681] Hardware name: Dell Inc.  Dell System XPS L502X/0MY6GN, 
BIOS A12 09/07/2012
[   24.916685] RIP: 0010:0x0
[   24.916691] Code: Bad RIP value.
[   24.916694] RSP: 0018:b618011efcd8 EFLAGS: 00010246
[   24.916697] RAX:  RBX: 9cc460f49600 RCX: 0001
[   24.916700] RDX: 9cc4740b9c00 RSI: 9cc460f49600 RDI: 9cc475ba6060
[   24.916702] RBP: 9cc475ba6060 R08:  R09: 
[   24.916704] R10: 9cc475b59240 R11:  R12: 9cc460f49610
[   24.916706] R13: 9531cdd0 R14:  R15: 9cc460f49600
[   24.916710] FS:  7fa5b86b9fc0() GS:9cc4762c() 
knlGS:
[   24.916712] CS:  0010 DS:  ES:  CR0: 80050033
[   24.916715] CR2: ffd6 CR3: 00022ec82004 CR4: 000606e0
[   24.916718] Call Trace:
[   24.916726]  do_dentry_open+0x13a/0x370
[   24.916735]  path_openat+0x2c6/0x1480
[   24.916740]  ? terminate_walk+0xe6/0x100
[   24.916744]  ? path_lookupat.isra.48+0xa3/0x220
[   24.916751]  ? reuse_swap_page+0x105/0x320
[   24.916755]  do_filp_open+0x93/0x100
[   24.916760]  ? __check_object_size+0x15d/0x189
[   24.916766]  do_sys_open+0x184/0x220
[   24.916773]  do_syscall_64+0x53/0x130
[   24.916779]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   24.916782] RIP: 0033:0x7fa5b88151ae
[   24.916786] Code: 25 00 00 41 00 3d 00 00 41 00 74 48 48 8d 05 59 65 0d 00 
8b 00 85 c0 75 69 89 f2 b8 01 01 00 00 48 89 fe bf 9c ff ff ff 0f 05 <48> 3d 00 
f0 ff ff 0f 87 a6 00 00 00 48 8b 4c 24 28 64 48 33 0c 25
[   24.916789] RSP: 002b:7ffdc0c65e80 EFLAGS: 0246 ORIG_RAX: 
0101
[   24.916792] RAX: ffda RBX: 56527315b870 RCX: 7fa5b88151ae
[   24.916794] RDX:  RSI: 7ffdc0c67230 RDI: ff9c
[   24.916796] RBP: 0008 R08: 0008 R09: 0001
[   24.916798] R10:  R11: 0246 R12: 7fa5b8c29805
[   24.916801] R13: 7fa5b8c29805 R14: 0001 R15: 565273163f00
[   24.916804] Modules linked in: msr btusb btrtl btbcm btintel bluetooth drbg 
ansi_cprng ecdh_generic ecc ctr ccm algif_aead des_generic algif_skcipher 
cpufreq_conservative cpufreq_powersave cmac cpufreq_userspace sha512_ssse3 
sha512_generic md4 algif_hash af_alg zram uvcvideo zsmalloc videobuf2_vmalloc 
videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass 
snd_hda_codec_hdmi snd_hda_codec_realtek arc4 crct10dif_pclmul 
snd_hda_codec_generic crc32_pclmul iwldvm ghash_clmulni_intel i915 mac80211 
snd_hda_intel aesni_intel snd_hda_codec iwlwifi snd_hda_core drm_kms_helper 
snd_hwdep aes_x86_64 crypto_simd snd_pcm cfg80211 cryptd drm dell_laptop 
glue_helper snd_timer ledtrig_audio dell_wmi intel_cstate iTCO_wdt evdev joydev 
intel_uncore mei_me dell_smbios iTCO_vendor_support snd mei i2c_algo_bit 
serio_raw pcc_cpufreq rfkill watchdog sg pcspkr sparse_keymap wmi_bmof 
soundcore dcdbas dell_wmi_descriptor
[   24.916861]  intel_rapl_perf dell_smo8800 battery ac button binfmt_misc 
ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic sr_mod cdrom 
sd_mod uas usb_storage hid_generic usbhid hid ahci libahci libata xhci_pci 
xhci_hcd ehci_pci scsi_mod ehci_hcd usbcore r8169 psmouse realtek crc32c_intel 
libphy lpc_ich i2c_i801 mfd_core wmi usb_common video
[   24.916892] CR2: 
[   24.916896] ---[ end trace ef320417b81ddc15 ]---
[   24.916899] RIP: 0010:0x0
[   24.916904] 

Bug#934991: marked as done (powertop: Powertop gets terminated with SIGKILL)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#934304: fixed in linux 5.2.9-1
has caused the Debian Bug report #934304,
regarding powertop: Powertop gets terminated with SIGKILL
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.)


-- 
934304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: powertop
Version: 2.10-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
Running `powertop` or `powertop --auto-tune`
   * What was the outcome of this action?
powertop gets terminated with SIGKILL (according to stack trace)
   * What outcome did you expect instead?
powertop should run normally

It worked fine on the previous unstable kernel (4.19.0-5 if I'm not mistaken).

Below is the output from `dmesg`:
---
[ 1047.234256] BUG: kernel NULL pointer dereference, address: 
[ 1047.234264] #PF: supervisor instruction fetch in kernel mode
[ 1047.234267] #PF: error_code(0x0010) - not-present page
[ 1047.234270] PGD 0 P4D 0
[ 1047.234277] Oops: 0010 [#14] SMP PTI
[ 1047.234283] CPU: 7 PID: 25879 Comm: powertop Tainted: G  D   
5.2.0-2-amd64 #1 Debian 5.2.7-1
[ 1047.234287] Hardware name: LENOVO 20L8S8TB00/20L8S8TB00, BIOS N22ET50W (1.27 
) 11/07/2018
[ 1047.234293] RIP: 0010:0x0
[ 1047.234301] Code: Bad RIP value.
[ 1047.234304] RSP: 0018:b76b0ae97cd8 EFLAGS: 00010246
[ 1047.234308] RAX:  RBX: 9f55ab10de00 RCX: 0001
[ 1047.234311] RDX: 9f55de602c00 RSI: 9f55ab10de00 RDI: 9f55e0f2dbc0
[ 1047.234314] RBP: 9f55e0f2dbc0 R08:  R09: 
[ 1047.234317] R10: 9f55e0edd9c0 R11:  R12: 9f55ab10de10
[ 1047.234319] R13: a6d1cdd0 R14:  R15: 9f55ab10de00
[ 1047.234324] FS:  7f9ac557a740() GS:9f55e15c() 
knlGS:
[ 1047.234327] CS:  0010 DS:  ES:  CR0: 80050033
[ 1047.234330] CR2: ffd6 CR3: 000451108002 CR4: 003606e0
[ 1047.234333] DR0:  DR1:  DR2: 
[ 1047.234336] DR3:  DR6: fffe0ff0 DR7: 0400
[ 1047.234338] Call Trace:
[ 1047.234350]  do_dentry_open+0x13a/0x370
[ 1047.234360]  path_openat+0x2c6/0x1480
[ 1047.234366]  ? terminate_walk+0xe6/0x100
[ 1047.234372]  ? path_lookupat.isra.48+0xa3/0x220
[ 1047.234379]  ? reuse_swap_page+0x105/0x320
[ 1047.234386]  do_filp_open+0x93/0x100
[ 1047.234393]  ? __check_object_size+0x15d/0x189
[ 1047.234401]  do_sys_open+0x184/0x220
[ 1047.234409]  do_syscall_64+0x53/0x130
[ 1047.234417]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 1047.234422] RIP: 0033:0x7f9ac56d71ae
[ 1047.234427] Code: 25 00 00 41 00 3d 00 00 41 00 74 48 48 8d 05 59 65 0d 00 
8b 00 85 c0 75 69 89 f2 b8 01 01 00 00 48 89 fe bf 9c ff
 ff ff 0f 05 <48> 3d 00 f0 ff ff 0f 87 a6 00 00 00 48 8b 4c 24 28 64 48 33 0c 25
[ 1047.234430] RSP: 002b:7ffeb3e55600 EFLAGS: 0246 ORIG_RAX: 
0101
[ 1047.234435] RAX: ffda RBX: 5602c630e870 RCX: 7f9ac56d71ae
[ 1047.234437] RDX:  RSI: 7ffeb3e569a0 RDI: ff9c
[ 1047.234440] RBP: 0008 R08: 0008 R09: 0001
[ 1047.234443] R10:  R11: 0246 R12: 7f9ac5aed805
[ 1047.234445] R13: 7f9ac5aed805 R14: 0001 R15: 5602c4f2efd0
[ 1047.234449] Modules linked in: ctr ccm fuse msr overlay arc4 intel_rapl 
iwlmvm mac80211 snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc
 x86_pkg_temp_thermal snd_soc_sst_dsp intel_powerclamp btusb coretemp 
snd_hda_ext_core iwlwifi mei_wdt snd_hda_codec_hdmi snd_soc_acpi
_intel_match kvm_intel snd_soc_acpi snd_hda_codec_realtek nls_ascii btrtl 
snd_hda_codec_generic snd_soc_core nls_cp437 btbcm btintel k
vm vfat fat bluetooth irqbypass snd_compress efi_pstore uvcvideo snd_hda_intel 
intel_cstate videobuf2_vmalloc elan_i2c sg wmi_bmof joy
dev intel_uncore serio_raw videobuf2_memops intel_rapl_perf snd_hda_codec 
efivars videobuf2_v4l2 drbg cfg80211 pcspkr snd_hda_core vid
eobuf2_common iTCO_wdt iTCO_vendor_support thinkpad_acpi watchdog snd_hwdep 
videodev snd_pcm nvram snd_timer hid_multitouch ledtrig_au
dio ansi_cprng media mei_me snd ucsi_acpi ecdh_generic soundcore typec_ucsi 

Bug#934369: marked as done (linux-image-5.2.0-1-amd64-unsigned: powertop -i 10 always causes kernel NULL pointer dereference)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#934304: fixed in linux 5.2.9-1
has caused the Debian Bug report #934304,
regarding linux-image-5.2.0-1-amd64-unsigned: powertop -i 10 always causes 
kernel NULL pointer dereference
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.)


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

Dear Maintainer,

When I run "powertop -i 10" it always triggers "kernel NULL pointer 
dereference".
I observed this issue on two different models on Panasonic notbooks.
I can always reproduce this. dmesg output is pasted below.

Best regards,
Ryutaroh Matsumoto

[ 1653.251287] BUG: kernel NULL pointer dereference, address: 
[ 1653.252724] #PF: supervisor instruction fetch in kernel mode
[ 1653.254161] #PF: error_code(0x0010) - not-present page
[ 1653.255580] PGD 0 P4D 0 
[ 1653.256875] Oops: 0010 [#1] SMP PTI
[ 1653.258313] CPU: 2 PID: 1927 Comm: powertop Tainted: GE 
5.2.0-1-amd64 #1 Debian 5.2.6-1
[ 1653.259375] Hardware name: Panasonic Corporation CF-LX3YEUCU/CFLX3-1L, BIOS 
V1.11L16 10/29/2013
[ 1653.260208] RIP: 0010:0x0
[ 1653.260973] Code: Bad RIP value.
[ 1653.261694] RSP: 0018:b2328376bcd8 EFLAGS: 00010246
[ 1653.262425] RAX:  RBX: 904c161b7400 RCX: 0001
[ 1653.263141] RDX: 904c15e4bc00 RSI: 904c161b7400 RDI: 904c1735e2b0
[ 1653.263854] RBP: 904c1735e2b0 R08:  R09: 
[ 1653.264565] R10: 904c17311840 R11:  R12: 904c161b7410
[ 1653.265276] R13: b591cbf0 R14:  R15: 904c161b7400
[ 1653.265976] FS:  7f8f41cdcfc0() GS:904c1790() 
knlGS:
[ 1653.266708] CS:  0010 DS:  ES:  CR0: 80050033
[ 1653.267420] CR2: ffd6 CR3: 0001a61d6003 CR4: 001606e0
[ 1653.268141] Call Trace:
[ 1653.268861]  do_dentry_open+0x13a/0x370
[ 1653.269588]  path_openat+0x2c6/0x1480
[ 1653.270337]  ? terminate_walk+0xe6/0x100
[ 1653.271059]  ? path_lookupat.isra.48+0xa3/0x220
[ 1653.271791]  ? reuse_swap_page+0x105/0x320
[ 1653.272513]  do_filp_open+0x93/0x100
[ 1653.273226]  ? __check_object_size+0x15d/0x189
[ 1653.273945]  do_sys_open+0x184/0x220
[ 1653.274690]  do_syscall_64+0x53/0x130
[ 1653.275426]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 1653.276170] RIP: 0033:0x7f8f420391ae
[ 1653.276909] Code: 25 00 00 41 00 3d 00 00 41 00 74 48 48 8d 05 59 65 0d 00 
8b 00 85 c0 75 69 89 f2 b8 01 01 00 00 48 89 fe bf 9c ff ff ff 0f 05 <48> 3d 00 
f0 ff ff 0f 87 a6 00 00 00 48 8b 4c 24 28 64 48 33 0c 25
[ 1653.278535] RSP: 002b:7ffc883a15b0 EFLAGS: 0246 ORIG_RAX: 
0101
[ 1653.279348] RAX: ffda RBX: 56490228b8b0 RCX: 7f8f420391ae
[ 1653.280172] RDX:  RSI: 7ffc883a2960 RDI: ff9c
[ 1653.281004] RBP: 0008 R08: 0008 R09: 0001
[ 1653.281834] R10:  R11: 0246 R12: 7f8f42405835
[ 1653.282691] R13: 7f8f42405835 R14: 0001 R15: 5649022971a0
[ 1653.283531] Modules linked in: msr(E) xt_CHECKSUM(E) xt_MASQUERADE(E) 
xt_conntrack(E) ipt_REJECT(E) nf_reject_ipv4(E) xt_tcpudp(E) nft_compat(E) 
tun(E) bridge(E) stp(E) llc(E) nft_counter(E) nft_chain_nat(E) nf_nat(E) 
nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) nf_tables(E) nfnetlink(E) 
ctr(E) ccm(E) cmac(E) bnep(E) nls_ascii(E) nls_cp437(E) intel_rapl(E) vfat(E) 
x86_pkg_temp_thermal(E) intel_powerclamp(E) fat(E) coretemp(E) kvm_intel(E) 
kvm(E) irqbypass(E) btusb(E) arc4(E) btrtl(E) btbcm(E) btintel(E) 
crct10dif_pclmul(E) crc32_pclmul(E) ghash_clmulni_intel(E) aesni_intel(E) 
aes_x86_64(E) bluetooth(E) iwlmvm(E) uvcvideo(E) videobuf2_vmalloc(E) 
videobuf2_memops(E) videobuf2_v4l2(E) crypto_simd(E) mac80211(E) cryptd(E) 
drbg(E) videobuf2_common(E) glue_helper(E) videodev(E) ansi_cprng(E) 
acpi_als(E) ecdh_generic(E) ecc(E) kfifo_buf(E) media(E) iwlwifi(E) 
snd_hda_codec_realtek(E) snd_hda_codec_generic(E) ledtrig_audio(E) 
industrialio(E) snd_hda_codec_hdmi(E) efi_pstore(E)
[ 1653.283553]  snd_hda_intel(E) mei_me(E) intel_cstate(E) intel_uncore(E) 
snd_hda_codec(E) snd_hda_core(E) joydev(E) efivars(E) snd_hwdep(E) mei(E) 
pcspkr(E) serio_raw(E) panasonic_laptop(E) rmi_smbus(E) intel_rapl_perf(E) 
sparse_keymap(E) sg(E) rmi_core(E) snd_pcm(E) iTCO_wdt(E) 
iTCO_vendor_support(E) cfg80211(E) snd_timer(E) snd(E) 

Bug#934091: marked as done (Missing HID driver modules (Most are fairly new since 5.0 or so))

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#934091: fixed in linux 5.2.9-1
has caused the Debian Bug report #934091,
regarding Missing HID driver modules (Most are fairly new since 5.0 or so)
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.)


-- 
934091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:linux
Keyboards, leds, remote controls etc.
CONFIG_HID_BIGBEN_FF
CONFIG_HID_GFRM
CONFIG_HID_GT683R
CONFIG_HID_MACALLY
CONFIG_HID_VIEWSONIC
CONFIG_HID_MALTRON
CONFIG_HID_U2FZERO
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.2.9-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 934...@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, 18 Aug 2019 22:54:21 +0100
Source: linux
Architecture: source
Version: 5.2.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 908712 925766 931707 933963 934091 934304 934309 934378 934824 934848
Changes:
 linux (5.2.9-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.8
 - scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
 - libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
 - libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
 - ALSA: usb-audio: Sanity checks for each pipe and EP types
 - ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
 - HID: wacom: fix bit shift for Cintiq Companion 2
 - HID: Add quirk for HP X1200 PIXART OEM mouse
 - atm: iphase: Fix Spectre v1 vulnerability (CVE-2017-5753)
 - bnx2x: Disable multi-cos feature.
 - drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case (Closes: #908712)
 - ife: error out when nla attributes are empty
 - ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
 - ip6_tunnel: fix possible use-after-free on xmit
 - ipip: validate header length in ipip_tunnel_xmit
 - [armhf,arm64] mvpp2: fix panic on module removal
 - [armhf,arm64] mvpp2: refactor MTU change code
 - net: bridge: delete local fdb on device init failure
 - net: bridge: mcast: don't delete permanent entries when fast leave is
   enabled
 - net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
 - net: fix ifindex collision during namespace removal
 - net/mlx5e: always initialize frag->last_in_page
 - net/mlx5: Use reversed order when unregister devices
 - net: phy: fixed_phy: print gpio error only if gpio node is present
 - net: phy: mscc: initialize stats array
 - net: sched: Fix a possible null-pointer dereference in dequeue_func()
 - net sched: update vlan action for batched events operations
 - net: sched: use temporary variable for actions indexes
 - net/smc: do not schedule tx_work in SMC_CLOSED state
 - [armhf,arm64] net: stmmac: Use netif_tx_napi_add() for TX polling
   function
 - tipc: compat: allow tipc commands without arguments
 - tipc: fix unitilized skb list crash
 - tun: mark small packets as owned by the tap sock
 - net/mlx5: Fix modify_cq_in alignment
 - net/mlx5e: Prevent encap flow counter update async to user query
 - r8169: don't use MSI before RTL8168d
 - net: fix bpf_xdp_adjust_head regression for generic-XDP
 - [x86] hv_sock: Fix hang when a connection is closed
 - net: phy: fix race in genphy_update_link
 - net/smc: avoid fallback in case of non-blocking connect
 - rocker: fix memory leaks of fib_work on two error return paths
 - net/mlx5: Add missing RDMA_RX capabilities
 - net/mlx5e: Fix matching of speed to PRM link modes
 - compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
 - [x86] drm/i915/vbt: Fix VBT parsing for the PSR section
 - Revert "mac80211: set 

Bug#933963: marked as done (New rtw88 driver missing from 5.2 and above)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#933963: fixed in linux 5.2.9-1
has caused the Debian Bug report #933963,
regarding New rtw88 driver missing from 5.2 and above
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.)


-- 
933963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: linux
CONFIG_RTW88=m and related options should be set or a bunch of laptops are 
going to lose wifi support.

CONFIG_RTW88_PCI=m
CONFIG_RTW88_8822BE=y
CONFIG_RTW88_8822CE=y
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.2.9-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 933...@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, 18 Aug 2019 22:54:21 +0100
Source: linux
Architecture: source
Version: 5.2.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 908712 925766 931707 933963 934091 934304 934309 934378 934824 934848
Changes:
 linux (5.2.9-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.8
 - scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
 - libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
 - libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
 - ALSA: usb-audio: Sanity checks for each pipe and EP types
 - ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
 - HID: wacom: fix bit shift for Cintiq Companion 2
 - HID: Add quirk for HP X1200 PIXART OEM mouse
 - atm: iphase: Fix Spectre v1 vulnerability (CVE-2017-5753)
 - bnx2x: Disable multi-cos feature.
 - drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case (Closes: #908712)
 - ife: error out when nla attributes are empty
 - ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
 - ip6_tunnel: fix possible use-after-free on xmit
 - ipip: validate header length in ipip_tunnel_xmit
 - [armhf,arm64] mvpp2: fix panic on module removal
 - [armhf,arm64] mvpp2: refactor MTU change code
 - net: bridge: delete local fdb on device init failure
 - net: bridge: mcast: don't delete permanent entries when fast leave is
   enabled
 - net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
 - net: fix ifindex collision during namespace removal
 - net/mlx5e: always initialize frag->last_in_page
 - net/mlx5: Use reversed order when unregister devices
 - net: phy: fixed_phy: print gpio error only if gpio node is present
 - net: phy: mscc: initialize stats array
 - net: sched: Fix a possible null-pointer dereference in dequeue_func()
 - net sched: update vlan action for batched events operations
 - net: sched: use temporary variable for actions indexes
 - net/smc: do not schedule tx_work in SMC_CLOSED state
 - [armhf,arm64] net: stmmac: Use netif_tx_napi_add() for TX polling
   function
 - tipc: compat: allow tipc commands without arguments
 - tipc: fix unitilized skb list crash
 - tun: mark small packets as owned by the tap sock
 - net/mlx5: Fix modify_cq_in alignment
 - net/mlx5e: Prevent encap flow counter update async to user query
 - r8169: don't use MSI before RTL8168d
 - net: fix bpf_xdp_adjust_head regression for generic-XDP
 - [x86] hv_sock: Fix hang when a connection is closed
 - net: phy: fix race in genphy_update_link
 - net/smc: avoid fallback in case of non-blocking connect
 - rocker: fix memory leaks of fib_work on two error return paths
 - net/mlx5: Add missing RDMA_RX capabilities
 - net/mlx5e: Fix matching of speed to PRM link modes
 - compat_ioctl: pppoe: fix PPPOEIOCSFWD handling
 - [x86] drm/i915/vbt: Fix VBT parsing for the PSR section
 - Revert "mac80211: set NETIF_F_LLTX when using intermediate 

Bug#934304: marked as done (linux-image-5.2.0-2-amd64: powertop aborts on version 5.2)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#934304: fixed in linux 5.2.9-1
has caused the Debian Bug report #934304,
regarding linux-image-5.2.0-2-amd64: powertop aborts on version 5.2
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.)


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

Dear Maintainer,

starting with version 5.2.0-2, powertop aborts, version 4.19.0-5 is OK




-- Package-specific info:
** Version:
Linux version 5.2.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 
(Debian 8.3.0-19)) #1 SMP Debian 5.2.7-1 (2019-08-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.2.0-2-amd64 
root=UUID=62878f00-afec-4500-affc-1e8ecd1c996e ro 
resume=/dev/disk/by-label/swap quiet nohz_full=1,2,3,4,5,6,7

** Not tainted

** Kernel log:
[   20.627518] AVX version of gcm_enc/dec engaged.
[   20.627518] AES CTR mode by8 optimization enabled
[   21.042236] media: Linux media interface: v0.10
[   21.067768] Console: switching to colour frame buffer device 240x67
[   21.072152] videodev: Linux video capture interface: v2.00
[   21.089373] snd_hda_intel :00:1b.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   21.091896] i915 :00:02.0: fb0: i915drmfb frame buffer device
[   21.092045] nouveau :01:00.0: NVIDIA GF108 (0c1400a1)
[   21.126179] nouveau :01:00.0: bios: version 70.08.a9.00.01
[   21.233964] nouveau :01:00.0: fb: 1024 MiB DDR3
[   21.251083] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[   21.251084] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
[   21.251085] iwlwifi :03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
[   21.251086] iwlwifi :03:00.0: Detected Intel(R) Centrino(R) Advanced-N 
6205 AGN, REV=0xB0
[   21.263890] iwlwifi :03:00.0: reporting RF_KILL (radio disabled)
[   21.263910] iwlwifi :03:00.0: RF_KILL bit toggled to disable radio.
[   21.296811] vga_switcheroo: enabled
[   21.296902] [TTM] Zone  kernel: Available graphics memory: 4031184 KiB
[   21.296903] [TTM] Zone   dma32: Available graphics memory: 2097152 KiB
[   21.296904] [TTM] Initializing pool allocator
[   21.296907] [TTM] Initializing DMA pool allocator
[   21.296929] nouveau :01:00.0: DRM: VRAM: 1024 MiB
[   21.296930] nouveau :01:00.0: DRM: GART: 1048576 MiB
[   21.296933] nouveau :01:00.0: DRM: TMDS table version 2.0
[   21.296934] nouveau :01:00.0: DRM: DCB version 4.0
[   21.296935] nouveau :01:00.0: DRM: DCB outp 00: 02000300 
[   21.296937] nouveau :01:00.0: DRM: DCB conn 00: 
[   21.297651] nouveau :01:00.0: DRM: MM: using COPY0 for buffer copies
[   21.298157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   21.298158] [drm] Driver supports precise vblank timestamp query.
[   21.326637] snd_hda_codec_realtek hdaudioC0D0: ALC269VC: SKU not ready 
0x909701f0
[   21.326958] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC269VC: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   21.326959] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   21.326960] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x15/0x0/0x0/0x0/0x0)
[   21.326961] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   21.326961] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[   21.326962] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   21.326963] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
[   21.326964] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[   21.334017] nouveau :01:00.0: DRM: allocated 1024x768 fb: 0x6, bo 
292cc6e2
[   21.334071] nouveau :01:00.0: fb1: nouveaudrmfb frame buffer device
[   21.334182] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on 
minor 1
[   21.346638] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[   21.388017] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card0/input15
[   21.388100] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input16
[   21.388168] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input17
[   21.388252] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1b.0/sound/card0/input18
[   21.400578] uvcvideo: Found UVC 1.00 device FJ Camera (04f2:b302)
[   21.438250] uvcvideo 1-1.1:1.0: Entity type for entity Extension 3 was not 
initialized!
[   21.438254] uvcvideo 1-1.1:1.0: Entity 

Bug#931707: marked as done (linux: HW_RANDOM_OMAP disabled for arm64 --> please enable)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#931707: fixed in linux 5.2.9-1
has caused the Debian Bug report #931707,
regarding linux: HW_RANDOM_OMAP disabled for arm64 --> please enable
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.)


-- 
931707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Severity: normal

Dear Maintainer,

While testing Debian 10 on a Marvell 8040 SoC I found that the rng and SSH were
coming up extremely slow, taking over a minute to start.

This is caused by somebody disabling the rng driver for arm64 kernels a long 
time ago:
linux (4.14.13-1) unstable; urgency=medium
...
  [ Riku Voipio ]
  * [arm64] disable CONFIG_HW_RANDOM_OMAP until the IRQ storm bug is fixed

What is this IRQ storm bug? Has it been fixed? Can we re-enable this driver?

Yours sincerely
Josua Mayer

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.1.0-trunk-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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)
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.2.9-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 931...@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, 18 Aug 2019 22:54:21 +0100
Source: linux
Architecture: source
Version: 5.2.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 908712 925766 931707 933963 934091 934304 934309 934378 934824 934848
Changes:
 linux (5.2.9-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.8
 - scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure
 - libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
 - libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
 - ALSA: usb-audio: Sanity checks for each pipe and EP types
 - ALSA: usb-audio: Fix gpf in snd_usb_pipe_sanity_check
 - HID: wacom: fix bit shift for Cintiq Companion 2
 - HID: Add quirk for HP X1200 PIXART OEM mouse
 - atm: iphase: Fix Spectre v1 vulnerability (CVE-2017-5753)
 - bnx2x: Disable multi-cos feature.
 - drivers/net/ethernet/marvell/mvmdio.c: Fix non OF case (Closes: #908712)
 - ife: error out when nla attributes are empty
 - ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6
 - ip6_tunnel: fix possible use-after-free on xmit
 - ipip: validate header length in ipip_tunnel_xmit
 - [armhf,arm64] mvpp2: fix panic on module removal
 - [armhf,arm64] mvpp2: refactor MTU change code
 - net: bridge: delete local fdb on device init failure
 - net: bridge: mcast: don't delete permanent entries when fast leave is
   enabled
 - net: bridge: move default pvid init/deinit to NETDEV_REGISTER/UNREGISTER
 - net: fix ifindex collision during namespace removal
 - net/mlx5e: always initialize frag->last_in_page
 - net/mlx5: Use reversed order when unregister devices
 - net: phy: fixed_phy: print gpio error only if gpio node is present
 - net: phy: mscc: initialize stats array
 - net: sched: Fix a possible null-pointer dereference in dequeue_func()
 - net sched: update vlan action for batched events operations
 - net: sched: use temporary variable for actions indexes
 - net/smc: do not schedule tx_work in SMC_CLOSED state
 - [armhf,arm64] net: stmmac: Use netif_tx_napi_add() for TX polling
   function
 - tipc: compat: allow tipc commands without arguments
 - tipc: fix unitilized skb list crash
 - tun: mark small packets as owned by the tap sock

Bug#934292: marked as done (powertop: running powertop introduces "kernel NULL pointer dereference")

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#934304: fixed in linux 5.2.9-1
has caused the Debian Bug report #934304,
regarding powertop: running powertop introduces "kernel NULL pointer 
dereference"
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.)


-- 
934304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: powertop
Version: 2.8-1+b2
Severity: normal

Dear Maintainer,

Just tried to run `powertop` (after Linux 5.2 upgrade, but not sure if it
worked for me before, ever used it):

```
$ sudo powertop
modprobe cpufreq_stats failedCannot load from file
/var/cache/powertop/saved_results.powertop
Cannot load from file /var/cache/powertop/saved_parameters.powertop
File will be loaded after taking minimum number of measurement(s) with
battery only 
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask f
RAPL device for cpu 0
RAPL Using PowerCap Sysfs : Domain Mask f
Nutraukta (killed)
```

Meanwhile, on kernel.log:
```
Aug  9 11:24:47 vinco kernel: [ 6493.332451] BUG: kernel NULL pointer 
dereference, address: 
Aug  9 11:24:47 vinco kernel: [ 6493.332455] #PF: supervisor instruction fetch 
in kernel mode
Aug  9 11:24:47 vinco kernel: [ 6493.332456] #PF: error_code(0x0010) - 
not-present page
Aug  9 11:24:47 vinco kernel: [ 6493.332458] PGD 0 P4D 0 
Aug  9 11:24:47 vinco kernel: [ 6493.332460] Oops: 0010 [#12] SMP PTI
Aug  9 11:24:47 vinco kernel: [ 6493.332463] CPU: 3 PID: 20189 Comm: powertop 
Tainted: G  DOE 5.2.0-2-amd64 #1 Debian 5.2.7-1
Aug  9 11:24:47 vinco kernel: [ 6493.332464] Hardware name: ASUSTeK COMPUTER 
INC. N551JM/N551JM, BIOS N551JM.205 02/13/2015
Aug  9 11:24:47 vinco kernel: [ 6493.332467] RIP: 0010:0x0
Aug  9 11:24:47 vinco kernel: [ 6493.332470] Code: Bad RIP value.
Aug  9 11:24:47 vinco kernel: [ 6493.332471] RSP: 0018:a3da897dbcd8 EFLAGS: 
00010246
Aug  9 11:24:47 vinco kernel: [ 6493.332473] RAX:  RBX: 
8917f2e5f800 RCX: 0001
Aug  9 11:24:47 vinco kernel: [ 6493.332474] RDX: 891b5bd60c00 RSI: 
8917f2e5f800 RDI: 891b5e773090
Aug  9 11:24:47 vinco kernel: [ 6493.332475] RBP: 891b5e773090 R08: 
 R09: 
Aug  9 11:24:47 vinco kernel: [ 6493.332476] R10: 891b5e725d80 R11: 
 R12: 8917f2e5f810
Aug  9 11:24:47 vinco kernel: [ 6493.332477] R13: 9c11cdd0 R14: 
 R15: 8917f2e5f800
Aug  9 11:24:47 vinco kernel: [ 6493.332479] FS:  7f619c6befc0() 
GS:891b5ecc() knlGS:
Aug  9 11:24:47 vinco kernel: [ 6493.332480] CS:  0010 DS:  ES:  CR0: 
80050033
Aug  9 11:24:47 vinco kernel: [ 6493.332482] CR2: ffd6 CR3: 
000341aba001 CR4: 001626e0
Aug  9 11:24:47 vinco kernel: [ 6493.332483] Call Trace:
Aug  9 11:24:47 vinco kernel: [ 6493.332488]  do_dentry_open+0x13a/0x370
Aug  9 11:24:47 vinco kernel: [ 6493.332493]  path_openat+0x2c6/0x1480
Aug  9 11:24:47 vinco kernel: [ 6493.332496]  ? 
mem_cgroup_commit_charge+0x80/0x4d0
Aug  9 11:24:47 vinco kernel: [ 6493.332499]  do_filp_open+0x93/0x100
Aug  9 11:24:47 vinco kernel: [ 6493.332502]  ? __check_object_size+0x15d/0x189
Aug  9 11:24:47 vinco kernel: [ 6493.332505]  do_sys_open+0x184/0x220
Aug  9 11:24:47 vinco kernel: [ 6493.332509]  do_syscall_64+0x53/0x130
Aug  9 11:24:47 vinco kernel: [ 6493.332513]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug  9 11:24:47 vinco kernel: [ 6493.332515] RIP: 0033:0x7f619c81a1ae
Aug  9 11:24:47 vinco kernel: [ 6493.332517] Code: 25 00 00 41 00 3d 00 00 41 
00 74 48 48 8d 05 59 65 0d 00 8b 00 85 c0 75 69 89 f2 b8 01 01 00 00 48 89 fe 
bf 9c ff ff ff 0f 05 <48> 3d 00 f0 ff ff 0f 87 a6 00 00 00 48 8b 4c 24 28 64 48 
33 0c 25
Aug  9 11:24:47 vinco kernel: [ 6493.332518] RSP: 002b:7ffdd911d5b0 EFLAGS: 
0246 ORIG_RAX: 0101
Aug  9 11:24:47 vinco kernel: [ 6493.332520] RAX: ffda RBX: 
561f01e77870 RCX: 7f619c81a1ae
Aug  9 11:24:47 vinco kernel: [ 6493.332521] RDX:  RSI: 
7ffdd911e960 RDI: ff9c
Aug  9 11:24:47 vinco kernel: [ 6493.332522] RBP: 0008 R08: 
0008 R09: 0001
Aug  9 11:24:47 vinco kernel: [ 6493.332523] R10:  R11: 
0246 R12: 7f619cc2e805
Aug  9 11:24:47 vinco kernel: [ 6493.332524] R13: 7f619cc2e805 R14: 
0001 R15: 561f01e82130
Aug  9 11:24:47 vinco kernel: [ 6493.332526] Modules linked in: msr rfcomm 

Bug#925766: marked as done (linux: ftbfs with GCC-9)

2019-08-18 Thread Debian Bug Tracking System
Your message dated Mon, 19 Aug 2019 05:32:12 +
with message-id 
and subject line Bug#925766: fixed in linux 5.2.9-1
has caused the Debian Bug report #925766,
regarding linux: ftbfs with GCC-9
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.)


-- 
925766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.19.28-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/linux_4.19.28-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-sched.1+ 
perf-sched.txt && \
mv /<>/debian/build/build-tools/tools/perf/perf-sched.1+ 
/<>/debian/build/build-tools/tools/perf/perf-sched.1
rm -f /<>/debian/build/build-tools/tools/perf/perf-kvm.1+ 
/<>/debian/build/build-tools/tools/perf/perf-kvm.1 && \
asciidoctor -b manpage -d manpage \
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-kvm.1+ perf-kvm.txt 
&& \
mv /<>/debian/build/build-tools/tools/perf/perf-kvm.1+ 
/<>/debian/build/build-tools/tools/perf/perf-kvm.1
rm -f /<>/debian/build/build-tools/tools/perf/perf-annotate.1+ 
/<>/debian/build/build-tools/tools/perf/perf-annotate.1 && \
asciidoctor -b manpage -d manpage \
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-annotate.1+ 
perf-annotate.txt && \
mv /<>/debian/build/build-tools/tools/perf/perf-annotate.1+ 
/<>/debian/build/build-tools/tools/perf/perf-annotate.1
rm -f /<>/debian/build/build-tools/tools/perf/perf-top.1+ 
/<>/debian/build/build-tools/tools/perf/perf-top.1 && \
asciidoctor -b manpage -d manpage \
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-top.1+ perf-top.txt 
&& \
mv /<>/debian/build/build-tools/tools/perf/perf-top.1+ 
/<>/debian/build/build-tools/tools/perf/perf-top.1
rm -f /<>/debian/build/build-tools/tools/perf/perf-stat.1+ 
/<>/debian/build/build-tools/tools/perf/perf-stat.1 && \
asciidoctor -b manpage -d manpage \
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-stat.1+ perf-stat.txt 
&& \
mv /<>/debian/build/build-tools/tools/perf/perf-stat.1+ 
/<>/debian/build/build-tools/tools/perf/perf-stat.1
rm -f /<>/debian/build/build-tools/tools/perf/perf-ftrace.1+ 
/<>/debian/build/build-tools/tools/perf/perf-ftrace.1 && \
asciidoctor -b manpage -d manpage \
-a compat-mode -I. -rasciidoctor-extensions -a mansource="perf" -a 
manmanual="perf Manual" -a revdate=2019-03-15 -aperf_version= -o 
/<>/debian/build/build-tools/tools/perf/perf-ftrace.1+ 
perf-ftrace.txt && \
mv /<>/debian/build/build-tools/tools/perf/perf-ftrace.1+ 

Processing of linux_5.2.9-1_source.changes

2019-08-18 Thread Debian FTP Masters
linux_5.2.9-1_source.changes uploaded successfully to localhost
along with the files:
  linux_5.2.9-1.dsc
  linux_5.2.9.orig.tar.xz
  linux_5.2.9-1.debian.tar.xz
  linux_5.2.9-1_source.buildinfo

Greetings,

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



Processed: found 929557 in 5.0.1-1~exp1

2019-08-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 929557 5.0.1-1~exp1
Bug #929557 [src:linux] linux: restore __kernel_fpu needed for zfs for 
AES-NI/AVX support [mainline not in debian yet]
Marked as found in versions linux/5.0.1-1~exp1.
> thanks
Stopping processing here.

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



Processed: Re: Bug#934331: linux: backport "dm: disable DISCARD if the underlying storage no longer supports it"?

2019-08-18 Thread Debian Bug Tracking System
Processing control commands:

> forwarded 934331 
> https://lore.kernel.org/stable/20190818155941.GA26766@eldamar.local/
Bug #934331 [linux] linux: backport "dm: disable DISCARD if the underlying 
storage no longer supports it"?
Set Bug forwarded-to-address to 
'https://lore.kernel.org/stable/20190818155941.GA26766@eldamar.local/'.

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



Bug#934331: linux: backport "dm: disable DISCARD if the underlying storage no longer supports it"?

2019-08-18 Thread Salvatore Bonaccorso
Control: forwarded 934331 
https://lore.kernel.org/stable/20190818155941.GA26766@eldamar.local/

Hi Chris,

On Fri, Aug 09, 2019 at 11:12:36PM +0200, Chris Hofstaedtler wrote:
> Package: linux
> Version: 4.9.168-1+deb9u4
> Severity: normal
> 
> Hi!
> 
> Today I ran into an issue that matches the description of upstream
> commit bcb44433bba5eaff293888ef22ffa07f1f0347d6:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bcb44433bba5eaff293888ef22ffa07f1f0347d6
> 
> > dm: disable DISCARD if the underlying storage no longer supports it
> >
> > Storage devices which report supporting discard commands like
> > WRITE_SAME_16 with unmap, but reject discard commands sent to the
> > storage device.  This is a clear storage firmware bug but it doesn't
> > change the fact that should a program cause discards to be sent to a
> > multipath device layered on this buggy storage, all paths can end up
> > failed at the same time from the discards, causing possible I/O loss.
> >
> > The first discard to a path will fail with Illegal Request, Invalid
> > field in cdb, e.g.:
> >  kernel: sd 8:0:8:19: [sdfn] tag#0 FAILED Result: hostbyte=DID_OK 
> > driverbyte=DRIVER_SENSE
> >  kernel: sd 8:0:8:19: [sdfn] tag#0 Sense Key : Illegal Request [current]
> >  kernel: sd 8:0:8:19: [sdfn] tag#0 Add. Sense: Invalid field in cdb
> >  kernel: sd 8:0:8:19: [sdfn] tag#0 CDB: Write same(16) 93 08 00 00 00 00 00 
> > a0 08 00 00 00 80 00 00 00
> >  kernel: blk_update_request: critical target error, dev sdfn, sector 
> > 10487808
> 
> The patch was CC'ed to stable but doesn't seem to appear in 4.19.y.
> 
> Unfortunately this appears to be a transient bug in the storage
> firmware, so I don't know how to reproduce it -- deleting and rescanning
> the sdX device has cleared the repeated error condition for now.
> 
> However I'd really like to avoid corrupting the involved file systems,
> so if bcb44433bba5eaff293888ef22ffa07f1f0347d6 could make it into either
> the 4.9 branch or the 4.19 branch, that'd be lovely.
> 
> I've also asked the storage vendor what they think about this, but I'm
> not going to hold my breath.

I have sent
https://lore.kernel.org/stable/20190818155941.GA26766@eldamar.local/
let's see what happends. 4.19 should be easier than 4.9, but given Ben
has backported the change to 3.16.72 this should be possible for both
4.9 and 4.19.

Regards,
Salvatore



Processed: bug 934331 is forwarded to https://lore.kernel.org/stable/20190818155941.GA26766@eldamar.local/

2019-08-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 934331 
> https://lore.kernel.org/stable/20190818155941.GA26766@eldamar.local/
Bug #934331 [linux] linux: backport "dm: disable DISCARD if the underlying 
storage no longer supports it"?
Ignoring request to change the forwarded-to-address of bug#934331 to the same 
value
> thanks
Stopping processing here.

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



Processed: your mail

2019-08-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 921542 5.0.1-1~exp1
Bug #921542 {Done: Ben Hutchings } [src:linux] tc qdisc 
kernel crash
Marked as fixed in versions linux/5.0.1-1~exp1.
> thanks
Stopping processing here.

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



Processed: your mail

2019-08-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 921542 5.0
Bug #921542 {Done: Ben Hutchings } [src:linux] tc qdisc 
kernel crash
The source 'linux' and version '5.0' do not appear to match any binary packages
Marked as fixed in versions linux/5.0.
> thanks
Stopping processing here.

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



Intel Wifi Solutions for Newer Kernel

2019-08-18 Thread thomasw
Hi,
sorry for not replying to the thread. I am not on the mailing list but will fix 
that after I send this message.
The issue you are reporting is a known issue with the 5.2 branch. If you use 
the firmware-iwlwifi from Buster, your troubles should go away. Its a 
compatibility issue with the latest firmware package and the latest kernel. Its 
strange because the older kernel actually works with the newer firmware but you 
need the older firmware for the newer kernel. I am currently using 5.2 with the 
older firmware from January that is in Buster and things are fine. On my 
particular hardware, the 5.3 branch of the kernel fixes the issue with the 
newer firmware.



Bug#934091: Missing HID driver modules (Most are fairly new since 5.0 or so)

2019-08-18 Thread Ben Hutchings
On Sun, 2019-08-18 at 10:26 -0400, thom...@fastmail.cn wrote:
> > I don't see any sign of CONFIG_HID_GT683R but have enabled the
> > others.
> I know all this is huge to maintain so I really appreciate all your
> help with this and you maintaining the Kernel. It is defined on line
> 383 of drivers/hid/kconfig. Hopefully that helps.

So it is.  I must have typed it wrongly when searching.

> It looks like its dependencies CONFIG_USB_HID=m and
> CONFIG_LEDS_CLASS=y are already set in the Debian kernel.

Thanks.

Ben.

-- 
Ben Hutchings
Larkinson's Law: All laws are basically false.




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


Processed: Re: Bug#930631: Wrong package reported.

2019-08-18 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 xserver-xorg-core
Bug #930631 [src:linux] linux-image-4.19.0-5-amd64: Fresh Buster install fails 
to boot to desktop
Bug reassigned from package 'src:linux' to 'xserver-xorg-core'.
No longer marked as found in versions linux/4.19.37-3.
Ignoring request to alter fixed versions of bug #930631 to the same values 
previously set

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



Bug#930631: Wrong package reported.

2019-08-18 Thread Ben Hutchings
Control: reassign -1 xserver-xorg-core

On Mon, 2019-08-05 at 22:44 +0100, Dai Trying wrote:
> This "bug" is actually with xserver-xorg-core package and is caused by the
> modesetting DDX driver, can this be changed here or do I need to file a new
> bug report?

I'm reassigning it, but you will probably need to provide more
information such as the version you're using and the contents of the
Xorg log file.

Ben.

-- 
Ben Hutchings
Larkinson's Law: All laws are basically false.




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


Processed: Re: Bug#934091: Missing HID driver modules (Most are fairly new since 5.0 or so)

2019-08-18 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #934091 [src:linux] Missing HID driver modules (Most are fairly new since 
5.0 or so)
Added tag(s) pending.

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



Bug#934091: Missing HID driver modules (Most are fairly new since 5.0 or so)

2019-08-18 Thread Ben Hutchings
Control: tag -1 pending

On Tue, 2019-08-06 at 17:54 -0400, thom...@fastmail.cn wrote:
> package: src:linux
> Keyboards, leds, remote controls etc.
> CONFIG_HID_BIGBEN_FF
> CONFIG_HID_GFRM
> CONFIG_HID_GT683R

I don't see any sign of CONFIG_HID_GT683R but have enabled the others.
Thanks,

Ben.

> CONFIG_HID_MACALLY
> CONFIG_HID_VIEWSONIC
> CONFIG_HID_MALTRON
> CONFIG_HID_U2FZERO
> 
-- 
Ben Hutchings
Larkinson's Law: All laws are basically false.




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


Processed: bug 934828 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=204141

2019-08-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 934828 https://bugzilla.kernel.org/show_bug.cgi?id=204141
Bug #934828 [src:linux] iwl_mvm_add_new_dqa_stream_wk BUG in lib/list_debug.c:56
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=204141'.
> thanks
Stopping processing here.

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



Bug#908712: Kernel quirks on QNAP TS-109 (Marvell orion)

2019-08-18 Thread Martin Michlmayr
* Arnaud Patard  [2019-08-02 10:58]:
> Sorry for the delay. I was waiting for some feedback before sending and
> then got busy with other stuff. I've now sent it:
> https://marc.info/?l=linux-netdev=156473570707976=2.

For the record, this has been accepted and queued for stable:
https://marc.info/?l=linux-netdev=156503710404939=2

-- 
Martin Michlmayr
https://www.cyrius.com/



Bug#935030: linux: radeon GPU freeze on 4.19(buster) but not on 5.2(unstable)

2019-08-18 Thread Tuxicoman
Source: linux
Severity: important

Dear Maintainer,

I often encouter GPU freezes using the buster kernel (4.19) and my AMD GPU
(Radeon 580) on 3D apps.

Here is a trace from dmesg:

[41030.750400] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=13431126, emitted seq=13431128
[41030.750405] [drm] GPU recovery disabled.
[41206.115499] INFO: task kworker/u8:0:6943 blocked for more than 120 seconds.
[41206.115504]   Tainted: G   OE 4.19.0-4-amd64 #1 Debian
4.19.28-2
[41206.115506] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[41206.115508] kworker/u8:0D0  6943  2 0x8000
[41206.115523] Workqueue: events_unbound commit_work [drm_kms_helper]
[41206.115525] Call Trace:
[41206.115532]  ? __schedule+0x2a2/0x870
[41206.115535]  ? __switch_to_asm+0x40/0x70
[41206.115537]  schedule+0x28/0x80
[41206.115539]  schedule_timeout+0x26d/0x390
[41206.115611]  ? dce110_timing_generator_get_position+0x5b/0x70 [amdgpu]
[41206.115673]  ? dce110_timing_generator_get_crtc_scanoutpos+0x70/0xb0
[amdgpu]
[41206.115676]  dma_fence_default_wait+0x238/0x2a0
[41206.115679]  ? dma_fence_release+0x90/0x90
[41206.115681]  dma_fence_wait_timeout+0xdd/0x100
[41206.115684]  reservation_object_wait_timeout_rcu+0x173/0x280
[41206.115748]  amdgpu_dm_do_flip+0x112/0x340 [amdgpu]
[41206.115811]  amdgpu_dm_atomic_commit_tail+0x750/0xdb0 [amdgpu]
[41206.115818]  ? wait_for_completion_timeout+0x3b/0x1a0
[41206.115828]  commit_tail+0x3d/0x70 [drm_kms_helper]
[41206.115833]  process_one_work+0x1a7/0x3a0
[41206.115836]  worker_thread+0x30/0x390
[41206.115838]  ? create_worker+0x1a0/0x1a0
[41206.115841]  kthread+0x112/0x130
[41206.115843]  ? kthread_bind+0x30/0x30
[41206.115845]  ret_from_fork+0x35/0x40

I can connect by SSH to the machine and force reboot.

The problem doesn't occur with kernel 5.2 from unstable.
See #928146



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

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