[Kernel-packages] [Bug 2052332] [NEW] package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed building boot with linux kernel 6.5.0-15.
Public bug reported: I reverted to 6.2.0-39 and purged headers and image for 6.5 since my computer cannot boot with 6.5+nvidia390 and when I use nouveau, my resolution is 640x320 and I can't proceed like this. Good luck with this one, thanks in advance. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 2 21:56:15 2024 DpkgHistoryLog: Start-Date: 2024-02-02 21:53:50 Commandline: /usr/bin/unattended-upgrade Install: linux-modules-extra-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-hwe-6.5-headers-6.5.0-15:amd64 (6.5.0-15.15~22.04.1, automatic), linux-modules-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-image-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-headers-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic) Upgrade: linux-image-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8), linux-headers-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8), linux-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8) ErrorMessage: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 InstallationDate: Installed on 2023-02-25 (342 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2052332 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed building boot with linux kernel 6.5.0-15. Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I reverted to 6.2.0-39 and purged headers and image for 6.5 since my computer cannot boot with 6.5+nvidia390 and when I use nouveau, my resolution is 640x320 and I can't proceed like this. Good luck with this one, thanks in advance. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 2 21:56:15 2024 DpkgHistoryLog: Start-Date: 2024-02-02 21:53:50 Commandline: /usr/bin/unattended-upgrade Install: linux-modules-extra-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-hwe-6.5-headers-6.5.0-15:amd64 (6.5.0-15.15~22.04.1, automatic), linux-modules-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-image-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-headers-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic) Upgrade: linux-image-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8), linux-headers-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8), linux-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8) ErrorMessage: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 InstallationDate: Installed on 2023-02-25 (342 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2052332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages Mor
[Kernel-packages] [Bug 1999748] Re: Unable to mount external SSD over TB3
I was able to make the SSD work with the following steps: $ vim /etc/default/grub add "pci=realloc,assign-busses,hpbussize=0x33" at the end of GRUB_CMDLINE_LINUX_DEFAULT $ sudo update-grub $ reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.70 dmi.board.name: Z590 Phantom Gaming-ITX/TB4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.70:bd07/27/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming-ITX/TB4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user)
[Kernel-packages] [Bug 1999748] Re: Unable to mount external SSD over TB3
Here is the dmesg output: $ sudo dmesg [93568.104835] pcieport :04:01.0: pciehp: Slot(1): Card present [93568.104845] pcieport :04:01.0: pciehp: Slot(1): Link Up [93568.240701] pci :06:00.0: [8086:15da] type 01 class 0x060400 [93568.240839] pci :06:00.0: enabling Extended Tags [93568.241140] pci :06:00.0: supports D1 D2 [93568.241144] pci :06:00.0: PME# supported from D0 D1 D2 D3hot D3cold [93568.241347] pci :06:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x4 link at :04:01.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link) [93568.241568] pcieport :04:01.0: ASPM: current common clock configuration is inconsistent, reconfiguring [93568.252602] pci :06:00.0: No bus number available for hot-added bridge [93568.252606] pcieport :04:01.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 06] add_size 20 add_align 10 [93568.252611] pcieport :04:01.0: BAR 15: no space for [mem size 0x0020 64bit pref] [93568.252613] pcieport :04:01.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [93568.252614] pcieport :04:01.0: BAR 15: no space for [mem size 0x0020 64bit pref] [93568.252615] pcieport :04:01.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [93568.252615] pcieport :04:01.0: PCI bridge to [bus 06] [93568.252626] pcieport :04:01.0: bridge window [io 0x6000-0x6fff] [93568.252630] pcieport :04:01.0: bridge window [mem 0x8400-0x840f] [93569.331131] thunderbolt 0-1: new device found, vendor=0x23e device=0xa011 [93569.331150] thunderbolt 0-1: Micronet Technology Fantom Drives eXtreme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends Intern
[Kernel-packages] [Bug 1999748] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1999748/+attachment/5635838/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.70 dmi.board.name: Z590 Phantom Gaming-ITX/TB4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.70:bd07/27/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming-ITX/TB4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8
[Kernel-packages] [Bug 1999748] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1999748/+attachment/5635837/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.70 dmi.board.name: Z590 Phantom Gaming-ITX/TB4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.70:bd07/27/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming-ITX/TB4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/
[Kernel-packages] [Bug 1999748] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1999748/+attachment/5635830/+files/Lsusb-v.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.70 dmi.board.name: Z590 Phantom Gaming-ITX/TB4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.70:bd07/27/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming-ITX/TB4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: leaf 1674 F pulseaudio + /dev/snd/controlC1: leaf 1674 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-11-25 (20 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 + RelatedPackageVersion
[Kernel-packages] [Bug 1999748] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1999748/+attachment/5635829/+files/Lsusb-t.txt -- 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/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.70 dmi.board.name: Z590 Phantom Gaming-ITX/TB4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.70:bd07/27/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming-ITX/TB4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot
[Kernel-packages] [Bug 1999748] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1999748/+attachment/5635828/+files/Lsusb.txt -- 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/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.70 dmi.board.name: Z590 Phantom Gaming-ITX/TB4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.70:bd07/27/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming-ITX/TB4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmli
[Kernel-packages] [Bug 1999748] Re: Unable to mount external SSD over TB3
More dmesg output, after unplugging the drive and re-plugging it (I added spaces when I unplugged and plugged back): $ sudo dmesg -w [93568.104835] pcieport :04:01.0: pciehp: Slot(1): Card present [93568.104845] pcieport :04:01.0: pciehp: Slot(1): Link Up [93568.240701] pci :06:00.0: [8086:15da] type 01 class 0x060400 [93568.240839] pci :06:00.0: enabling Extended Tags [93568.241140] pci :06:00.0: supports D1 D2 [93568.241144] pci :06:00.0: PME# supported from D0 D1 D2 D3hot D3cold [93568.241347] pci :06:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x4 link at :04:01.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link) [93568.241568] pcieport :04:01.0: ASPM: current common clock configuration is inconsistent, reconfiguring [93568.252602] pci :06:00.0: No bus number available for hot-added bridge [93568.252606] pcieport :04:01.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 06] add_size 20 add_align 10 [93568.252611] pcieport :04:01.0: BAR 15: no space for [mem size 0x0020 64bit pref] [93568.252613] pcieport :04:01.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [93568.252614] pcieport :04:01.0: BAR 15: no space for [mem size 0x0020 64bit pref] [93568.252615] pcieport :04:01.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [93568.252615] pcieport :04:01.0: PCI bridge to [bus 06] [93568.252626] pcieport :04:01.0: bridge window [io 0x6000-0x6fff] [93568.252630] pcieport :04:01.0: bridge window [mem 0x8400-0x840f] [93569.331131] thunderbolt 0-1: new device found, vendor=0x23e device=0xa011 [93569.331150] thunderbolt 0-1: Micronet Technology Fantom Drives eXtreme [94255.288786] pcieport :04:01.0: pciehp: Slot(1): Card not present [94255.288801] pcieport :06:00.0: can't change power state from D3cold to D0 (config space inaccessible) [94255.828576] thunderbolt 0-1: device disconnected [94266.388547] pcieport :04:01.0: pciehp: Slot(1): Card present [94266.388556] pcieport :04:01.0: pciehp: Slot(1): Link Up [94266.524274] pci :06:00.0: [8086:15da] type 01 class 0x060400 [94266.524376] pci :06:00.0: enabling Extended Tags [94266.524605] pci :06:00.0: supports D1 D2 [94266.524606] pci :06:00.0: PME# supported from D0 D1 D2 D3hot D3cold [94266.524776] pci :06:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x4 link at :04:01.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link) [94266.524888] pcieport :04:01.0: ASPM: current common clock configuration is inconsistent, reconfiguring [94266.536375] pci :06:00.0: No bus number available for hot-added bridge [94266.536378] pcieport :04:01.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 06] add_size 20 add_align 10 [94266.536382] pcieport :04:01.0: BAR 15: no space for [mem size 0x0020 64bit pref] [94266.536384] pcieport :04:01.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [94266.536385] pcieport :04:01.0: BAR 15: no space for [mem size 0x0020 64bit pref] [94266.536385] pcieport :04:01.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [94266.536386] pcieport :04:01.0: PCI bridge to [bus 06] [94266.536396] pcieport :04:01.0: bridge window [io 0x6000-0x6fff] [94266.536400] pcieport :04:01.0: bridge window [mem 0x8400-0x840f] [94267.181918] thunderbolt 0-1: new device found, vendor=0x23e device=0xa011 [94267.181920] thunderbolt 0-1: Micronet Technology Fantom Drives eXtreme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thunderbolt-tools in Ubuntu. Matching subscriptions: Kernel Packages https://bugs.launchpad.net/bugs/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/med
[Kernel-packages] [Bug 1999748] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1999748/+attachment/5635827/+files/Lspci-vt.txt -- 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/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.70 dmi.board.name: Z590 Phantom Gaming-ITX/TB4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.70:bd07/27/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming-ITX/TB4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/bo
[Kernel-packages] [Bug 1999748] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1999748/+attachment/5635824/+files/CurrentDmesg.txt -- 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/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.70 dmi.board.name: Z590 Phantom Gaming-ITX/TB4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.70:bd07/27/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming-ITX/TB4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_I
[Kernel-packages] [Bug 1999748] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1999748/+attachment/5635825/+files/IwConfig.txt -- 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/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.70 dmi.board.name: Z590 Phantom Gaming-ITX/TB4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.70:bd07/27/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming-ITX/TB4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/bo
[Kernel-packages] [Bug 1999748] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1999748/+attachment/5635826/+files/Lspci.txt -- 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/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy wayland-session Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/27/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.70 dmi.board.name: Z590 Phantom Gaming-ITX/TB4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.70:bd07/27/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming-ITX/TB4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leaf 1674 F pulseaudio /dev/snd/controlC1: leaf 1674 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-25 (20 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmli
[Kernel-packages] [Bug 1999748] Re: Unable to mount external SSD over TB3
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: leaf 1674 F pulseaudio + /dev/snd/controlC1: leaf 1674 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-11-25 (20 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=ba6c1a3e-79a1-4c8b-944e-ed0352c02f4b ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-56-generic N/A + linux-backports-modules-5.15.0-56-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.7 + Tags: jammy wayland-session + Uname: Linux 5.15.0-56-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/27/2021 + dmi.bios.release: 5.19 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: P1.70 + dmi.board.name: Z590 Phantom Gaming-ITX/TB4 + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP1.70:bd07/27/2021:br5.19:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ590PhantomGaming-ITX/TB4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1999748/+attachment/5635823/+files/AlsaInfo.txt -- 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/1999748 Title: Unable to mount external SSD over TB3 Status in thunderbolt-tools package in Ubuntu: Confirmed Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ aut
[Kernel-packages] [Bug 1999748] [NEW] Unable to mount external SSD over TB3
Public bug reported: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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/1999748 Title: Unable to mount external SSD over TB3 Status in linux package in Ubuntu: Incomplete Bug description: I have a Micronet Technology Fantom Drives eXtreme SSD drive. It is connected to my PC (with nobo X570 Phantom Gaming-ITX/TB3). When I connect the drive with a TB3 cable, it becomes authorized as expected. $ boltctl ● Micronet Technology Fantom Drives eXtreme ├─ type: peripheral ├─ name: Fantom Drives eXtreme ├─ vendor:Micronet Technology ├─ uuid: 00ca782d-dcfa-3e02-- ├─ generation:Thunderbolt 3 ├─ status:authorized │ ├─ domain: 0deb8780-00cc-9858-- │ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s │ └─ authflags: none ├─ authorized:Thu 15 Dec 2022 08:48:39 AM UTC ├─ connected: Thu 15 Dec 2022 08:48:39 AM UTC └─ stored:Thu 15 Dec 2022 07:02:21 AM UTC ├─ policy: iommu └─ key:no However, I don't see the disk in "Disk" application or anywhere else. I checked "/media/" too. It looks like TB3 is recognizing that something was plugged but it doesn't mount the drive. Note that if I connect the same drive in a ThinkPad Carbon Gen 9 with the same TB3 cable, it gets recognized and mounted as expected. They both run the same version of Ubuntu: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999748/+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 1929255] Re: update-initrd-links creates incorrect symlinks
@xnox I see that the status for Bionic is still _Fix Committed_ but not _Fix Released_. Am I not understanding this well enough ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [Impact] ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. [Test Plan] * Install new linux-base and initramfs-tools * create /etc/kernel-img.conf with do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes * Install one kernel flavour, check that symlinks in /boot have sane targets * Install another kernel, check that symlinks in /boot/ have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it). and check that symlinks in /boot have sane targets. * Purge all kernel, and remove symlinks in /boot * Update /etc/kernel-img.conf to do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no * Install one kernel flavour, check that symlinks in / have sane targets * Install another kernel, check that symlinks in / have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it) * remove all kernels, purge initramfs-tools, clean up symlinks in / and /boot * repeat all of the above, without having initramfs-tools installed. I.e. install kernels _without_ recommneds. [Where problems could occur] * The rewritten postinst.d script now simply mostly calls linux- update-links like the normal linux-image postinst script does. One has to make sure that .deb installations of kernels happens correctly and that installkernel way of installing kernels happens correctly. Under different kernel-img.conf settings. The previous incarnations of fixing this and related issues did not account for the above cases and codepaths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+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 1929255] Re: update-initrd-links creates incorrect symlinks
Is something going to be done to fix the regressions reported for Bionic and Focal ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [Impact] ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. [Test Plan] * Install new linux-base and initramfs-tools * create /etc/kernel-img.conf with do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes * Install one kernel flavour, check that symlinks in /boot have sane targets * Install another kernel, check that symlinks in /boot/ have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it). and check that symlinks in /boot have sane targets. * Purge all kernel, and remove symlinks in /boot * Update /etc/kernel-img.conf to do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no * Install one kernel flavour, check that symlinks in / have sane targets * Install another kernel, check that symlinks in / have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it) * remove all kernels, purge initramfs-tools, clean up symlinks in / and /boot * repeat all of the above, without having initramfs-tools installed. I.e. install kernels _without_ recommneds. [Where problems could occur] * The rewritten postinst.d script now simply mostly calls linux- update-links like the normal linux-image postinst script does. One has to make sure that .deb installations of kernels happens correctly and that installkernel way of installing kernels happens correctly. Under different kernel-img.conf settings. The previous incarnations of fixing this and related issues did not account for the above cases and codepaths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+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 1929255] Re: update-initrd-links creates incorrect symlinks
Sure, I proposed the patch as a quick fix that would allow users to get things running back again shortly. But if there are more academic ways to workaround this, feel free to give me pointers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Confirmed Status in linux-base source package in Bionic: Confirmed Bug description: ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. ## Solution A solution is proposed through the attached patch file. ## System information Description: Ubuntu 18.04.5 LTS Release: 18.04 Uname: Linux 5.3.0-53-generic x86_64 ## Package information Package: linux-base 4.5ubuntu1.5 PackageArchitecture: all SourcePackage: linux-base Tags: bionic package-from-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+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 1929255] Re: update-initrd-links creates incorrect symlinks
** Tags removed: regresion-proposed ** Tags added: regression-proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Confirmed Status in linux-base source package in Bionic: Confirmed Bug description: ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. ## Solution A solution is proposed through the attached patch file. ## System information Description: Ubuntu 18.04.5 LTS Release: 18.04 Uname: Linux 5.3.0-53-generic x86_64 ## Package information Package: linux-base 4.5ubuntu1.5 PackageArchitecture: all SourcePackage: linux-base Tags: bionic package-from-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+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 1929255] Re: update-initrd-links creates incorrect symlinks
Related to https://bugs.launchpad.net/ubuntu/+source/linux- base/+bug/1877088 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Confirmed Bug description: ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. ## Solution A solution is proposed through the attached patch file. ## System information Description: Ubuntu 18.04.5 LTS Release: 18.04 Uname: Linux 5.3.0-53-generic x86_64 ## Package information Package: linux-base 4.5ubuntu1.5 PackageArchitecture: all SourcePackage: linux-base Tags: bionic package-from-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+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 1929255] [NEW] update-initrd-links creates incorrect symlinks
Public bug reported: ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. ## Solution A solution is proposed through the attached patch file. ## System information Description:Ubuntu 18.04.5 LTS Release:18.04 Uname: Linux 5.3.0-53-generic x86_64 ## Package information Package: linux-base 4.5ubuntu1.5 PackageArchitecture: all SourcePackage: linux-base Tags: bionic package-from-proposed ** Affects: linux-base (Ubuntu) Importance: Undecided Status: New ** Tags: bionic installkernel ** Patch added: "Proposed patch" https://bugs.launchpad.net/bugs/1929255/+attachment/5499310/+files/xx-update-initrd-links.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: New Bug description: ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. ## Solution A solution is proposed through the attached patch file. ## System information Description: Ubuntu 18.04.5 LTS Release: 18.04 Uname: Linux 5.3.0-53-generic x86_64 ## Package information Package: linux-base 4.5ubuntu1.5 PackageArchitecture: all SourcePackage: linux-base Tags: bionic package-from-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+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 1820363] Re: NEC/Renesas PCI USB3 Cards (uPD720201) Host halt failed, -19
@Mike Many Thanks for your answer. The PCI-X is a 4 ports with 2 channels. The PCIe is 7 ports with an unknown number of channels. The PCI-X was intended to be used with a HP Proliant for external Backup purpose which is running Ubuntu Server 18.04 LTS. No more PCIe slots are available because they are used by the Smart Array RAID Controller. I will try to revert back this weekend to 2.0.2.0 using the last survival Windows. But if I understand well what you mean I have no chance to get the PCI-X adapter working with any kernel with a version > 4.9 ? I really appreciate your help. Thank you Mike. Kr -- 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/1820363 Title: NEC/Renesas PCI USB3 Cards (uPD720201) Host halt failed, -19 Status in linux package in Ubuntu: Confirmed Bug description: Hello, Using Ubuntu installation media (ubuntu-18.04.2-server-amd64.iso / ubuntu-18.04.[1-2]-live-server-amd64.iso / Ubuntu Live 18.04.2 iso / Ubuntu Mate Live Ubuntu Live 18.04.[1-2] iso) Startup is hanging with : [0.214796] pci :0d:00.0: [1912:0014] type 00 class 0x0c0330 [0.215620] pci :0d:00.0: reg 0x10: [mem 0xfdbf-0xfdbf1fff 64bit] [0.219160] pci :0d:00.0: PME# supported from D0 D3hot D3cold [ 79.272644] xhci_hcd :0d:00.0: xHCI Host Controller [ 79.272710] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 7 [ 79.535236] xhci_hcd :0d:00.0: Host halt failed, -19 [ 79.535291] xhci_hcd :0d:00.0: can't setup: -19 [ 79.535347] xhci_hcd :0d:00.0: USB bus 7 deregistered [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 I'm facing exactly the same bug as these one: https://www.mail-archive.com/linux-usb@vger.kernel.org/msg102138.html https://bugs.gentoo.org/show_bug.cgi?id=612704 I installed Ubuntu Server 18.04.2 without the PCI card without trouble and then reinserted the PCI Card computer never start always hanging at the same steps as above. I managed to start only once time with the PCI card plugged by adding "pci=nomsi" to the kernel command line using an Ubuntu Mate Live media with persistence and had this output: [0.214796] pci :0d:00.0: [1912:0014] type 00 class 0x0c0330 [0.215620] pci :0d:00.0: reg 0x10: [mem 0xfdbf-0xfdbf1fff 64bit] [0.219160] pci :0d:00.0: PME# supported from D0 D3hot D3cold [8.041967] xhci_hcd :0d:00.0: Resetting [9.062082] xhci_hcd :0d:00.0: timed out waiting for pending transaction; performing function level reset anyway [ 10.406071] xhci_hcd :0d:00.0: not ready 1123ms after FLR; waiting [ 11.462075] xhci_hcd :0d:00.0: not ready 2147ms after FLR; waiting [ 13.542072] xhci_hcd :0d:00.0: not ready 4195ms after FLR; waiting [ 17.894085] xhci_hcd :0d:00.0: not ready 8291ms after FLR; waiting [ 26.342086] xhci_hcd :0d:00.0: not ready 16483ms after FLR; waiting [ 44.006072] xhci_hcd :0d:00.0: not ready 32867ms after FLR; waiting [ 78.822072] xhci_hcd :0d:00.0: not ready 65635ms after FLR; giving up [ 79.222070] xhci_hcd :0d:00.0: Refused to change power state, currently in D3 [ 79.272644] xhci_hcd :0d:00.0: xHCI Host Controller [ 79.272710] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 7 [ 79.535236] xhci_hcd :0d:00.0: Host halt failed, -19 [ 79.535291] xhci_hcd :0d:00.0: can't setup: -19 [ 79.535347] xhci_hcd :0d:00.0: USB bus 7 deregistered [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 It was lucky because it never worked again. PCI card was not working but computer started. Here you can find included lspci -vv, lshw and full dmesg taken from during this unique startup with the PCI Card. I tried the same PCI Card with two computers and always had the same results. Kernel is hanging with "xhci_hcd :0d:00.0: init :0d:00.0 fail, -19" and nothing more. I tried this PCI Card with a CentOS 7.3 on same computer and kernel (3.10) is starting well and PCI card is fully working. Many thanks for your assistance. I apologize if it's an already reported bug. Kind Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820363/+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 1820363] Re: NEC/Renesas PCI USB3 Cards (uPD720201) Host halt failed, -19
Hello, I can't produce more log because kernel hangs at startup. Can't start computer without the PCI card and insert when powered on. @Mike, The card has firmware 2.0.2.6 which seems to the last version. She was provided with 2.0.2.0 and tried too with 2.0.2.4. I updated to the last version using Windows on an other computer which has PCI-X slots. I tested this PCI card on a Gigabyte mainboard and an HP Proliant mainboard and each time kernel hangs with the same error "Host halt failed, -19". If you have some links I can try to update firmware of the card with other releases. I have too the PCIe version based on the same chip "Renesas Technology Corp. uPD720201" and kernel is not hanging with the PCIe version. It seems to be related to the PCI/PCI-X. I never done a kernel bisection and will try to follow Ubuntu documentation that I found. Kind Regards -- 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/1820363 Title: NEC/Renesas PCI USB3 Cards (uPD720201) Host halt failed, -19 Status in linux package in Ubuntu: Confirmed Bug description: Hello, Using Ubuntu installation media (ubuntu-18.04.2-server-amd64.iso / ubuntu-18.04.[1-2]-live-server-amd64.iso / Ubuntu Live 18.04.2 iso / Ubuntu Mate Live Ubuntu Live 18.04.[1-2] iso) Startup is hanging with : [0.214796] pci :0d:00.0: [1912:0014] type 00 class 0x0c0330 [0.215620] pci :0d:00.0: reg 0x10: [mem 0xfdbf-0xfdbf1fff 64bit] [0.219160] pci :0d:00.0: PME# supported from D0 D3hot D3cold [ 79.272644] xhci_hcd :0d:00.0: xHCI Host Controller [ 79.272710] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 7 [ 79.535236] xhci_hcd :0d:00.0: Host halt failed, -19 [ 79.535291] xhci_hcd :0d:00.0: can't setup: -19 [ 79.535347] xhci_hcd :0d:00.0: USB bus 7 deregistered [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 I'm facing exactly the same bug as these one: https://www.mail-archive.com/linux-usb@vger.kernel.org/msg102138.html https://bugs.gentoo.org/show_bug.cgi?id=612704 I installed Ubuntu Server 18.04.2 without the PCI card without trouble and then reinserted the PCI Card computer never start always hanging at the same steps as above. I managed to start only once time with the PCI card plugged by adding "pci=nomsi" to the kernel command line using an Ubuntu Mate Live media with persistence and had this output: [0.214796] pci :0d:00.0: [1912:0014] type 00 class 0x0c0330 [0.215620] pci :0d:00.0: reg 0x10: [mem 0xfdbf-0xfdbf1fff 64bit] [0.219160] pci :0d:00.0: PME# supported from D0 D3hot D3cold [8.041967] xhci_hcd :0d:00.0: Resetting [9.062082] xhci_hcd :0d:00.0: timed out waiting for pending transaction; performing function level reset anyway [ 10.406071] xhci_hcd :0d:00.0: not ready 1123ms after FLR; waiting [ 11.462075] xhci_hcd :0d:00.0: not ready 2147ms after FLR; waiting [ 13.542072] xhci_hcd :0d:00.0: not ready 4195ms after FLR; waiting [ 17.894085] xhci_hcd :0d:00.0: not ready 8291ms after FLR; waiting [ 26.342086] xhci_hcd :0d:00.0: not ready 16483ms after FLR; waiting [ 44.006072] xhci_hcd :0d:00.0: not ready 32867ms after FLR; waiting [ 78.822072] xhci_hcd :0d:00.0: not ready 65635ms after FLR; giving up [ 79.222070] xhci_hcd :0d:00.0: Refused to change power state, currently in D3 [ 79.272644] xhci_hcd :0d:00.0: xHCI Host Controller [ 79.272710] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 7 [ 79.535236] xhci_hcd :0d:00.0: Host halt failed, -19 [ 79.535291] xhci_hcd :0d:00.0: can't setup: -19 [ 79.535347] xhci_hcd :0d:00.0: USB bus 7 deregistered [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 It was lucky because it never worked again. PCI card was not working but computer started. Here you can find included lspci -vv, lshw and full dmesg taken from during this unique startup with the PCI Card. I tried the same PCI Card with two computers and always had the same results. Kernel is hanging with "xhci_hcd :0d:00.0: init :0d:00.0 fail, -19" and nothing more. I tried this PCI Card with a CentOS 7.3 on same computer and kernel (3.10) is starting well and PCI card is fully working. Many thanks for your assistance. I apologize if it's an already reported bug. Kind Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820363/+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 1820363] Re: NEC/Renesas PCI USB3 Cards (uPD720201) Host halt failed, -19
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1820363 Title: NEC/Renesas PCI USB3 Cards (uPD720201) Host halt failed, -19 Status in linux package in Ubuntu: Confirmed Bug description: Hello, Using Ubuntu installation media (ubuntu-18.04.2-server-amd64.iso / ubuntu-18.04.[1-2]-live-server-amd64.iso / Ubuntu Live 18.04.2 iso / Ubuntu Mate Live Ubuntu Live 18.04.[1-2] iso) Startup is hanging with : [0.214796] pci :0d:00.0: [1912:0014] type 00 class 0x0c0330 [0.215620] pci :0d:00.0: reg 0x10: [mem 0xfdbf-0xfdbf1fff 64bit] [0.219160] pci :0d:00.0: PME# supported from D0 D3hot D3cold [ 79.272644] xhci_hcd :0d:00.0: xHCI Host Controller [ 79.272710] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 7 [ 79.535236] xhci_hcd :0d:00.0: Host halt failed, -19 [ 79.535291] xhci_hcd :0d:00.0: can't setup: -19 [ 79.535347] xhci_hcd :0d:00.0: USB bus 7 deregistered [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 I'm facing exactly the same bug as these one: https://www.mail-archive.com/linux-usb@vger.kernel.org/msg102138.html https://bugs.gentoo.org/show_bug.cgi?id=612704 I installed Ubuntu Server 18.04.2 without the PCI card without trouble and then reinserted the PCI Card computer never start always hanging at the same steps as above. I managed to start only once time with the PCI card plugged by adding "pci=nomsi" to the kernel command line using an Ubuntu Mate Live media with persistence and had this output: [0.214796] pci :0d:00.0: [1912:0014] type 00 class 0x0c0330 [0.215620] pci :0d:00.0: reg 0x10: [mem 0xfdbf-0xfdbf1fff 64bit] [0.219160] pci :0d:00.0: PME# supported from D0 D3hot D3cold [8.041967] xhci_hcd :0d:00.0: Resetting [9.062082] xhci_hcd :0d:00.0: timed out waiting for pending transaction; performing function level reset anyway [ 10.406071] xhci_hcd :0d:00.0: not ready 1123ms after FLR; waiting [ 11.462075] xhci_hcd :0d:00.0: not ready 2147ms after FLR; waiting [ 13.542072] xhci_hcd :0d:00.0: not ready 4195ms after FLR; waiting [ 17.894085] xhci_hcd :0d:00.0: not ready 8291ms after FLR; waiting [ 26.342086] xhci_hcd :0d:00.0: not ready 16483ms after FLR; waiting [ 44.006072] xhci_hcd :0d:00.0: not ready 32867ms after FLR; waiting [ 78.822072] xhci_hcd :0d:00.0: not ready 65635ms after FLR; giving up [ 79.222070] xhci_hcd :0d:00.0: Refused to change power state, currently in D3 [ 79.272644] xhci_hcd :0d:00.0: xHCI Host Controller [ 79.272710] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 7 [ 79.535236] xhci_hcd :0d:00.0: Host halt failed, -19 [ 79.535291] xhci_hcd :0d:00.0: can't setup: -19 [ 79.535347] xhci_hcd :0d:00.0: USB bus 7 deregistered [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 It was lucky because it never worked again. PCI card was not working but computer started. Here you can find included lspci -vv, lshw and full dmesg taken from during this unique startup with the PCI Card. I tried the same PCI Card with two computers and always had the same results. Kernel is hanging with "xhci_hcd :0d:00.0: init :0d:00.0 fail, -19" and nothing more. I tried this PCI Card with a CentOS 7.3 on same computer and kernel (3.10) is starting well and PCI card is fully working. Many thanks for your assistance. I apologize if it's an already reported bug. Kind Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820363/+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 1820363] [NEW] NEC/Renesas PCI USB3 Cards (uPD720201) Host halt failed, -19
Public bug reported: Hello, Using Ubuntu installation media (ubuntu-18.04.2-server-amd64.iso / ubuntu-18.04.[1-2]-live-server-amd64.iso / Ubuntu Live 18.04.2 iso / Ubuntu Mate Live Ubuntu Live 18.04.[1-2] iso) Startup is hanging with : [0.214796] pci :0d:00.0: [1912:0014] type 00 class 0x0c0330 [0.215620] pci :0d:00.0: reg 0x10: [mem 0xfdbf-0xfdbf1fff 64bit] [0.219160] pci :0d:00.0: PME# supported from D0 D3hot D3cold [ 79.272644] xhci_hcd :0d:00.0: xHCI Host Controller [ 79.272710] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 7 [ 79.535236] xhci_hcd :0d:00.0: Host halt failed, -19 [ 79.535291] xhci_hcd :0d:00.0: can't setup: -19 [ 79.535347] xhci_hcd :0d:00.0: USB bus 7 deregistered [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 I'm facing exactly the same bug as these one: https://www.mail-archive.com/linux-usb@vger.kernel.org/msg102138.html https://bugs.gentoo.org/show_bug.cgi?id=612704 I installed Ubuntu Server 18.04.2 without the PCI card without trouble and then reinserted the PCI Card computer never start always hanging at the same steps as above. I managed to start only once time with the PCI card plugged by adding "pci=nomsi" to the kernel command line using an Ubuntu Mate Live media with persistence and had this output: [0.214796] pci :0d:00.0: [1912:0014] type 00 class 0x0c0330 [0.215620] pci :0d:00.0: reg 0x10: [mem 0xfdbf-0xfdbf1fff 64bit] [0.219160] pci :0d:00.0: PME# supported from D0 D3hot D3cold [8.041967] xhci_hcd :0d:00.0: Resetting [9.062082] xhci_hcd :0d:00.0: timed out waiting for pending transaction; performing function level reset anyway [ 10.406071] xhci_hcd :0d:00.0: not ready 1123ms after FLR; waiting [ 11.462075] xhci_hcd :0d:00.0: not ready 2147ms after FLR; waiting [ 13.542072] xhci_hcd :0d:00.0: not ready 4195ms after FLR; waiting [ 17.894085] xhci_hcd :0d:00.0: not ready 8291ms after FLR; waiting [ 26.342086] xhci_hcd :0d:00.0: not ready 16483ms after FLR; waiting [ 44.006072] xhci_hcd :0d:00.0: not ready 32867ms after FLR; waiting [ 78.822072] xhci_hcd :0d:00.0: not ready 65635ms after FLR; giving up [ 79.222070] xhci_hcd :0d:00.0: Refused to change power state, currently in D3 [ 79.272644] xhci_hcd :0d:00.0: xHCI Host Controller [ 79.272710] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 7 [ 79.535236] xhci_hcd :0d:00.0: Host halt failed, -19 [ 79.535291] xhci_hcd :0d:00.0: can't setup: -19 [ 79.535347] xhci_hcd :0d:00.0: USB bus 7 deregistered [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 It was lucky because it never worked again. PCI card was not working but computer started. Here you can find included lspci -vv, lshw and full dmesg taken from during this unique startup with the PCI Card. I tried the same PCI Card with two computers and always had the same results. Kernel is hanging with "xhci_hcd :0d:00.0: init :0d:00.0 fail, -19" and nothing more. I tried this PCI Card with a CentOS 7.3 on same computer and kernel (3.10) is starting well and PCI card is fully working. Many thanks for your assistance. I apologize if it's an already reported bug. Kind Regards ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic ** Attachment added: "lspci -vv, lshw and full dmesg" https://bugs.launchpad.net/bugs/1820363/+attachment/5246647/+files/lspci-lshw-dmesg%404.15.0-29-generic.txt ** Description changed: Hello, Using Ubuntu installation media (ubuntu-18.06.2-server-amd64.iso / ubuntu-18.06.[1-2]-live-server-amd64.iso / Ubuntu Live 18.06.2 iso / Ubuntu Mate Live Ubuntu Live 18.06.[1-2] iso) Startup is hanging with : [0.214796] pci :0d:00.0: [1912:0014] type 00 class 0x0c0330 [0.215620] pci :0d:00.0: reg 0x10: [mem 0xfdbf-0xfdbf1fff 64bit] [0.219160] pci :0d:00.0: PME# supported from D0 D3hot D3cold [ 79.272644] xhci_hcd :0d:00.0: xHCI Host Controller [ 79.272710] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 7 [ 79.535236] xhci_hcd :0d:00.0: Host halt failed, -19 [ 79.535291] xhci_hcd :0d:00.0: can't setup: -19 [ 79.535347] xhci_hcd :0d:00.0: USB bus 7 deregistered - [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 + [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 I'm facing exactly the same bug as these one: https://www.mail-archive.com/linux-usb@vger.kernel.org/msg102138.html https://bugs.gentoo.org/show_bug.cgi?id=612704 I installed Ubuntu Server 18.04.2 without the PCI card without trouble and then reinserted the PCI Card computer never start always hanging at the same steps as above. I managed to start only once time with the PCI card plugged by adding "pci=nomsi" to the
[Kernel-packages] [Bug 1760851] Re: ethernet wired adapter lost
After a second reboot, the wired adapter device reappeared. And since this, it never disappeared again. I suppose this bug could be closed. -- 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/1760851 Title: ethernet wired adapter lost Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: When i upgraded kernel from linux-image-4.4.0-112-generic to linux- image-4.4.0-116-generic, my dell xps lost the wired network adapter. On this laptop the ethernet wired adapter is on usb-c extension. When i boot on my old kernel : * The device is named enxd481d74f12bb. * The address looks to be /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enxd481d74f12bb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fcombernous 7044 F pulseaudio Date: Tue Apr 3 14:18:14 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=7c5d4db9-e495-4d8b-ac3e-12534cd9fdd2 InstallationDate: Installed on 2017-05-19 (319 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=ce828ede-44e4-4f8a-a8c4-422e1815674d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-112-generic N/A linux-backports-modules-4.4.0-112-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760851/+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 1760851] Re: ethernet wired adapter lost
I used commands "apt-mark hold" and "apt-mark manual" on follwing packages : linux-headers-4.4.0-112 linux-headers-4.4.0-112-generic linux-image-4.4.0-112-generic linux-image-extra-4.4.0-112-generic linux-signed-image-4.4.0-112-generic linux-tools-4.4.0-112 linux-tools-4.4.0-112-generic Is it enough ? -- 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/1760851 Title: ethernet wired adapter lost Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: When i upgraded kernel from linux-image-4.4.0-112-generic to linux- image-4.4.0-116-generic, my dell xps lost the wired network adapter. On this laptop the ethernet wired adapter is on usb-c extension. When i boot on my old kernel : * The device is named enxd481d74f12bb. * The address looks to be /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enxd481d74f12bb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fcombernous 7044 F pulseaudio Date: Tue Apr 3 14:18:14 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=7c5d4db9-e495-4d8b-ac3e-12534cd9fdd2 InstallationDate: Installed on 2017-05-19 (319 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=ce828ede-44e4-4f8a-a8c4-422e1815674d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-112-generic N/A linux-backports-modules-4.4.0-112-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760851/+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 1760851] Re: ethernet wired adapter lost
I need you explain how to ensure that kernel vmlinuz-4.4.0-112-generic will not be uninstalled by installing the new one. Only this one work as expected. -- 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/1760851 Title: ethernet wired adapter lost Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: When i upgraded kernel from linux-image-4.4.0-112-generic to linux- image-4.4.0-116-generic, my dell xps lost the wired network adapter. On this laptop the ethernet wired adapter is on usb-c extension. When i boot on my old kernel : * The device is named enxd481d74f12bb. * The address looks to be /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enxd481d74f12bb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fcombernous 7044 F pulseaudio Date: Tue Apr 3 14:18:14 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=7c5d4db9-e495-4d8b-ac3e-12534cd9fdd2 InstallationDate: Installed on 2017-05-19 (319 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=ce828ede-44e4-4f8a-a8c4-422e1815674d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-112-generic N/A linux-backports-modules-4.4.0-112-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760851/+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 1760851] Re: ethernet wired adapter lost
** Summary changed: - ethernet wired adepter lost + ethernet wired adapter lost ** Description changed: When i upgraded kernel from linux-image-4.4.0-112-generic to linux- image-4.4.0-116-generic, my dell xps lost the wired network adapter. - On this host the adpater is on usb-c extension. When i boot on my old kernel : - * The device is named enxd481d74f12bb. - * The address looks to be /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enxd481d74f12bb + On this host the adapter is on usb-c extension. When i boot on my old kernel : + * The device is named enxd481d74f12bb. + * The address looks to be /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enxd481d74f12bb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: fcombernous 7044 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: fcombernous 7044 F pulseaudio Date: Tue Apr 3 14:18:14 2018 DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-xenial-amd64-20160624-2 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=7c5d4db9-e495-4d8b-ac3e-12534cd9fdd2 InstallationDate: Installed on 2017-05-19 (319 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=ce828ede-44e4-4f8a-a8c4-422e1815674d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-4.4.0-112-generic N/A - linux-backports-modules-4.4.0-112-generic N/A - linux-firmware 1.157.17 + linux-restricted-modules-4.4.0-112-generic N/A + linux-backports-modules-4.4.0-112-generic N/A + linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. ** Description changed: When i upgraded kernel from linux-image-4.4.0-112-generic to linux- image-4.4.0-116-generic, my dell xps lost the wired network adapter. - On this host the adapter is on usb-c extension. When i boot on my old kernel : + On this laptop the ethernet wired adapter is on usb-c extension. When i boot on my old kernel : * The device is named enxd481d74f12bb. * The address looks to be /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enxd481d74f12bb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fcombernous 7044 F pulseaudio Date: Tue Apr 3 14:18:14 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=7c5d4db9-e495-4d8b-ac3e-12534cd9fdd2 InstallationDate: Installed on 2017-05-19 (319 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=ce828ede-44e4-4f8a-a8c4-422e1815674d ro quiet splash vt.handoff=7
[Kernel-packages] [Bug 1760851] [NEW] ethernet wired adapter lost
Public bug reported: When i upgraded kernel from linux-image-4.4.0-112-generic to linux- image-4.4.0-116-generic, my dell xps lost the wired network adapter. On this laptop the ethernet wired adapter is on usb-c extension. When i boot on my old kernel : * The device is named enxd481d74f12bb. * The address looks to be /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enxd481d74f12bb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fcombernous 7044 F pulseaudio Date: Tue Apr 3 14:18:14 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=7c5d4db9-e495-4d8b-ac3e-12534cd9fdd2 InstallationDate: Installed on 2017-05-19 (319 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=ce828ede-44e4-4f8a-a8c4-422e1815674d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-112-generic N/A linux-backports-modules-4.4.0-112-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- 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/1760851 Title: ethernet wired adapter lost Status in linux package in Ubuntu: Confirmed Bug description: When i upgraded kernel from linux-image-4.4.0-112-generic to linux- image-4.4.0-116-generic, my dell xps lost the wired network adapter. On this laptop the ethernet wired adapter is on usb-c extension. When i boot on my old kernel : * The device is named enxd481d74f12bb. * The address looks to be /sys/devices/pci:00/:00:1c.0/:01:00.0/:02:02.0/:39:00.0/usb4/4-1/4-1.4/4-1.4:1.0/net/enxd481d74f12bb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-112-generic 4.4.0-112.135 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fcombernous 7044 F pulseaudio Date: Tue Apr 3 14:18:14 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=7c5d4db9-e495-4d8b-ac3e-12534cd9fdd2 InstallationDate: Installed on 2017-05-19 (319 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=ce828ede-44e4-4f8a-a8c4-422e1815674d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-112-generic N/A linux-backports-modules-4.4.0-112-generic N/A linux-firmware 1.157.17 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS
[Kernel-packages] [Bug 1753797] [NEW] package linux-firmware 1.157.16 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: My system is a toshiba satellite that was originally windows and i converted to ubuntu after several errors led to me erasing my harddrive and installing ubuntu. I frequently need to manually fsck /dev/sda2. I have also found that it is difficult to install updates on this system. I typically need to reboot and manually fsck then attempt reinstall. I believe that I am running ubuntu 16.43. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.16 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Mar 6 06:57:06 2018 Dependencies: DuplicateSignature: package:linux-firmware:1.157.16 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package linux-firmware (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-12-25 (70 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: linux-firmware Title: package linux-firmware 1.157.16 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1753797 Title: package linux-firmware 1.157.16 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux-firmware package in Ubuntu: New Bug description: My system is a toshiba satellite that was originally windows and i converted to ubuntu after several errors led to me erasing my harddrive and installing ubuntu. I frequently need to manually fsck /dev/sda2. I have also found that it is difficult to install updates on this system. I typically need to reboot and manually fsck then attempt reinstall. I believe that I am running ubuntu 16.43. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.16 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Tue Mar 6 06:57:06 2018 Dependencies: DuplicateSignature: package:linux-firmware:1.157.16 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package linux-firmware (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-12-25 (70 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: linux-firmware Title: package linux-firmware 1.157.16 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1753797/+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 1346687] Re: Ubuntu 14 KVM Guest I/O Elevator Non-configurable
any news ? -- 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/1346687 Title: Ubuntu 14 KVM Guest I/O Elevator Non-configurable Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 14.04 guest runs pretty much standard standard configuration: KVM hypervisor, ACPI and APIC enabled, virtio disk bus, raw storage format... While running this project, I am also involved in testing SSD drives across different Linux distributions and their support for discard option (TRIM). To cut the story short, Ubuntu-based KVM guest did not set any scheduler on the boot disk vda): # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom deadline 1 0B 0B vda disk 1 0B 0B vda1 part 1 0B 0B vda2 part 1 0B 0B vda5 part 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B That is in stark contrast with other distributions running almost identical KVM guest configuration (with the exception of the root file system using BTRFS instead of EXT4 on SUSE). Oracle Linux 6.5: # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom deadline 1 0B 0B vda disk deadline 1 0B 0B vda1 part deadline 1 0B 0B vda2 part deadline 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B OpenSUSE 13.1: # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom cfq 1 0B 0B vda disk cfq 1 0B 0B vda1 part cfq 1 0B 0B vda2 part cfq 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B Indeed, checking elevator capabilities for boot disk on Ubuntu KVM guest showed: # cat /sys/block/vda/queue/scheduler none Other Linux distributions show more options: # cat /sys/block/vda/queue/scheduler noop deadline [cfq] As well, attempts to change the elevator on Ubuntu guest fail. For example: # echo noop > /sys/block/vda/queue/scheduler # echo $? 0 # cat /sys/block/vda/queue/scheduler none Setting it globally in /etc/default/grub and updating it via update- grub2 fails too. In the meantime, to automate check of elevators (schedulers) and discard support for SSD drives and thin-provisioned volumes on Linux, I wrote simple Perl script: http://www.circlingcycle.com.au/Unix-sources/Linux-check-IO-scheduler- and-discard-support.pl.txt Part of the results on RHEL 6.5 server would look like: INFO: I/O elevator (scheduler) and discard support summary INFO: Hard Disk sdb configured with I/O scheduler "cfq" INFO: SSD sda configured with I/O scheduler "deadline" supports discard operation INFO: Hard Disk sdc configured with I/O scheduler "cfq" INFO: Hard Disk sdi configured with I/O scheduler "cfq" INFO: Hard Disk sdh configured with I/O scheduler "cfq" The Ubuntu KVM guest runs latest paches: Linux ubuntu14-vm2.circlingcycle.com.au 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Regards, Dusan Baljevic VK2COT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1346687/+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 1585523] [NEW] backlight issue with HP Envy 17 under Ubuntu 14.04
Public bug reported: Having tried all the kernel options suggested on the page https://wiki.ubuntu.com/Kernel/Debugging/Backlight I never saw the backlight files under /sys/class/backlight and the function keys are not working. See below some info on my environment and all the degug info as per requested in the above mentioned wiki in the attached file. Regards, Fabien $ uname -a Linux HPMATE 3.16.0-33-generic #44~14.04.1-Ubuntu SMP Fri Mar 13 10:33:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Kernel option from Grub : none $ ll /sys/class/backlight total 0 drwxr-xr-x 2 root root 0 mai 25 09:38 ./ drwxr-xr-x 55 root root 0 mai 25 09:38 ../ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 CurrentDesktop: MATE Date: Wed May 25 09:50:46 2016 InstallationDate: Installed on 2016-05-21 (4 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Attachment added: "backlight_debug_info.tar.gz" https://bugs.launchpad.net/bugs/1585523/+attachment/4669983/+files/backlight_debug_info.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1585523 Title: backlight issue with HP Envy 17 under Ubuntu 14.04 Status in linux-lts-utopic package in Ubuntu: New Bug description: Having tried all the kernel options suggested on the page https://wiki.ubuntu.com/Kernel/Debugging/Backlight I never saw the backlight files under /sys/class/backlight and the function keys are not working. See below some info on my environment and all the degug info as per requested in the above mentioned wiki in the attached file. Regards, Fabien $ uname -a Linux HPMATE 3.16.0-33-generic #44~14.04.1-Ubuntu SMP Fri Mar 13 10:33:29 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Kernel option from Grub : none $ ll /sys/class/backlight total 0 drwxr-xr-x 2 root root 0 mai 25 09:38 ./ drwxr-xr-x 55 root root 0 mai 25 09:38 ../ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-33-generic 3.16.0-33.44~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 CurrentDesktop: MATE Date: Wed May 25 09:50:46 2016 InstallationDate: Installed on 2016-05-21 (4 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323) SourcePackage: linux-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1585523/+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 1557776] Re: CONFIG_AUFS_XATTR is not set
I installed linux-image-4.2.0-36-generic, version 4.2.0-36.41 from wily-proposed. I got yet : $> grep AUFS_X /boot/config-4.2.0-36-generic # CONFIG_AUFS_XATTR is not set -- 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/1557776 Title: CONFIG_AUFS_XATTR is not set Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: Fix Committed Status in linux source package in Xenial: Fix Released Bug description: I am using ubuntu 15.10 with kernel linux-image-4.2.0-27-generic. The setting CONFIG_AUFS_XATTR is not set. With the previous ubuntu version 15.04 and linux- image-3.19.0-42-generic this setting was compiled as CONFIG_AUFS_XATTR=y Without CONFIG_AUFS_XATTR docker users using the AUFS driver can not work with capabilities. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557776/+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 1514851] [NEW] package linux-image-3.13.0-68-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generi
Public bug reported: ubuntu 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-68-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexandra 2125 F pulseaudio Date: Tue Nov 10 14:33:40 2015 DpkgTerminalLog: Log started: 2015-11-08 20:43:11 Log ended: 2015-11-08 20:46:43 Log started: 2015-11-10 14:33:31 ErrorMessage: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generic » vers « /boot/vmlinuz-3.13.0-68-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) HibernationDevice: RESUME=UUID=81ebcde1-859b-44f8-b71a-12d82b0b207b InstallationDate: Installed on 2015-07-03 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Packard Bell Easynote TE69BMP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-3.13.0-68-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generic » vers « /boot/vmlinuz-3.13.0-68-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V2.11 dmi.board.name: Easynote TE69BMP dmi.board.vendor: Packard Bell dmi.board.version: V2.11 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV2.11:bd04/07/2014:svnPackardBell:pnEasynoteTE69BMP:pvrV2.11:rvnPackardBell:rnEasynoteTE69BMP:rvrV2.11:cvnPackardBell:ct10:cvrChassisVersion: dmi.product.name: Easynote TE69BMP dmi.product.version: V2.11 dmi.sys.vendor: Packard Bell ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1514851 Title: package linux-image-3.13.0-68-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generic » vers « /boot/vmlinuz-3.13.0-68-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) Status in linux package in Ubuntu: New Bug description: ubuntu 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-68-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexandra 2125 F pulseaudio Date: Tue Nov 10 14:33:40 2015 DpkgTerminalLog: Log started: 2015-11-08 20:43:11 Log ended: 2015-11-08 20:46:43 Log started: 2015-11-10 14:33:31 ErrorMessage: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generic » vers « /boot/vmlinuz-3.13.0-68-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) HibernationDevice: RESUME=UUID=81ebcde1-859b-44f8-b71a-12d82b0b207b InstallationDate: Installed on 2015-07-03 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Packard Bell Easynote TE69BMP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-3.13.0-68-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generic » vers « /boot/vmlinuz-3.13.0-68-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V2.11 dmi.board.name: Easynote TE69BMP dmi.board.vendor: Packard Bell dmi.board.version: V2.11 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV2.11:bd04/07/2014:svnPackardBell:pnEasynot
[Kernel-packages] [Bug 1514852] [NEW] package linux-image-extra-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: ubuntu 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-67-generic 3.13.0-67.110 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexandra 2125 F pulseaudio Date: Sun Nov 8 20:46:15 2015 DpkgTerminalLog: Log started: 2015-11-08 20:43:11 ErrorMessage: problèmes de dépendances - laissé non configuré HibernationDevice: RESUME=UUID=81ebcde1-859b-44f8-b71a-12d82b0b207b InstallationDate: Installed on 2015-07-03 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Packard Bell Easynote TE69BMP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V2.11 dmi.board.name: Easynote TE69BMP dmi.board.vendor: Packard Bell dmi.board.version: V2.11 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV2.11:bd04/07/2014:svnPackardBell:pnEasynoteTE69BMP:pvrV2.11:rvnPackardBell:rnEasynoteTE69BMP:rvrV2.11:cvnPackardBell:ct10:cvrChassisVersion: dmi.product.name: Easynote TE69BMP dmi.product.version: V2.11 dmi.sys.vendor: Packard Bell ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1514852 Title: package linux-image-extra-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in linux package in Ubuntu: New Bug description: ubuntu 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-67-generic 3.13.0-67.110 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexandra 2125 F pulseaudio Date: Sun Nov 8 20:46:15 2015 DpkgTerminalLog: Log started: 2015-11-08 20:43:11 ErrorMessage: problèmes de dépendances - laissé non configuré HibernationDevice: RESUME=UUID=81ebcde1-859b-44f8-b71a-12d82b0b207b InstallationDate: Installed on 2015-07-03 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Packard Bell Easynote TE69BMP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V2.11 dmi.board.name: Easynote TE69BMP dmi.board.vendor: Packard Bell dmi.board.version: V2.11 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV2.11:bd04/07/2014:svnPackardBell:pnEasynoteTE69BMP:pvrV2.11:rvnPackardBell:rnEasynoteTE69BMP:rvrV2.11:cvnPackardBell:ct10:cvrChassisVersion: dmi.product.name: Easynote TE69BMP dmi.product.version: V2.11 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514852/+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 1514848] [NEW] package linux-image-extra-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: ubuntu 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-67-generic 3.13.0-67.110 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexandra 2125 F pulseaudio Date: Sun Nov 8 20:46:15 2015 DpkgTerminalLog: Log started: 2015-11-08 20:43:11 ErrorMessage: problèmes de dépendances - laissé non configuré HibernationDevice: RESUME=UUID=81ebcde1-859b-44f8-b71a-12d82b0b207b InstallationDate: Installed on 2015-07-03 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Packard Bell Easynote TE69BMP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V2.11 dmi.board.name: Easynote TE69BMP dmi.board.vendor: Packard Bell dmi.board.version: V2.11 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV2.11:bd04/07/2014:svnPackardBell:pnEasynoteTE69BMP:pvrV2.11:rvnPackardBell:rnEasynoteTE69BMP:rvrV2.11:cvnPackardBell:ct10:cvrChassisVersion: dmi.product.name: Easynote TE69BMP dmi.product.version: V2.11 dmi.sys.vendor: Packard Bell ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1514848 Title: package linux-image-extra-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in linux package in Ubuntu: New Bug description: ubuntu 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-67-generic 3.13.0-67.110 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexandra 2125 F pulseaudio Date: Sun Nov 8 20:46:15 2015 DpkgTerminalLog: Log started: 2015-11-08 20:43:11 ErrorMessage: problèmes de dépendances - laissé non configuré HibernationDevice: RESUME=UUID=81ebcde1-859b-44f8-b71a-12d82b0b207b InstallationDate: Installed on 2015-07-03 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Packard Bell Easynote TE69BMP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V2.11 dmi.board.name: Easynote TE69BMP dmi.board.vendor: Packard Bell dmi.board.version: V2.11 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV2.11:bd04/07/2014:svnPackardBell:pnEasynoteTE69BMP:pvrV2.11:rvnPackardBell:rnEasynoteTE69BMP:rvrV2.11:cvnPackardBell:ct10:cvrChassisVersion: dmi.product.name: Easynote TE69BMP dmi.product.version: V2.11 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514848/+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 1514843] [NEW] package linux-image-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie
Public bug reported: Description:Ubuntu 14.04.3 LTS Release:14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-67-generic 3.13.0-67.110 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexandra 2125 F pulseaudio Date: Sun Nov 8 20:46:15 2015 DpkgTerminalLog: Log started: 2015-11-08 20:43:11 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 HibernationDevice: RESUME=UUID=81ebcde1-859b-44f8-b71a-12d82b0b207b InstallationDate: Installed on 2015-07-03 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Packard Bell Easynote TE69BMP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V2.11 dmi.board.name: Easynote TE69BMP dmi.board.vendor: Packard Bell dmi.board.version: V2.11 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV2.11:bd04/07/2014:svnPackardBell:pnEasynoteTE69BMP:pvrV2.11:rvnPackardBell:rnEasynoteTE69BMP:rvrV2.11:cvnPackardBell:ct10:cvrChassisVersion: dmi.product.name: Easynote TE69BMP dmi.product.version: V2.11 dmi.sys.vendor: Packard Bell ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1514843 Title: package linux-image-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 Status in linux package in Ubuntu: New Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-67-generic 3.13.0-67.110 ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexandra 2125 F pulseaudio Date: Sun Nov 8 20:46:15 2015 DpkgTerminalLog: Log started: 2015-11-08 20:43:11 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 HibernationDevice: RESUME=UUID=81ebcde1-859b-44f8-b71a-12d82b0b207b InstallationDate: Installed on 2015-07-03 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Packard Bell Easynote TE69BMP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-3.13.0-67-generic 3.13.0-67.110 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V2.11 dmi.board.name: Easynote TE69BMP dmi.board.vendor: Packard Bell dmi.board.version: V2.11 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV2.11:bd04/07/2014:svnPackardBell:pnEasynoteTE69BMP:pvrV2.11:rvnPackardBell:rnEasynoteTE69BMP:rvrV2.11:cvnPackardBell:ct10:cvrChassisVersion: dmi.product.name: Easynote TE69BMP dmi.product.version: V2.11 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1514843/+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 1514847] [NEW] package linux-image-3.13.0-68-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generi
Public bug reported: ubuntu 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-68-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexandra 2125 F pulseaudio Date: Tue Nov 10 14:33:40 2015 DpkgTerminalLog: Log started: 2015-11-08 20:43:11 Log ended: 2015-11-08 20:46:43 Log started: 2015-11-10 14:33:31 ErrorMessage: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generic » vers « /boot/vmlinuz-3.13.0-68-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) HibernationDevice: RESUME=UUID=81ebcde1-859b-44f8-b71a-12d82b0b207b InstallationDate: Installed on 2015-07-03 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Packard Bell Easynote TE69BMP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-3.13.0-68-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generic » vers « /boot/vmlinuz-3.13.0-68-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V2.11 dmi.board.name: Easynote TE69BMP dmi.board.vendor: Packard Bell dmi.board.version: V2.11 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV2.11:bd04/07/2014:svnPackardBell:pnEasynoteTE69BMP:pvrV2.11:rvnPackardBell:rnEasynoteTE69BMP:rvrV2.11:cvnPackardBell:ct10:cvrChassisVersion: dmi.product.name: Easynote TE69BMP dmi.product.version: V2.11 dmi.sys.vendor: Packard Bell ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1514847 Title: package linux-image-3.13.0-68-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generic » vers « /boot/vmlinuz-3.13.0-68-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) Status in linux package in Ubuntu: New Bug description: ubuntu 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-68-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26 Uname: Linux 3.13.0-65-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexandra 2125 F pulseaudio Date: Tue Nov 10 14:33:40 2015 DpkgTerminalLog: Log started: 2015-11-08 20:43:11 Log ended: 2015-11-08 20:46:43 Log started: 2015-11-10 14:33:31 ErrorMessage: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generic » vers « /boot/vmlinuz-3.13.0-68-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) HibernationDevice: RESUME=UUID=81ebcde1-859b-44f8-b71a-12d82b0b207b InstallationDate: Installed on 2015-07-03 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Packard Bell Easynote TE69BMP ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-65-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-3.13.0-68-generic (not installed) failed to install/upgrade: impossible de copier les données extraites pour « ./boot/vmlinuz-3.13.0-68-generic » vers « /boot/vmlinuz-3.13.0-68-generic.dpkg-new » : échec d'écriture (Aucun espace disponible sur le périphérique) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: Packard Bell dmi.bios.version: V2.11 dmi.board.name: Easynote TE69BMP dmi.board.vendor: Packard Bell dmi.board.version: V2.11 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPackardBell:bvrV2.11:bd04/07/2014:svnPackardBell:pnEasynot
[Kernel-packages] [Bug 532137] Re: Wacom Intuos2 tablet hotplug only works once after booting
Sadly, the problem is still not fixed on last xubuntu 14.04.1, same result on a linux Mint. -- 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/532137 Title: Wacom Intuos2 tablet hotplug only works once after booting Status in X.Org X server: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “xf86-input-wacom” package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-input-wacom The following two tablets do not work out plug-and-play of the box in Lucid: 056a:0041 Wacom Co., Ltd Intuos2 4x5 056a:0044 Wacom Co., Ltd Intuos2 12x12 messages/syslog: Mar 4 14:17:37 cool kernel: [94581.248021] usb 3-2: new full speed USB device using uhci_hcd and address 6 Mar 4 14:17:37 cool kernel: [94581.416147] usb 3-2: configuration #1 chosen from 1 choice Mar 4 14:17:37 cool kernel: [94581.419397] input: Wacom Intuos2 4x5 as /devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0/input/input18 ProblemType: Bug Architecture: i386 Date: Thu Mar 4 14:36:17 2010 DistroRelease: Ubuntu 10.04 Package: xserver-xorg-input-wacom 1:0.10.3+20100109-1ubuntu1 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-15-generic root=/dev/mapper/hostname-root ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-15.22-generic SourcePackage: nvidia-graphics-drivers Uname: Linux 2.6.32-15-generic i686 dmi.bios.date: 06/05/2006 dmi.bios.vendor: Intel Corp. dmi.bios.version: MQ96510J.86A.0372.2006.0605.1717 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DG965MQ dmi.board.vendor: Intel Corporation dmi.board.version: AAD37419-102 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrMQ96510J.86A.0372.2006.0605.1717:bd06/05/2006:svn:pn:pvr:rvnIntelCorporation:rnDG965MQ:rvrAAD37419-102:cvn:ct2:cvr: glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucidarchitecture: i686kernel: 2.6.32-15-generic To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/532137/+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 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name
I tested on a KINGSTON v300 and a v100 and everything works fine. I used the discard mount option as it seems to be the most efficient to detect this misbehavior. And then I started: sudo apt-get build-dep libreoffice; apt-get source -b libreoffice It worked fine, I also tried with periodic fstrim -v / No problem either. I'm now starting to do the same test on a Kingspec C3000.6 and several other models from the same manufacturer. -- 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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Triaged Bug description: fs goes into read-only mode while building LibreOffice. WORKAROUND: Disable discard option - /dev/mapper/volumegroup-root/ ext4discard,noatime,nodiratime,errors=remount-ro01 disabling ncq has no effect. $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629543: block 214443457: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=262404
[Kernel-packages] [Bug 1259829] Re: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name
What kind of heavy simple test can I run on my Kingston and Kingspec SSDs to know if they also are affected by this kind of problems ? A simple testing method should help build the whitelist/blacklist. I have access to several SSDs from a lot of manufacturers, the only ones that are not already whitelisted are Kingston and Kingspec, I have some of them of various models, so I may be able to help. I'm already using them with discard enabled, but I'm not usually doing anything crazy on them. If I should compile LibreOffice or do some kind of stress testing on them, I will if you ask me. -- 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/1259829 Title: htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 Status in “linux” package in Ubuntu: Triaged Bug description: fs goes into read-only mode while building LibreOffice. WORKAROUND: Disable discard option - /dev/mapper/volumegroup-root/ ext4discard,noatime,nodiratime,errors=remount-ro01 disabling ncq has no effect. $ dmesg ... [ 2045.473249] virbr0: port 1(vnet0) entered forwarding state [ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready [10660.961381] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [11822.935891] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629599: block 214443464: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1667681412, rec_len=45654, name_len=39 [11822.935896] Aborting journal on device dm-1-8. [11822.935998] EXT4-fs (dm-1): Remounting filesystem read-only [11822.960425] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629605: block 214443466: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2707156714, rec_len=19312, name_len=162 [11850.985003] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629557: block 214443458: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=512948573, rec_len=8858, name_len=176 [11850.985276] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629465: block 214443455: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=160939375, rec_len=26085, name_len=126 [11850.985499] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629325: block 214443451: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=2322664969, rec_len=33791, name_len=132 [11850.985927] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629467: block 214443456: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=954332768, rec_len=21653, name_len=30 [11850.986409] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629074: block 214443433: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=2061605548, rec_len=4984, name_len=3 [11850.986831] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53628835: block 214443432: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=3523041938, rec_len=53167, name_len=41 [11850.987001] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629098: block 214443436: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4225920287, rec_len=35138, name_len=75 [11850.987466] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629275: block 214443449: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=923253145, rec_len=44001, name_len=144 [11850.988115] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629270: block 214443448: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=1892288796, rec_len=55247, name_len=58 [11851.042303] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629300: block 214443450: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=1809316884, rec_len=4208, name_len=195 [11851.042938] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629401: block 214443453: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=4223616103, rec_len=36326, name_len=130 [11851.045745] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629406: block 214443454: comm rm: bad entry in directory: rec_len % 4 != 0 - offset=0(0), inode=415237227, rec_len=24702, name_len=59 [11851.125849] EXT4-fs error (device dm-1): htree_dirblock_to_tree:920: inode #53629101: block 214443437: comm rm: bad entry in directory: directory entry across range - offset=0(0), inode=23292377, rec_len=28820, name_len=135 [11851.126086] EXT4-fs error (
