Bug 1731915 - Regression: System suspension, Bluetooth and touch screen do not work on >=5.1; Thinkpad X395
Summary: Regression: System suspension, Bluetooth and touch screen do not work on >=5....
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 30
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-22 11:37 UTC by Carmen Bianca Bakker
Modified: 2020-08-11 18:01 UTC (History)
19 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-03 16:39:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
5.1.18 kernel dmesg (104.42 KB, text/plain)
2019-07-22 11:37 UTC, Carmen Bianca Bakker
no flags Details
output of `inxi -z -v7` (6.22 KB, text/plain)
2019-07-22 11:39 UTC, Carmen Bianca Bakker
no flags Details
5.3.0 kernel dmesg (157.71 KB, text/plain)
2019-07-22 11:52 UTC, Carmen Bianca Bakker
no flags Details
5.1.16 Tumbleweed dmesg (288.01 KB, text/plain)
2019-07-22 14:11 UTC, Carmen Bianca Bakker
no flags Details
5.0.9 kernel dmesg (98.44 KB, text/plain)
2019-07-22 14:36 UTC, Carmen Bianca Bakker
no flags Details
5.2.9 dmesg with suspend bug occuring (532.83 KB, text/plain)
2019-08-28 11:57 UTC, Michael Pobega
no flags Details
5.3.2 kernel (F31) dmesg (3.46 MB, text/plain)
2019-10-06 13:24 UTC, Carmen Bianca Bakker
no flags Details
5.5.0-0.rc5.git0.1 kernel dmesg (943.54 KB, text/plain)
2020-01-15 01:20 UTC, Carmen Bianca Bakker
no flags Details

Description Carmen Bianca Bakker 2019-07-22 11:37:48 UTC
Created attachment 1592573 [details]
5.1.18 kernel dmesg

1. Please describe the problem:

On the latest version of Fedora Workstation 30, system suspension, Bluetooth, and touch screen do not work on a Thinkpad X395.

"Do not work" is defined for each component as such:

- System suspension: When typing `systemctl suspend`, the system tries to suspend. The screen turns off, and the system immediately resumes. You need to hit the power button a few times before the screen will come back on.

- Bluetooth: When opening Bluetooth in GNOME Settings, no Bluetooth devices are discovered, and it is impossible to connect to Bluetooth devices that are already paired. Strangely, Bluetooth works *sometimes*, but not reliably.

- Touch screen: When touching anywhere on the screen, nothing happens.


2. What is the Version-Release number of the kernel:

Output of `uname -a`:

Linux thinkpad-x395 5.1.18-300.fc30.x86_64 #1 SMP Mon Jul 15 15:42:34 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

On Fedora 30 + kernel 5.0.9, Bluetooth and the touch screen work reliably. Suspension does not. Booting takes extremely long on this kernel (3 minutes), while systemd waits on the following messages:

- "udev Wait for Complete Device Initialization"

- "Initialize the iWARP/InfiniBand/RDMA stack in the kernel"

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

The steps to reproduce the issue are described above.


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

The problems also occur with the latest 5.2 kernel.


6. Are you running any modules that not shipped with directly Fedora's kernel?:

No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Carmen Bianca Bakker 2019-07-22 11:39:39 UTC
Created attachment 1592575 [details]
output of `inxi -z -v7`

This is a list of the system's internal components.

Comment 2 Carmen Bianca Bakker 2019-07-22 11:42:21 UTC
As an additional comment, because the default format didn't ask this question: The three named components (suspension, Bluetooth, touch screen) work as expected on a live USB of Ubuntu 19.04, which has kernel 5.0.something.

Comment 3 Carmen Bianca Bakker 2019-07-22 11:52:10 UTC
Created attachment 1592577 [details]
5.3.0 kernel dmesg

Comment 4 Carmen Bianca Bakker 2019-07-22 14:11:41 UTC
Created attachment 1592602 [details]
5.1.16 Tumbleweed dmesg

I tested a distribution with a >=5.1 kernel to see if the issue also exists there. I chose `openSUSE-Tumbleweed-GNOME-Live-x86_64-Snapshot20190718-Media.iso`. The live session was incredibly and inexplicably sluggish, but Bluetooth and the touch screen both appeared to work. System suspension did not work. I attached the output of `sudo journalctl`.

Comment 5 Carmen Bianca Bakker 2019-07-22 14:36:49 UTC
Created attachment 1592606 [details]
5.0.9 kernel dmesg

Here's the dmesg log for 5.0.9. Bluetooth and touch screen work, but suspension is broken (and the computer won't resume from suspension).

Comment 6 Justin M. Forbes 2019-08-20 17:42:41 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs.

Fedora 30 has now been rebased to 5.2.9-200.fc30.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31.

If you experience different issues, please open a new bug report for those.

Comment 7 Carmen Bianca Bakker 2019-08-21 09:37:51 UTC
Issue persists on Kernel 5.2.8 on Fedora 30.

Comment 8 Carmen Bianca Bakker 2019-08-28 08:12:47 UTC
Workaround:

Using the rawhide kernel (5.3.0-0.rc5.git2.1.fc32.x86_64) and a udev rules file, everything appears to work smoothly. I placed `80-intel9260-btusb.rules` in /etc/udev/rules.d, with the following contents:

# Disable wakeup on Intel 9260 bluetooth to allow suspend/resume
SUBSYSTEM=="usb" ATTR{idVendor}=="8087", ATTR{idProduct}=="0025" \
	SUBSYSTEMS=="usb" DRIVERS=="usb" \
	ATTR{power/wakeup}="disabled"

This was found by running `cat /sys/bus/usb/devices/*/power/wakeup` as suggested here: https://old.reddit.com/r/thinkpad/comments/cveeyl/linux_on_t495t495sx395_suspendresume_fix/

Comment 9 Michael Pobega 2019-08-28 11:57:29 UTC
Created attachment 1608994 [details]
5.2.9 dmesg with suspend bug occuring

I've attached the dmesg from my machine, you can see everything after the "PM: suspend entry" at 05:31:38 is caused by the bug.

Comment 10 Carmen Bianca Bakker 2019-10-06 13:23:53 UTC
The workaround works well for Bluetooth and touch screen, but the machine still (occasionally) hangs trying to suspend. Found an upstream report at https://bugzilla.kernel.org/show_bug.cgi?id=204611

Attaching journalctl output for Fedora 31, kernel 5.3.2.

Comment 11 Carmen Bianca Bakker 2019-10-06 13:24:49 UTC
Created attachment 1622913 [details]
5.3.2 kernel (F31) dmesg

Comment 12 Carmen Bianca Bakker 2020-01-15 01:20:12 UTC
Created attachment 1652342 [details]
5.5.0-0.rc5.git0.1 kernel dmesg

System suspension reliably works since one of the kernel 5.4 updates. Bluetooth and touch screen sometimes fail after a while. Look for "xHCI host controller not responding, assume dead" in the attached logs. I cannot reliably trigger the failure of Bluetooth and touch screen. They always fail together.

Comment 13 Justin M. Forbes 2020-03-03 16:36:47 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs.

Fedora 30 has now been rebased to 5.5.7-100.fc30.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31.

If you experience different issues, please open a new bug report for those.

Comment 14 Carmen Bianca Bakker 2020-03-03 16:39:05 UTC
Problem resolved with kernel 5.5.x in Fedora 31.

Comment 15 Pyae Phyo Khine 2020-08-11 18:01:03 UTC
Please Help me.
I am facing "not play 4K .ts file and Dolby Sound System" and "power consumption is more use than windows OS" in Fedora 32.


Note You need to log in before you can comment on or make changes to this bug.