hi,
Not sure if I'm posting this in the right place or not I have posted in another forum months ago. Any body know how to solve the problem atm?
I got this problem ever since the 13.1 slackware64 release this has been annoying for months the slackware64 installed in a vmware workstation guest machine, the problem is that when the host (real pc) entered sleep while it resumes from sleep the guest vmware workstation running slackware64 13.1 the kernel starts to crash and broadcasting error messages inside the Konsole in every single tabs, here I attach the trace of kernel fault in dmesg.txt I hope it will get fixed next slackware64 release.

cheers,

a bit too much copy & paste, imho. Can't see wood for the trees/ It did look as if gpm was involved. Do you need it?
The way to go at that is to get a core and go at it with gdb. It's talking about soft interrupts a lot. That kernel is rock solid.

I would think that the host couldn't sleep (?)

Wouldn't that (the host sleeping) "remove" the hardware from the guest since the guest gets "virtualized" hardware provided by the host.

If I rode on hardware and my hardware dissappeared on me, I might panic or otherwise at least not have anything to ride.

But maybe they (guest) supposed to go into a "freeze" state and come out of it that I'm not aware of.

--
Alan.

I think you have the correct idea. The errors in the OP's trace indicates that the kernel believes that a block request from a device timed out.

I believe that when the host machine enters sleep mode, you would have to instruct the various VMs running to go into sleep mode first. I have no idea how you would do that.

That stands to reason that a block request from a (hardware) device timed out.

The clock still ticks forward all the while that my bicycle (hardware) had disappeared completely out from under me. (I'm likely to have an oops or otherwise to c r a s h onto the tarmac).

My request cannot return to me for the duration of while the disappeared hardware remains disappeared.

After 5 hours of slept, host wakes up and guest gets the hardware back and the request returns (also from a now 5 hour forwarded) clock. Since timeout is in moments or few minutes -- oh my gosh, 5 hours, we are most definitely timed out -- our hardware must have gone away since this request didn't return for 5 hours. We cannot run without our hardware (bicycle) so (gravity and physics does its thing) we crash to a halt on the tarmac.

Hey, poof, hardware goes, disappears. Hey, poof, hardware comes back, returns (but it's too late, since we timed out, we crash).

Maybe they have a guest kit to make it smart enough to discern but I'm unaware.

I don't, haven't put Linux as guest. I use silly Win as guest with Linux always the host. I never yet had the sleep / crash problem.

Different so called sleep(s) exists too.

As in like it's not always that contents of ram get written to disk so that ram can sleep too.