| - chomwitt (QUIT: Ping timeout: 260 seconds) (~chomwitt@athedsl-351954.home.otenet.gr) | 02:01 | |
| - mtm (QUIT: Ping timeout: 260 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 02:04 | |
| + bkeys1 (~Thunderbi@c-67-191-106-248.hsd1.fl.comcast.net) | 02:37 | |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 04:10 | |
| - bkeys1 (QUIT: Ping timeout: 268 seconds) (~Thunderbi@c-67-191-106-248.hsd1.fl.comcast.net) | 04:25 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 04:29 | |
| + chomwitt (~chomwitt@2a02:587:dc0c:c200:442:40c1:9d7f:23d1) | 08:22 | |
| - qwer (QUIT: Ping timeout: 268 seconds) (~qwer@37-48-42-176.nat.epc.tmcz.cz) | 08:52 | |
| + qwer (~qwer@37-48-42-176.nat.epc.tmcz.cz) | 08:53 | |
| - qwer (QUIT: Ping timeout: 265 seconds) (~qwer@37-48-42-176.nat.epc.tmcz.cz) | 09:06 | |
| + qwer (~qwer@37-48-25-45.nat.epc.tmcz.cz) | 09:24 | |
| - qwer (QUIT: Ping timeout: 252 seconds) (~qwer@37-48-25-45.nat.epc.tmcz.cz) | 09:34 | |
| + qwer (~qwer@78-80-105-103.customers.tmcz.cz) | 09:54 | |
| - qwer (QUIT: Ping timeout: 252 seconds) (~qwer@78-80-105-103.customers.tmcz.cz) | 11:33 | |
| + qwer (~qwer@78-80-123-210.customers.tmcz.cz) | 11:54 | |
| - qwer (QUIT: Ping timeout: 265 seconds) (~qwer@78-80-123-210.customers.tmcz.cz) | 11:59 | |
| - chomwitt (QUIT: Ping timeout: 264 seconds) (~chomwitt@2a02:587:dc0c:c200:442:40c1:9d7f:23d1) | 11:59 | |
| + chomwitt (~chomwitt@2a02:587:dc0c:c200:9b5d:e3:b4f7:170c) | 12:39 | |
| - mtm (QUIT: Ping timeout: 268 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 14:04 | |
| minute | sigrid: love it! | 14:55 |
|---|---|---|
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 16:09 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 17:14 | |
| - vagrantc (QUIT: Ping timeout: 246 seconds) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 17:58 | |
| + vagrantc (~vagrant@97-120-22-213.ptld.qwest.net) | 18:02 | |
| josch | vkoskiv: is this what you are seeing after suspend: | 21:27 |
| josch | [ 3560.478661] nvme nvme0: Identify Controller failed (-4) | 21:27 |
| josch | [ 3560.483940] nvme nvme0: Removing after probe failure status: -5 | 21:27 |
| josch | [ 3560.518587] nvme0n1: detected capacity change from 1953525168 to 0 | 21:27 |
| josch | [ 3560.518671] EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 53477388 starting block 4097144) | 21:27 |
| josch | [ 3560.535988] EXT4-fs warning (device dm-2): ext4_end_bio:343: I/O error 10 writing to inode 9964422 starting block 39878656) | 21:27 |
| josch | [ 3560.536046] Buffer I/O error on device dm-2, logical block 4097144 | 21:27 |
| josch | just before suspending, the kernel log said: | 21:28 |
| josch | [ 3499.205647] nvme 0001:01:00.0: Unable to change power state from D3hot to D0, device inaccessible | 21:28 |
| josch | I got a WD Blue SN550 | 21:30 |
| vkoskiv | josch: Yeah, something like that. the first error is the QID <n> timeout, disabling controller | 21:30 |
| vkoskiv | The rest are exactly as yours there | 21:30 |
| josch | Ah, right, I got that one too: | 21:30 |
| josch | [ 3560.442616] nvme nvme0: I/O 26 QID 0 timeout, disable controller | 21:30 |
| vkoskiv | Did you find a solution to that? | 21:31 |
| vkoskiv | The fundamental issue when waking is: nvme 0001:01:00.0: Unable to change power state from D3hot to D0, device inaccessible | 21:31 |
| vkoskiv | (I think) | 21:32 |
| vkoskiv | That shows up when waking up, and the rest of the errors happen after, when the system tries writing to the disk | 21:32 |
| josch | I have no solution. | 21:32 |
| vkoskiv | :( | 21:33 |
| vkoskiv | Don't know if the store accepts returns on SSDs | 21:33 |
| vkoskiv | Makes it hard to daily this thing again if I can't suspend and resume | 21:33 |
| josch | Suspend always failed for me so I haven't tried for a long time. | 21:34 |
| josch | Now I tried again and it woke up and then this happened. :( | 21:34 |
| vkoskiv | Yeah. I could go back to my Intel SSD that only freezes occasionally. | 21:34 |
| vkoskiv | That one did fine when resuming from suspend | 21:34 |
| josch | I wonder if this is a new problem. Reading https://community.mnt.re/t/confirmed-working-nvme-drives/224 it seems like at least five people have a WD blue. | 21:36 |
| sigrid | does that need a solution? | 21:37 |
| sigrid | does it make the system not work? | 21:37 |
| josch | sigrid: it makes resume from suspend not work | 21:37 |
| vkoskiv | I did someone somewhere in a post mention that it might be a recent 5.19 regression | 21:37 |
| sigrid | ok, i tried 550 resume and it works fine | 21:38 |
| sigrid | i only have this power state warning | 21:38 |
| vkoskiv | I had a brief period of excitement that I might be able to file a kernel patch that applies a quirk to this model of device to disable the deepest power states | 21:38 |
| josch | sigrid: with linux 5.19? | 21:38 |
| sigrid | no | 21:38 |
| vkoskiv | But disabling the power state thing entirely did't help | 21:38 |
| sigrid | 5.18 | 21:39 |
| vkoskiv | I have the SN570 | 21:39 |
| vkoskiv | (I don't know what the difference is) | 21:39 |
| josch | phew... i do not have time to bisect the kernel these days... :( | 21:39 |
| vkoskiv | I don't remember how to compile and install a test kernel even | 21:39 |
| vkoskiv | I could try adding that quirk anyway to see if it would resolve the issue. | 21:39 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!