Confirmed this happens under xen, not under native hardware or vmware.
Reproduced on various xen hosts with both i686-pae and amd64 kernels in
DomU.
On a side note: DomU doesn't come back up on a restart, it seems like
it's destroyed and not recreated. Seems like this too was introduced
with linux 3.0.0-1, perhaps a separate bug should be filed?
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e46cdcf.9000...@gedalya.net
