It seemed that the driver thought all disk activity was done, but the drive still had some stuff in it's internal cache when the machine finished processing the shutdown, and cut the power. The delay fixed that problem
To my understanding that was the reason why SHL added the delay in xwp code. It's another story that this version of xwp source code never found the way to the public until I started uploading betas.
and 4 seconds at shutdown is hardly noticeable. It probably doesn't need to be more than 1 second, but machines are getting faster, and disk caches are getting bigger, so some delay is probably a good thing. Why not use more time than anybody might think is necessary. 200 ms might be enough, most of the time, but so is 1000 ms. 199 ms may not be enough. Who really cares how long it takes to shut down a machine, as long as it gets done right.
This all is a workaround for a problem either not understand or not solved in the right way. I consider workarounds only as second best choice. There must be a proper solution and I've no evidence that Steven ones is not the correct one. I'm happy if you can prove the opposite. But for this you have to -
- use the latest AN ACPI
- and the latest xwp beta
- and the 'apcitool shutdown' has to work reliable
- and xwp shutdown does not
- and xwp shutdown with delay does
If all these things are true then we should discuss the proper value of delay. Otherwise I would suggest Pete to look for a real fix for his problem.
I want to say that I do not post this to offend against someone but only cause I want to fix xwp if it has bugs and make it even more perfect.