On May 2, 2018, at 9:14 AM, Frantisek Zatloukal <fzatl...@redhat.com> wrote:
Hans, can't this be affected also by different disk vendors (drive vendor in Lenovo laptop can vary even in same model) and different firmware of disks? Also, drive FW is upgradeable in Lenovo laptops. On Wed, May 2, 2018 at 5:39 PM, Hans de Goede <hdego...@redhat.com> wrote: > Hi, > > > On 05/01/2018 10:40 AM, Lorenzo Dalrio wrote: > >> Hi, >> i run fedora 28 on a t450 since it was promoted to beta working with it >> 8-10 hours per day without any issue. >> >> System Information >> Manufacturer: LENOVO >> Product Name: 20BUS003IX >> Version: ThinkPad T450 >> >> # cat /sys/class/scsi_host/host*/link_power_management_policy >> med_power_with_dipm >> med_power_with_dipm >> med_power_with_dipm >> >> === START OF INFORMATION SECTION === >> Model Family: SanDisk based SSDs >> Device Model: SanDisk SD7UB3Q256G1001 >> Serial Number: 153446402316 >> LU WWN Device Id: 5 001b44 ec5b3450c >> Firmware Version: X2240501 >> User Capacity: 256,060,514,304 bytes [256 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 T13/2015-D revision 3 >> SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s) >> Local Time is: Tue May 1 08:39:01 2018 UTC >> SMART support is: Available - device has SMART capability. >> SMART support is: Enabled >> > > Ok, so it seems that not everyone is affected, thank you for the > info. > > Can you do: > > cat /sys/class/dmi/id/bios_version /sys/class/dmi/id/bios_date > > And let me know the output. Also related to this have you > updated your BIOS recently / are you in the habbit > of tracking BIOS updates? I'm wondering if this is BIOS > version related. I’m going to go out on a limb and suggest that the problem might be with power management, not with SATA per se. On a modern Intel system, an NVMe device that hasn’t internally gone to sleep will prevent the PCIe link from going into an ASPM sleep state, and that, in turn, will keep the whole system from going into a deep PCn state. I could easily believe that there’s a bug where nasty ACPI things like brightness hotkeys go terribly wrong in deep PC states. I would also believe that the lack of SATA LPM will also block deep PC states. And I’d believe that the laptop has an electrical problem that only affects Linux for mysterious reasons. As an experiment, could some affected users try running ‘while true; do true; done” or otherwise pinning a CPU at 100% and seeing if the problem goes away?
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/JIWZE2WQSTN4YZAXNZ76UPNH4SJN4FXF/
