Bug#927209: /boot/vmlinuz-4.19.0-4-amd64: Accupoint and touchpad (buttons) non-functional on Toshiba X30 and X40
Package: src:linux Version: 4.19.28-2 Severity: normal File: /boot/vmlinuz-4.19.0-4-amd64 The Toshiba X30 and X40 have an Accupoint (equivalent to a TrackPoint on a Lenovo laptop). This doesn't work in Linux in a rather annoying way: If I try to move the cursor with the Accupoint, it doesn't move. However, subsequent attempts to move the pointer with the trackpad do not move the pointer on-screen; instead each motion event delivers a button touch event, effectively delivering rapid-fire clicking of whatever is beneath the pointer. The more I moved the Accupoint before switching to the Touchpad, the longer it remains stuck in this state. Maybe the hardware is sending data to the kernel that it doesn't understand, and the kernel misinterprets it until it's all been consumed... I'm attaching the output of 'evtest /dev/input/event5' showing both the trackpad operating normally, and it operating after the Accupoint is poked. In addition, while the touchpad delivers motion events and button press events from pushing down on it (there's a physical switch triggered when enough force is applied by the user's finger), the physical buttons above the touch pad (left/right mouse button) don't work. Pushing them causes no events to be emitted according to evtest. -- Package-specific info: ** Version: Linux version 4.19.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-4-amd64 root=/dev/mapper/fragarach-root ro quiet zswap.enabled=1 swapaccount=1 splash ** Tainted: U (64) * Userspace-defined naughtiness. ** Kernel log: [ 8794.842745] pci :05:01.0: bridge window [mem 0xa000-0xb7ef] [ 8794.842751] pci :05:01.0: bridge window [mem 0x4000-0x5fff 64bit pref] [ 8794.842759] pci :05:02.0: PCI bridge to [bus 3a] [ 8794.842766] pci :05:02.0: bridge window [mem 0xb7f0-0xb7ff] [ 8794.842777] pci :05:04.0: PCI bridge to [bus 3b-6e] [ 8794.842783] pci :05:04.0: bridge window [mem 0xb800-0xcdff] [ 8794.842789] pci :05:04.0: bridge window [mem 0x6000-0x89ff 64bit pref] [ 8794.842797] pci :04:00.0: PCI bridge to [bus 05-6e] [ 8794.842803] pci :04:00.0: bridge window [mem 0xa000-0xce0f] [ 8794.842809] pci :04:00.0: bridge window [mem 0x4000-0x89ff 64bit pref] [ 8794.848162] xhci_hcd :3a:00.0: xHCI Host Controller [ 8794.848170] xhci_hcd :3a:00.0: new USB bus registered, assigned bus number 3 [ 8794.849320] xhci_hcd :3a:00.0: hcc params 0x200077c1 hci version 0x110 quirks 0x9810 [ 8794.849633] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 8794.849636] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 8794.849638] usb usb3: Product: xHCI Host Controller [ 8794.849640] usb usb3: Manufacturer: Linux 4.19.0-4-amd64 xhci-hcd [ 8794.849643] usb usb3: SerialNumber: :3a:00.0 [ 8794.849844] hub 3-0:1.0: USB hub found [ 8794.849856] hub 3-0:1.0: 2 ports detected [ 8794.850447] xhci_hcd :3a:00.0: xHCI Host Controller [ 8794.850454] xhci_hcd :3a:00.0: new USB bus registered, assigned bus number 4 [ 8794.850459] xhci_hcd :3a:00.0: Host supports USB 3.1 Enhanced SuperSpeed [ 8794.850510] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19 [ 8794.850513] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 8794.850515] usb usb4: Product: xHCI Host Controller [ 8794.850518] usb usb4: Manufacturer: Linux 4.19.0-4-amd64 xhci-hcd [ 8794.850520] usb usb4: SerialNumber: :3a:00.0 [ 8794.850671] hub 4-0:1.0: USB hub found [ 8794.850683] hub 4-0:1.0: 2 ports detected [ 8795.186197] usb 3-1: new high-speed USB device number 2 using xhci_hcd [ 8795.335758] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee1, bcdDevice= 4.40 [ 8795.335766] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 8795.335770] usb 3-1: Product: Pixel 3 [ 8795.335775] usb 3-1: Manufacturer: Google [ 8795.335779] usb 3-1: SerialNumber: 88EX01280 [ 8795.804568] usb 1-5: USB disconnect, device number 10 [ 8796.110230] usb 1-5: new full-speed USB device number 12 using xhci_hcd [ 8796.259646] usb 1-5: New USB device found, idVendor=1fd2, idProduct=6014, bcdDevice= 1.00 [ 8796.259653] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 8796.259657] usb 1-5: Product: LGDisplay Incell Touch [ 8796.259662] usb 1-5: Manufacturer: Melfas [ 8796.264591] input: Melfas LGDisplay Incell Touch as /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/0003:1FD2:6014.000C/input/input24 [ 8796.265032] hid-generic 0003:1FD2:6014.000C: input,hidraw0: USB HID v1.11 Device [Melfas LGDisplay Incell Touch] on usb-:00:14.0-5/input0 [ 8796.266425] hid-generic 0003:1FD2:6014.000D: hiddev0,hidraw1: USB HID v1.11 Device [Melfas LGDisplay Incell Touch] on usb-:00:14.0-5/input1 [ 8800.046056] uc
Bug#927210: /boot/vmlinuz-4.19.0-4-amd64: Accupoint and touchpad (buttons) non-functional on Toshiba X30 and X40
Package: src:linux Version: 4.19.28-2 Severity: normal File: /boot/vmlinuz-4.19.0-4-amd64 The Toshiba X30 and X40 have an Accupoint (equivalent to a TrackPoint on a Lenovo laptop). This doesn't work in Linux in a rather annoying way: If I try to move the cursor with the Accupoint, it doesn't move. However, subsequent attempts to move the pointer with the trackpad do not move the pointer on-screen; instead each motion event delivers a button touch event, effectively delivering rapid-fire clicking of whatever is beneath the pointer. The more I moved the Accupoint before switching to the Touchpad, the longer it remains stuck in this state. Maybe the hardware is sending data to the kernel that it doesn't understand, and the kernel misinterprets it until it's all been consumed... I'm attaching the output of 'evtest /dev/input/event5' showing both the trackpad operating normally, and it operating after the Accupoint is poked. In addition, while the touchpad delivers motion events and button press events from pushing down on it (there's a physical switch triggered when enough force is applied by the user's finger), the physical buttons above the touch pad (left/right mouse button) don't work. Pushing them causes no events to be emitted according to evtest. -- Package-specific info: ** Version: Linux version 4.19.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-4-amd64 root=/dev/mapper/fragarach-root ro quiet zswap.enabled=1 swapaccount=1 splash ** Tainted: U (64) * Userspace-defined naughtiness. ** Kernel log: [ 8794.842745] pci :05:01.0: bridge window [mem 0xa000-0xb7ef] [ 8794.842751] pci :05:01.0: bridge window [mem 0x4000-0x5fff 64bit pref] [ 8794.842759] pci :05:02.0: PCI bridge to [bus 3a] [ 8794.842766] pci :05:02.0: bridge window [mem 0xb7f0-0xb7ff] [ 8794.842777] pci :05:04.0: PCI bridge to [bus 3b-6e] [ 8794.842783] pci :05:04.0: bridge window [mem 0xb800-0xcdff] [ 8794.842789] pci :05:04.0: bridge window [mem 0x6000-0x89ff 64bit pref] [ 8794.842797] pci :04:00.0: PCI bridge to [bus 05-6e] [ 8794.842803] pci :04:00.0: bridge window [mem 0xa000-0xce0f] [ 8794.842809] pci :04:00.0: bridge window [mem 0x4000-0x89ff 64bit pref] [ 8794.848162] xhci_hcd :3a:00.0: xHCI Host Controller [ 8794.848170] xhci_hcd :3a:00.0: new USB bus registered, assigned bus number 3 [ 8794.849320] xhci_hcd :3a:00.0: hcc params 0x200077c1 hci version 0x110 quirks 0x9810 [ 8794.849633] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 8794.849636] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 8794.849638] usb usb3: Product: xHCI Host Controller [ 8794.849640] usb usb3: Manufacturer: Linux 4.19.0-4-amd64 xhci-hcd [ 8794.849643] usb usb3: SerialNumber: :3a:00.0 [ 8794.849844] hub 3-0:1.0: USB hub found [ 8794.849856] hub 3-0:1.0: 2 ports detected [ 8794.850447] xhci_hcd :3a:00.0: xHCI Host Controller [ 8794.850454] xhci_hcd :3a:00.0: new USB bus registered, assigned bus number 4 [ 8794.850459] xhci_hcd :3a:00.0: Host supports USB 3.1 Enhanced SuperSpeed [ 8794.850510] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19 [ 8794.850513] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 8794.850515] usb usb4: Product: xHCI Host Controller [ 8794.850518] usb usb4: Manufacturer: Linux 4.19.0-4-amd64 xhci-hcd [ 8794.850520] usb usb4: SerialNumber: :3a:00.0 [ 8794.850671] hub 4-0:1.0: USB hub found [ 8794.850683] hub 4-0:1.0: 2 ports detected [ 8795.186197] usb 3-1: new high-speed USB device number 2 using xhci_hcd [ 8795.335758] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee1, bcdDevice= 4.40 [ 8795.335766] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 8795.335770] usb 3-1: Product: Pixel 3 [ 8795.335775] usb 3-1: Manufacturer: Google [ 8795.335779] usb 3-1: SerialNumber: 88EX01280 [ 8795.804568] usb 1-5: USB disconnect, device number 10 [ 8796.110230] usb 1-5: new full-speed USB device number 12 using xhci_hcd [ 8796.259646] usb 1-5: New USB device found, idVendor=1fd2, idProduct=6014, bcdDevice= 1.00 [ 8796.259653] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 8796.259657] usb 1-5: Product: LGDisplay Incell Touch [ 8796.259662] usb 1-5: Manufacturer: Melfas [ 8796.264591] input: Melfas LGDisplay Incell Touch as /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/0003:1FD2:6014.000C/input/input24 [ 8796.265032] hid-generic 0003:1FD2:6014.000C: input,hidraw0: USB HID v1.11 Device [Melfas LGDisplay Incell Touch] on usb-:00:14.0-5/input0 [ 8796.266425] hid-generic 0003:1FD2:6014.000D: hiddev0,hidraw1: USB HID v1.11 Device [Melfas LGDisplay Incell Touch] on usb-:00:14.0-5/input1 [ 8800.046056] uc
Processed: closing 927210
Processing commands for cont...@bugs.debian.org: > close 927210 Bug #927210 [src:linux] /boot/vmlinuz-4.19.0-4-amd64: Accupoint and touchpad (buttons) non-functional on Toshiba X30 and X40 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 927210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927211: /boot/vmlinuz-4.19.0-4-amd64: Accupoint and touchpad (buttons) non-functional on Toshiba X30 and X40
Package: src:linux Version: 4.19.28-2 Severity: normal File: /boot/vmlinuz-4.19.0-4-amd64 The Toshiba X30 and X40 have an Accupoint (equivalent to a TrackPoint on a Lenovo laptop). This doesn't work in Linux in a rather annoying way: If I try to move the cursor with the Accupoint, it doesn't move. However, subsequent attempts to move the pointer with the trackpad do not move the pointer on-screen; instead each motion event delivers a button touch event, effectively delivering rapid-fire clicking of whatever is beneath the pointer. The more I moved the Accupoint before switching to the Touchpad, the longer it remains stuck in this state. Maybe the hardware is sending data to the kernel that it doesn't understand, and the kernel misinterprets it until it's all been consumed... I'm attaching the output of 'evtest /dev/input/event5' showing both the trackpad operating normally, and it operating after the Accupoint is poked. In addition, while the touchpad delivers motion events and button press events from pushing down on it (there's a physical switch triggered when enough force is applied by the user's finger), the physical buttons above the touch pad (left/right mouse button) don't work. Pushing them causes no events to be emitted according to evtest. -- Package-specific info: ** Version: Linux version 4.19.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15) ** Command line: BOOT_IMAGE=/vmlinuz-4.19.0-4-amd64 root=/dev/mapper/fragarach-root ro quiet zswap.enabled=1 swapaccount=1 splash ** Tainted: U (64) * Userspace-defined naughtiness. ** Kernel log: [ 8794.842745] pci :05:01.0: bridge window [mem 0xa000-0xb7ef] [ 8794.842751] pci :05:01.0: bridge window [mem 0x4000-0x5fff 64bit pref] [ 8794.842759] pci :05:02.0: PCI bridge to [bus 3a] [ 8794.842766] pci :05:02.0: bridge window [mem 0xb7f0-0xb7ff] [ 8794.842777] pci :05:04.0: PCI bridge to [bus 3b-6e] [ 8794.842783] pci :05:04.0: bridge window [mem 0xb800-0xcdff] [ 8794.842789] pci :05:04.0: bridge window [mem 0x6000-0x89ff 64bit pref] [ 8794.842797] pci :04:00.0: PCI bridge to [bus 05-6e] [ 8794.842803] pci :04:00.0: bridge window [mem 0xa000-0xce0f] [ 8794.842809] pci :04:00.0: bridge window [mem 0x4000-0x89ff 64bit pref] [ 8794.848162] xhci_hcd :3a:00.0: xHCI Host Controller [ 8794.848170] xhci_hcd :3a:00.0: new USB bus registered, assigned bus number 3 [ 8794.849320] xhci_hcd :3a:00.0: hcc params 0x200077c1 hci version 0x110 quirks 0x9810 [ 8794.849633] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 [ 8794.849636] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 8794.849638] usb usb3: Product: xHCI Host Controller [ 8794.849640] usb usb3: Manufacturer: Linux 4.19.0-4-amd64 xhci-hcd [ 8794.849643] usb usb3: SerialNumber: :3a:00.0 [ 8794.849844] hub 3-0:1.0: USB hub found [ 8794.849856] hub 3-0:1.0: 2 ports detected [ 8794.850447] xhci_hcd :3a:00.0: xHCI Host Controller [ 8794.850454] xhci_hcd :3a:00.0: new USB bus registered, assigned bus number 4 [ 8794.850459] xhci_hcd :3a:00.0: Host supports USB 3.1 Enhanced SuperSpeed [ 8794.850510] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19 [ 8794.850513] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 8794.850515] usb usb4: Product: xHCI Host Controller [ 8794.850518] usb usb4: Manufacturer: Linux 4.19.0-4-amd64 xhci-hcd [ 8794.850520] usb usb4: SerialNumber: :3a:00.0 [ 8794.850671] hub 4-0:1.0: USB hub found [ 8794.850683] hub 4-0:1.0: 2 ports detected [ 8795.186197] usb 3-1: new high-speed USB device number 2 using xhci_hcd [ 8795.335758] usb 3-1: New USB device found, idVendor=18d1, idProduct=4ee1, bcdDevice= 4.40 [ 8795.335766] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 8795.335770] usb 3-1: Product: Pixel 3 [ 8795.335775] usb 3-1: Manufacturer: Google [ 8795.335779] usb 3-1: SerialNumber: 88EX01280 [ 8795.804568] usb 1-5: USB disconnect, device number 10 [ 8796.110230] usb 1-5: new full-speed USB device number 12 using xhci_hcd [ 8796.259646] usb 1-5: New USB device found, idVendor=1fd2, idProduct=6014, bcdDevice= 1.00 [ 8796.259653] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 8796.259657] usb 1-5: Product: LGDisplay Incell Touch [ 8796.259662] usb 1-5: Manufacturer: Melfas [ 8796.264591] input: Melfas LGDisplay Incell Touch as /devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/0003:1FD2:6014.000C/input/input24 [ 8796.265032] hid-generic 0003:1FD2:6014.000C: input,hidraw0: USB HID v1.11 Device [Melfas LGDisplay Incell Touch] on usb-:00:14.0-5/input0 [ 8796.266425] hid-generic 0003:1FD2:6014.000D: hiddev0,hidraw1: USB HID v1.11 Device [Melfas LGDisplay Incell Touch] on usb-:00:14.0-5/input1 [ 8800.046056] uc
Processed: closing 927211
Processing commands for cont...@bugs.debian.org: > close 927211 Bug #927211 [src:linux] /boot/vmlinuz-4.19.0-4-amd64: Accupoint and touchpad (buttons) non-functional on Toshiba X30 and X40 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 927211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#927246: usbip: QEMU destructively resets USBIP devices
Package: usbip Version: 2.0+4.9.144-3.1 Severity: normal Tags: upstream Dear Maintainer, Attempting to pass a usbip device to qemu fails. Qemu resets the device and it does not reappear. Dmesg prompts warn of checking the cable connection and that the device does not enumerate. It is suspected qemu reenumerates the device and this causes usbip to drop the connection but I can not be sure. The device passes to a VM when done directly. -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-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) Versions of packages usbip depends on: ii libc6 2.24-11+deb9u4 ii libudev1 232-25+deb9u11 ii libwrap0 7.6.q-26 ii usbutils 1:007-4+b1 usbip recommends no packages. usbip suggests no packages. -- no debconf information
Bug#927247: usbip: qemu destructively resets usbip device
Package: usbip Version: 2.0+4.9.144-3.1 Severity: important Dear Maintainer, When passing a usbip device to qemu, qemu appears to reenumerate the device which causes the connection to the usbipd to become upset. The device is then unavailable for use in the VM or on the usbip client. The device in question is an HID device and works when passed through on what is intended to the be the server computer to a VM. Modules were blacklisted to ensure they did not upset qemu's capture of the device fds. Once the VM starts dmesg logs failure to enumerate messages, and admonishes the user to check the cable. I apologize for marking the bug as important but it makes the package useless for my purposes. Cheers, sg -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-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) Versions of packages usbip depends on: ii libc6 2.24-11+deb9u4 ii libudev1 232-25+deb9u11 ii libwrap0 7.6.q-26 ii usbutils 1:007-4+b1 usbip recommends no packages. usbip suggests no packages. -- no debconf information
Bug#927184: SATA SSD affected as well
Looks like SATA SSD affected as well. Another example: Device r/s w/s rMB/s wMB/s rrqm/s wrqm/s %rrqm %wrqm r_await w_await aqu-sz rareq-sz wareq-sz svctm %util sda 0.47 8.94 0.01 0.48 0.00 8.05 0.10 47.39 0.25 1.29 0.97 11.60 54.71 101.89 95.93 cat /proc/diskstats 8 0 sda 491891 492 11411048 123425 9276833 8357440 1015034844 11962746 0 995354116 1004716180 196878 0 1461959742 168844 8 1 sda1 626 12 9590 187 77 249 56356 333 0 340 616 161 0 269038 137 8 2 sda2 4500 182 41464 1101 20884 15531 348440 2415 0 2604 3184 0 0 0 0 8 3 sda3 486635 298 11353698 122074 9222603 8341660 1014630048 11958045 0 2035580 9165808 196717 0 1461690704 168706 Model: ATA INTEL SSDSC2BB48 (scsi) Disk /dev/sda: 480GB
Bug#927252: linux-4.19.0-4-arm64: Enable SPI CAN drivers for ARM/AARCH64
Package: src:linux Version: 4.19.28-2 Severity: wishlist Tags: patch Dear Maintainer, Please consider enabling the SPI-attached CAN bus drivers in the Debian kernel. They are useful on ARM SoCs with an SPI bus, such as the Raspberry Pi. The Raspbian kernel package already includes these drivers, and they do no harm on platforms that don't use them. To load these drivers, a suitable DeviceTree config is required. Thank you! Here's a patch for .config: --- a/.config 2019-03-15 02:16:04.0 + +++ b/.config 2019-04-16 21:46:33.124431597 + @@ -1696,8 +1699,8 @@ # # CAN SPI interfaces # -# CONFIG_CAN_HI311X is not set -# CONFIG_CAN_MCP251X is not set +CONFIG_CAN_HI311X=m +CONFIG_CAN_MCP251X=m # # CAN USB interfaces -- Package-specific info: ** Version: Linux version 4.19.0-4-arm64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15) ** Command line: bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 dma.dmachans=0x7f35 bcm2709.boardrev=0xa020d3 bcm2709.serial=0xffbcac2c bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=29 bcm2709.disk_led_active_low=0 smsc95xx.macaddr=B8:27:EB:BC:AC:2C vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=tty0 root=/dev/mmcblk0p2 rw elevator=deadline fsck.repair=yes net.ifnames=0 cma=256M rootwait ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Device Tree model: Raspberry Pi 3 Model B Plus Rev 1.3 ** Loaded modules: at24 i2c_dev ip6t_REJECT nf_reject_ipv6 nft_counter ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment nft_compat nf_tables nfnetlink nls_ascii nls_cp437 vfat fat btsdio bluetooth vc4 drbg snd_soc_core ansi_cprng ecdh_generic snd_pcm_dmaengine snd_pcm microchip brcmfmac snd_timer snd soundcore brcmutil lan78xx cec cfg80211 drm_kms_helper of_mdio fixed_phy drm libphy rfkill vchiq(C) pwm_bcm2835 bcm2835_thermal bcm2835_rng rng_core bcm2835_wdt leds_gpio ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb aes_arm64 dwc2 udc_core usbcore sdhci_iproc sdhci_pltfm sdhci usb_common bcm2835 i2c_bcm2835 phy_generic ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 4.19.0-4-arm64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-4-arm64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0-4-arm64 recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 ii irqbalance 1.5.0-3 Versions of packages linux-image-4.19.0-4-arm64 suggests: pn debian-kernel-handbook pn linux-doc-4.19 Versions of packages linux-image-4.19.0-4-arm64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x ii firmware-brcm8021120190114-1 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
