You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

I have a different experience. My 3.10 kernel crashes horribly as a VirtualBox (ver 4.2.16) guest (host is Windows 8) unless I turn off both pre-emption and dynamic tick. Looks like the OP's 3.10 crashes as a VirtualBox host, instead.

I'm running current with 3.10.5 kernel as a guest OS, with guest additions installed, under virtualbox 4.2.16 r86992 with windows 7 ultimate as the host OS. I've not experience one issue with it. Runs flawlessly. I'm using the generic kernel too.

Same problem here!
I finally got it fixed by blacklisting module 'mei-me'

Code:

john@linux:~$ cat /etc/modprobe.d/BLACKLIST-mei.conf
# Do not load the kernel mei modules, since they interfere with S3
blacklist mei-me

Can't take credit as I got the recommendation from fearless leader PV
...
Sorry! Should have included that my problem also include a flood of the lines below in syslog. However the last line of my and your kernel dump are identical.

Thanks for pointing out the details about your syslog. I looked under /var/log/ and it turns out syslog's size has ballooned to 522MB in the past 2-3 days with millions of lines similar to the ones you posted above.
I just blacklisted mei-me as I had a second crash earlier today, will see how this goes.

I'd suggest to temporarily disable/remove all non-stock kernel modules like virtualbox's or graphics adapter's and try if it would cause better stability. If you are running machine with an integrated Intel GA using the messy i915 driver you are probably out of luck as there were wild changes in recent past fixing various longstanding issues but bringing new ones. Some of the crap is fixed in 3.11.x but diffs cann't be applied to 3.10.x and devs are currently too busy/lazy/incompetent to backport them

The desktop is running the stock Slackware kernel and modules + VirtualBox as a host. If blacklisting module mei-me doesn't do it then I'd rather revert the kernel (3.2.x through 3.9.x have all been rock solid on that pc).

I'm monitoring another machine, a laptop with Intel HD 3000, running the same kernel (no issues so far).
Both machines seem to use the i915 driver, the desktop has an integrated Intel Graphics Media Accelerator, not sure if this is a different chip than the laptop's HD 3000 but so far the laptop has been very stable.

Using a "stock" slackware-current, without binary blobs, nor virtualbox... my hardware is a sony vaio VPCEC4C5E with a radeon card.

This is the first time in... I don't know, 5+ years... then 2 times in 2 days... the first time I didn't notice, the second one I noticed the same "Worqueue: events mei_timer [mei]" present in the screen shot of the first message...

I know stats aren't the full story, and severity of bugs is just as if not more important than quantity, but does anyone else find the following somewhat scary on something that is supposed to be "stable"?