[Kernel-packages] [Bug 1844443] Re: Version check wrapper scripts for e.g. perf packaged in linux-tools-common prevent usage in a Docker container e.g. on Kubernetes
There's not really an applicable Ubuntu kernel to collect logs for; the problem is only apparent in a container on top of a host that doesn't run a recognized kernel. ** 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/183 Title: Version check wrapper scripts for e.g. perf packaged in linux-tools- common prevent usage in a Docker container e.g. on Kubernetes Status in linux package in Ubuntu: Confirmed Bug description: The `perf` profiling tool, and a few other tools, are part of the Linux project. Ubuntu gets them from a package specific to the running kernel version, and uses wrapper scripts installed as e.g. /usr/bin/perf to dispatch to the appropriate version for the running kernel. This appears to involve not only checking the actual kernel version number (e.g. 4.15.0) but also the patch level/build number and flavor that Ubuntu adds (e.g. 4.15.0-62-generic) if found in the kernel version. This is perfectly fine on a real system, where Ubuntu's package manager is actually in control of the kernel. But Ubuntu is also fantastically popular as a base for Docker images, and in a Docker container you have to take your lumps and run on whatever kernel version the host happens to be using, even if the host isn't using an official Ubuntu kernel, or running Ubuntu at all. As currently designed, the linux-tools-common wrapper scripts cannot work reliably in a Docker environment. When running in my particular Kubernetes environment (where the host is some kind of Red Hat Enterprise Linux derivative), this problem manifests as the following exchange: root@adamnovak-pod:/vg# perf record ls WARNING: perf not found for kernel 3.10.0 You may need to install the following packages for this specific kernel: linux-tools-3.10.0 You may also want to install one of the following packages to keep up to date: linux-tools root@adamnovak-pod:/vg# apt install linux-tools-3.10.0 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-tools-3.10.0 E: Couldn't find any package by glob 'linux-tools-3.10.0' E: Couldn't find any package by regex 'linux-tools-3.10.0' However, the perf binary I happen to have installed, when I get it to try to run, at least appears to work, despite the kernel version mismatch. In larger tests, I've gotten perfectly fine profiling data. root@adamnovak-pod:/vg# /usr/lib/linux-tools/4.15.0-62-generic/perf record ls bin deps perf.data scripts [ perf record: Woken up 2 times to write data ] [ perf record: Captured and wrote 0.002 MB perf.data (10 samples) ] root@adamnovak-pod:/vg# So it is not clear that the level of specificity enforced by the wrapper scripts is actually necessary. There are a few potential solutions I can see to this problem: 1. Modify the scripts to treat the lack of the exact right tool version being installed as a warning instead of an error, and have them select the closest version to run instead. 2. Create linux-tools-3.10.0 ish through linux-tools-5.x.x packages, containing builds of perf and co. derived from those official mainline kernels, and a metapackage to install all of them. Then the package that you get prompted to install when running in a container will exist, and you will be able to install it to have a toolset that has a high probability of being compatible with the kernel you are running on. A container that needs to be portable between different hosts can install the metapackage. 3. Create a package that conflicts with linux-tools-common and provides some arbitrary version of the tools. People who want a toolset that can run in a container can install that package instead, and bear the responsibility for what happens if the tools provided don't work with the kernel that happens to be running. 4. Hook into the alternatives system; allow the user to switch between packages providing the tools for different kernel versions, with the default being the dispatch script. The workaround I am currently using is running this as soon as I get inside the container, to clobber the wrapper script with whatever actual binary I have installed: cp /usr/lib/linux-tools/*/perf /usr/bin/perf However, this is a pretty terrible hack. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-tools-common 4.15.0-62.69 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion:
[Kernel-packages] [Bug 1844443] Re: Version check wrapper scripts for e.g. perf packaged in linux-tools-common prevent usage in a Docker container e.g. on Kubernetes
I reported this bug from this container running on an Ubuntu-based host where I built it. When I tried to run ubuntu-bug in the container on the host where I actually encountered the problem, it refused to report the bug due to... a non-Ubuntu kernel! -- 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/183 Title: Version check wrapper scripts for e.g. perf packaged in linux-tools- common prevent usage in a Docker container e.g. on Kubernetes Status in linux package in Ubuntu: Incomplete Bug description: The `perf` profiling tool, and a few other tools, are part of the Linux project. Ubuntu gets them from a package specific to the running kernel version, and uses wrapper scripts installed as e.g. /usr/bin/perf to dispatch to the appropriate version for the running kernel. This appears to involve not only checking the actual kernel version number (e.g. 4.15.0) but also the patch level/build number and flavor that Ubuntu adds (e.g. 4.15.0-62-generic) if found in the kernel version. This is perfectly fine on a real system, where Ubuntu's package manager is actually in control of the kernel. But Ubuntu is also fantastically popular as a base for Docker images, and in a Docker container you have to take your lumps and run on whatever kernel version the host happens to be using, even if the host isn't using an official Ubuntu kernel, or running Ubuntu at all. As currently designed, the linux-tools-common wrapper scripts cannot work reliably in a Docker environment. When running in my particular Kubernetes environment (where the host is some kind of Red Hat Enterprise Linux derivative), this problem manifests as the following exchange: root@adamnovak-pod:/vg# perf record ls WARNING: perf not found for kernel 3.10.0 You may need to install the following packages for this specific kernel: linux-tools-3.10.0 You may also want to install one of the following packages to keep up to date: linux-tools root@adamnovak-pod:/vg# apt install linux-tools-3.10.0 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-tools-3.10.0 E: Couldn't find any package by glob 'linux-tools-3.10.0' E: Couldn't find any package by regex 'linux-tools-3.10.0' However, the perf binary I happen to have installed, when I get it to try to run, at least appears to work, despite the kernel version mismatch. In larger tests, I've gotten perfectly fine profiling data. root@adamnovak-pod:/vg# /usr/lib/linux-tools/4.15.0-62-generic/perf record ls bin deps perf.data scripts [ perf record: Woken up 2 times to write data ] [ perf record: Captured and wrote 0.002 MB perf.data (10 samples) ] root@adamnovak-pod:/vg# So it is not clear that the level of specificity enforced by the wrapper scripts is actually necessary. There are a few potential solutions I can see to this problem: 1. Modify the scripts to treat the lack of the exact right tool version being installed as a warning instead of an error, and have them select the closest version to run instead. 2. Create linux-tools-3.10.0 ish through linux-tools-5.x.x packages, containing builds of perf and co. derived from those official mainline kernels, and a metapackage to install all of them. Then the package that you get prompted to install when running in a container will exist, and you will be able to install it to have a toolset that has a high probability of being compatible with the kernel you are running on. A container that needs to be portable between different hosts can install the metapackage. 3. Create a package that conflicts with linux-tools-common and provides some arbitrary version of the tools. People who want a toolset that can run in a container can install that package instead, and bear the responsibility for what happens if the tools provided don't work with the kernel that happens to be running. 4. Hook into the alternatives system; allow the user to switch between packages providing the tools for different kernel versions, with the default being the dispatch script. The workaround I am currently using is running this as soon as I get inside the container, to clobber the wrapper script with whatever actual binary I have installed: cp /usr/lib/linux-tools/*/perf /usr/bin/perf However, this is a pretty terrible hack. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-tools-common 4.15.0-62.69 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion:
[Kernel-packages] [Bug 1844443] [NEW] Version check wrapper scripts for e.g. perf packaged in linux-tools-common prevent usage in a Docker container e.g. on Kubernetes
Public bug reported: The `perf` profiling tool, and a few other tools, are part of the Linux project. Ubuntu gets them from a package specific to the running kernel version, and uses wrapper scripts installed as e.g. /usr/bin/perf to dispatch to the appropriate version for the running kernel. This appears to involve not only checking the actual kernel version number (e.g. 4.15.0) but also the patch level/build number and flavor that Ubuntu adds (e.g. 4.15.0-62-generic) if found in the kernel version. This is perfectly fine on a real system, where Ubuntu's package manager is actually in control of the kernel. But Ubuntu is also fantastically popular as a base for Docker images, and in a Docker container you have to take your lumps and run on whatever kernel version the host happens to be using, even if the host isn't using an official Ubuntu kernel, or running Ubuntu at all. As currently designed, the linux-tools-common wrapper scripts cannot work reliably in a Docker environment. When running in my particular Kubernetes environment (where the host is some kind of Red Hat Enterprise Linux derivative), this problem manifests as the following exchange: root@adamnovak-pod:/vg# perf record ls WARNING: perf not found for kernel 3.10.0 You may need to install the following packages for this specific kernel: linux-tools-3.10.0 You may also want to install one of the following packages to keep up to date: linux-tools root@adamnovak-pod:/vg# apt install linux-tools-3.10.0 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-tools-3.10.0 E: Couldn't find any package by glob 'linux-tools-3.10.0' E: Couldn't find any package by regex 'linux-tools-3.10.0' However, the perf binary I happen to have installed, when I get it to try to run, at least appears to work, despite the kernel version mismatch. In larger tests, I've gotten perfectly fine profiling data. root@adamnovak-pod:/vg# /usr/lib/linux-tools/4.15.0-62-generic/perf record ls bin deps perf.data scripts [ perf record: Woken up 2 times to write data ] [ perf record: Captured and wrote 0.002 MB perf.data (10 samples) ] root@adamnovak-pod:/vg# So it is not clear that the level of specificity enforced by the wrapper scripts is actually necessary. There are a few potential solutions I can see to this problem: 1. Modify the scripts to treat the lack of the exact right tool version being installed as a warning instead of an error, and have them select the closest version to run instead. 2. Create linux-tools-3.10.0 ish through linux-tools-5.x.x packages, containing builds of perf and co. derived from those official mainline kernels, and a metapackage to install all of them. Then the package that you get prompted to install when running in a container will exist, and you will be able to install it to have a toolset that has a high probability of being compatible with the kernel you are running on. A container that needs to be portable between different hosts can install the metapackage. 3. Create a package that conflicts with linux-tools-common and provides some arbitrary version of the tools. People who want a toolset that can run in a container can install that package instead, and bear the responsibility for what happens if the tools provided don't work with the kernel that happens to be running. 4. Hook into the alternatives system; allow the user to switch between packages providing the tools for different kernel versions, with the default being the dispatch script. The workaround I am currently using is running this as soon as I get inside the container, to clobber the wrapper script with whatever actual binary I have installed: cp /usr/lib/linux-tools/*/perf /usr/bin/perf However, this is a pretty terrible hack. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-tools-common 4.15.0-62.69 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Sep 17 19:20:29 2019 Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-62-generic root=/dev/mapper/hex--vg-root ro splash quiet vt.handoff=1
Re: [Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
Do I have to downgrade my system from Dingo to Cosmic in order to test this in Cosmic, to keep my bug from being closed? May 20, 2019 7:02 AM, "Ubuntu Kernel Bot" wrote: > This bug is awaiting verification that the kernel in -proposed solves > the problem. Please test the kernel and update this bug with the > results. If the problem is solved, change the tag 'verification-needed- > cosmic' to 'verification-done-cosmic'. If the problem still exists, > change the tag 'verification-needed-cosmic' to 'verification-failed- > cosmic'. > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > ** Tags added: verification-needed-cosmic > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1824259 > > Title: > Headphone jack switch sense is inverted: plugging in headphones > disables headphone output > > Status in linux package in Ubuntu: > Fix Committed > Status in linux source package in Bionic: > Fix Committed > Status in linux source package in Cosmic: > Fix Committed > Status in linux source package in Disco: > Fix Committed > > Bug description: > [Impact] > On the LattePanda board, the headphone detection signal is not correct, it is > inverted: plugging in headphones disables headphone output > > [Fix] > In the codec driver, there already is a fixup, just set the inv_jd1_1 to true. > > [Test Case] > It is tested by the bug reporter, please refer to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/comments/23 > > [Regression Risk] > Low. This fix is specific to a board which is defined by DMI strings. > > My machine is a LattePanda board, which uses a "chtrt5645" device as a sound > card. It has a single > headphone output jack, which I think is a TRRS jack, with a mic input, such > as is normally used on > phones. > > When I don't have headphones plugged in, the system thinks headphones > *are* plugged in. Gnome Control Center shows my audio device as being > headphones. If I insert a headphone connector partway into the jack, I > can even get sound in the headphones. > > But if I plug the headphones all the way in, the system decided that I > have *un*plugged the headphones, and switches output over to > "Speaker". The system doesn't actually have a speaker, only a > headphone jack. And when the system switches over to "Speaker", I get > no sound out of the headphones, even if I open "pavucontrol" and swap > over to "Headphones (unplugged)" on the "Output Devices" tab. > > This is what "pacmd"'s "list-cards" command says with my headphones > *unplugged*: > > 2 card(s) available. > index: 0 > name: > driver: > owner module: 7 > properties: > alsa.card = "1" > alsa.card_name = "Intel HDMI/DP LPE Audio" > alsa.long_card_name = "Intel HDMI/DP LPE Audio" > alsa.driver_name = "snd_hdmi_lpe_audio" > device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" > sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" > device.bus = "pci" > device.vendor.id = "8086" > device.vendor.name = "Intel Corporation" > device.product.id = "22b0" > device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Series PCI Configuration > Registers" > device.string = "1" > device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx > Series PCI Configuration > Registers" > module-udev-detect.discovered = "1" > device.icon_name = "audio-card-pci" > profiles: > output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: > no) > output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, > available: no) > output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, > available: no) > output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, > available: no) > output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority > 600, available: no) > output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority > 600, available: no) > output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, > available: no) > output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority > 600, available: no) > output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority > 600, available: no) > off: Off (priority 0, available: unknown) > active profile: > ports: > hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, > available: no) > properties: > device.icon_name = "video-display" > hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, > available: no) > properties: > device.icon_name = "video-display" > hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, > available: no) > properties: >
[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
OK, this second deb seems to solve my problem! The headphone jack state is detected correctly without the quirk! Thanks! -- 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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority 8000, available:
[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
Here's the whole `sudo dmidecode` output (attached). ** Attachment added: "Output of sudo dmidecode for the LattePanda" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+attachment/5258402/+files/dmidecode.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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1"
[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
Hello, Thank you for looking into this. I installed the DKMS module deb (which built itself against kernel 5.0.0-13, which is what the system is now updated to), commented out the quirk-setting line in my module config file, and rebooted. I now have no sound; list-cards in pacmd shows me that it thinks the headphone output is unavailable when plugged in, again. 1 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority 8000, available: unknown) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink/#0: Built-in Audio Headphones + Speaker sources: alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink.monitor/#0: Monitor of Built-in Audio Headphones + Speaker alsa_input.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__source/#1: Built-in Audio Headset Microphone + Internal Analog Microphone ports: [Out] Headphones: Headphones (priority 100, latency offset 0 usec, available: no) properties: [Out] Speaker: Speaker (priority 100, latency offset 0 usec, available: unknown) properties: [In] HSMic: Headset Microphone (priority 100, latency offset 0 usec, available: no) properties: [In] Mic: Internal Analog Microphone (priority 150, latency offset 0 usec, available: unknown) properties: I'm going to put it back the way I had it (remove the deb and reinstate the quirk). Is there anything else I can test? Or any more DMI info you would like? Is there something special I can do to make sure the module override actually loaded? Thanks, -Adam -- 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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1"
[Kernel-packages] [Bug 1824259] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255462/+files/ProcCpuinfoMinimal.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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles:
[Kernel-packages] [Bug 1824259] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255463/+files/ProcInterrupts.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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi:
[Kernel-packages] [Bug 1824259] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255461/+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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority
[Kernel-packages] [Bug 1824259] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255466/+files/UdevDb.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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority
[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
apport information ** Tags added: apport-collected ** Description changed: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority 8000, available: unknown) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink/#0: Built-in Audio Headphones + Speaker sources: alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink.monitor/#0: Monitor of Built-in Audio
[Kernel-packages] [Bug 1824259] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255459/+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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default
[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
I set the bug to Confirmed, despite being the original reporter, because the bot told me to. The Apport logs I posted are form the system with my workaround enabled. I also blacklisted the HDMI audio module, since I don't use HDMI audio, and I thought it might help. It didn't seem to, but I never unblacklisted it. -- 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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0"
[Kernel-packages] [Bug 1824259] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255467/+files/WifiSyslog.txt ** 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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1"
[Kernel-packages] [Bug 1824259] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255458/+files/CRDA.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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority 8000,
[Kernel-packages] [Bug 1824259] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255460/+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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default
[Kernel-packages] [Bug 1824259] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255465/+files/PulseList.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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default
[Kernel-packages] [Bug 1824259] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255464/+files/ProcModules.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/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in linux package in Ubuntu: Confirmed Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default
[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
This is actually a kernel bug, in Linux. The issue is the absence of
platform data for this particular board in the snd_soc_rt5645 module.
The issue can be worked around by creating
/etc/modprobe.d/hacksound.conf with the following contents:
# Invert jack detection (1) and use detection mode 2 (2).
options snd_soc_rt5645 quirk=0x21
This takes advantage of the "quirk" option for the module, added in
https://github.com/torvalds/linux/commit/4999b0214b05a08b42bbafcb29a0b9c413002d3f,
which allows overriding the platform data it usually just has built into
it about how audio jacks are hooked up on particular systems.
It looks like this board needs special system info added to
sound/soc/codecs/rt5645.c, keyed on DMI data. The platform data would
look something like:
static const struct rt5645_platform_data lattepanda_platform_data = {
.jd_mode = 2,
.inv_jd1_1 = true
};
Here's the DMI data for the motherboard; it's a bit generic. I can
provide other DMI data to match on if needed.
Base Board Information
Manufacturer: AMI Corporation
Product Name: Cherry Trail CR
Version: Default string
Serial Number: Default string
Asset Tag: Default string
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Default string
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
** Package changed: alsa-lib (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1824259
Title:
Headphone jack switch sense is inverted: plugging in headphones
disables headphone output
Status in linux package in Ubuntu:
Incomplete
Bug description:
My machine is a LattePanda board, which uses a "chtrt5645" device as a
sound card. It has a single headphone output jack, which I think is a
TRRS jack, with a mic input, such as is normally used on phones.
When I don't have headphones plugged in, the system thinks headphones
*are* plugged in. Gnome Control Center shows my audio device as being
headphones. If I insert a headphone connector partway into the jack, I
can even get sound in the headphones.
But if I plug the headphones all the way in, the system decided that I
have *un*plugged the headphones, and switches output over to
"Speaker". The system doesn't actually have a speaker, only a
headphone jack. And when the system switches over to "Speaker", I get
no sound out of the headphones, even if I open "pavucontrol" and swap
over to "Headphones (unplugged)" on the "Output Devices" tab.
This is what "pacmd"'s "list-cards" command says with my headphones
*unplugged*:
2 card(s) available.
index: 0
name:
driver:
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path =
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2)
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2)
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3)
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3)
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile:
ports:
hdmi-output-0:
[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
This may be a kernel driver bug, and a regression from 4.12. See http://www.lattepanda.com/topic-p24689.html?sid=1fa88916eb19dd9d65e0abd3ecbf6210#p24689 This may be a missing piece of platform data in the kernel that would tell it to invert jack detection on this particular board. I will try testing with the functionality added to the kernel in https://github.com/torvalds/linux/commit/4999b0214b05a08b42bbafcb29a0b9c413002d3f which lets you tinker with the platform data at runtime. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in alsa-lib package in Ubuntu: New Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path =
[Kernel-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
If I save the ALSA state with the headphones unplugged to a file:
sudo alsactl --file=settings-out.txt store
And then plug in the headphones and restore it:
sudo alsactl --file=settings-out.txt restore
I still get no sound. But then diffing the final state against the
unplugged state did find this:
control.175 {
iface CARD
name 'Headphone Jack'
- value false
+ value true
comment {
access read
type BOOLEAN
count 1
}
}
control.176 {
iface CARD
name 'Headset Mic Jack'
- value false
+ value true
comment {
access read
type BOOLEAN
count 1
}
}
I need to convince ALSA to report/interpret those boolean jack states
the other way around.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1824259
Title:
Headphone jack switch sense is inverted: plugging in headphones
disables headphone output
Status in alsa-lib package in Ubuntu:
New
Bug description:
My machine is a LattePanda board, which uses a "chtrt5645" device as a
sound card. It has a single headphone output jack, which I think is a
TRRS jack, with a mic input, such as is normally used on phones.
When I don't have headphones plugged in, the system thinks headphones
*are* plugged in. Gnome Control Center shows my audio device as being
headphones. If I insert a headphone connector partway into the jack, I
can even get sound in the headphones.
But if I plug the headphones all the way in, the system decided that I
have *un*plugged the headphones, and switches output over to
"Speaker". The system doesn't actually have a speaker, only a
headphone jack. And when the system switches over to "Speaker", I get
no sound out of the headphones, even if I open "pavucontrol" and swap
over to "Headphones (unplugged)" on the "Output Devices" tab.
This is what "pacmd"'s "list-cards" command says with my headphones
*unplugged*:
2 card(s) available.
index: 0
name:
driver:
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path =
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2)
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2)
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3)
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3)
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile:
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency
offset 0 usec, available: no)
[Kernel-packages] [Bug 1824259] [NEW] Headphone jack switch sense is inverted: plugging in headphones disables headphone output
Public bug reported: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority 8000, available: unknown) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink/#0: Built-in Audio Headphones + Speaker sources: alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink.monitor/#0: Monitor of Built-in Audio Headphones + Speaker alsa_input.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__source/#1:
[Kernel-packages] [Bug 1810207] [NEW] r8152 Ethernet adapter disconnects with a transmit queue timeout
Public bug reported: The r8152 Ethernet device in my Lattepanda board just disconnected from my network while I was uploading some files over the LAN. dmesg reported this: [1036155.155084] [ cut here ] [1036155.155099] NETDEV WATCHDOG: enx00e04c368b17 (r8152): transmit queue 0 timed out [1036155.155201] WARNING: CPU: 0 PID: 0 at /build/linux-vxxS7y/linux-4.15.0/net/sched/sch_generic.c:323 dev_watchdog+0x221/0x230 [1036155.155207] Modules linked in: xt_nat xt_tcpudp veth ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc overlay aufs nls_iso8859_1 snd_soc_sst_cht_bsw_rt5645 axp288_fuel_gauge axp288_adc axp288_charger industrialio axp20x_pek extcon_axp288 gpio_keys intel_rapl intel_powerclamp coretemp kvm_intel kvm irqbypass punit_atom_debug crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cdc_ether cryptd usbnet intel_cstate r8152 mii cdc_acm snd_intel_sst_acpi snd_intel_sst_core mei_txe snd_soc_sst_atom_hifi2_platform snd_soc_acpi mei snd_seq_midi snd_soc_acpi_intel_match [1036155.14] snd_seq_midi_event processor_thermal_device snd_rawmidi intel_soc_dts_iosf lpc_ich snd_hdmi_lpe_audio snd_seq snd_soc_rt5645 snd_soc_rl6231 snd_soc_core intel_hid snd_compress sparse_keymap snd_seq_device axp20x_i2c ac97_bus dw_dmac snd_pcm_dmaengine goodix axp20x snd_pcm dw_dmac_core snd_timer pwm_lpss_platform snd pwm_lpss soundcore spi_pxa2xx_platform 8250_dw int3400_thermal int3406_thermal acpi_thermal_rel int3403_thermal mac_hid int340x_thermal_zone soc_button_array intel_int0002_vgpio acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid mmc_block i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm video sdhci_acpi sdhci [1036155.155901] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW 4.15.0-43-generic #46-Ubuntu [1036155.155907] Hardware name: Default string Default string/Cherry Trail CR, BIOS DF-BI-7-S70CR200-CC55F-022-B 05/15/2018 [1036155.155920] RIP: 0010:dev_watchdog+0x221/0x230 [1036155.155929] RSP: 0018:9b977fc03e58 EFLAGS: 00010286 [1036155.155941] RAX: RBX: RCX: 0006 [1036155.155948] RDX: 0007 RSI: 0092 RDI: 9b977fc16490 [1036155.155955] RBP: 9b977fc03e88 R08: 0001 R09: 043e [1036155.155963] R10: 9b977fc03ee0 R11: R12: 0001 [1036155.155969] R13: 9b97725c1000 R14: 9b97725c1478 R15: 9b976d4ede80 [1036155.155981] FS: () GS:9b977fc0() knlGS: [1036155.155988] CS: 0010 DS: ES: CR0: 80050033 [1036155.155995] CR2: 7ffe98d7e008 CR3: 00017540a000 CR4: 001006f0 [1036155.156003] Call Trace: [1036155.156014] [1036155.156039] ? dev_deactivate_queue.constprop.33+0x60/0x60 [1036155.156055] call_timer_fn+0x30/0x130 [1036155.156069] run_timer_softirq+0x3fb/0x450 [1036155.156081] ? ktime_get+0x43/0xa0 [1036155.156094] ? lapic_next_deadline+0x26/0x30 [1036155.156108] __do_softirq+0xe4/0x2bb [1036155.156124] irq_exit+0xb8/0xc0 [1036155.156135] smp_apic_timer_interrupt+0x79/0x130 [1036155.156147] apic_timer_interrupt+0x84/0x90 [1036155.156153] [1036155.156169] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 [1036155.156175] RSP: 0018:ad803e10 EFLAGS: 0246 ORIG_RAX: ff11 [1036155.156187] RAX: 9b977fc22880 RBX: 0003ae60abf28410 RCX: 001f [1036155.156193] RDX: 0003ae60abf28410 RSI: fff7e3411b99 RDI: [1036155.156200] RBP: ad803e50 R08: 0001 R09: 027c [1036155.156206] R10: ad803de0 R11: 1e6e R12: 9b977fc2c400 [1036155.156213] R13: 0003 R14: ad971cb8 R15: [1036155.156234] cpuidle_enter+0x17/0x20 [1036155.156248] call_cpuidle+0x23/0x40 [1036155.156259] do_idle+0x18c/0x1f0 [1036155.156272] cpu_startup_entry+0x73/0x80 [1036155.156287] rest_init+0xae/0xb0 [1036155.156302] start_kernel+0x4dc/0x4fd [1036155.156314] x86_64_start_reservations+0x24/0x26 [1036155.156324] x86_64_start_kernel+0x74/0x77 [1036155.156339] secondary_startup_64+0xa5/0xb0 [1036155.156348] Code: 38 00 49 63 4e e8 eb 92 4c 89 ef c6 05 f9 d7 d8 00 01 e8 83 35 fd ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 30 99 59 ad e8 df 95 80 ff <0f> 0b eb c0 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 [1036155.156580] ---[ end trace 5a05a48c7e597e05 ]--- [1036155.156645] r8152 1-4:1.0 enx00e04c368b17: Tx timeout [1036157.235268] r8152 1-4:1.0 enx00e04c368b17: Tx status -2 [1036157.235353] r8152 1-4:1.0 enx00e04c368b17: Tx status -2 [1036157.235431] r8152 1-4:1.0 enx00e04c368b17: Tx status -2
[Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
I don't seem to have access to change the tag, but I can confirm that
4.15.0-34-generic from -proposed solves the problem. So the tag should
be verification-done-bionic.
--
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/1777338
Title:
Linux 4.15.0-23 crashes during the boot process with a "Unable to
handle kernel NULL pointer dereference" message
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
Mainline commit 1f50ddb4f418 introduced a regression. That commit added
speculative_store_bypass_ht_init() to the per-CPU initialization sequence.
However, speculative_store_bypass_ht_init() needs to be called on each CPU for
PV guests, as well.
The regresssion prevents systems from booting.
The patch to fix this regression has also been cc'd to upstream stable,
but it has not landed in Bionic as of yet.
== Fix ==
74899d92e666 ("x86/xen: Add call of speculative_store_bypass_ht_init() to PV
paths")
== Regression Potential ==
Low. This patch fixes a current regressionThis patch has also been
submitted to upstream stable, so it has had additional upstream review.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
I went to boot my computer today and it wouldn't boot.
I get an "Unable to handle kernel NULL pointer dereference" message
during the boot process, and, a bit after that, a message from the
kernel watchdog about CPU #0 being stuck. Then the boot process stops
completely.
I was able to boot the system by telling Grub to load 4.15.0-22, which
works perfectly fine, so there has been a regression.
I am running Ubuntu as a Xen dom0, if that matters. I haven't tried
booting the offending kernel version without Xen.
I'm not sure where, if anywhere, these messages go on disk, for
posting.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-23-generic 4.15.0-23.25
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 17 10:12:58 2018
InstallationDate: Installed on 2017-08-06 (314 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed
UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+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
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I have tested the provided kernel and it works for me under Xen. Thank you for fixing the bug! I look forward to seeing this in the real releases. [anovak@octagon ~]$ uname -a Linux octagon 4.15.0-31-generic #34~lp1777338 SMP Tue Aug 7 14:57:12 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux On Mon, Aug 13, 2018 at 8:48 AM, Joseph Salisbury wrote: > The hashes are: > > 63d7e9ca7710792e1603953b0ec14337 linux-image- > unsigned-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb > > 8cca692f07f9edbb56dec15375bc9979 linux- > modules-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb > > df24a98ec4769f33a9831a5aaeb9f437 linux-modules- > extra-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+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
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
Thanks for preparing this kernel; I am downloading it now. What are the expected hashes of the files, so that I can verify the insecure downloads? On Tue, Aug 7, 2018 at 8:49 AM, Joseph Salisbury wrote: > I built a test kernel with commit 74899d92e3dc7671a8017b3146dcd4735f3b. > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1777338 > > Can you test this kernel and see if it resolves this bug? > > If this kernel also fixes the bug, I'll submit an SRU request. > > > Note about installing test kernels: > • If the test kernel is prior to 4.15(Bionic) you need to install the > linux-image and linux-image-extra .deb packages. > • If the test kernel is 4.15(Bionic) or newer, you need to install the > linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. > > Thanks in advance! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+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 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I grabbed commit 74899d92e3dc7671a8017b3146dcd4735f3b "x86/xen: Add call of speculative_store_bypass_ht_init() to PV paths" from g...@github.com:torvalds/linux.git and cherry-picked it on top of the tag Ubuntu-4.15.0-29.31, and built the kernel, and now it boots fine as dom0! I think that that patch fixes this bug. How can I get this commit to be pulled into the main Ubuntu kernel development branch, to be released in the official kernel builds? -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+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 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
I've been advised by Juergen Gross that not having "x86/xen: Add call of speculative_store_bypass_ht_init() to PV paths" from the mainline kernel might contribute to this problem. I am trying to pull that in now. -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+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
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
I'm not finding any kernel packages in bionic-proposed; maybe they were released already? I've installed and tested 4.15.0-29 from the normal repos; it has the same null pointer dereference at address 8 issue. On Tue, Jul 24, 2018, 09:17 Joseph Salisbury wrote: > Thanks for finishing up the bisect! > > Would it be possible for you to test the proposed kernel and post back if > it resolves this bug? > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. > > Thank you in advance! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions > -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+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
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I have finished the bisect. 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c is the first bad commit. I tested it and it displays the problem, and I tested abd39ac1da07b433fc570332ee9ad938b5071760 right before it and that one boots fine. On Sat, Jul 21, 2018 at 9:42 AM, Adam Novak wrote: > That one works. On to 5856293c78e552c012835e667d66775bba20b4f7. > > I suspect 3f6a3b035f91 and abd39ac1da07 may be the real problem, since > the CPU I am using is an AMD Ryzen chip, and those are tinkering > specifically with how the kernel handles those. > > On Fri, Jul 20, 2018 at 10:23 PM, Adam Novak wrote: >> OK, I tried that one and it still exhibited the issue. I'm going to >> try 91762b4035d9da8c266e2cb3dbc552052434bbf0 next. >> >> On Fri, Jul 20, 2018 at 9:08 PM, Adam Novak wrote: >>> Thanks! >>> >>> I have tested this kernel; it doesn't work, so the problem is between >>> fc8704280f2ada9f61f08a2d5adc0dab169cc207 and >>> 8eca6add0defde203282476d7969a7c13bbd7d91. >>> >>> I've gotten set up with a kernel build environment; I think I can >>> finish the git bisect myself, but looking at the commits in that >>> range, I have no hope of actually fixing the underlying bug myself. >>> I'm building 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c now. >>> >>> On Tue, Jul 17, 2018 at 11:24 AM, Joseph Salisbury >>> wrote: >>>> I built the next test kernel, up to the following commit: >>>> fc8704280f2ada9f61f08a2d5adc0dab169cc207 >>>> >>>> The test kernel can be downloaded from: >>>> http://kernel.ubuntu.com/~jsalisbury/lp1777338 >>>> >>>> Can you test that kernel and report back if it has the bug or not? I >>>> will build the next test kernel based on your test results. >>>> >>>> Thanks in advance >>>> >>>> >>>> MD5SUM of files: >>>> d76993d34e1203375090a47c4de8ebfe >>>> linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>>> >>>> 5b89b2341b858bbe2bcae88e3efaf8c8 linux- >>>> modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>>> >>>> 6928b4ad5f2a861ad674ff88a4745471 linux-modules- >>>> extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>>> >>>> -- >>>> You received this bug notification because you are subscribed to the bug >>>> report. >>>> https://bugs.launchpad.net/bugs/1777338 >>>> >>>> Title: >>>> Linux 4.15.0-23 crashes during the boot process with a "Unable to >>>> handle kernel NULL pointer dereference" message >>>> >>>> Status in linux package in Ubuntu: >>>> In Progress >>>> Status in linux source package in Bionic: >>>> In Progress >>>> >>>> Bug description: >>>> I went to boot my computer today and it wouldn't boot. >>>> >>>> I get an "Unable to handle kernel NULL pointer dereference" message >>>> during the boot process, and, a bit after that, a message from the >>>> kernel watchdog about CPU #0 being stuck. Then the boot process stops >>>> completely. >>>> >>>> I was able to boot the system by telling Grub to load 4.15.0-22, which >>>> works perfectly fine, so there has been a regression. >>>> >>>> I am running Ubuntu as a Xen dom0, if that matters. I haven't tried >>>> booting the offending kernel version without Xen. >>>> >>>> I'm not sure where, if anywhere, these messages go on disk, for >>>> posting. >>>> >>>> ProblemType: Bug >>>> DistroRelease: Ubuntu 18.04 >>>> Package: linux-image-4.15.0-23-generic 4.15.0-23.25 >>>> ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 >>>> Uname: Linux 4.15.0-22-generic x86_64 >>>> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair >>>> ApportVersion: 2.20.9-0ubuntu7.1 >>>> Architecture: amd64 >>>> CurrentDesktop: ubuntu:GNOME >>>> Date: Sun Jun 17 10:12:58 2018 >>>> InstallationDate: Installed on 2017-08-06 (314 days ago) >>>> InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) >>>> ProcEnviron: >>>>TERM=xterm-256color >>>>PATH=(custom, no user) >>>>XDG_RUNTIME_DIR= >>>>
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
That one works. On to 5856293c78e552c012835e667d66775bba20b4f7. I suspect 3f6a3b035f91 and abd39ac1da07 may be the real problem, since the CPU I am using is an AMD Ryzen chip, and those are tinkering specifically with how the kernel handles those. On Fri, Jul 20, 2018 at 10:23 PM, Adam Novak wrote: > OK, I tried that one and it still exhibited the issue. I'm going to > try 91762b4035d9da8c266e2cb3dbc552052434bbf0 next. > > On Fri, Jul 20, 2018 at 9:08 PM, Adam Novak wrote: >> Thanks! >> >> I have tested this kernel; it doesn't work, so the problem is between >> fc8704280f2ada9f61f08a2d5adc0dab169cc207 and >> 8eca6add0defde203282476d7969a7c13bbd7d91. >> >> I've gotten set up with a kernel build environment; I think I can >> finish the git bisect myself, but looking at the commits in that >> range, I have no hope of actually fixing the underlying bug myself. >> I'm building 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c now. >> >> On Tue, Jul 17, 2018 at 11:24 AM, Joseph Salisbury >> wrote: >>> I built the next test kernel, up to the following commit: >>> fc8704280f2ada9f61f08a2d5adc0dab169cc207 >>> >>> The test kernel can be downloaded from: >>> http://kernel.ubuntu.com/~jsalisbury/lp1777338 >>> >>> Can you test that kernel and report back if it has the bug or not? I >>> will build the next test kernel based on your test results. >>> >>> Thanks in advance >>> >>> >>> MD5SUM of files: >>> d76993d34e1203375090a47c4de8ebfe >>> linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>> >>> 5b89b2341b858bbe2bcae88e3efaf8c8 linux- >>> modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>> >>> 6928b4ad5f2a861ad674ff88a4745471 linux-modules- >>> extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/1777338 >>> >>> Title: >>> Linux 4.15.0-23 crashes during the boot process with a "Unable to >>> handle kernel NULL pointer dereference" message >>> >>> Status in linux package in Ubuntu: >>> In Progress >>> Status in linux source package in Bionic: >>> In Progress >>> >>> Bug description: >>> I went to boot my computer today and it wouldn't boot. >>> >>> I get an "Unable to handle kernel NULL pointer dereference" message >>> during the boot process, and, a bit after that, a message from the >>> kernel watchdog about CPU #0 being stuck. Then the boot process stops >>> completely. >>> >>> I was able to boot the system by telling Grub to load 4.15.0-22, which >>> works perfectly fine, so there has been a regression. >>> >>> I am running Ubuntu as a Xen dom0, if that matters. I haven't tried >>> booting the offending kernel version without Xen. >>> >>> I'm not sure where, if anywhere, these messages go on disk, for >>> posting. >>> >>> ProblemType: Bug >>> DistroRelease: Ubuntu 18.04 >>> Package: linux-image-4.15.0-23-generic 4.15.0-23.25 >>> ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 >>> Uname: Linux 4.15.0-22-generic x86_64 >>> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair >>> ApportVersion: 2.20.9-0ubuntu7.1 >>> Architecture: amd64 >>> CurrentDesktop: ubuntu:GNOME >>> Date: Sun Jun 17 10:12:58 2018 >>> InstallationDate: Installed on 2017-08-06 (314 days ago) >>> InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) >>> ProcEnviron: >>>TERM=xterm-256color >>>PATH=(custom, no user) >>>XDG_RUNTIME_DIR= >>>LANG=en_US.UTF-8 >>>SHELL=/bin/bash >>> SourcePackage: linux-signed >>> UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) >>> >>> To manage notifications about this bug go to: >>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I tried that one and it still exhibited the issue. I'm going to try 91762b4035d9da8c266e2cb3dbc552052434bbf0 next. On Fri, Jul 20, 2018 at 9:08 PM, Adam Novak wrote: > Thanks! > > I have tested this kernel; it doesn't work, so the problem is between > fc8704280f2ada9f61f08a2d5adc0dab169cc207 and > 8eca6add0defde203282476d7969a7c13bbd7d91. > > I've gotten set up with a kernel build environment; I think I can > finish the git bisect myself, but looking at the commits in that > range, I have no hope of actually fixing the underlying bug myself. > I'm building 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c now. > > On Tue, Jul 17, 2018 at 11:24 AM, Joseph Salisbury > wrote: >> I built the next test kernel, up to the following commit: >> fc8704280f2ada9f61f08a2d5adc0dab169cc207 >> >> The test kernel can be downloaded from: >> http://kernel.ubuntu.com/~jsalisbury/lp1777338 >> >> Can you test that kernel and report back if it has the bug or not? I >> will build the next test kernel based on your test results. >> >> Thanks in advance >> >> >> MD5SUM of files: >> d76993d34e1203375090a47c4de8ebfe >> linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >> >> 5b89b2341b858bbe2bcae88e3efaf8c8 linux- >> modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >> >> 6928b4ad5f2a861ad674ff88a4745471 linux-modules- >> extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1777338 >> >> Title: >> Linux 4.15.0-23 crashes during the boot process with a "Unable to >> handle kernel NULL pointer dereference" message >> >> Status in linux package in Ubuntu: >> In Progress >> Status in linux source package in Bionic: >> In Progress >> >> Bug description: >> I went to boot my computer today and it wouldn't boot. >> >> I get an "Unable to handle kernel NULL pointer dereference" message >> during the boot process, and, a bit after that, a message from the >> kernel watchdog about CPU #0 being stuck. Then the boot process stops >> completely. >> >> I was able to boot the system by telling Grub to load 4.15.0-22, which >> works perfectly fine, so there has been a regression. >> >> I am running Ubuntu as a Xen dom0, if that matters. I haven't tried >> booting the offending kernel version without Xen. >> >> I'm not sure where, if anywhere, these messages go on disk, for >> posting. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 18.04 >> Package: linux-image-4.15.0-23-generic 4.15.0-23.25 >> ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 >> Uname: Linux 4.15.0-22-generic x86_64 >> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair >> ApportVersion: 2.20.9-0ubuntu7.1 >> Architecture: amd64 >> CurrentDesktop: ubuntu:GNOME >> Date: Sun Jun 17 10:12:58 2018 >> InstallationDate: Installed on 2017-08-06 (314 days ago) >> InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) >> ProcEnviron: >>TERM=xterm-256color >>PATH=(custom, no user) >>XDG_RUNTIME_DIR= >>LANG=en_US.UTF-8 >>SHELL=/bin/bash >> SourcePackage: linux-signed >> UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
Thanks! I have tested this kernel; it doesn't work, so the problem is between fc8704280f2ada9f61f08a2d5adc0dab169cc207 and 8eca6add0defde203282476d7969a7c13bbd7d91. I've gotten set up with a kernel build environment; I think I can finish the git bisect myself, but looking at the commits in that range, I have no hope of actually fixing the underlying bug myself. I'm building 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c now. On Tue, Jul 17, 2018 at 11:24 AM, Joseph Salisbury wrote: > I built the next test kernel, up to the following commit: > fc8704280f2ada9f61f08a2d5adc0dab169cc207 > > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1777338 > > Can you test that kernel and report back if it has the bug or not? I > will build the next test kernel based on your test results. > > Thanks in advance > > > MD5SUM of files: > d76993d34e1203375090a47c4de8ebfe > linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb > > 5b89b2341b858bbe2bcae88e3efaf8c8 linux- > modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb > > 6928b4ad5f2a861ad674ff88a4745471 linux-modules- > extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I've tested this kernel, and it works just fine under Xen, from what I can tell. The system comes up just fine: Linux octagon 4.15.0-23-generic #26~lp1777338Commit8eca6add0 SMP Wed Jun 27 15:50:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux The offending commit must be later. On Thu, Jul 5, 2018 at 8:32 AM, Joseph Salisbury wrote: > Here are the md5sum hashes of the files needed to install the test > kernel: > > d5f16dcf0080db1268d3b3477c911cd7 linux-image- > unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commit8eca6add0_amd64.deb > > 1d7504d8e691ba64d552a2d507179882 linux- > modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commit8eca6add0_amd64.deb > > b004fa6244e3e038b0d67c86e0218536 linux-modules- > extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commit8eca6add0_amd64.deb > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+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
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
Hello, Thanks for putting this together. I tried to get the kernels you built, but I'm having trouble establishing a secure (https) connection to kernel.ubuntu.com. It looks like the server might not offer https. Can you give me the expected hashes of the files so I can verify the downloads? Thanks, -Adam On Wed, Jun 27, 2018 at 10:34 AM, Joseph Salisbury wrote: > I started a kernel bisect between v4.15.0-22 and v4.15.0-23. The kernel > bisect will require testing of about 7-10 test kernels. > > I built the first test kernel, up to the following commit: > 8eca6add0defde203282476d7969a7c13bbd7d91 > > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1777338 > > Can you test that kernel and report back if it has the bug or not? I > will build the next test kernel based on your test results. > > > Thanks in advance > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+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
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
I updated my BIOS and tested the -24 kernel, as was recommended. It definitely doesn't work any better. It still has the null dereference problem, and then it prints a bunch of smp_call_function_too_many errors, apparently forever. On Tue, Jun 19, 2018, 08:11 Joseph Salisbury wrote: > Can you see if this issue exists in the 4.15.0-24 kernel: > > https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/15010188 > > Note about installing test kernels: > • If the test kernel is prior to 4.15(Bionic) you need to install the > linux-image and linux-image-extra .deb packages. > • If the test kernel is 4.15(Bionic) or newer, you need to install the > linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. > > Thanks in advance! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions > -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+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 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
This also affects the mainline kernel build 4.17.0-041700.201806041953 that I was testing for another bug. I've attached a photo of the screen with the issue occurring, in that version. Booting not under Xen seems to work around the issue, and the system comes up, but that's not useful for me because I need Xen. ** Attachment added: "Screenshot of the null pointer dereference message" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1777338/+attachment/5153715/+files/Screenshot.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux-signed package in Ubuntu: New Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1777338/+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 1775487] Re: Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports
The drive that was giving me this problem failed. I got a replacement (which is notionally the same model, with the same USB ID 0781:5581), and, on kernel 4.15-22, under Xen, the new drive seems to work fine in USB 3 ports. However, I also tested with the latest v4.17 kernel from the given link (4.17.0-041700.201806041953) That kernel does not boot under Xen where I run my system (it seems to suffer from https://bugs.launchpad.net/ubuntu/+source/linux- signed/+bug/1777338). When I load it outside of Xen, it does not mount my home directory, because it is on a ZFS disk and the provided builds do not seem to include ZFS support. It also does seem to work fine with the drive, but it has other substantial problems. -- 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/1775487 Title: Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports Status in linux package in Ubuntu: Incomplete Bug description: I have a 128 GB Sandisk Ultra USB Flash Drive. It works when I plug it into a USB 2.0 port, or if I partially insert it into a USB 3.0 port (so the USB 3 pins don't make contact). Here's what lsusb says about it: Bus 001 Device 005: ID 0781:5581 SanDisk Corp. Ultra And dmesg from a successful connection: [ 1269.667097] usb 3-1.4: new high-speed USB device number 6 using xhci_hcd [ 1269.779871] usb 3-1.4: New USB device found, idVendor=0781, idProduct=5581 [ 1269.779875] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1269.779878] usb 3-1.4: Product: Ultra [ 1269.779880] usb 3-1.4: Manufacturer: SanDisk [ 1269.779883] usb 3-1.4: SerialNumber: 4C530001080228105161 [ 1269.780937] usb-storage 3-1.4:1.0: USB Mass Storage device detected [ 1269.781346] scsi host10: usb-storage 3-1.4:1.0 [ 1270.800187] scsi 10:0:0:0: Direct-Access SanDisk Ultra 1.00 PQ: 0 ANSI: 6 [ 1270.800733] sd 10:0:0:0: Attached scsi generic sg3 type 0 [ 1270.800919] sd 10:0:0:0: [sdd] 240254976 512-byte logical blocks: (123 GB/115 GiB) [ 1270.801887] sd 10:0:0:0: [sdd] Write Protect is off [ 1270.801891] sd 10:0:0:0: [sdd] Mode Sense: 43 00 00 00 [ 1270.802269] sd 10:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 1270.811703] sdd: sdd1 [ 1270.813869] sd 10:0:0:0: [sdd] Attached SCSI removable disk But if I insert the drive all the way into a USB 3.0 port on a hub, I get nothing. And on a USB 3.0 port on the machine directly, I get this in dmesg: [ 1395.230629] xhci_hcd :03:00.0: Cannot set link state. [ 1395.230641] usb usb2-port4: cannot disable (err = -32) [ 1396.966273] xhci_hcd :03:00.0: Cannot set link state. [ 1396.966285] usb usb2-port4: cannot disable (err = -32) [ 1398.706493] xhci_hcd :03:00.0: Cannot set link state. [ 1398.706505] usb usb2-port4: cannot disable (err = -32) [ 1400.446161] xhci_hcd :03:00.0: Cannot set link state. [ 1400.446172] usb usb2-port4: cannot disable (err = -32) [ 1402.182073] xhci_hcd :03:00.0: Cannot set link state. [ 1402.182085] usb usb2-port4: cannot disable (err = -32) ...repeats until unplugged... It doesn't show up in lsusb in the USB 3.0 port. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:22:35 2018 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2017-08-06 (304 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed Symptom: storage UpgradeStatus: Upgraded to bionic on 2018-05-29 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775487/+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 1777338] [NEW] Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
Public bug reported: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux-signed package in Ubuntu: New Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1777338/+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 1775487] [NEW] Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports
Public bug reported: I have a 128 GB Sandisk Ultra USB Flash Drive. It works when I plug it into a USB 2.0 port, or if I partially insert it into a USB 3.0 port (so the USB 3 pins don't make contact). Here's what lsusb says about it: Bus 001 Device 005: ID 0781:5581 SanDisk Corp. Ultra And dmesg from a successful connection: [ 1269.667097] usb 3-1.4: new high-speed USB device number 6 using xhci_hcd [ 1269.779871] usb 3-1.4: New USB device found, idVendor=0781, idProduct=5581 [ 1269.779875] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1269.779878] usb 3-1.4: Product: Ultra [ 1269.779880] usb 3-1.4: Manufacturer: SanDisk [ 1269.779883] usb 3-1.4: SerialNumber: 4C530001080228105161 [ 1269.780937] usb-storage 3-1.4:1.0: USB Mass Storage device detected [ 1269.781346] scsi host10: usb-storage 3-1.4:1.0 [ 1270.800187] scsi 10:0:0:0: Direct-Access SanDisk Ultra1.00 PQ: 0 ANSI: 6 [ 1270.800733] sd 10:0:0:0: Attached scsi generic sg3 type 0 [ 1270.800919] sd 10:0:0:0: [sdd] 240254976 512-byte logical blocks: (123 GB/115 GiB) [ 1270.801887] sd 10:0:0:0: [sdd] Write Protect is off [ 1270.801891] sd 10:0:0:0: [sdd] Mode Sense: 43 00 00 00 [ 1270.802269] sd 10:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 1270.811703] sdd: sdd1 [ 1270.813869] sd 10:0:0:0: [sdd] Attached SCSI removable disk But if I insert the drive all the way into a USB 3.0 port on a hub, I get nothing. And on a USB 3.0 port on the machine directly, I get this in dmesg: [ 1395.230629] xhci_hcd :03:00.0: Cannot set link state. [ 1395.230641] usb usb2-port4: cannot disable (err = -32) [ 1396.966273] xhci_hcd :03:00.0: Cannot set link state. [ 1396.966285] usb usb2-port4: cannot disable (err = -32) [ 1398.706493] xhci_hcd :03:00.0: Cannot set link state. [ 1398.706505] usb usb2-port4: cannot disable (err = -32) [ 1400.446161] xhci_hcd :03:00.0: Cannot set link state. [ 1400.446172] usb usb2-port4: cannot disable (err = -32) [ 1402.182073] xhci_hcd :03:00.0: Cannot set link state. [ 1402.182085] usb usb2-port4: cannot disable (err = -32) ...repeats until unplugged... It doesn't show up in lsusb in the USB 3.0 port. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:22:35 2018 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2017-08-06 (304 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed Symptom: storage UpgradeStatus: Upgraded to bionic on 2018-05-29 (8 days ago) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1775487 Title: Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports Status in linux-signed package in Ubuntu: New Bug description: I have a 128 GB Sandisk Ultra USB Flash Drive. It works when I plug it into a USB 2.0 port, or if I partially insert it into a USB 3.0 port (so the USB 3 pins don't make contact). Here's what lsusb says about it: Bus 001 Device 005: ID 0781:5581 SanDisk Corp. Ultra And dmesg from a successful connection: [ 1269.667097] usb 3-1.4: new high-speed USB device number 6 using xhci_hcd [ 1269.779871] usb 3-1.4: New USB device found, idVendor=0781, idProduct=5581 [ 1269.779875] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1269.779878] usb 3-1.4: Product: Ultra [ 1269.779880] usb 3-1.4: Manufacturer: SanDisk [ 1269.779883] usb 3-1.4: SerialNumber: 4C530001080228105161 [ 1269.780937] usb-storage 3-1.4:1.0: USB Mass Storage device detected [ 1269.781346] scsi host10: usb-storage 3-1.4:1.0 [ 1270.800187] scsi 10:0:0:0: Direct-Access SanDisk Ultra 1.00 PQ: 0 ANSI: 6 [ 1270.800733] sd 10:0:0:0: Attached scsi generic sg3 type 0 [ 1270.800919] sd 10:0:0:0: [sdd] 240254976 512-byte logical blocks: (123 GB/115 GiB) [ 1270.801887] sd 10:0:0:0: [sdd] Write Protect is off [ 1270.801891] sd 10:0:0:0: [sdd] Mode Sense: 43 00 00 00 [ 1270.802269] sd 10:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 1270.811703] sdd: sdd1 [ 1270.813869] sd 10:0:0:0: [sdd] Attached SCSI removable disk But if I insert the drive all the way into a USB 3.0 port on a hub,
[Kernel-packages] [Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
It looks like the drive is replying with an ILLEGAL REQUEST/INVALID FIELD IN CDB error to all the interesting SCSI commands, and to pretty much anything hdparm sends it. I've also tried throwing sdparm at it. The only page sdparm can get out of it is the basic identification page: [anovak@octagon hdparm-9.54]$ sudo sdparm -i /dev/sdg /dev/sdg: Seagate Backup+ Hub BKD781 Device identification VPD page: Addressed logical unit: designator type: NAA, code set: Binary 0x5001 But this has convinced me that I am actually communicating with the disk itself. Is there any way the kernel/driver could be tinkering with the commands that hdparm used to send that worked and which now fail? Or is there some kind of initialization that isn't being done that would put the disk in a mode where it is willing to do more things? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1774569 Title: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04 Status in gsmartcontrol package in Ubuntu: New Status in hdparm package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: I recently upgraded from 17.10 to 18.04. After the upgrade, I noticed that my Seagate Backup+ Hub external drive was displaying a series of puzzling symptoms: 1. gsmartcontrol can't get SMART data from the drive. I am pretty sure it used to report SMART data? Here's a log of it not working: [hz] Warning: exit: Command line did not parse. [app] execute_smartctl(): Smartctl binary did not execute cleanly. [app] StorageDevice::execute_device_smartctl(): Smartctl binary did not execute cleanly. [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. [hz] Warning: exit: Some SMART command to the disk failed, or there was a checksum error in a SMART data structure [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. 2. hdparm used to be able to spin down the drive. I had it configured to spin it down after a few minutes of inactivity, in the hdparm config file. Now that no longer happens, and hdparm can't seem to talk to the drive meaningfully at all: [anovak@octagon ~]$ sudo hdparm -I /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA device, with non-removable media Standards: Likely used: 1 Configuration: Logical max current cylinders 0 0 heads 0 0 sectors/track 0 0 -- Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 0 MBytes device size with M = 1000*1000: 0 MBytes cache/buffer size = unknown Capabilities: IORDY not likely Cannot perform double-word IO R/W multiple sector transfer: not supported DMA: not supported PIO: pio0 [anovak@octagon ~]$ sudo hdparm -y /dev/sdb /dev/sdb: issuing standby command SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I think this may be related to https://askubuntu.com/questions/1037997 /upgraded-to-18-04-usb-harddrive-doesn-t-idle-anymore which is someone else having the same problem. 3. The ZFS tools think the drive is hosed: [anovak@octagon ~]$ sudo zpool status hub pool: hub state: UNAVAIL status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://zfsonlinux.org/msg/ZFS-8000-5E scan: none requested config: NAME STATE READ WRITE CKSUM hubUNAVAIL 0 0 0 insufficient replicas ata-ST6000DM003-2CY186_ZF200PC8 UNAVAIL 0 0 0 This may be related to the drive having adopted a new /dev/disk/by-id name during the upgrade? I think it was
[Kernel-packages] [Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
I pulled the hdparm binary from Artful, and it can't spin down the drive with -y either. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1774569 Title: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04 Status in gsmartcontrol package in Ubuntu: New Status in hdparm package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: I recently upgraded from 17.10 to 18.04. After the upgrade, I noticed that my Seagate Backup+ Hub external drive was displaying a series of puzzling symptoms: 1. gsmartcontrol can't get SMART data from the drive. I am pretty sure it used to report SMART data? Here's a log of it not working: [hz] Warning: exit: Command line did not parse. [app] execute_smartctl(): Smartctl binary did not execute cleanly. [app] StorageDevice::execute_device_smartctl(): Smartctl binary did not execute cleanly. [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. [hz] Warning: exit: Some SMART command to the disk failed, or there was a checksum error in a SMART data structure [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. 2. hdparm used to be able to spin down the drive. I had it configured to spin it down after a few minutes of inactivity, in the hdparm config file. Now that no longer happens, and hdparm can't seem to talk to the drive meaningfully at all: [anovak@octagon ~]$ sudo hdparm -I /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA device, with non-removable media Standards: Likely used: 1 Configuration: Logical max current cylinders 0 0 heads 0 0 sectors/track 0 0 -- Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 0 MBytes device size with M = 1000*1000: 0 MBytes cache/buffer size = unknown Capabilities: IORDY not likely Cannot perform double-word IO R/W multiple sector transfer: not supported DMA: not supported PIO: pio0 [anovak@octagon ~]$ sudo hdparm -y /dev/sdb /dev/sdb: issuing standby command SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I think this may be related to https://askubuntu.com/questions/1037997 /upgraded-to-18-04-usb-harddrive-doesn-t-idle-anymore which is someone else having the same problem. 3. The ZFS tools think the drive is hosed: [anovak@octagon ~]$ sudo zpool status hub pool: hub state: UNAVAIL status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://zfsonlinux.org/msg/ZFS-8000-5E scan: none requested config: NAME STATE READ WRITE CKSUM hubUNAVAIL 0 0 0 insufficient replicas ata-ST6000DM003-2CY186_ZF200PC8 UNAVAIL 0 0 0 This may be related to the drive having adopted a new /dev/disk/by-id name during the upgrade? I think it was "ata- ST6000DM003-2CY186_ZF200PC8" when I added it to my zpool by its symlink under /dev/disks/by-id, but now it is "usb- Seagate_Backup+_Hub_BK_NA8TQC87-0:0": [anovak@octagon ~]$ ls -lah /dev/disk/by-id/usb-Seagate_Backup+_Hub_BK_NA8TQC87-0\:0 lrwxrwxrwx 1 root root 9 May 31 20:52 /dev/disk/by-id/usb-Seagate_Backup+_Hub_BK_NA8TQC87-0:0 -> ../../sdb This *shouldn't* cause trouble; you should be able to export the zpool and re-import it under the new name. But zpool import shows nothing to import: [anovak@octagon ~]$ sudo zpool import no pools available to import And I also can't export or even destroy the busted zpool, because zpool doesn't think it exists for exporting or destroying purposes: [anovak@octagon ~]$ sudo zpool export
[Kernel-packages] [Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
Even after rebooting with the drive for the zpool physically removed from the system, I still had a zpool I couldn't destroy, export, or otherwise remove from the listing. Using "sudo zpool status -Pv" I worked out that my ZFS was actually expecting to find the data on partition 1 of the drive: errors: No known data errors pool: hub state: UNAVAIL status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://zfsonlinux.org/msg/ZFS-8000-5E scan: none requested config: NAME STATE READ WRITE CKSUM hub UNAVAIL 0 0 0 insufficient replicas /dev/disk/by-id/ata-ST6000DM003-2CY186_ZF200PC8-part1 UNAVAIL 0 0 0 I'd previously tried symlinking the old device name to the new one, but I was inspired to try it with just the partition: [anovak@octagon ~]$ cd /dev/disk/by-id/ [anovak@octagon by-id]$ sudo ln -s 'usb-Seagate_Backup+_Hub_BK_NA8TQC87-0:0-part1' ata-ST6000DM003-2CY186_ZF200PC8-part1 When I did that, the pool immediately came back online, and I was able to export it to make it go away. Then I managed to import it under a more stable name with "sudo zpool import -a -d /dev/disk/by-partuuid/". I still can't see the drive data in gsmartcontrol, and I still can't spin it down, but at least I can now use it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1774569 Title: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04 Status in gsmartcontrol package in Ubuntu: New Status in hdparm package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Bug description: I recently upgraded from 17.10 to 18.04. After the upgrade, I noticed that my Seagate Backup+ Hub external drive was displaying a series of puzzling symptoms: 1. gsmartcontrol can't get SMART data from the drive. I am pretty sure it used to report SMART data? Here's a log of it not working: [hz] Warning: exit: Command line did not parse. [app] execute_smartctl(): Smartctl binary did not execute cleanly. [app] StorageDevice::execute_device_smartctl(): Smartctl binary did not execute cleanly. [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. [hz] Warning: exit: Some SMART command to the disk failed, or there was a checksum error in a SMART data structure [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. 2. hdparm used to be able to spin down the drive. I had it configured to spin it down after a few minutes of inactivity, in the hdparm config file. Now that no longer happens, and hdparm can't seem to talk to the drive meaningfully at all: [anovak@octagon ~]$ sudo hdparm -I /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA device, with non-removable media Standards: Likely used: 1 Configuration: Logical max current cylinders 0 0 heads 0 0 sectors/track 0 0 -- Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 0 MBytes device size with M = 1000*1000: 0 MBytes cache/buffer size = unknown Capabilities: IORDY not likely Cannot perform double-word IO R/W multiple sector transfer: not supported DMA: not supported PIO: pio0 [anovak@octagon ~]$ sudo hdparm -y /dev/sdb /dev/sdb: issuing standby command SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I think this may be related to https://askubuntu.com/questions/1037997 /upgraded-to-18-04-usb-harddrive-doesn-t-idle-anymore which is someone else having the same problem. 3. The ZFS tools think the drive is hosed: [anovak@octagon
[Kernel-packages] [Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
Nope, my speculation is definitely wrong. The disk shows up in lsscsi: [anovak@octagon ~]$ lsscsi ... [9:0:0:0]diskSeagate Backup+ Hub BK D781 /dev/sdb Also, it shows up in lsusb -t with a "uas" driver. Maybe the problem is the uas driver itself? Here's the full description of the USB device, if that helps: [anovak@octagon ~]$ sudo lsusb -v -d 0bc2:ab38 Bus 001 Device 008: ID 0bc2:ab38 Seagate RSS LLC Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0bc2 Seagate RSS LLC idProduct 0xab38 bcdDevice1.00 iManufacturer 2 Seagate iProduct3 Backup+ Hub BK iSerial 1 NA8TQC87 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 85 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 4 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 98 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Data-in pipe (0x03) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Data-out pipe (0x04) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Status pipe (0x02) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Command pipe (0x01) Binary Object Store Descriptor: bLength 5 bDescriptorType15 wTotalLength 22 bNumDeviceCaps 2 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType16 bDevCapabilityType 2 bmAttributes 0xf41e Link Power Management (LPM) Supported SuperSpeed USB Device Capability: bLength10 bDescriptorType16 bDevCapabilityType 3 bmAttributes 0x00 wSpeedsSupported 0x000e Device can operate at Full Speed (12Mbps) Device can operate at High Speed (480Mbps) Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 1 Lowest fully-functional device speed is Full
