I had a look at the e1000e driver and tried a new version of that, so I installed a new version of that. It suspended fine today (in circumstances that have previously caused a problem). I'll run like this for a week before updating the bios. I think its version 2.3.2 in saucy, not sure why it would be so far backlevel, there is also a 2.5.4 stable version.
There are a few power related changes:
* Upstream - commit e60b22c5b7e59db09a7c9490b1e132c7e49ae904 (e1000e: fix accessing to suspended device)
* Upstream - commit 66148babe728f3e00e13c56f6b0ecf325abd80da (e1000e: fix runtime power management transitions)
* Cleanup/refactor - Runtime Power Management flow
* Refactor/fix system hibernate flow
I had a look at the e1000e driver and tried a new version of that, so I installed a new version of that. It suspended fine today (in circumstances that have previously caused a problem). I'll run like this for a week before updating the bios. I think its version 2.3.2 in saucy, not sure why it would be so far backlevel, there is also a 2.5.4 stable version.
jammy@pk0k4dr:~$ sudo ethtool -i eth0
driver: e1000e
version: 2.4.14-NAPI
firmware-version: 0.13-3
There are a few power related changes: 09a7c9490b1e132 c7e49ae904 (e1000e: fix accessing to suspended device) 00e13c56f6b0ecf 325abd80da (e1000e: fix runtime power management transitions)
* Upstream - commit e60b22c5b7e59db
* Upstream - commit 66148babe728f3e
* Cleanup/refactor - Runtime Power Management flow
* Refactor/fix system hibernate flow