[Completed post here. There was only a little bit more to write. The moral is, Do not reply while tired.]
On Tue, Sep 17, 2024, at 09:14, Brian May via luv-main wrote: > "Sara Marcondes" <[email protected]> writes: >> Just to give my 2ยข, I'm going to guess it is something to do with ... > Also I have a nagging suspicion: > > Just before this problem started up, the battery got drained to 0. Not > sure if this is because the computer didn't go to sleep correctly when I > thought it had, or if it was because it woke up during sleep. Or maybe > the computer already encountered this issue and I hadn't notice. But the > computer wouldn't turn on for a while, and seemed incredible slow to > start charging (I didn't time it, I probably was slightly on the > impatient side at the time). Eventually it did charge, and I got it back > to 100% charge. And that is when I first had the suspend/resume issues. Just some random thoughts along these lines: When you were having the original trouble with NVMe errors on suspend / resume, was that suspend / resume on battery power or on mains power? It's conceivable that if the battery got damaged somehow by the deep discharge, then it might not have enough juice to bring the machine out of suspend โ or even if you're on mains power, the battery might be drawing enough current to "brown-out" the system, and the NVMe drive might just be the most sensitive component. But if the battery were in bad shape, then you'd be getting much reduced running time on battery, which you haven't mentioned. I've had laptops that wouldn't boot even on mains power (from power brick) with the battery connected, but would boot fine if I physically disconnected the battery โ presumably because the battery was pulling in too much power trying to recharge. Maybe the charging circuitry was broken. A lot depends on the design of your particular machine. Caveats: Some laptops *require* the battery to be in place, and bad things can happen if you try to run off the external power pack without the battery in place. The Pine64 Pinebook Pro is one such. To run it without the battery in place, you have to connect up a special by-pass cable. Most laptops will run fine from external power with the battery disconnected, but it would be wise to check. Maybe there's a repair guide for you on iFixit.com. And if you are opening up your laptop, take the usual precautions against static discharge and short-circuits. What I was going to say is that if it is feasible to disconnect the battery, you could try to see whether the error happens when you're running without the battery connected. Of course, if you're doing suspend-to-RAM, then you'll need to keep power supplied while suspended. But then, from your most recent report, it seems that the problem has more-or-less gone away. So the above is maybe just stuff to keep in mind if it recurs. Maybe the battery's settled a bit in time. Maybe it's a different problem altogether, like configuration as Sara suggested. These things can take a lot of time and work to track down. [Your favorite trouble-shooting story goes here. :-)] One thing I'll add, though: Most systems will report 100% relative to what they think is the current battery capacity. That 100% might be only a fraction of the battery's original capacity. I guess a question is whether you're still getting much the same running time on battery. โ Smiles, Les. _______________________________________________ luv-main mailing list -- [email protected] To unsubscribe send an email to [email protected]
