Hello Friends: =============================== The problem, in bullet form: =============================== - Lenovo Y700 Laptop ( http://lnv.gy/2GKQSZT ) - Running Fedora-26/x86_64bit - The disk partition is split between Windows-10 and Fedora-26. When booted into Windows-10, the issue below (which I'm about to describe) doesn't happen at all. ============================== PROBLEM: ============================== Randomly, the system stops respond to the laptop's KEYBOARD and TRACKPAD input. Note that the display is NOT touch-enabled. The Fedora-26 O/S still, itself, remains functional because I can (1) see activity on the screen (like a new web email arriving), and (2) can also ssh(1) into the laptop and do whatever; for example kill processes. Speaking of which, I try killing various processes while ssh(1)ed into the laptop, including Xorg, but nothing restores KEYBOARD and TRACKPAD responsiveness. Also, the quick PRESS/RELEASE action of the laptop Power Button also becomes unresponsive when this happens. Doing that is supposed to initiate a graceful O/S shutdown and power off, but it doesn't respond to that quick PRESS/RELEASE. So the only thing left to do, is PRESS/HOLD for a hard power off. Another oddity during this situation is that, when -- from a remote ssh(1) session -- I reboot the Y700 laptop (e.g. root@y700# init 6), it gets to the BIOS but then hangs there forever, never completing the reboot. So the only way to get out of this situation, is to hard power off the laptop. That even a reboot/init 6 can't complete means that something about the O/S and hardware interaction has becomes hosed. In summary, all of the above things stop working when this state is reached -- again it happens randomly and about once per day. (._.) Again, when booted into Windows 10, none of this happens. I've done "dnf -y update" many times, hoping that this will stop happening, but the problem persists across all updates . Any ideas? Thank you in advance! =:)
I forgot to mention that closing the laptop lid -- which is configured to put the O/S to sleep -- also stops responding when this happens. Meaning the laptop stays on after closing the lid. In sum, it appears that the Kernel loses the ability to process laptop Keyboard, Trackpad and Lid interrupts/events. I suspect this happens with other Lenovo models, too.
I suspect it may be the ideapad_laptop driver, since this problem arises when I'm using the trackpad (not when typing the keyboard). Anyone seeing this bug and this thread? Help please.
(In reply to prismalytics from comment #2) > I suspect it may be the ideapad_laptop driver, since this problem arises > when I'm using the trackpad (not when typing the keyboard). > > Anyone seeing this bug and this thread? Help please. I have the same laptop, and I have disabled the ideapad_laptop driver a long time ago as a proposed solution to broken wifi, and I do not have this issue that you're describing. You may be right.
Thank you Basil for your feedback. Since my post above, I disabled that driver, too. Sadly, the problem still came back. The only difference between when Windows-10 is running and when Fedora-27 is running (
Thank you Basil for your feedback. Since my Comment-2 post above, I had disabled the ideapad_laptop driver. Sadly, the problem still came back. I also upgraded from FC-26 to FC-27 and updated this ticket. That didn't resolve my issue. The only difference between when WINDOWS-10 is running and when FEDORA-27 is running, is that each uses a different physical boot disk. Fedora uses a "Samsung SSD 850 PRO 512GB" disk, with details shown below. However, as mentioned, when the freeze issue arises the machine is still functional. I can SSH into it and all works fine. So I don't this disk a the problem, but I'm documenting it here just in case. Disk details next: user@y700$ sudo smartctl -a /dev/sdb1 smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.15.6-300.fc27.x86_64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Samsung based SSDs Device Model: Samsung SSD 850 PRO 512GB Serial Number: S39FNX0J552798E LU WWN Device Id: 5 002538 d41feee31 Firmware Version: EXM04B6Q User Capacity: 512,110,190,592 bytes [512 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4c SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Mar 12 00:07:22 2018 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x53) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 265) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 1 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1534 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 717 177 Wear_Leveling_Count 0x0013 099 099 000 Pre-fail Always - 5 179 Used_Rsvd_Blk_Cnt_Tot 0x0013 100 100 010 Pre-fail Always - 0 181 Program_Fail_Cnt_Total 0x0032 100 100 010 Old_age Always - 0 182 Erase_Fail_Count_Total 0x0032 100 100 010 Old_age Always - 0 183 Runtime_Bad_Block 0x0013 100 100 010 Pre-fail Always - 0 187 Uncorrectable_Error_Cnt 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0032 068 056 000 Old_age Always - 32 195 ECC_Error_Rate 0x001a 200 200 000 Old_age Always - 0 199 CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 235 POR_Recovery_Count 0x0012 099 099 000 Old_age Always - 62 241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 2213706520 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing 255 0 65535 Read_scanning was never started Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
Any help? What would make Fedora (25, 26, and now 27, including any kernel) suddenly stop responding to the laptop ENCLOSURE (trackpad, keyboard, laptop lid close), yet still ssh-able to? I need help. This has been going on for a long time now. What diagnostics can I get when this happens, since I can still ssh in? Nothing that I see pops out at me. Remember that this is an Optimus laptop... Hybrid with nVidia card and onboard Intel graphics, in case that helps. But again, what would make Fedora suddenly stop responding to the laptop ENCLOSURE (trackpad, keyboard, laptop lid close)? Please Help.
Created attachment 1412828 [details] Logs of: this morning I suspended, this afternoon I woke it up, it failed, I suspended it again with the power button, it failed again, I powered it off the bad way Hi there, I'm affected too. My laptop is Asus F550ZE. My symptoms are: 1. Recover from suspend/hibernate. You can even recover by pressing any laptop keyobard key. 2. Sometimes it will not recognize the laptop and touchpad. 3. Only workaround is to power off and power on again. If I use the laptop's poweroff button to suspend the computer, I can still boot it back on just by pressing any key, but then the keys are recognized no more. I'm attaching all maybe-related logs.
Hello... I updated my BIOS, and so far that seems to have resolved my issue. I wasn't aware that an update existed until I checked. I will update this bug if it should resurface. @Yajo try updating your BIOS if one is available. Maybe that will help your situation.
Mine has last update already installed :/
Created attachment 1450413 [details] logs Today it happened again to me. The good thing is that this time I had a mouse plugged in, so I could still use it to manage the computer. By using the mouse, I clicked on "Log in as another user" (From the password entry gnome lock screen), and got to GDM. There, I could use both laptop keyboard and touchpad. I chose my opened session, entered the password, and when logged in, again keyboard and trackpad were unusable. With the USB mouse, I closed session, and back again in GDM I could use all normally to start a brand new session. All hardware worked then. No reboot needed. This reveals that a good workaround to this issue is to use some external USB input device to log out and in again. It also shows it's not a hardware bug. I attach logs produced in the mean time (I took 5 mins of logs, I hope some of it is useful). Thanks!
*********** 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 27 kernel bugs. Fedora 27 has now been rebased to 4.17.7-100.fc27. 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 28, and are still experiencing this issue, please change the version to Fedora 28. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
Please reopen, I'm on F28 and it's still happening the same. Thanks!
We apologize for the inconvenience. There is 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 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. 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 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
Hello. As mentioned a while back, I was able to resolve this issue with laptop BIOS upgrade. Of course, this does not explain why it started happening after never happening before, so it may well pop up again for others.