Bug#908216: btrfs blocked for more than 120 seconds
Package: src:linux Version: 4.19.12-1~bpo9+1 Severity: important The only solution is to revert to 4.17. Jan 19 18:14:35 vhost004 kernel: INFO: task btrfs-transacti:691 blocked for more than 120 seconds. Jan 19 18:14:35 vhost004 kernel: Tainted: G I E 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1 Jan 19 18:14:35 vhost004 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 19 18:14:35 vhost004 kernel: btrfs-transacti D0 691 2 0x8000 Jan 19 18:14:35 vhost004 kernel: Call Trace: Jan 19 18:14:35 vhost004 kernel: ? __schedule+0x3f5/0x880 Jan 19 18:14:35 vhost004 kernel: schedule+0x32/0x80 Jan 19 18:14:35 vhost004 kernel: btrfs_start_ordered_extent+0xed/0x120 [btrfs] Jan 19 18:14:35 vhost004 kernel: ? remove_wait_queue+0x60/0x60 Jan 19 18:14:35 vhost004 kernel: btrfs_wait_ordered_range+0xa0/0x100 [btrfs] Jan 19 18:14:35 vhost004 kernel: __btrfs_wait_cache_io+0x46/0x1c0 [btrfs] Jan 19 18:14:35 vhost004 kernel: btrfs_start_dirty_block_groups+0x1ad/0x4b0 [btrfs] Jan 19 18:14:35 vhost004 kernel: btrfs_commit_transaction+0xc8/0x8a0 [btrfs] Jan 19 18:14:35 vhost004 kernel: ? start_transaction+0x8f/0x3e0 [btrfs] Jan 19 18:14:35 vhost004 kernel: transaction_kthread+0x157/0x180 [btrfs] Jan 19 18:14:35 vhost004 kernel: kthread+0xf8/0x130 Jan 19 18:14:35 vhost004 kernel: ? btrfs_cleanup_transaction+0x500/0x500 [btrfs] Jan 19 18:14:35 vhost004 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Jan 19 18:14:35 vhost004 kernel: ret_from_fork+0x35/0x40 Jan 19 18:16:35 vhost004 kernel: INFO: task btrfs-transacti:691 blocked for more than 120 seconds. Jan 19 18:16:35 vhost004 kernel: Tainted: G I E 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1 Jan 19 18:16:35 vhost004 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 19 18:16:35 vhost004 kernel: btrfs-transacti D0 691 2 0x8000 Jan 19 18:16:35 vhost004 kernel: Call Trace: Jan 19 18:16:35 vhost004 kernel: ? __schedule+0x3f5/0x880 Jan 19 18:16:35 vhost004 kernel: schedule+0x32/0x80 Jan 19 18:16:35 vhost004 kernel: btrfs_start_ordered_extent+0xed/0x120 [btrfs] Jan 19 18:16:35 vhost004 kernel: ? remove_wait_queue+0x60/0x60 Jan 19 18:16:35 vhost004 kernel: btrfs_wait_ordered_range+0xa0/0x100 [btrfs] Jan 19 18:16:35 vhost004 kernel: __btrfs_wait_cache_io+0x46/0x1c0 [btrfs] Jan 19 18:16:35 vhost004 kernel: btrfs_start_dirty_block_groups+0x1ad/0x4b0 [btrfs] Jan 19 18:16:35 vhost004 kernel: btrfs_commit_transaction+0xc8/0x8a0 [btrfs] Jan 19 18:16:35 vhost004 kernel: ? start_transaction+0x8f/0x3e0 [btrfs] Jan 19 18:16:35 vhost004 kernel: transaction_kthread+0x157/0x180 [btrfs] Jan 19 18:16:35 vhost004 kernel: kthread+0xf8/0x130 Jan 19 18:16:35 vhost004 kernel: ? btrfs_cleanup_transaction+0x500/0x500 [btrfs] Jan 19 18:16:35 vhost004 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Jan 19 18:16:35 vhost004 kernel: ret_from_fork+0x35/0x40 Jan 19 18:16:37 vhost004 crmd[1539]: notice: High CPU load detected: 55.71 Jan 19 18:17:01 vhost004 CRON[15470]: pam_unix(cron:session): session opened for user root by (uid=0) Jan 19 18:17:01 vhost004 CRON[15471]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jan 19 18:17:01 vhost004 CRON[15470]: pam_unix(cron:session): session closed for user root Jan 19 18:17:07 vhost004 crmd[1539]: notice: High CPU load detected: 41.509998 Jan 19 18:17:37 vhost004 crmd[1539]: notice: High CPU load detected: 32.63 Jan 19 18:18:07 vhost004 crmd[1539]: notice: High CPU load detected: 27.27 Jan 19 18:18:36 vhost004 kernel: INFO: task btrfs-transacti:691 blocked for more than 120 seconds. Jan 19 18:18:36 vhost004 kernel: Tainted: G I E 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1 Jan 19 18:18:36 vhost004 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 19 18:18:36 vhost004 kernel: btrfs-transacti D0 691 2 0x8000 Jan 19 18:18:36 vhost004 kernel: Call Trace: Jan 19 18:18:36 vhost004 kernel: ? __schedule+0x3f5/0x880 Jan 19 18:18:36 vhost004 kernel: schedule+0x32/0x80 Jan 19 18:18:36 vhost004 kernel: btrfs_start_ordered_extent+0xed/0x120 [btrfs] Jan 19 18:18:36 vhost004 kernel: ? remove_wait_queue+0x60/0x60 Jan 19 18:18:36 vhost004 kernel: btrfs_wait_ordered_range+0xa0/0x100 [btrfs] Jan 19 18:18:36 vhost004 kernel: __btrfs_wait_cache_io+0x46/0x1c0 [btrfs] Jan 19 18:18:36 vhost004 kernel: btrfs_start_dirty_block_groups+0x1ad/0x4b0 [btrfs] Jan 19 18:18:36 vhost004 kernel: btrfs_commit_transaction+0xc8/0x8a0 [btrfs] Jan 19 18:18:36 vhost004 kernel: ? start_transaction+0x8f/0x3e0 [btrfs] Jan 19 18:18:36 vhost004 kernel: transaction_kthread+0x157/0x180 [btrfs] Jan 19 18:18:36 vhost004 kernel: kthread+0xf8/0x130 Jan 19 18:18:36 vhost004 kernel: ? btrfs_cleanup_transaction+0x500/0x500 [btrfs] Jan 19 18:18:36 vhost004 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Jan 19
Bug#908216: btrfs blocked for more than 120 seconds
Package: src:linux Version: 4.19.12-1~bpo9+1 Severity: important Yes, the btrfs hung task problem still exists in the latest kernel. Jan 19 18:40:41 vhost003 kernel: INFO: task btrfs-transacti:666 blocked for more than 120 seconds. Jan 19 18:40:41 vhost003 kernel: Tainted: G I E 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1 Jan 19 18:40:41 vhost003 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 19 18:40:41 vhost003 kernel: btrfs-transacti D 0 666 2 0x8000 Jan 19 18:40:41 vhost003 kernel: Call Trace: Jan 19 18:40:41 vhost003 kernel: ? __schedule+0x3f5/0x880 Jan 19 18:40:41 vhost003 kernel: schedule+0x32/0x80 Jan 19 18:40:41 vhost003 kernel: btrfs_start_ordered_extent+0xed/0x120 [btrfs] Jan 19 18:40:41 vhost003 kernel: ? remove_wait_queue+0x60/0x60 Jan 19 18:40:41 vhost003 kernel: btrfs_wait_ordered_range+0xa0/0x100 [btrfs] Jan 19 18:40:41 vhost003 kernel: __btrfs_wait_cache_io+0x46/0x1c0 [btrfs] Jan 19 18:40:41 vhost003 kernel: btrfs_start_dirty_block_groups+0x1ad/0x4b0 [btrfs] Jan 19 18:40:41 vhost003 kernel: btrfs_commit_transaction+0xc8/0x8a0 [btrfs] Jan 19 18:40:41 vhost003 kernel: ? start_transaction+0x8f/0x3e0 [btrfs] Jan 19 18:40:41 vhost003 kernel: transaction_kthread+0x157/0x180 [btrfs] Jan 19 18:40:41 vhost003 kernel: kthread+0xf8/0x130 Jan 19 18:40:41 vhost003 kernel: ? btrfs_cleanup_transaction+0x500/0x500 [btrfs] Jan 19 18:40:41 vhost003 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Jan 19 18:40:41 vhost003 kernel: ret_from_fork+0x35/0x40 Jan 19 18:42:42 vhost003 kernel: INFO: task btrfs-transacti:666 blocked for more than 120 seconds. Jan 19 18:42:42 vhost003 kernel: Tainted: G I E 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1 Jan 19 18:42:42 vhost003 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 19 18:42:42 vhost003 kernel: btrfs-transacti D0 666 2 0x8000 Jan 19 18:42:42 vhost003 kernel: Call Trace: Jan 19 18:42:42 vhost003 kernel: ? __schedule+0x3f5/0x880 Jan 19 18:42:42 vhost003 kernel: schedule+0x32/0x80 Jan 19 18:42:42 vhost003 kernel: btrfs_start_ordered_extent+0xed/0x120 [btrfs] Jan 19 18:42:42 vhost003 kernel: ? remove_wait_queue+0x60/0x60 Jan 19 18:42:42 vhost003 kernel: btrfs_wait_ordered_range+0xa0/0x100 [btrfs] Jan 19 18:42:42 vhost003 kernel: __btrfs_wait_cache_io+0x46/0x1c0 [btrfs] Jan 19 18:42:42 vhost003 kernel: btrfs_start_dirty_block_groups+0x1ad/0x4b0 [btrfs] Jan 19 18:42:42 vhost003 kernel: btrfs_commit_transaction+0xc8/0x8a0 [btrfs] Jan 19 18:42:42 vhost003 kernel: ? start_transaction+0x8f/0x3e0 [btrfs] Jan 19 18:42:42 vhost003 kernel: transaction_kthread+0x157/0x180 [btrfs] Jan 19 18:42:42 vhost003 kernel: kthread+0xf8/0x130 Jan 19 18:42:42 vhost003 kernel: ? btrfs_cleanup_transaction+0x500/0x500 [btrfs] Jan 19 18:42:42 vhost003 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Jan 19 18:42:42 vhost003 kernel: ret_from_fork+0x35/0x40 Jan 19 18:44:43 vhost003 kernel: INFO: task btrfs-transacti:666 blocked for more than 120 seconds. Jan 19 18:44:43 vhost003 kernel: Tainted: G I E 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1 Jan 19 18:44:43 vhost003 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 19 18:44:43 vhost003 kernel: btrfs-transacti D0 666 2 0x8000 Jan 19 18:44:43 vhost003 kernel: Call Trace: Jan 19 18:44:43 vhost003 kernel: ? __schedule+0x3f5/0x880 Jan 19 18:44:43 vhost003 kernel: schedule+0x32/0x80 Jan 19 18:44:43 vhost003 kernel: btrfs_start_ordered_extent+0xed/0x120 [btrfs] Jan 19 18:44:43 vhost003 kernel: ? remove_wait_queue+0x60/0x60 Jan 19 18:44:43 vhost003 kernel: btrfs_wait_ordered_range+0xa0/0x100 [btrfs] Jan 19 18:44:43 vhost003 kernel: __btrfs_wait_cache_io+0x46/0x1c0 [btrfs] Jan 19 18:44:43 vhost003 kernel: btrfs_start_dirty_block_groups+0x1ad/0x4b0 [btrfs] Jan 19 18:44:43 vhost003 kernel: btrfs_commit_transaction+0xc8/0x8a0 [btrfs] Jan 19 18:44:43 vhost003 kernel: ? start_transaction+0x8f/0x3e0 [btrfs] Jan 19 18:44:43 vhost003 kernel: transaction_kthread+0x157/0x180 [btrfs] Jan 19 18:44:43 vhost003 kernel: kthread+0xf8/0x130 Jan 19 18:44:43 vhost003 kernel: ? btrfs_cleanup_transaction+0x500/0x500 [btrfs] Jan 19 18:44:43 vhost003 kernel: ? kthread_create_worker_on_cpu+0x70/0x70 Jan 19 18:44:43 vhost003 kernel: ret_from_fork+0x35/0x40 Jan 19 18:46:43 vhost003 kernel: INFO: task btrfs-transacti:666 blocked for more than 120 seconds. Jan 19 18:46:43 vhost003 kernel: Tainted: G I E 4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1 Jan 19 18:46:43 vhost003 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 19 18:46:43 vhost003 kernel: btrfs-transacti D0 666 2 0x8000 Jan 19 18:46:43 vhost003 kernel: Call Trace: Jan 19 18:46:43 vhost003 kernel: ? __schedule+0x3f5/0x880 Jan 19 18:46:43 vhost003 kernel: schedule+0x32/0x80 Jan 19 18:46:43 vhost003
Processed: reassign 919826 to src:linux, severity of 919826 is important
Processing commands for cont...@bugs.debian.org: > reassign 919826 src:linux 4.19.12-1 Bug #919826 [linux-image-4.19.0-1-arm64] linux-image-4.19.0-1-arm64: Loading Linux 4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic Bug reassigned from package 'linux-image-4.19.0-1-arm64' to 'src:linux'. Ignoring request to alter found versions of bug #919826 to the same values previously set Ignoring request to alter fixed versions of bug #919826 to the same values previously set Bug #919826 [src:linux] linux-image-4.19.0-1-arm64: Loading Linux 4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic Marked as found in versions linux/4.19.12-1. > severity 919826 important Bug #919826 [src:linux] linux-image-4.19.0-1-arm64: Loading Linux 4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 919826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919826 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 919656 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 919656 src:linux 4.19.12-1 Bug #919656 [linux-image-amd64] usb - surface dock - ethernet - fix included Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-latest/101. Ignoring request to alter fixed versions of bug #919656 to the same values previously set Bug #919656 [src:linux] usb - surface dock - ethernet - fix included Marked as found in versions linux/4.19.12-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 919656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 919648 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 919648 src:linux 4.19.13-1 Bug #919648 [linux-image-amd64] i2c - Elantech touchscreen - Surface GO - not recognized properly - but working in general with changes Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-latest/101. Ignoring request to alter fixed versions of bug #919648 to the same values previously set Bug #919648 [src:linux] i2c - Elantech touchscreen - Surface GO - not recognized properly - but working in general with changes Marked as found in versions linux/4.19.13-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 919648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 919648 in 4.19.13-1, found 919648 in 4.19.12-1
Processing commands for cont...@bugs.debian.org: > notfound 919648 4.19.13-1 Bug #919648 [src:linux] i2c - Elantech touchscreen - Surface GO - not recognized properly - but working in general with changes No longer marked as found in versions linux/4.19.13-1. > found 919648 4.19.12-1 Bug #919648 [src:linux] i2c - Elantech touchscreen - Surface GO - not recognized properly - but working in general with changes Marked as found in versions linux/4.19.12-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 919648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Processed: your mail
On Sat, 2019-01-19 at 22:36 +, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > reassign 919648 linux-image-amd64 4.19+101 This is not correct. Bugs should be reassigned to the responsible source package if the binary package name is not stable. In this case, that would be src:linux. linux-image-amd64 is a metapackage built from src:linux-latest, which is certainly not responsible for this bug. Ben. -- Ben Hutchings You can't have everything. Where would you put it? signature.asc Description: This is a digitally signed message part
Bug#919826: linux-image-4.19.0-1-arm64: Loading Linux 4.19.0-1-arm64 Loading initial ramdisk error: out of memory system panic
Package: linux-image-4.19.0-1-arm64 Severity: critical Justification: breaks the whole system Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? upgrading kernel in Buster from 4.18.0-3-arm64 via apt-get dist-upgrade * What exactly did you do (or not do) that was effective (or ineffective)? root@sally:~# uname -a Linux sally 4.18.0-3-arm64 #1 SMP Debian 4.18.20-2 (2018-11-23) aarch64 GNU/Linux root@sally:~# ## update apt/sources to point to a mirror (was DVD) root@sally:~# apt-get update Hit:1 http://ftp.uk.debian.org/debian buster InRelease Hit:2 http://security.debian.org/debian-security buster/updates InRelease Reading package lists... Done root@sally:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libhunspell-1.6-0 liblvm2app2.2 liblvm2cmd2.02 libpython3.6-minimal libpython3.6-stdlib python3.6 python3.6-minimal Use 'apt autoremove' to remove them. The following NEW packages will be installed: apparmor firmware-linux-free irqbalance libaio1 libdns-export1104 libhunspell-1.7-0 libisc-export1100 liblvm2cmd2.03 libnftables0 libnftnl11 libnuma1 libpython3.7-minimal libpython3.7-stdlib libuchardet0 linux-image-4.19.0-1-arm64 nftables python3.7 python3.7-minimal The following packages will be upgraded: adwaita-icon-theme apt apt-utils bash-completion bind9-host bsdutils dash dbus dbus-user-session dconf-gsettings-backend dconf-service dmeventd dmsetup e2fsprogs enchant fdisk file gcc-8-base gir1.2-atk-1.0 gir1.2-freedesktop gir1.2-gdkpixbuf-2.0 gir1.2-glib-2.0 gir1.2-gtk-3.0 gir1.2-pango-1.0 gir1.2-vte-2.91 glib-networking glib-networking-common glib-networking-services gpgv grep groff-base grub-common grub-efi-arm64 grub-efi-arm64-bin grub-efi-arm64-signed grub2-common gtk-update-icon-cache gzip init init-system-helpers iproute2 iptables isc-dhcp-client isc-dhcp-common klibc-utils krb5-locales libapparmor1 libapt-inst2.0 libapt-pkg5.0 libatk1.0-0 libatk1.0-data libbind9-161 libblkid1 libc-bin libc-l10n libc6 libcairo-gobject2 libcairo2 libcap-ng0 libcom-err2 libcroco3 libcryptsetup12 libcups2 libdbus-1-3 libdconf1 libdebconfclient0 libdevmapper-event1.02.1 libdevmapper1.02.1 libdns1104 libedit2 libefiboot1 libefivar1 libelf1 libenchant1c2a libext2fs2 libfdisk1 libfribidi0 libfstrm0 libfuse2 libgcc1 libgcrypt20 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common libgirepository-1.0-1 libglib2.0-0 libglib2.0-data libgmp10 libgnutls30 libgpg-error0 libgraphite2-3 libgssapi-krb5-2 libgtk-3-0 libgtk-3-bin libgtk-3-common libharfbuzz0b libhogweed4 libicu63 libip4tc0 libip6tc0 libiptc0 libisc1100 libisccc161 libisccfg163 libjansson4 libjson-glib-1.0-0 libjson-glib-1.0-common libk5crypto3 libklibc libkrb5-3 libkrb5support0 libldap-2.4-2 libldap-common liblwres161 liblz4-1 libmagic-mgc libmagic1 libmount1 libnettle6 libnghttp2-14 libpam-modules libpam-modules-bin libpam-runtime libpam-systemd libpam0g libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libperl5.28 libpixman-1-0 libpng16-16 libproxy1v5 libpython3-stdlib libpython3.6-minimal libpython3.6-stdlib librsvg2-2 librsvg2-common libsemanage-common libsemanage1 libsmartcols1 libsoup-gnome2.4-1 libsoup2.4-1 libsqlite3-0 libss2 libstdc++6 libsystemd0 libudev1 libuuid1 libvte-2.91-0 libvte-2.91-common libxcb-render0 libxcb-shm0 libxcb1 libxml2 libxtables12 libzstd1 linux-image-arm64 locales lvm2 man-db mount openssh-client openssh-server openssh-sftp-server os-prober perl perl-base perl-modules-5.28 publicsuffix python3 python3-chardet python3-debianbts python3-gi python3-gi-cairo python3-minimal python3-pkg-resources python3-pycurl python3-pysimplesoap python3-six python3.6 python3.6-minimal rsyslog sed systemd systemd-sysv sysvinit-utils tar task-english task-ssh-server tasksel tasksel-data telnet tzdata ucf udev util-linux util-linux-locales vim-common vim-tiny wget xdg-user-dirs xxd 203 upgraded, 18 newly installed, 0 to remove and 0 not upgraded. Need to get 144 MB of archives. After this operation, 260 MB of additional disk space will be used. Do you want to continue? [Y/n] --- 8< --- Get:207 http://ftp.uk.debian.org/debian buster/main arm64 linux-image-4.19.0-1-arm64 arm64 4.19.12-1 [39.7 MB] Get:208 http://ftp.uk.debian.org/debian buster/main arm64 linux-image-arm64 arm64 4.19+101 [7,952 B] --- 8< --- Processing triggers for systemd (240-4) ... Setting up grub-efi-arm64 (2.02+dfsg1-10) ... Installing for arm64-efi platform. Installation finished. No error reported. Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.19.0-1-arm64 Found initrd
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > retitle 919648 i2c - Elantech touchscreen - Surface GO - not recognized Bug #919648 [linux-image-amd64] i2c - Elantech touchscreen - Surface GO - not recognized properly Changed Bug title to 'i2c - Elantech touchscreen - Surface GO - not recognized' from 'i2c - Elantech touchscreen - Surface GO - not recognized properly'. > properly - but working in general with changes Unknown command or malformed arguments to command. > -- Stopping processing here. Please contact me if you need assistance. -- 919648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 919656 linux-image-amd64 4.19+101 Bug #919656 [linux-image-4.19.0-1-amd64] usb - surface dock - ethernet - fix included Bug reassigned from package 'linux-image-4.19.0-1-amd64' to 'linux-image-amd64'. Ignoring request to alter found versions of bug #919656 to the same values previously set Ignoring request to alter fixed versions of bug #919656 to the same values previously set Bug #919656 [linux-image-amd64] usb - surface dock - ethernet - fix included Marked as found in versions linux-latest/101. > -- Stopping processing here. Please contact me if you need assistance. -- 919656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 919648 linux-image-amd64 4.19+101 Bug #919648 [linux-image-4.19.0-1-amd64] i2c - Elantech touchscreen - Surface GO - not recognized properly Bug reassigned from package 'linux-image-4.19.0-1-amd64' to 'linux-image-amd64'. Ignoring request to alter found versions of bug #919648 to the same values previously set Ignoring request to alter fixed versions of bug #919648 to the same values previously set Bug #919648 [linux-image-amd64] i2c - Elantech touchscreen - Surface GO - not recognized properly Marked as found in versions linux-latest/101. > -- Stopping processing here. Please contact me if you need assistance. -- 919648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919648 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919706: Removed package(s) from experimental
We believe that the bug you reported is now fixed; the following package(s) have been removed from experimental: acpi-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 acpi-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 acpi-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 ata-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 ata-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 ata-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 ata-modules-4.10.0-rc6-arm64-di | 4.10~rc6-1~exp2 | arm64 ata-modules-4.10.0-rc6-armmp-di | 4.10~rc6-1~exp2 | armhf ata-modules-4.10.0-rc6-powerpc64le-di | 4.10~rc6-1~exp2 | ppc64el btrfs-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 btrfs-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 btrfs-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 btrfs-modules-4.10.0-rc6-arm64-di | 4.10~rc6-1~exp2 | arm64 btrfs-modules-4.10.0-rc6-armmp-di | 4.10~rc6-1~exp2 | armhf btrfs-modules-4.10.0-rc6-powerpc64le-di | 4.10~rc6-1~exp2 | ppc64el btrfs-modules-4.10.0-rc6-s390x-di | 4.10~rc6-1~exp2 | s390x cdrom-core-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 cdrom-core-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 cdrom-core-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 cdrom-core-modules-4.10.0-rc6-arm64-di | 4.10~rc6-1~exp2 | arm64 cdrom-core-modules-4.10.0-rc6-powerpc64le-di | 4.10~rc6-1~exp2 | ppc64el crc-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 crc-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 crc-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 crc-modules-4.10.0-rc6-arm64-di | 4.10~rc6-1~exp2 | arm64 crc-modules-4.10.0-rc6-armmp-di | 4.10~rc6-1~exp2 | armhf crc-modules-4.10.0-rc6-powerpc64le-di | 4.10~rc6-1~exp2 | ppc64el crc-modules-4.10.0-rc6-s390x-di | 4.10~rc6-1~exp2 | s390x crypto-dm-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 crypto-dm-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 crypto-dm-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 crypto-dm-modules-4.10.0-rc6-arm64-di | 4.10~rc6-1~exp2 | arm64 crypto-dm-modules-4.10.0-rc6-armmp-di | 4.10~rc6-1~exp2 | armhf crypto-dm-modules-4.10.0-rc6-powerpc64le-di | 4.10~rc6-1~exp2 | ppc64el crypto-dm-modules-4.10.0-rc6-s390x-di | 4.10~rc6-1~exp2 | s390x crypto-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 crypto-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 crypto-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 crypto-modules-4.10.0-rc6-arm64-di | 4.10~rc6-1~exp2 | arm64 crypto-modules-4.10.0-rc6-armmp-di | 4.10~rc6-1~exp2 | armhf crypto-modules-4.10.0-rc6-powerpc64le-di | 4.10~rc6-1~exp2 | ppc64el crypto-modules-4.10.0-rc6-s390x-di | 4.10~rc6-1~exp2 | s390x dasd-extra-modules-4.10.0-rc6-s390x-di | 4.10~rc6-1~exp2 | s390x dasd-modules-4.10.0-rc6-s390x-di | 4.10~rc6-1~exp2 | s390x efi-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 efi-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 efi-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 efi-modules-4.10.0-rc6-arm64-di | 4.10~rc6-1~exp2 | arm64 efi-modules-4.10.0-rc6-armmp-di | 4.10~rc6-1~exp2 | armhf event-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 event-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 event-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 event-modules-4.10.0-rc6-arm64-di | 4.10~rc6-1~exp2 | arm64 event-modules-4.10.0-rc6-armmp-di | 4.10~rc6-1~exp2 | armhf event-modules-4.10.0-rc6-powerpc64le-di | 4.10~rc6-1~exp2 | ppc64el ext4-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 ext4-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 ext4-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 ext4-modules-4.10.0-rc6-arm64-di | 4.10~rc6-1~exp2 | arm64 ext4-modules-4.10.0-rc6-armmp-di | 4.10~rc6-1~exp2 | armhf ext4-modules-4.10.0-rc6-powerpc64le-di | 4.10~rc6-1~exp2 | ppc64el ext4-modules-4.10.0-rc6-s390x-di | 4.10~rc6-1~exp2 | s390x fancontrol-modules-4.10.0-rc6-powerpc64le-di | 4.10~rc6-1~exp2 | ppc64el fat-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 fat-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 fat-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 fat-modules-4.10.0-rc6-arm64-di | 4.10~rc6-1~exp2 | arm64 fat-modules-4.10.0-rc6-armmp-di | 4.10~rc6-1~exp2 | armhf fat-modules-4.10.0-rc6-powerpc64le-di | 4.10~rc6-1~exp2 | ppc64el fat-modules-4.10.0-rc6-s390x-di | 4.10~rc6-1~exp2 | s390x fb-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 fb-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 fb-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 fb-modules-4.10.0-rc6-arm64-di | 4.10~rc6-1~exp2 | arm64 fb-modules-4.10.0-rc6-armmp-di | 4.10~rc6-1~exp2 | armhf firewire-core-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386 firewire-core-modules-4.10.0-rc6-686-pae-di | 4.10~rc6-1~exp2 | i386 firewire-core-modules-4.10.0-rc6-amd64-di | 4.10~rc6-1~exp2 | amd64 firewire-core-modules-4.10.0-rc6-powerpc64le-di | 4.10~rc6-1~exp2 | ppc64el fuse-modules-4.10.0-rc6-686-di | 4.10~rc6-1~exp2 | i386
Bug#919648: Sources found so far
After digging a bit around I found https://github.com/torvalds/linux/bl ob/master/drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c but I was not able to find the place where the device is described and where the properties are described. Here is also some information listed https:// www.kernel.org/doc/html/v4.19/driver-api/i2c.html And also here, which seems to be the touchpad driver https://github.com /torvalds/linux/blob/master/drivers/input/touchscreen/elants_i2c.c Which information would be needed to solve the timeout issue as also the not valid recognized battery?
Bug#919807: src:linux: Please consider CONFIG_TLS=m
Package: src:linux Severity: wishlist Dear Maintainer, it would be great to have CONFIG_TLS enabled (as module like in fedora I guess) to help experiment with this functionality. Thanks! Christoph -- System Information: Debian Release: 9.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing'), (150, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.20.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) signature.asc Description: PGP signature
