[Kernel-packages] [Bug 2034916] Re: NIC RTL8168 randomly disconnected from pci bus
** Description changed: After kernel update to 6.2.0-26 and newer. The my device experience network problem from time to time. In the end, I found the NIC card actually fall off from the pcie bus: ``` lspci -vnnk 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev ff) (prog-if ff) DeviceName: GLAN !!! Unknown header type 7f Kernel modules: r8169 ``` Only reboot can reinitiate the nic. 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The NIC is this one https://linux- hardware.org/?id=pci:10ec-8168-1043-208f dmesg: Sep 08 10:51:39 : [ cut here ] Sep 08 10:51:39 : NETDEV WATCHDOG: eno2 (r8169): transmit queue 0 timed out Sep 08 10:51:39 : WARNING: CPU: 10 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x21f/0x230 - Sep 08 10:51:39 : Modules linked in: rfcomm xt_CHECKSUM nvme_fabrics nft_chain_nat xt_MASQUERADE nf_nat xfrm_user xfrm_algo cmac algif_hash algif_skc> - Sep 08 10:51:39 : typec_ucsi btintel spi_nor hid_multitouch mei_pxp mei_hdcp kvm iwlmvm typec ee1004 mtd intel_rapl_msr snd_seq_midi btmtk i915 btrf> - Sep 08 10:51:39 : asus_wmi ledtrig_audio sparse_keymap platform_profile hid_generic uas usbhid usb_storage nvidia_drm(POE) nvidia_modeset(POE) nvidi> + Sep 08 10:51:39 : Modules linked in: rfcomm xt_CHECKSUM nvme_fabrics nft_chain_nat xt_MASQUERADE nf_nat xfrm_user xfrm_algo cmac algif_hash algif_skci + pher af_alg bnep ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_c + onntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat sunrpc nf_tables nfnetlink binfmt_misc dm_crypt nls_iso8859_1 snd_hda_codec_realtek snd_hda_codec_generic snd_sof + _pci_intel_cnl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd + _sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_soc_core snd_hda_codec_hdmi snd_compress ac97_bus snd_pcm_dmae + ngine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec intel_tcc_cooling x86_pkg_temp_thermal snd_hda_core intel_powerclamp snd_hwdep btusb btrtl uc + si_ccg snd_pcm cmdlinepart btbcm kvm_intel + Sep 08 10:51:39 : typec_ucsi btintel spi_nor hid_multitouch mei_pxp mei_hdcp kvm iwlmvm typec ee1004 mtd intel_rapl_msr snd_seq_midi btmtk i915 btrfs + mac80211 snd_seq_midi_event irqbypass bluetooth snd_rawmidi rapl blake2b_generic drm_buddy libarc4 snd_seq ttm intel_cstate xor mfd_aaeon snd_seq_device ecdh_gene + ric asus_nb_wmi input_leds iwlwifi joydev raid6_pq processor_thermal_device_pci_legacy ecc wmi_bmof mxm_wmi snd_timer drm_display_helper processor_thermal_device s + nd r8169 cec processor_thermal_rfim i2c_i801 rc_core cfg80211 spi_intel_pci i2c_nvidia_gpu processor_thermal_mbox soundcore spi_intel i2c_ccgx_ucsi realtek intel_l + pss_pci mei_me i2c_algo_bit i2c_smbus processor_thermal_rapl intel_lpss mei intel_rapl_common idma64 intel_pch_thermal intel_soc_dts_iosf int3403_thermal int3400_t + hermal int340x_thermal_zone acpi_thermal_rel acpi_tad acpi_pad asus_wireless mac_hid nvidia_uvm(POE) sch_fq_codel pstore_blk ramoops pstore_zone reed_solomon efi_p + store xfs libcrc32c wacom hid_asus + Sep 08 10:51:39 : asus_wmi ledtrig_audio sparse_keymap platform_profile hid_generic uas usbhid usb_storage nvidia_drm(POE) nvidia_modeset(POE) nvidia + (POE) crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha512_ssse3 aesni_intel drm_kms_helper nvme crypto_simd cryptd drm nvme_co + re serio_raw ahci i2c_hid_acpi syscopyarea nvme_common libahci i2c_hid sysfillrect xhci_pci sysimgblt xhci_pci_renesas hid video wmi pinctrl_cannonlake overlay ipt + able_filter ip6table_filter ip6_tables br_netfilter bridge stp llc arp_tables coretemp msr parport_pc ppdev lp parport ip_tables x_tables autofs4 Sep 08 10:51:39 : CPU: 10 PID: 0 Comm: swapper/10 Tainted: P OE 6.2.0-32-generic #32~22.04.1-Ubuntu Sep 08 10:51:39 : Hardware name: ASUSTeK COMPUTER INC. ROG Strix G731GW_G731GW/G731GW, BIOS G731GW.309 01/29/2021 Sep 08 10:51:39 : RIP: 0010:dev_watchdog+0x21f/0x230 - Sep 08 10:51:39 : Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 66 83 78 01 01 e8 56 00 f8 ff 44 89 f1 4c 89 e6 48 c7 c7 08 4f 84 91 48 89 c2 e8 61 df 2b ff> + Sep 08 10:51:39 : Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 66 83 78 01 01 e8 56 00 f8 ff 44 89 f1 4c 89 e6 48 c7 c7 08 4f 84 91 48 89 c2 e8 61 df 2b ff <0f> 0b e9 22 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 Sep 08 10:51:39 : RSP: 0018:ace9c0378e70 EFLAGS: 00010246 Sep 08 10:51:39 : RAX: RBX: 9944cf17c4c8 RCX: Sep 08 10:51:39 :
[Kernel-packages] [Bug 2034916] Re: NIC RTL8168 randomly disconnected from pci bus
unfortunately I don't have that right now. And when network is dead apport-collect won't work. But I added some trace info from dmseg, hope that will help a little. ** Description changed: After kernel update to 6.2.0-26 and newer. The my device experience network problem from time to time. In the end, I found the NIC card actually fall off from the pcie bus: ``` lspci -vnnk 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev ff) (prog-if ff) DeviceName: GLAN !!! Unknown header type 7f Kernel modules: r8169 ``` Only reboot can reinitiate the nic. 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The NIC is this one https://linux- hardware.org/?id=pci:10ec-8168-1043-208f + + dmesg: + + Sep 08 10:51:39 : [ cut here ] + Sep 08 10:51:39 : NETDEV WATCHDOG: eno2 (r8169): transmit queue 0 timed out + Sep 08 10:51:39 : WARNING: CPU: 10 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x21f/0x230 + Sep 08 10:51:39 : Modules linked in: rfcomm xt_CHECKSUM nvme_fabrics nft_chain_nat xt_MASQUERADE nf_nat xfrm_user xfrm_algo cmac algif_hash algif_skc> + Sep 08 10:51:39 : typec_ucsi btintel spi_nor hid_multitouch mei_pxp mei_hdcp kvm iwlmvm typec ee1004 mtd intel_rapl_msr snd_seq_midi btmtk i915 btrf> + Sep 08 10:51:39 : asus_wmi ledtrig_audio sparse_keymap platform_profile hid_generic uas usbhid usb_storage nvidia_drm(POE) nvidia_modeset(POE) nvidi> + Sep 08 10:51:39 : CPU: 10 PID: 0 Comm: swapper/10 Tainted: P OE 6.2.0-32-generic #32~22.04.1-Ubuntu + Sep 08 10:51:39 : Hardware name: ASUSTeK COMPUTER INC. ROG Strix G731GW_G731GW/G731GW, BIOS G731GW.309 01/29/2021 + Sep 08 10:51:39 : RIP: 0010:dev_watchdog+0x21f/0x230 + Sep 08 10:51:39 : Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 66 83 78 01 01 e8 56 00 f8 ff 44 89 f1 4c 89 e6 48 c7 c7 08 4f 84 91 48 89 c2 e8 61 df 2b ff> + Sep 08 10:51:39 : RSP: 0018:ace9c0378e70 EFLAGS: 00010246 + Sep 08 10:51:39 : RAX: RBX: 9944cf17c4c8 RCX: + Sep 08 10:51:39 : RDX: RSI: RDI: + Sep 08 10:51:39 : RBP: ace9c0378e98 R08: R09: + Sep 08 10:51:39 : R10: R11: R12: 9944cf17c000 + Sep 08 10:51:39 : R13: 9944cf17c41c R14: R15: + Sep 08 10:51:39 : FS: () GS:9953fdc8() knlGS: + Sep 08 10:51:39 : CS: 0010 DS: ES: CR0: 80050033 + Sep 08 10:51:39 : CR2: 24e000389000 CR3: 000d32e10002 CR4: 003706e0 + Sep 08 10:51:39 : Call Trace: + Sep 08 10:51:39 : + Sep 08 10:51:39 : ? show_regs+0x72/0x90 + Sep 08 10:51:39 : ? dev_watchdog+0x21f/0x230 + Sep 08 10:51:39 : ? __warn+0x8d/0x160 + Sep 08 10:51:39 : ? dev_watchdog+0x21f/0x230 + Sep 08 10:51:39 : ? report_bug+0x1bb/0x1d0 + Sep 08 10:51:39 : ? handle_bug+0x46/0x90 + Sep 08 10:51:39 : ? exc_invalid_op+0x19/0x80 + Sep 08 10:51:39 : ? asm_exc_invalid_op+0x1b/0x20 + Sep 08 10:51:39 : ? dev_watchdog+0x21f/0x230 + Sep 08 10:51:39 : ? __pfx_dev_watchdog+0x10/0x10 + Sep 08 10:51:39 : call_timer_fn+0x29/0x160 + Sep 08 10:51:39 : ? __pfx_dev_watchdog+0x10/0x10 + Sep 08 10:51:39 : __run_timers.part.0+0x1fb/0x2b0 + Sep 08 10:51:39 : ? ktime_get+0x43/0xc0 + Sep 08 10:51:39 : ? __pfx_tick_sched_timer+0x10/0x10 + Sep 08 10:51:39 : ? lapic_next_deadline+0x2c/0x50 + Sep 08 10:51:39 : ? clockevents_program_event+0xb2/0x140 + Sep 08 10:51:39 : run_timer_softirq+0x2a/0x60 + Sep 08 10:51:39 : __do_softirq+0xda/0x330 + Sep 08 10:51:39 : ? hrtimer_interrupt+0x12b/0x250 + Sep 08 10:51:39 : __irq_exit_rcu+0xa2/0xd0 + Sep 08 10:51:39 : irq_exit_rcu+0xe/0x20 + Sep 08 10:51:39 : sysvec_apic_timer_interrupt+0x96/0xb0 + Sep 08 10:51:39 : + Sep 08 10:51:39 : + Sep 08 10:51:39 : asm_sysvec_apic_timer_interrupt+0x1b/0x20 + Sep 08 10:51:39 : RIP: 0010:cpuidle_enter_state+0xde/0x6f0 + Sep 08 10:51:39 : Code: 79 51 6f e8 a4 34 45 ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 52 13 44 ff 80 7d d0 00 0f 85 e8 00 00 00 fb 0f 1f 44 00 00> + Sep 08 10:51:39 : RSP: 0018:ace9c015fe28 EFLAGS: 0246 + Sep 08 10:51:39 : RAX: RBX: cce9bfc80100 RCX: + Sep 08 10:51:39 : RDX: 000a RSI: RDI: + Sep 08 10:51:39 : RBP: ace9c015fe78 R08: R09: + Sep 08 10:51:39 : R10: R11: R12: 922c2840 + Sep 08 10:51:39 : R13: 0004 R14: 0004 R15: 02c008948c36 + Sep 08 10:51:39 : ? cpuidle_enter_state+0xce/0x6f0 + Sep 08 10:51:39 : cpuidle_enter+0x2e/0x50 + Sep 08 10:51:39 : cpuidle_idle_call+0x14f/0x1e0 + Sep 08 10:51:39 :
[Kernel-packages] [Bug 2034916] Re: NIC RTL8168 randomly disconnected from pci bus
I am not sure, because bug 2031537's lspci does not show `!!! Unknown header type 7f` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2034916 Title: NIC RTL8168 randomly disconnected from pci bus Status in linux-hwe-6.2 package in Ubuntu: New Bug description: After kernel update to 6.2.0-26 and newer. The my device experience network problem from time to time. In the end, I found the NIC card actually fall off from the pcie bus: ``` lspci -vnnk 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev ff) (prog-if ff) DeviceName: GLAN !!! Unknown header type 7f Kernel modules: r8169 ``` Only reboot can reinitiate the nic. 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/Linux The NIC is this one https://linux- hardware.org/?id=pci:10ec-8168-1043-208f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2034916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870597] Re: libinput says "your system is too slow"
The problem come back again after recent updates in ubuntu 20.04. System is stuttering when moving mouse and typing on keyboard: mutter3.36.9-0ubuntu0.20.04.2 xserver-xorg-input-libinput 0.29.0-1 libinput10:amd64 1.15.5-1ubuntu0.3 GNOME Shell 3.36.9 xorg-server 2:1.20.13-1ubuntu1~20.04.3 5.15.0-46-generic Lot of errors like following in journald: ``` /usr/lib/gdm3/gdm-x-session[4273]: (EE) client bug: timer event16 debounce short: scheduled expiry is in the past (-2ms), your system is too slow /usr/lib/gdm3/gdm-x-session[4273]: (EE) client bug: timer event16 debounce: scheduled expiry is in the past (-1ms), your system is too slow ``` Other DE does not have this issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in libinput: Fix Released Status in Linux: Confirmed Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 759725] Re: The kernel is no longer readable by non-root users
this actually make ubuntu much insecure because you have to run most tools with sudo and normally those tools recommend user NOT to run it with root. Other distros are still readable by normal user and they harden it via selinux. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/759725 Title: The kernel is no longer readable by non-root users Status in linux package in Ubuntu: Won't Fix Bug description: The mode of the latest kernel has changed so it is no longer readable by non-root users: -rw-r--r-- 1 root root 4336016 2010-10-17 01:37 /boot/vmlinuz-2.6.35-22-generic -rw-r--r-- 1 root root 4336912 2010-11-24 12:46 /boot/vmlinuz-2.6.35-23-generic -rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic -rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic This prevents people from using this kernel to boot qemu virtual machines as non-root. Please change the mode back to make the kernel readable. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 Regression: Yes Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory AplayDevices: aplay: device_list:240: no soundcards found... Architecture: amd64 ArecordDevices: arecord: device_list:240: no soundcards found... CRDA: Error: [Errno 2] No such file or directory Date: Wed Apr 13 13:05:01 2011 HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) IwConfig: lono wireless extensions. eth0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Red Hat KVM PciMultimedia: ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash RelatedPackageVersions: linux-restricted-modules-2.6.35-22-generic N/A linux-backports-modules-2.6.35-22-generic N/A linux-firmware 1.50 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.modalias: dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.0.0PC:cvnRedHat:ct1:cvr: dmi.product.name: KVM dmi.product.version: RHEL 6.0.0 PC dmi.sys.vendor: Red Hat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894104] Re: Patriot PXD USB SSD cannot be mount with type-C connector
and I am pretty sure it worked on older kernel a few weeks ago. It is a brand new device, I just formated it and backed up files onto it a few weeks ago. Unfortunately I do not have older kernel than 5.4.0-42 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894104 Title: Patriot PXD USB SSD cannot be mount with type-C connector Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: New Bug description: It works fine a few weeks ago. But after recent kernel/driver updates. It stops working. It still works if I connect it to USB 3.1 5000M port. if I connect it to 1M port, it stops working. I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the smart data. But any block operation will fail with remote I/O error: mount, format, dd, etc The port is find, I connected other device to it, it is still working without issue. The USB controller and storage device are: ``` USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory ``` kernel ``` 5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` The dmesg: ``` [ 841.199638] usb 2-2: new SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd [ 841.220480] usb 2-2: New USB device found, idVendor=13fe, idProduct=2570, bcdDevice=52.04 [ 841.220485] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 841.220489] usb 2-2: Product: Patriot Memory [ 841.220492] usb 2-2: Manufacturer: PXD [ 841.220495] usb 2-2: SerialNumber: 5112005142442DD319 [ 841.249317] usbcore: registered new interface driver usb-storage [ 841.257779] scsi host1: uas [ 841.257877] usbcore: registered new interface driver uas [ 841.258567] scsi 1:0:0:0: Direct-Access PXD Patriot Memory 5204 PQ: 0 ANSI: 6 [ 841.259142] sd 1:0:0:0: Attached scsi generic sg1 type 0 [ 843.227753] sd 1:0:0:0: [sdb] 4000797360 512-byte logical blocks: (2.05 TB/1.86 TiB) [ 843.227754] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 843.227876] sd 1:0:0:0: [sdb] Write Protect is off [ 843.227877] sd 1:0:0:0: [sdb] Mode Sense: 5f 00 00 08 [ 843.228071] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 843.228272] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes) [ 843.270539] sdb: sdb1 sdb2 [ 843.271928] sd 1:0:0:0: [sdb] Attached SCSI disk [ 906.555686] systemd-journald[516]: Successfully sent stream file descriptor to service manager. [ 1022.377340] systemd-journald[516]: Successfully sent stream file descriptor to service manager. [ 1224.144553] sd 1:0:0:0: [sdb] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 1224.144560] sd 1:0:0:0: [sdb] tag#5 Sense Key : Hardware Error [current] [ 1224.144562] sd 1:0:0:0: [sdb] tag#5 ASC=0x44 <>ASCQ=0x99 [ 1224.144564] sd 1:0:0:0: [sdb] tag#5 CDB: Read(10) 28 00 00 06 40 00 00 00 01 00 [ 1224.144567] blk_update_request: critical target error, dev sdb, sector 409600 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0 [ 1224.144588] XFS (sdb1): SB validate failed with error -121. [ 1272.199769] systemd-journald[516]: Successfully sent stream file descriptor to service manager. ``` The kernel log: ``` Sep 6 11:35:22 kernel: [ 841.199638] usb 2-2: new SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd Sep 6 11:35:22 kernel: [ 841.220480] usb 2-2: New USB device found, idVendor=13fe, idProduct=2570, bcdDevice=52.04 Sep 6 11:35:22 kernel: [ 841.220485] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 6 11:35:22 kernel: [ 841.220489] usb 2-2: Product: Patriot Memory Sep 6 11:35:22 kernel: [ 841.220492] usb 2-2: Manufacturer: PXD Sep 6 11:35:22 kernel: [ 841.220495] usb 2-2: SerialNumber: 5112005142442DD319 Sep 6 11:35:22 kernel: [ 841.249317] usbcore: registered new interface driver usb-storage Sep 6 11:35:22 kernel: [ 841.257779] scsi host1: uas Sep 6 11:35:22 kernel: [ 841.257877] usbcore: registered new interface driver uas Sep 6 11:35:22 kernel: [ 841.258567] scsi 1:0:0:0: Direct-Access PXD Patriot Memory 5204 PQ: 0 ANSI: 6 Sep 6 11:35:22 kernel: [ 841.259142] sd 1:0:0:0: Attached scsi generic sg1 type 0 Sep 6 11:35:24 kernel: [ 843.227753] sd 1:0:0:0: [sdb] 4000797360 512-byte logical blocks: (2.05 TB/1.86 TiB) Sep 6 11:35:24 kernel: [ 843.227754] sd 1:0:0:0: [sdb] 4096-byte physical blocks Sep 6 11:35:24 kernel: [ 843.227876] sd 1:0:0:0: [sdb] Write Protect is off Sep 6 11:35:24 kernel: [ 843.227877] sd 1:0:0:0: [sdb] Mode Sense: 5f 00 00 08 Sep 6 11:35:24 kernel: [ 843.228071] sd 1:0:0:0:
[Kernel-packages] [Bug 1894104] Re: Patriot PXD USB SSD cannot be mount with type-C connector
@Matthew I boot int o 5.4.0-42, it has different symptom, now the `udisksctl mount -b /dev/sdb1` halt for more than 10 mins and the dmesg is different, it does not error out immediately, but repetitively reset the handle. [ 83.317249] systemd-journald[597]: Successfully sent stream file descriptor to service manager. [ 92.750180] usb 2-2: new SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd [ 92.775135] usb 2-2: New USB device found, idVendor=13fe, idProduct=2570, bcdDevice=52.04 [ 92.775140] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 92.775144] usb 2-2: Product: Patriot Memory [ 92.775146] usb 2-2: Manufacturer: PXD [ 92.775148] usb 2-2: SerialNumber: 5112005142442DD319 [ 92.804959] usbcore: registered new interface driver usb-storage [ 92.813302] scsi host1: uas [ 92.813411] usbcore: registered new interface driver uas [ 92.813813] scsi 1:0:0:0: Direct-Access PXD Patriot Memory 5204 PQ: 0 ANSI: 6 [ 92.814407] sd 1:0:0:0: Attached scsi generic sg1 type 0 [ 94.784086] sd 1:0:0:0: [sdb] 4000797360 512-byte logical blocks: (2.05 TB/1.86 TiB) [ 94.784092] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 94.784246] sd 1:0:0:0: [sdb] Write Protect is off [ 94.784251] sd 1:0:0:0: [sdb] Mode Sense: 5f 00 00 08 [ 94.784492] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 94.784850] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes) [ 94.811392] sdb: sdb1 sdb2 [ 94.814205] sd 1:0:0:0: [sdb] Attached SCSI disk [ 114.748031] systemd-journald[597]: Successfully sent stream file descriptor to service manager. [ 220.511826] XFS (sdb1): Mounting V5 Filesystem [ 251.324415] sd 1:0:0:0: [sdb] tag#7 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT [ 251.324424] sd 1:0:0:0: [sdb] tag#7 CDB: Write(10) 2a 00 06 46 41 10 00 04 00 00 [ 251.328955] sd 1:0:0:0: [sdb] tag#6 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT [ 251.328962] sd 1:0:0:0: [sdb] tag#6 CDB: Write(10) 2a 00 06 46 4d 10 00 04 00 00 [ 251.336191] sd 1:0:0:0: [sdb] tag#5 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT [ 251.336200] sd 1:0:0:0: [sdb] tag#5 CDB: Write(10) 2a 00 06 46 49 10 00 04 00 00 [ 251.343184] sd 1:0:0:0: [sdb] tag#4 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT [ 251.343192] sd 1:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 06 46 45 10 00 04 00 00 [ 251.392372] scsi host1: uas_eh_device_reset_handler start [ 251.521091] usb 2-2: reset SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd [ 251.545897] scsi host1: uas_eh_device_reset_handler success [ 269.017285] systemd-journald[597]: Successfully sent stream file descriptor to service manager. [ 282.052398] scsi host1: uas_eh_device_reset_handler start [ 282.080099] sd 1:0:0:0: [sdb] tag#27 uas_zap_pending 0 uas-tag 1 inflight: CMD [ 282.080102] sd 1:0:0:0: [sdb] tag#27 CDB: Write(10) 2a 00 06 46 45 10 00 04 00 00 [ 282.080104] sd 1:0:0:0: [sdb] tag#24 uas_zap_pending 0 uas-tag 2 inflight: CMD [ 282.080106] sd 1:0:0:0: [sdb] tag#24 CDB: Write(10) 2a 00 06 46 49 10 00 04 00 00 [ 282.080107] sd 1:0:0:0: [sdb] tag#25 uas_zap_pending 0 uas-tag 3 inflight: CMD [ 282.080108] sd 1:0:0:0: [sdb] tag#25 CDB: Write(10) 2a 00 06 46 4d 10 00 04 00 00 [ 282.080110] sd 1:0:0:0: [sdb] tag#26 uas_zap_pending 0 uas-tag 4 inflight: CMD [ 282.080111] sd 1:0:0:0: [sdb] tag#26 CDB: Write(10) 2a 00 06 46 41 10 00 04 00 00 [ 282.212899] usb 2-2: reset SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd [ 282.237614] scsi host1: uas_eh_device_reset_handler success [ 312.772520] scsi host1: uas_eh_device_reset_handler start [ 312.796212] sd 1:0:0:0: [sdb] tag#8 uas_zap_pending 0 uas-tag 1 inflight: CMD [ 312.796220] sd 1:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 06 46 45 10 00 04 00 00 [ 312.796226] sd 1:0:0:0: [sdb] tag#9 uas_zap_pending 0 uas-tag 2 inflight: CMD [ 312.796230] sd 1:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 06 46 41 10 00 04 00 00 [ 312.796235] sd 1:0:0:0: [sdb] tag#10 uas_zap_pending 0 uas-tag 3 inflight: CMD [ 312.796239] sd 1:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 06 46 4d 10 00 04 00 00 [ 312.796244] sd 1:0:0:0: [sdb] tag#11 uas_zap_pending 0 uas-tag 4 inflight: CMD [ 312.796247] sd 1:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 06 46 49 10 00 04 00 00 [ 312.924964] usb 2-2: reset SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd [ 312.949609] scsi host1: uas_eh_device_reset_handler success [ 343.488693] scsi host1: uas_eh_device_reset_handler start [ 343.512169] sd 1:0:0:0: [sdb] tag#17 uas_zap_pending 0 uas-tag 1 inflight: CMD [ 343.512178] sd 1:0:0:0: [sdb] tag#17 CDB: Write(10) 2a 00 06 46 49 10 00 04 00 00 [ 343.512184] sd 1:0:0:0: [sdb] tag#16 uas_zap_pending 0 uas-tag 2 inflight: CMD [ 343.512189] sd 1:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 06 46 4d 10 00 04 00 00 [ 343.512194] sd 1:0:0:0: [sdb]
[Kernel-packages] [Bug 1894104] Re: Patriot PXD USB SSD cannot be mount with type-C connector
** Description changed: It works fine a few weeks ago. But after recent kernel/driver updates. It stops working. It still works if I connect it to USB 3.1 5000M port. if I connect it to 1M port, it stops working. I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the smart data. But any block operation will fail with remote I/O error: mount, format, dd, etc The port is find, I connected other device to it, it is still working without issue. The USB controller and storage device are: ``` USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory ``` kernel ``` 5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` + The dmesg: + ``` + [ 841.199638] usb 2-2: new SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd + [ 841.220480] usb 2-2: New USB device found, idVendor=13fe, idProduct=2570, bcdDevice=52.04 + [ 841.220485] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 + [ 841.220489] usb 2-2: Product: Patriot Memory + [ 841.220492] usb 2-2: Manufacturer: PXD + [ 841.220495] usb 2-2: SerialNumber: 5112005142442DD319 + [ 841.249317] usbcore: registered new interface driver usb-storage + [ 841.257779] scsi host1: uas + [ 841.257877] usbcore: registered new interface driver uas + [ 841.258567] scsi 1:0:0:0: Direct-Access PXD Patriot Memory 5204 PQ: 0 ANSI: 6 + [ 841.259142] sd 1:0:0:0: Attached scsi generic sg1 type 0 + [ 843.227753] sd 1:0:0:0: [sdb] 4000797360 512-byte logical blocks: (2.05 TB/1.86 TiB) + [ 843.227754] sd 1:0:0:0: [sdb] 4096-byte physical blocks + [ 843.227876] sd 1:0:0:0: [sdb] Write Protect is off + [ 843.227877] sd 1:0:0:0: [sdb] Mode Sense: 5f 00 00 08 + [ 843.228071] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA + [ 843.228272] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes) + [ 843.270539] sdb: sdb1 sdb2 + [ 843.271928] sd 1:0:0:0: [sdb] Attached SCSI disk + [ 906.555686] systemd-journald[516]: Successfully sent stream file descriptor to service manager. + [ 1022.377340] systemd-journald[516]: Successfully sent stream file descriptor to service manager. + [ 1224.144553] sd 1:0:0:0: [sdb] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE + [ 1224.144560] sd 1:0:0:0: [sdb] tag#5 Sense Key : Hardware Error [current] + [ 1224.144562] sd 1:0:0:0: [sdb] tag#5 ASC=0x44 <>ASCQ=0x99 + [ 1224.144564] sd 1:0:0:0: [sdb] tag#5 CDB: Read(10) 28 00 00 06 40 00 00 00 01 00 + [ 1224.144567] blk_update_request: critical target error, dev sdb, sector 409600 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0 + [ 1224.144588] XFS (sdb1): SB validate failed with error -121. + [ 1272.199769] systemd-journald[516]: Successfully sent stream file descriptor to service manager. + + ``` + + The kernel log: + ``` + Sep 6 11:35:22 kernel: [ 841.199638] usb 2-2: new SuperSpeedPlus Gen 2 USB device number 5 using xhci_hcd + Sep 6 11:35:22 kernel: [ 841.220480] usb 2-2: New USB device found, idVendor=13fe, idProduct=2570, bcdDevice=52.04 + Sep 6 11:35:22 kernel: [ 841.220485] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 + Sep 6 11:35:22 kernel: [ 841.220489] usb 2-2: Product: Patriot Memory + Sep 6 11:35:22 kernel: [ 841.220492] usb 2-2: Manufacturer: PXD + Sep 6 11:35:22 kernel: [ 841.220495] usb 2-2: SerialNumber: 5112005142442DD319 + Sep 6 11:35:22 kernel: [ 841.249317] usbcore: registered new interface driver usb-storage + Sep 6 11:35:22 kernel: [ 841.257779] scsi host1: uas + Sep 6 11:35:22 kernel: [ 841.257877] usbcore: registered new interface driver uas + Sep 6 11:35:22 kernel: [ 841.258567] scsi 1:0:0:0: Direct-Access PXD Patriot Memory 5204 PQ: 0 ANSI: 6 + Sep 6 11:35:22 kernel: [ 841.259142] sd 1:0:0:0: Attached scsi generic sg1 type 0 + Sep 6 11:35:24 kernel: [ 843.227753] sd 1:0:0:0: [sdb] 4000797360 512-byte logical blocks: (2.05 TB/1.86 TiB) + Sep 6 11:35:24 kernel: [ 843.227754] sd 1:0:0:0: [sdb] 4096-byte physical blocks + Sep 6 11:35:24 kernel: [ 843.227876] sd 1:0:0:0: [sdb] Write Protect is off + Sep 6 11:35:24 kernel: [ 843.227877] sd 1:0:0:0: [sdb] Mode Sense: 5f 00 00 08 + Sep 6 11:35:24 kernel: [ 843.228071] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA + Sep 6 11:35:24 kernel: [ 843.228272] sd 1:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes) + Sep 6 11:35:24 kernel: [ 843.270539] sdb: sdb1 sdb2 + Sep 6 11:35:24 kernel: [ 843.271928] sd 1:0:0:0: [sdb] Attached SCSI disk + Sep 6 11:41:45 kernel: [ 1224.144553] sd 1:0:0:0: [sdb] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE + Sep 6 11:41:45 kernel: [
[Kernel-packages] [Bug 1894104] [NEW] Patriot PXD USB SSD cannot be mount with type-C connector
Public bug reported: It works fine a few weeks ago. But after recent kernel/driver updates. It stops working. It still works if I connect it to USB 3.1 5000M port. if I connect it to 1M port, it stops working. I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the smart data. But any block operation will fail with remote I/O error: mount, format, dd, etc The port is find, I connected other device to it, it is still working without issue. The USB controller and storage device are: ``` USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory ``` kernel ``` 5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: It works fine a few weeks ago. But after recent kernel/driver updates. It stop working. It still work if I connect it to USB 3.1 5000M port. if I connect it to 1M port, it stop working. I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the smart data. But any block operation will fail with remote I/O error: mount, format, dd, etc The port is find, I connected other device to it, it is still working without issue. The USB controller and storage device are: ``` USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory ``` + + kernel + ``` + 5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux + ``` ** Description changed: It works fine a few weeks ago. But after recent kernel/driver updates. - It stop working. It still work if I connect it to USB 3.1 5000M port. if - I connect it to 1M port, it stop working. + It stops working. It still works if I connect it to USB 3.1 5000M port. + if I connect it to 1M port, it stops working. I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the smart data. But any block operation will fail with remote I/O error: mount, format, dd, etc The port is find, I connected other device to it, it is still working without issue. The USB controller and storage device are: ``` USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory ``` kernel ``` 5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894104 Title: Patriot PXD USB SSD cannot be mount with type-C connector Status in linux package in Ubuntu: New Bug description: It works fine a few weeks ago. But after recent kernel/driver updates. It stops working. It still works if I connect it to USB 3.1 5000M port. if I connect it to 1M port, it stops working. I can still use `smartctl -a -d sntjmicron /dev/sdx` to obtain the smart data. But any block operation will fail with remote I/O error: mount, format, dd, etc The port is find, I connected other device to it, it is still working without issue. The USB controller and storage device are: ``` USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) ID 13fe:2570 Kingston Technology Company Inc. Patriot Memory ``` kernel ``` 5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
