"Les Kitchen" <[email protected]> writes: > 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.
The battery appears to be fine. So far. I haven't tested it by draining it again, but the estimated battery time left appeared to be reasonable. And I was using for about an hour on battery today. The computer was plugged into mains at the time errors happened. > 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. :-)] Yes, seems like nothing to do now, unless it happens again. I have a number of crazy theories, but no evidence. Other crazy theories, of which I am extremely skeptical: * Maybe first charge to 100% after battery dead flat consumes more power or something. * Maybe something weird about the power adaptor I was using. This adaptor eems to be fine now though, even through entire suspend/resume cycle while battery is charging. -- Brian May @ Linux Penguins _______________________________________________ luv-main mailing list -- [email protected] To unsubscribe send an email to [email protected]
