-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Chromebook] UFS disk device type "unknown" #753
Comments
It isn't tlp that's spamming the log but a bad kernel commit. It's still unclear though why tlp isn't properly identifying the disk. |
Hi, I have no idea what a "UFS drive" is supposed to be and what type of controller it uses, obviously it's not SATA/AHCI. Please show the output of
|
Here's the output (main and EFI):
|
@micmalti Sorry for the late reply. I'm currently busy with the 1.7 beta. I checked the kernel docs for UFS
but couldn't figure out how UFS pm works. Without having the hardware, I can neither investigate further nor develop or even test anything. Your output shows the controller as PCIe device, so at least runtime pm will be enabled ("auto") on battery power :
|
That's fine by me. It's just a reporting issue then. |
[x] I've read and accepted the Bug Reporting Howto
[x] I've provided all required
tlp-stat
outputs via Gist (see below)Describe the bug
Hi, I've been happily using tlp for 5+ years and never had any issues until I recently switched over to a new laptop. Now, I keep getting this kernel message every 5 seconds at random intervals, both on battery and AC:
sd 0:0:0:0: [sda] Starting disk
From what I understand, a similar message is reported whenever tlp endlessly tries to stop/start the laptop disk, so I checked powertop and confirmed that the
Runtime PM for disk sda
option was marked as 'good'. The recommendation for disabling this option is to uncommentSATA_LINKPWR_DENYLIST="hostX"
, yet when I rantlp-stat -d
to determine the host, it seems as though the disk isn't being recognized by tlp: tlp-statIs this perhaps due to a general lack of support for UFS drives, which this particular model is making use of (SDINFDO4-128G)?
The text was updated successfully, but these errors were encountered: