Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
Hi, I've rebased my two kernel config patches, attached, to the latest v4.17.17-1 buster kernel. These patches enable kernel features for newer ARM64 servers. 0001-arm64-Use-default-of-CONFIG_ACPI_NFIT-m.patch 0002-arm64-Updates-for-ACPI-servers.patch The issue that Riku brought up of how to support HPE m400 moonshot systems when ACPI_APEI is enabled has been resolved on the arm-kernel ML [1]. In summary, the latest released m400 firmware did not support APEI, and so no special work-around or kernel quirk support is needed. With the resolution of that issue I feel these patches are ready to apply. Please consider. [1] https://www.spinics.net/lists/arm-kernel/msg670446.html (efi: add contents of LinuxExtraArgs EFI var to command line) -Geoff >From 7d93f2d534f3ba60b94402b337e165d34e1caf25 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Wed, 13 Jun 2018 10:50:57 -0700 Subject: [PATCH 1/7] [arm64] Use default of CONFIG_ACPI_NFIT=m Commit ed497f3cb706d0e0f63844b064d9ebbf6f33b052 (Add server and 96boards options) added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but the commit message mentions nothing about why this was done. Remove the arm64 specific setting and use the default of module build. Cc: Riku Voipio Signed-off-by: Geoff Levand --- debian/config/arm64/config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index adf3e60bd9f5..72f2dadc16e3 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -71,7 +71,7 @@ CONFIG_ACPI_NUMA=y ## ## file: drivers/acpi/nfit/Kconfig ## -CONFIG_ACPI_NFIT=y +CONFIG_ACPI_NFIT=m ## ## file: drivers/android/Kconfig -- 2.14.1 >From 10f4c4399f54d99f293047c3d6dfeba08849526e Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Wed, 13 Jun 2018 10:50:57 -0700 Subject: [PATCH 2/7] [arm64] Updates for ACPI servers o Enable CONFIG_SCHED_SMT for hyperthreading processors. o Enable CONFIG_ARM64_LSE_ATOMICS for v8.1 processors. o Enable a number of ACPI options likely to be available on servers. o CONFIG_ACPI_APEI selects PSTORE, so remove the arm64 specific setting. Signed-off-by: Geoff Levand --- debian/config/arm64/config | 29 - 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index 72f2dadc16e3..250395babf59 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -9,6 +9,7 @@ CONFIG_ARM64_ERRATUM_834220=y CONFIG_ARM64_VA_BITS_48=y ## end choice CONFIG_SCHED_MC=y +CONFIG_SCHED_SMT=y CONFIG_NR_CPUS=256 CONFIG_NUMA=y CONFIG_SECCOMP=y @@ -24,6 +25,7 @@ CONFIG_RANDOMIZE_BASE=y CONFIG_RANDOMIZE_MODULE_REGION_FULL=y CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y CONFIG_COMPAT=y +CONFIG_ARM64_LSE_ATOMICS=y ## ## file: arch/arm64/crypto/Kconfig @@ -67,6 +69,21 @@ CONFIG_ARCH_XGENE=y ## CONFIG_ACPI=y CONFIG_ACPI_NUMA=y +CONFIG_ACPI_PCI_SLOT=y +CONFIG_ACPI_HED=y +CONFIG_ACPI_BGRT=y +CONFIG_ACPI_WATCHDOG=y +CONFIG_ACPI_CONFIGFS=m + +## +## file: drivers/acpi/apei/Kconfig +## +CONFIG_ACPI_APEI=y +CONFIG_ACPI_APEI_GHES=y +CONFIG_ACPI_APEI_PCIEAER=y +CONFIG_ACPI_APEI_SEA=y +CONFIG_ACPI_APEI_MEMORY_FAILURE=y +CONFIG_ACPI_APEI_EINJ=m ## ## file: drivers/acpi/nfit/Kconfig @@ -222,6 +239,12 @@ CONFIG_EXTCON_USB_GPIO=m ## CONFIG_RASPBERRYPI_FIRMWARE=y +## +## file: drivers/firmware/efi/Kconfig +## +CONFIG_UEFI_CPER=y +CONFIG_UEFI_CPER_ARM=y + ## ## file: drivers/gpio/Kconfig ## @@ -1097,6 +1120,7 @@ CONFIG_VIRTIO_MMIO=m ## file: drivers/watchdog/Kconfig ## CONFIG_GPIO_WATCHDOG=m +CONFIG_WDAT_WDT=m CONFIG_ARM_SP805_WATCHDOG=m CONFIG_ARM_SBSA_WATCHDOG=m CONFIG_DW_WATCHDOG=m @@ -1107,11 +1131,6 @@ CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_MESON_WATCHDOG=m CONFIG_BCM2835_WDT=m -## -## file: fs/pstore/Kconfig -## -CONFIG_PSTORE=y - ## ## file: mm/Kconfig ## -- 2.14.1
Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
Hi, I've rebased my two kernel config patches, attached, to the latest v4.17.17-1 buster kernel. These patches enable kernel features for newer ARM64 servers. 0001-arm64-Use-default-of-CONFIG_ACPI_NFIT-m.patch 0002-arm64-Updates-for-ACPI-servers.patch The issue that Riku brought up of how to support HPE m400 moonshot systems when ACPI_APEI is enabled has been resolved on the arm-kernel ML [1]. In summary, the latest released m400 firmware did not support APEI, and so no special work-around or kernel quirk support is needed. With the resolution of that issue I feel these patches are ready to apply. Please consider. [1] https://www.spinics.net/lists/arm-kernel/msg670446.html (efi: add contents of LinuxExtraArgs EFI var to command line) -Geoff >From 7d93f2d534f3ba60b94402b337e165d34e1caf25 Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Wed, 13 Jun 2018 10:50:57 -0700 Subject: [PATCH 1/7] [arm64] Use default of CONFIG_ACPI_NFIT=m Commit ed497f3cb706d0e0f63844b064d9ebbf6f33b052 (Add server and 96boards options) added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but the commit message mentions nothing about why this was done. Remove the arm64 specific setting and use the default of module build. Cc: Riku Voipio Signed-off-by: Geoff Levand --- debian/config/arm64/config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index adf3e60bd9f5..72f2dadc16e3 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -71,7 +71,7 @@ CONFIG_ACPI_NUMA=y ## ## file: drivers/acpi/nfit/Kconfig ## -CONFIG_ACPI_NFIT=y +CONFIG_ACPI_NFIT=m ## ## file: drivers/android/Kconfig -- 2.14.1 >From 10f4c4399f54d99f293047c3d6dfeba08849526e Mon Sep 17 00:00:00 2001 From: Geoff Levand Date: Wed, 13 Jun 2018 10:50:57 -0700 Subject: [PATCH 2/7] [arm64] Updates for ACPI servers o Enable CONFIG_SCHED_SMT for hyperthreading processors. o Enable CONFIG_ARM64_LSE_ATOMICS for v8.1 processors. o Enable a number of ACPI options likely to be available on servers. o CONFIG_ACPI_APEI selects PSTORE, so remove the arm64 specific setting. Signed-off-by: Geoff Levand --- debian/config/arm64/config | 29 - 1 file changed, 24 insertions(+), 5 deletions(-) diff --git a/debian/config/arm64/config b/debian/config/arm64/config index 72f2dadc16e3..250395babf59 100644 --- a/debian/config/arm64/config +++ b/debian/config/arm64/config @@ -9,6 +9,7 @@ CONFIG_ARM64_ERRATUM_834220=y CONFIG_ARM64_VA_BITS_48=y ## end choice CONFIG_SCHED_MC=y +CONFIG_SCHED_SMT=y CONFIG_NR_CPUS=256 CONFIG_NUMA=y CONFIG_SECCOMP=y @@ -24,6 +25,7 @@ CONFIG_RANDOMIZE_BASE=y CONFIG_RANDOMIZE_MODULE_REGION_FULL=y CONFIG_ARM64_ACPI_PARKING_PROTOCOL=y CONFIG_COMPAT=y +CONFIG_ARM64_LSE_ATOMICS=y ## ## file: arch/arm64/crypto/Kconfig @@ -67,6 +69,21 @@ CONFIG_ARCH_XGENE=y ## CONFIG_ACPI=y CONFIG_ACPI_NUMA=y +CONFIG_ACPI_PCI_SLOT=y +CONFIG_ACPI_HED=y +CONFIG_ACPI_BGRT=y +CONFIG_ACPI_WATCHDOG=y +CONFIG_ACPI_CONFIGFS=m + +## +## file: drivers/acpi/apei/Kconfig +## +CONFIG_ACPI_APEI=y +CONFIG_ACPI_APEI_GHES=y +CONFIG_ACPI_APEI_PCIEAER=y +CONFIG_ACPI_APEI_SEA=y +CONFIG_ACPI_APEI_MEMORY_FAILURE=y +CONFIG_ACPI_APEI_EINJ=m ## ## file: drivers/acpi/nfit/Kconfig @@ -222,6 +239,12 @@ CONFIG_EXTCON_USB_GPIO=m ## CONFIG_RASPBERRYPI_FIRMWARE=y +## +## file: drivers/firmware/efi/Kconfig +## +CONFIG_UEFI_CPER=y +CONFIG_UEFI_CPER_ARM=y + ## ## file: drivers/gpio/Kconfig ## @@ -1097,6 +1120,7 @@ CONFIG_VIRTIO_MMIO=m ## file: drivers/watchdog/Kconfig ## CONFIG_GPIO_WATCHDOG=m +CONFIG_WDAT_WDT=m CONFIG_ARM_SP805_WATCHDOG=m CONFIG_ARM_SBSA_WATCHDOG=m CONFIG_DW_WATCHDOG=m @@ -1107,11 +1131,6 @@ CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_MESON_WATCHDOG=m CONFIG_BCM2835_WDT=m -## -## file: fs/pstore/Kconfig -## -CONFIG_PSTORE=y - ## ## file: mm/Kconfig ## -- 2.14.1
Bug#907717: linux-image-4.17.0-0.bpo.3-amd64: random backtrace caused by refcount on Xorg
Package: src:linux Version: 4.17.17-1~bpo9+1 Severity: normal Dear Maintainer, I had installed new kernel from debian backports repository, but im experiencing some backtrace logs in system kern.log file. This does not affect systems stability. Backtrace is caused by refcount and its affecting Xorg process. My machine is running with nonfree firmware for APU and other devices which require nonfree firmware to function properly. Thank you for your time and i hope this helps improve debians stability -- Package-specific info: ** Version: Linux version 4.17.0-0.bpo.3-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian 4.17.17-1~bpo9+1 (2018-08-27) ** Command line: BOOT_IMAGE=/vmlinuz-4.17.0-0.bpo.3-amd64 root=/dev/mapper/debian--stretch-root ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends Inc. bios_version: 3401 board_vendor: ASUSTeK COMPUTER INC. board_name: PRIME A320M-K board_version: Rev X.0x ** Loaded modules: pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) xt_tcpudp xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter binfmt_misc dm_thin_pool amdkfd dm_persistent_data dm_bio_prison dm_bufio libcrc32c amdgpu eeepc_wmi wmi_bmof snd_hda_codec_realtek asus_wmi snd_hda_codec_hdmi snd_hda_codec_generic sparse_keymap rfkill snd_hda_intel snd_hda_codec chash edac_mce_amd snd_hda_core kvm_amd gpu_sched ttm snd_hwdep snd_pcm ccp rng_core drm_kms_helper snd_timer kvm drm snd sg soundcore irqbypass shpchp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel k10temp evdev serio_raw fam15h_power i2c_algo_bit sp5100_tco pcspkr video button wmi pcc_cpufreq acpi_cpufreq parport_pc ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb dm_mod sr_mod cdrom sd_mod hid_generic uas usbhid usb_storage hid crc32c_intel aesni_intel aes_x86_64 ahci xhci_pci crypto_simd libahci cryptd glue_helper xhci_hcd libata usbcore i2c_piix4 r8169 mii scsi_mod usb_common gpio_amdpt gpio_generic ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:1576] Subsystem: ASUSTeK Computer Inc. Device [1043:8719] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev e2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Carrizo [1043:8719] 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: amdgpu 00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio [1002:9840] Subsystem: ASUSTeK Computer Inc. Kabini HDMI/DP Audio [1043:8719] 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: snd_hda_intel 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:157b] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:157b] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:09.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device [1022:157d] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: snd_hda_intel 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller [1022:7914] (rev 20) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. FCH USB XHCI Controller [1043:8719] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2
Bug#883181: marked as done (linux-image-4.9.0-4-amd64: Default stretch kernel raises cgroup strack traces under high load)
Your message dated Fri, 31 Aug 2018 19:31:38 +0100 with message-id and subject line Re: Bug#883181: linux-image-4.9.0-4-amd64: Default stretch kernel raises cgroup strack traces under high load has caused the Debian Bug report #883181, regarding linux-image-4.9.0-4-amd64: Default stretch kernel raises cgroup strack traces under high load 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.) -- 883181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.9.51-1 Severity: serious Justification: Policy 2.2.1 -- Package-specific info: ** Version: Linux version 4.9.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 root=/dev/mapper/de--bln--vm--017--vg-root ro quiet ** Not tainted ** Kernel log: [1.533757] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null) [1.847797] ip_tables: (C) 2000-2006 Netfilter Core Team [1.912833] 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) [1.912859] systemd[1]: Detected virtualization vmware. [1.912863] systemd[1]: Detected architecture x86-64. [1.914546] systemd[1]: Set hostname to . [2.058639] random: crng init done [2.131752] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [2.131812] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [2.131843] systemd[1]: Listening on Syslog Socket. [2.131885] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [2.131920] systemd[1]: Listening on udev Control Socket. [2.131955] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [2.363268] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro [2.516531] systemd-journald[833]: Received request to flush runtime journal from PID 1 [2.819683] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 [2.819691] ACPI: Power Button [PWRF] [2.819819] ACPI: AC Adapter [ACAD] (on-line) [2.875315] input: PC Speaker as /devices/platform/pcspkr/input/input5 [2.881700] vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16 [2.881767] vmw_vmci :00:07.7: Using capabilities 0xc [2.882410] Guest personality initialized and is active [2.882410] VMCI host device registered (name=vmci, major=10, minor=58) [2.882410] Initialized host personality [2.930410] [drm] Initialized [2.941291] sd 0:0:0:0: Attached scsi generic sg0 type 0 [2.941374] sd 0:0:1:0: Attached scsi generic sg1 type 0 [2.941446] sd 0:0:2:0: Attached scsi generic sg2 type 0 [2.941516] sd 0:0:3:0: Attached scsi generic sg3 type 0 [2.941562] sr 2:0:0:0: Attached scsi generic sg4 type 5 [3.012775] [drm] DMA map mode: Using physical TTM page addresses. [3.012868] [drm] Capabilities: [3.012873] [drm] Rect copy. [3.012874] [drm] Cursor. [3.012875] [drm] Cursor bypass. [3.012876] [drm] Cursor bypass 2. [3.012877] [drm] 8bit emulation. [3.012878] [drm] Alpha cursor. [3.012879] [drm] Extended Fifo. [3.012880] [drm] Multimon. [3.012881] [drm] Pitchlock. [3.012882] [drm] Irq mask. [3.012883] [drm] Display Topology. [3.012884] [drm] GMR. [3.012885] [drm] Traces. [3.012886] [drm] GMR2. [3.012887] [drm] Screen Object 2. [3.012888] [drm] Command Buffers. [3.012889] [drm] Command Buffers 2. [3.012890] [drm] Guest Backed Resources. [3.012891] [drm] DX Features. [3.012893] [drm] Max GMR ids is 64 [3.012894] [drm] Max number of GMR pages is 65536 [3.012895] [drm] Max dedicated hypervisor surface memory is 0 kiB [3.012896] [drm] Maximum display memory size is 4096 kiB [3.012898] [drm] VRAM at 0xe800 size is 4096 kiB [3.012899] [drm] MMIO at 0xfe00 size is 256 kiB [3.012901] [drm] global init. [3.013022] [TTM] Zone kernel: Available graphics memory: 60855752 kiB [3.013023] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [3.013024] [TTM] Initializing pool allocator [3.013029] [TTM] Initializing DMA pool allocator [3.013122] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [3.013127] [drm] No driver support for vblank timestamp query.
Bug#906189: linux-image-4.17.0-1-amd64: Laptop does not suspend in 4.17 - worked up to 4.16
Control: tag -1 moreinfo On Wed, 2018-08-15 at 12:32 +0200, Christoph Haas wrote: > Package: src:linux > Version: 4.17.8-1 > Severity: important > > Dear Maintainer, > > I am using Debian Sid. Since the upgrade to linux-image-4.17.x I cannot > suspend my Lenovo X230 laptop any more. I close the lid or run > "systemctl suspend" to suspend the laptop but the laptop's power LED > blinks and after a few seconds the laptop resumes automatically. > This effect is easily reproducible. > > Booting into 4.16.0-2-amd64 works well. > > Linux kernel image 4.17.0-2 shows the mentioned problem. > > It appears the multiple people on the internet ran into this problem. I > did not find a workaround to this problem and will work with 4.16 now. [...] Has this been reported upstream (Bugzilla or an upstream mailing list)? You didn't include any kernel log messages for the failed suspend, which might help to explain this. Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#906189: linux-image-4.17.0-1-amd64: Laptop does not suspend in 4.17 - worked up to 4.16
Processing control commands: > tag -1 moreinfo Bug #906189 [src:linux] linux-image-4.17.0-1-amd64: Laptop does not suspend in 4.17 - worked up to 4.16 Added tag(s) moreinfo. -- 906189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#906189: linux-image-4.17.0-1-amd64: Laptop does not suspend in 4.17 - worked up to 4.16
Felix Hagemann writes: > Package: src:linux > Version: 4.17.17-1 > Followup-For: Bug #906189 > > Dear Maintainer, > > I do see exactly the same behaviour on a Thinkpad X1 Carbon (Gen. 2). > I had the same problem on my dell e7270, but it was fixed by a BIOS upgrade. Something to try? d
Bug#883181: linux-image-4.9.0-4-amd64: Default stretch kernel raises cgroup strack traces under high load
Hi Romain Hardly, as this system is now in production as a build server, running a bpo kernel. Linux 4.16.0-0.bpo.1-amd64 #1 SMP Debian 4.16.5-1~bpo9+1 (2018-05-06) x86_64 GNU/Linux Best regards Tom -Original Message- From: Romain Perier [mailto:romain.per...@gmail.com] Sent: Mittwoch, 29. August 2018 19:55 To: 883...@bugs.debian.org Subject: Bug#883181: linux-image-4.9.0-4-amd64: Default stretch kernel raises cgroup strack traces under high load Hi, The last linux kernel in stretch being 4.9.110, could you re-test with this kernel please ? Thanks, Regards, Romain On Thu, Nov 30, 2017 at 11:54:00AM +, Tom Stocker wrote: > Package: src:linux > Version: 4.9.51-1 > Severity: serious > Justification: Policy 2.2.1 > > > > -- Package-specific info: > ** Version: > Linux version 4.9.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version > 6.3.0 20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.51-1 (2017-09-28) > > ** Command line: > BOOT_IMAGE=/boot/vmlinuz-4.9.0-4-amd64 > root=/dev/mapper/de--bln--vm--017--vg-root ro quiet > > ** Not tainted > > ** Kernel log: > [1.533757] EXT4-fs (dm-1): mounted filesystem with ordered data mode. > Opts: (null) > [1.847797] ip_tables: (C) 2000-2006 Netfilter Core Team > [1.912833] 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) > [1.912859] systemd[1]: Detected virtualization vmware. > [1.912863] systemd[1]: Detected architecture x86-64. > [1.914546] systemd[1]: Set hostname to . > [2.058639] random: crng init done > [2.131752] systemd[1]: Set up automount Arbitrary Executable File Formats > File System Automount Point. > [2.131812] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. > [2.131843] systemd[1]: Listening on Syslog Socket. > [2.131885] systemd[1]: Started Forward Password Requests to Wall > Directory Watch. > [2.131920] systemd[1]: Listening on udev Control Socket. > [2.131955] systemd[1]: Started Dispatch Password Requests to Console > Directory Watch. > [2.363268] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro > [2.516531] systemd-journald[833]: Received request to flush runtime > journal from PID 1 > [2.819683] input: Power Button as > /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 > [2.819691] ACPI: Power Button [PWRF] > [2.819819] ACPI: AC Adapter [ACAD] (on-line) > [2.875315] input: PC Speaker as /devices/platform/pcspkr/input/input5 > [2.881700] vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16 > [2.881767] vmw_vmci :00:07.7: Using capabilities 0xc > [2.882410] Guest personality initialized and is active > [2.882410] VMCI host device registered (name=vmci, major=10, minor=58) > [2.882410] Initialized host personality > [2.930410] [drm] Initialized > [2.941291] sd 0:0:0:0: Attached scsi generic sg0 type 0 > [2.941374] sd 0:0:1:0: Attached scsi generic sg1 type 0 > [2.941446] sd 0:0:2:0: Attached scsi generic sg2 type 0 > [2.941516] sd 0:0:3:0: Attached scsi generic sg3 type 0 > [2.941562] sr 2:0:0:0: Attached scsi generic sg4 type 5 > [3.012775] [drm] DMA map mode: Using physical TTM page addresses. > [3.012868] [drm] Capabilities: > [3.012873] [drm] Rect copy. > [3.012874] [drm] Cursor. > [3.012875] [drm] Cursor bypass. > [3.012876] [drm] Cursor bypass 2. > [3.012877] [drm] 8bit emulation. > [3.012878] [drm] Alpha cursor. > [3.012879] [drm] Extended Fifo. > [3.012880] [drm] Multimon. > [3.012881] [drm] Pitchlock. > [3.012882] [drm] Irq mask. > [3.012883] [drm] Display Topology. > [3.012884] [drm] GMR. > [3.012885] [drm] Traces. > [3.012886] [drm] GMR2. > [3.012887] [drm] Screen Object 2. > [3.012888] [drm] Command Buffers. > [3.012889] [drm] Command Buffers 2. > [3.012890] [drm] Guest Backed Resources. > [3.012891] [drm] DX Features. > [3.012893] [drm] Max GMR ids is 64 > [3.012894] [drm] Max number of GMR pages is 65536 > [3.012895] [drm] Max dedicated hypervisor surface memory is 0 kiB > [3.012896] [drm] Maximum display memory size is 4096 kiB > [3.012898] [drm] VRAM at 0xe800 size is 4096 kiB > [3.012899] [drm] MMIO at 0xfe00 size is 256 kiB > [3.012901] [drm] global init. > [3.013022] [TTM] Zone kernel: Available graphics memory: 60855752 kiB > [3.013023] [TTM] Zone dma32: Available graphics memory: 2097152 kiB > [3.013024] [TTM] Initializing pool allocator > [3.013029] [TTM] Initializing DMA pool allocator > [3.013122] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [3.013127] [drm] No driver support for vblank timestamp query. > [3.013382] [drm] Screen Target Display device initialized > [3.013441] [drm] width 64
Bug#893393: linux-image-amd64: Kernel panic on active outgoing traffic through Huawei E173 modem in NDIS (CDC) mode
Phil writes: > Hi, I hope you're all doing well. > > Shall we/I maybe reopen a new issue? I believe so. I am almost sure we fixed the original memset BUG in cdc_ncm_fill_tx_frame. Or at least one of them... So you are probably seeing another issue if you still have problems with that fix in place. Although the issues may or may not be related. But still, aother bug report would make it easier to track given that we alread have one fix for 893393. > I'm still affected by this and I'd could use some advice how to debug > the issue a little bit better, especially since the kexec kernel > crashdumps appear not to be helpful. Can I maybe compile the module with > special debug flags and load it via. dkms or something? Crash reports of some sort are best. But any info is useful. Like what device is this really and what mode is in currently in? What driver does it use? Most Huawei firmwares will support many different modes using different USB drivers. But laptop internal modems are most likely not tested with anything but the Windows MBIM class driver, since that is the certification requirement and only target platform. You can enable the little debugging that's already in the drivers by doing something like echo 'module cdc_ncm +fp' >/sys/kernel/debug/dynamic_debug/control echo 'module cdc_mbim +fp' >/sys/kernel/debug/dynamic_debug/control echo 'module huawei_cdc_ncm +fp' >/sys/kernel/debug/dynamic_debug/control See https://www.kernel.org/doc/html/v4.11/admin-guide/dynamic-debug-howto.html Not sure it will be useful to debug a freeze though. > I don't see any actual changes in [cdc_ncm.c][cdc_ncm], besides the one > change in `cdc_ncm_unbind`. Not sure I understood this... Are you referring to the fix for bug 893393? That's part of the v4.9.111 stable release: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/usb/cdc_ncm.c?h=linux-4.9.y&id=35fd10aeb2248cc7f8d3d48ccc2eff1cf19918f4 > Also I'm confused why this is happening now again, I managed to do an > rsync upload with ~10GB over night back then - and my system didn't > crash - but right now even if I'm just trying to upload a picture to > twitter via. Firefox my laptop freezes. Freezing without any Oops or similar? Bjørn
