Bug#900581: linux: Enable Buster kernel features for newer ARM64 servers.
Hi Ben, On 09/21/2018 04:20 PM, Ben Hutchings wrote: > I've applied these, with some changes: > > 0001: Rather than changing the setting of CONFIG_ACPI_NFIT for arm64, I > removed it entirely as it would be redundant with the top-level config. > > 0002: I dropped several of the config symbols which are automatic. Any > config symbol that doesn't have a description can only be enabled via > other symbols that select it. These shouldn't be mentioned in > debian/config files. > > I also removed CONFIG_ACPI_CONFIGFS as I have a concern that this > feature allows subverting Secure Boot. If this feature is important to > you, I can investigate further and maybe add a patch to conditionally > disable it at run-time instead. The changes you've committed look fine. I have no need for CONFIG_ACPI_CONFIGFS. If it seems a risk, then I think it OK to have it disabled until a real need comes up. -Geoff
Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209
[copied Roger and Ian] * Ralf Hemberger [2018-09-13 00:56]: > I ugraded the kernel to the stretch-backports version with apt. > After reboot the kernel couldn't find the PHY [41.082447], > subsequently followed a kernel oops / crash, systemd-udevd crashes. > [ 23.578592] serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 5, base_baud = > 1041) is a 16550A > [ 23.588924] libphy: Fixed MDIO Bus: probed > [ 23.593128] i2c /dev entries driver > [ 23.598678] ledtrig-cpu: registered to indicate activity on CPUs ... > [ 40.477188] gpio gpiochip0: uevent: failed to send synthetic uevent > [ 40.594004] systemd-journald[221]: Received request to flush runtime > journal from PID 1 > [ 41.006693] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 > [ 41.082447] libphy: PHY orion-mdio-mii:08 not found > [ 41.617923] marvell-cesa mv_crypto: CESA device successfully registered > [ 41.669309] libphy: PHY orion-mdio-mii:08 not found > [ 41.674709] Unable to handle kernel NULL pointer dereference at virtual > address 000c > [ 41.682935] pgd = (ptrval) > [ 41.685714] [000c] *pgd= > [ 41.689321] Internal error: Oops: 5 [#1] ARM > [ 41.693586] Modules linked in: orion_wdt(+) mvmdio(+) usb_common nls_base > marvell_cesa(+) des_generic mv643xx_eth evdev gpio_keys ip_tables x_tables > sha256_generic hmac ipv6 autofs4 ext4 crc16 mbcache jbd2 fscrypto ecb raid10 > raid456 libcrc32c crc32c_generic async_raid6_recov async_memcpy async_pq > async_xor xor async_tx raid6_pq raid0 multipath linear mtdblock mtd_blkdevs > raid1 md_mod sd_mod cfi_cmdset_0001 sata_mv libata cfi_probe cfi_util > gen_probe scsi_mod physmap mtd chipreg rtc_s35390a > [ 41.737243] CPU: 0 PID: 259 Comm: systemd-udevd Not tainted > 4.17.0-0.bpo.3-marvell #1 Debian 4.17.17-1~bpo9+1 > [ 41.747122] Hardware name: QNAP TS-109/TS-209 > [ 41.751507] PC is at of_clk_get+0x24/0x60 > [ 41.72] LR is at orion_mdio_probe+0x118/0x2d8 [mvmdio] > [ 41.761039] pc : []lr : []psr: 6013 > [ 41.767294] sp : d7bc7cc8 ip : c0551e68 fp : d68c2fa4 > [ 41.772511] r10: r9 : d6ebda84 r8 : c0551d98 > [ 41.34] r7 : c0551d88 r6 : d6ebd800 r5 : d6ebda80 r4 : d7bc7cd0 > [ 41.784253] r3 : r2 : r1 : r0 : > [ 41.790777] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment > none > [ 41.797897] Control: a005317f Table: 16034000 DAC: 0051 > [ 41.803643] Process systemd-udevd (pid: 259, stack limit = 0x(ptrval)) > [ 41.810165] Stack: (0xd7bc7cc8 to 0xd7bc8000) > [ 41.814536] 7cc0: 0014 014080c0 c0223bc8 c0019740 > 000f1072 > [ 41.822714] 7ce0: d68c1550 0084 d68c1540 c029996c a013 d68c1550 > 0084 > [ 41.830898] 7d00: c0551d98 c0299a50 fe072004 c0223c20 c0551eb0 d6ebda80 > d6ebd800 c0551eb0 > [ 41.839080] 7d20: d6ebda80 bf36f428 d78f5b40 d685d180 d78f5b40 c04961cd > d6eb2000 d6ebda84 > [ 41.847259] 7d40: 0124 c0551d98 bf36fbb0 c05cffbc > 0124 0010 > [ 41.855443] 7d60: d68c2fa4 c0298460 c0551d98 bf36fbb0 c0296bdc > bf36fbb0 c0551d98 > [ 41.863624] 7d80: c0551d98 c0551dcc bf36fbb0 0001 0124 > d7bc7f50 c0296e04 > [ 41.871809] 7da0: c0551d98 bf36fbb0 c0296d7c c0294da0 d788a64c d7804ed0 > bf36fbb0 d6e011e0 > [ 41.879990] 7dc0: c057e898 c0295fa4 bf36fb38 bf36fb39 006f bf36fbb0 > c0549028 bf372000 > [ 41.888170] 7de0: c0297548 bf36fc00 c0549028 bf372000 c000aafc > 0001 > [ 41.896355] 7e00: d7bde8f8 0080007f d78ec220 0080007f d6e4 0001 > 80d1 c0119a0c > [ 41.904535] 7e20: 0080007f c011ac9c c0127c48 d68c2fa4 c0127d1c > d7801e60 014000c0 > [ 41.912717] 7e40: bf36fc00 82df77ca bf36fc00 0001 d68c1d60 d68c2f80 > 0001 c007a0cc > [ 41.920900] 7e60: bf36fc00 d7800fe4 bf36fc00 0001 bf36fc48 c00793a8 > bf36fc0c 7fff > [ 41.929083] 7e80: bf36fc00 c0076ac0 c00765ec c03d57d8 0074 d95f8e80 > bf36fdc4 b6ec43a0 > [ 41.937260] 7ea0: 001a d95f6000 d7bc7ed8 > > [ 41.945432] 7ec0: 6e72656b 6c65 > > [ 41.953605] 7ee0: > > [ 41.961783] 7f00: 82df77ca 7fff b6ec43a0 0007 > 017b c00091e4 > [ 41.969964] 7f20: d7bc6000 0080 01e05220 c0079aa8 7fff > 0003 > [ 41.978147] 7f40: d95f6000 2ef8 d95f6ba3 d95f6000 > 2ef8 d95f8930 > [ 41.986327] 7f60: d95f87b0 d95f7f9c 0de0 0f90 > 0c38 > [ 41.994511] 7f80: 0022 0023 001b 0018 0013 > 2b486500 01df95a0 > [ 42.002693] 7fa0: c00091b8 2b486500 01df95a0 0007 b6ec43a0 > b6ec4eb4 > [ 42.010876] 7fc0: 2b486500 01df95a0
Bug#909475: task jbd2 blocked for more than 120 seconds
Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: important Dear Maintainer, * What led up to the situation? See below for log extract. * What exactly did you do (or not do) that was effective (or ineffective)? A reboot was required. * What are the associated lines from the log file? Sep 23 21:41:16 vhost001 kernel: INFO: task jbd2/sdc1-8:634 blocked for more than 120 seconds. Sep 23 21:41:16 vhost001 kernel: Not tainted 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1 Sep 23 21:41:16 vhost001 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Sep 23 21:41:16 vhost001 kernel: jbd2/sdc1-8 D0 634 2 0x8000 Sep 23 21:41:16 vhost001 kernel: Call Trace: Sep 23 21:41:16 vhost001 kernel: ? __schedule+0x3f5/0x880 Sep 23 21:41:16 vhost001 kernel: ? __switch_to_asm+0x40/0x70 Sep 23 21:41:16 vhost001 kernel: ? __switch_to_asm+0x34/0x70 Sep 23 21:41:16 vhost001 kernel: ? bit_wait+0x50/0x50 Sep 23 21:41:16 vhost001 kernel: schedule+0x32/0x80 Sep 23 21:41:16 vhost001 kernel: io_schedule+0x12/0x40 Sep 23 21:41:16 vhost001 kernel: bit_wait_io+0xd/0x50 Sep 23 21:41:16 vhost001 kernel: __wait_on_bit+0x55/0x80 Sep 23 21:41:16 vhost001 kernel: out_of_line_wait_on_bit+0x8b/0xb0 Sep 23 21:41:16 vhost001 kernel: ? init_wait_var_entry+0x40/0x40 Sep 23 21:41:16 vhost001 kernel: jbd2_journal_commit_transaction+0x10ab/0x1870 [jbd2] Sep 23 21:41:16 vhost001 kernel: ? __switch_to_asm+0x40/0x70 Sep 23 21:41:16 vhost001 kernel: ? kjournald2+0xc1/0x260 [jbd2] Sep 23 21:41:16 vhost001 kernel: kjournald2+0xc1/0x260 [jbd2] Sep 23 21:41:16 vhost001 kernel: ? remove_wait_queue+0x60/0x60 Sep 23 21:41:16 vhost001 kernel: kthread+0xf8/0x130 Sep 23 21:41:16 vhost001 kernel: ? commit_timeout+0x10/0x10 [jbd2] Sep 23 21:41:16 vhost001 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Sep 23 21:41:16 vhost001 kernel: ret_from_fork+0x35/0x40 Sep 23 21:41:16 vhost001 kernel: INFO: task kworker/u24:0:1407 blocked for more than 120 seconds. Sep 23 21:41:16 vhost001 kernel: Not tainted 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1 Sep 23 21:41:16 vhost001 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Sep 23 21:41:16 vhost001 kernel: kworker/u24:0 D0 1407 2 0x8000 Sep 23 21:41:16 vhost001 kernel: Workqueue: writeback wb_workfn (flush-8:32) Sep 23 21:41:16 vhost001 kernel: Call Trace: Sep 23 21:41:16 vhost001 kernel: ? __schedule+0x3f5/0x880 Sep 23 21:41:16 vhost001 kernel: schedule+0x32/0x80 Sep 23 21:41:16 vhost001 kernel: io_schedule+0x12/0x40 Sep 23 21:41:16 vhost001 kernel: wbt_wait+0x2b1/0x400 Sep 23 21:41:16 vhost001 kernel: ? remove_wait_queue+0x60/0x60 Sep 23 21:41:16 vhost001 kernel: blk_mq_make_request+0x107/0x510 Sep 23 21:41:16 vhost001 kernel: generic_make_request+0x1e7/0x410 Sep 23 21:41:16 vhost001 kernel: ? submit_bio+0x6c/0x140 Sep 23 21:41:16 vhost001 kernel: submit_bio+0x6c/0x140 Sep 23 21:41:16 vhost001 kernel: ext4_io_submit+0x48/0x60 [ext4] Sep 23 21:41:16 vhost001 kernel: ext4_bio_write_page+0x26a/0x520 [ext4] Sep 23 21:41:16 vhost001 kernel: mpage_submit_page+0x52/0x70 [ext4] Sep 23 21:41:16 vhost001 kernel: mpage_process_page_bufs+0x101/0x110 [ext4] Sep 23 21:41:16 vhost001 kernel: mpage_prepare_extent_to_map+0x1e6/0x2b0 [ext4] Sep 23 21:41:16 vhost001 kernel: ext4_writepages+0x41c/0xe00 [ext4] Sep 23 21:41:16 vhost001 kernel: ? br_dev_xmit+0x23d/0x3c0 [bridge] Sep 23 21:41:16 vhost001 kernel: ? lock_timer_base+0x74/0x90 Sep 23 21:41:16 vhost001 kernel: ? dev_hard_start_xmit+0xa3/0x1f0 Sep 23 21:41:16 vhost001 kernel: ? do_writepages+0x1a/0x60 Sep 23 21:41:16 vhost001 kernel: do_writepages+0x1a/0x60 Sep 23 21:41:16 vhost001 kernel: __writeback_single_inode+0x3d/0x320 Sep 23 21:41:16 vhost001 kernel: ? e1000_xmit_frame+0xbaf/0xf10 [e1000e] Sep 23 21:41:16 vhost001 kernel: writeback_sb_inodes+0x221/0x4b0 Sep 23 21:41:16 vhost001 kernel: __writeback_inodes_wb+0x87/0xb0 Sep 23 21:41:16 vhost001 kernel: wb_writeback+0x288/0x320 Sep 23 21:41:16 vhost001 kernel: ? cpumask_next+0x16/0x20 Sep 23 21:41:16 vhost001 kernel: ? wb_workfn+0x37c/0x450 Sep 23 21:41:16 vhost001 kernel: wb_workfn+0x37c/0x450 Sep 23 21:41:16 vhost001 kernel: process_one_work+0x191/0x370 Sep 23 21:41:16 vhost001 kernel: worker_thread+0x4f/0x3b0 Sep 23 21:41:16 vhost001 kernel: kthread+0xf8/0x130 Sep 23 21:41:16 vhost001 kernel: ? rescuer_thread+0x340/0x340 Sep 23 21:41:16 vhost001 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Sep 23 21:41:16 vhost001 kernel: ret_from_fork+0x35/0x40 Sep 23 21:43:17 vhost001 kernel: INFO: task jbd2/sdc1-8:634 blocked for more than 120 seconds. Sep 23 21:43:17 vhost001 kernel: Not tainted 4.18.0-0.bpo.1-amd64 #1 Debian 4.18.6-1~bpo9+1 Sep 23 21:43:17 vhost001 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Sep 23 21:43:17 vhost001 kernel: jbd2/sdc1-8 D0 634 2 0x8000 Sep 23
Bug#909473: fstrim shows incorrect trimmed size after reboot
Package: src:linux Version: 4.18.8-1 Severity: normal Hi, Not sure who to blame here, but when running fstrim -va it show the size of the disk it has trimmed, if I'm running fstrim again it shows 0 for all the disk. If I reboot, and then run fstrim again it shows (almost) the same value as the 1st time. All the disks have the discard option enabled, all fs are ext4, except /boot which is ext2/ See the logs: bigon@valinor:~$ journalctl -u fstrim.service -- Logs begin at Sat 2018-09-08 12:48:02 CEST, end at Mon 2018-09-24 13:32:05 CEST. -- sep 17 10:44:21 valinor systemd[1]: Starting Discard unused blocks... sep 17 10:44:51 valinor fstrim[11186]: /var/cache/apt-cacher-ng : 930,1 MiB (975245312 octets) taillés sep 17 10:44:51 valinor fstrim[11186]: /var/lib/sbuild/build : 9,8 GiB (10463989760 octets) taillés sep 17 10:44:51 valinor fstrim[11186]: /var/lib/libvirt : 17,9 GiB (19241095168 octets) taillés sep 17 10:44:51 valinor fstrim[11186]: /var/lib/docker : 10 GiB (10713788416 octets) taillés sep 17 10:44:51 valinor fstrim[11186]: /var/lib/flatpak : 1,4 GiB (1496272896 octets) taillés sep 17 10:44:51 valinor fstrim[11186]: /home : 11,3 GiB (12105969664 octets) taillés sep 17 10:44:51 valinor fstrim[11186]: /boot : 126,9 MiB (133014528 octets) taillés sep 17 10:44:51 valinor fstrim[11186]: / : 8,6 GiB (9217847296 octets) taillés sep 17 10:44:51 valinor systemd[1]: Started Discard unused blocks. -- Reboot -- sep 24 10:12:35 valinor systemd[1]: Starting Discard unused blocks... sep 24 10:13:08 valinor fstrim[26936]: /var/lib/sbuild/build : 9,8 GiB (10455736320 octets) taillés sep 24 10:13:08 valinor fstrim[26936]: /var/cache/apt-cacher-ng : 922,8 MiB (967565312 octets) taillés sep 24 10:13:08 valinor fstrim[26936]: /var/lib/libvirt : 17,9 GiB (19241095168 octets) taillés sep 24 10:13:08 valinor fstrim[26936]: /var/lib/docker : 11,4 GiB (12180299776 octets) taillés sep 24 10:13:08 valinor fstrim[26936]: /var/lib/flatpak : 1,4 GiB (1496272896 octets) taillés sep 24 10:13:08 valinor fstrim[26936]: /home : 11 GiB (11825807360 octets) taillés sep 24 10:13:08 valinor fstrim[26936]: /boot : 126,9 MiB (133008384 octets) taillés sep 24 10:13:08 valinor fstrim[26936]: / : 8,6 GiB (9219850240 octets) taillés sep 24 10:13:08 valinor systemd[1]: Started Discard unused blocks. -- Reboot -- sep 24 13:20:54 valinor systemd[1]: Starting Discard unused blocks... sep 24 13:21:28 valinor fstrim[6751]: /var/lib/docker : 11,4 GiB (12181008384 octets) taillés sep 24 13:21:28 valinor fstrim[6751]: /var/cache/apt-cacher-ng : 793,9 MiB (832487424 octets) taillés sep 24 13:21:28 valinor fstrim[6751]: /var/lib/libvirt : 17,9 GiB (19241095168 octets) taillés sep 24 13:21:28 valinor fstrim[6751]: /home : 10,8 GiB (11617431552 octets) taillés sep 24 13:21:28 valinor fstrim[6751]: /var/lib/sbuild/build : 9,8 GiB (10463989760 octets) taillés sep 24 13:21:28 valinor fstrim[6751]: /var/lib/flatpak : 1,4 GiB (1496272896 octets) taillés sep 24 13:21:28 valinor fstrim[6751]: /boot : 126,9 MiB (133008384 octets) taillés sep 24 13:21:28 valinor fstrim[6751]: / : 8,6 GiB (9211752448 octets) taillés sep 24 13:21:28 valinor systemd[1]: Started Discard unused blocks. sep 24 13:32:05 valinor systemd[1]: Starting Discard unused blocks... sep 24 13:32:05 valinor fstrim[7323]: /var/lib/docker : 0 B (0 octets) taillés sep 24 13:32:05 valinor fstrim[7323]: /var/cache/apt-cacher-ng : 0 B (0 octets) taillés sep 24 13:32:05 valinor fstrim[7323]: /var/lib/libvirt : 0 B (0 octets) taillés sep 24 13:32:05 valinor fstrim[7323]: /home : 0 B (0 octets) taillés sep 24 13:32:05 valinor fstrim[7323]: /var/lib/sbuild/build : 0 B (0 octets) taillés sep 24 13:32:05 valinor fstrim[7323]: /var/lib/flatpak : 0 B (0 octets) taillés sep 24 13:32:05 valinor fstrim[7323]: /boot : 0 B (0 octets) taillés sep 24 13:32:05 valinor fstrim[7323]: / : 0 B (0 octets) taillés sep 24 13:32:05 valinor systemd[1]: Started Discard unused blocks. There is definitely something boggus here Kind regards, Laurent Bigonville -- Package-specific info: ** Version: Linux version 4.18.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-29)) #1 SMP Debian 4.18.8-1 (2018-09-18) ** Command line: BOOT_IMAGE=/vmlinuz-4.18.0-1-amd64 root=/dev/mapper/valinor--vg-root ro quiet splash audit=1 selinux=1 security=selinux ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: LENOVO product_name: 20CK0002MB product_version: ThinkPad T550 chassis_vendor: LENOVO chassis_version: None bios_vendor: LENOVO bios_version: N11ET46W (1.22 ) board_vendor: LENOVO board_name: 20CK0002MB board_version: SDK0E50510 WIN ** Loaded modules: fuse nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter overlay xt_CHECKSUM ipt_MASQUERADE xt_conntrack ipt_REJECT xt_tcpudp tun bridge stp llc nf_tables_set devlink nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4
Bug#896911: e1000e msix interrupts broken in linux 4.15
On Tue, Sep 18, 2018 at 01:37:34PM +0100, Ben Hutchings wrote: > Greg, > > On Tue, 2018-09-18 at 13:29 +0100, Ben Hutchings wrote: > > On Tue, 2018-09-18 at 09:12 +, Yanhui He wrote: > > > Hi David, > > > > > > Would you please help us push this fix in the new Debian release? > > > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896911 > > > > David Miller doesn't send updates for 4.9 any more. > > > > Based on your list of commit subjects, I found: > > > > 745d0bd3af99 e1000e: Remove Other from EIAC > > 1f0ea19722ef Partial revert "e1000e: Avoid receiver overrun interrupt > > bursts" > > 361a954e6a72 e1000e: Fix queue interrupt re-raising in Other interrupt > > 116f4a640b31 e1000e: Avoid missed interrupts following ICR read > > 4e7dc08e57c9 e1000e: Fix check_for_link return value with autoneg off > > 3016e0a0c912 Revert "e1000e: Separate signaling for link check/link up" > > e2710dbf0dc1 e1000e: Fix link check race condition > > > > "e1000e: Fix check_for_link return value with autoneg off" was already > > appplied to 4.9-stable but the others have not been. > > Please queue up the above commits for 4.14 (they apply cleanly). > > Please queue up the patches from the attached mailbox file for 4.9. > > Your other stable branches should be unaffected. Thanks for these, all now queued up. greg k-h
[stretch-pu] Upload of 4.9.128
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, [in case not everyone follow IRC] As far as I can tell, we are currently on sync with upstream for 4.9 (at 4.9.128) and it seems that we don't have ABI breaks handling (at least on amd64). Would it make sense to upload right now so we update -pu (which is at 4.9.110 for now) and get a chance to test the whole build accross all architectures? As far as I can tell next point release has not been scheduled yet so there's no urgency, but I think it'd be nice if we could generally have more testing of the kernel in -pu before the point release is done. I can take care of the upload if needed but it's merely about the decision I guess. Thoughts? Regards, - -- Yves-Alexis -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAluop0oACgkQ3rYcyPpX RFtSIwgAzKE0goZlAeYeaauh0Xarl47EBJTwOfOzMcadNN9+Xv5InN7kQFY2fk6z EgOx5ayAhxd46iWz++Kfh5/Nq5hH5UepazGfvsiEdtQnRVD5++/ezq8LZACIPiSH L/gvJNfMpaSf93Nk6OBsuthyzLFzuRMaonYmYSM+g579BnnerI5GfN5WGdLRjZxz bo288y4rNwCjvIPdPYS9gLjC6d+mqT7HtbraSnalwoxr9xUfGB+vVMLIVhQu3CQs b8ZdqvfCFg8FzgoJ/uS/JvWz7CrEnbZqOixw+NcnQUf+kZmkMpP9U7Ip34IwuNY/ 34F0JxSt6ab8ra5Cf8v6+OOy4SG8cQ== =HHjS -END PGP SIGNATURE-
