> > > Didn't you just tried vmware ;) I've got similar messages at
> > > initialisation time of vmware too.
> > Now that you speak of it, yes, I was using VMware at the time. But what I
> > really wanted to know if those messages are dangerous to Linux.
> There is no point reporting Linux bugs with stuff like vmware loaded. If you
> can't duplicate the problem -without- vmware loaded (this goes for any
> other binary only Xserver/module) then report the problem to whoever wrote.
> it - in this case vmware tech support.
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to email@example.com
> Please read the FAQ at http://www.tux.org/lkml/
Just like to point out that the source to the vmware kernel modules is availble
along with a diff for the X server. Not binary only :).
While I'm mailing the list, Daylight saving's time just came about. Linux
automatically updated the time (or perhaps a daemon I'm unaware of), however
when I rebooted the time went back an hour (e.g. the system clock wasn't
changed). This happened on both of my Linux boxes. When I used date --set to
set the time, the time went back an hour when I rebooted (both boxes). My
question is, is this a date problem, a Linux problem, or a BIOS problem?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/