LinuxQuestions.org - [SOLVED] 3.10.5 kernel unstable?

Page 2 of 4

Show 50 post(s) from this thread on one page

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - 3.10.5 kernel unstable? (https://www.linuxquestions.org/questions/slackware-14/3-10-5-kernel-unstable-4175472734/)

astrogeek

08-09-2013 07:15 PM

Another testimonial... 3.10.5 is running here without issues on Phenom II/Nvidia.

guanx

08-09-2013 07:50 PM

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.

bassplayer69

08-09-2013 08:45 PM

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.

dr.s	08-11-2013 08:12 PM

Quote:

Originally Posted by AlleyTrotter (Post 5006248)

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.

Code:

Aug  3 09:57:55 linux kernel: [ 1172.798841] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING

Aug  3 09:57:55 linux kernel: [ 1172.799750] mei_me 0000:00:16.0: reset: wrong host start response

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.

dr.s	08-11-2013 08:14 PM

Quote:

Originally Posted by danielldaniell (Post 5006086)

This happens for me also, on a Dell Inspiron 5110. It would help if your image would be a bit more clear...

Shaky hands, and forgot to turn off the flash :D but the lines look almost identical to the ones in the image you posted.

dr.s	08-11-2013 08:28 PM

Quote:

Originally Posted by guanx (Post 5006605)

...Looks like the OP's 3.10 crashes as a VirtualBox host, instead.

Yes the crash occurs on a desktop running Slack current with 3.10.5 and is a VirtualBox host, not a guest.

dr.s	08-11-2013 08:37 PM

Quote:

Originally Posted by dunric (Post 5006181)

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.

_ZeD_

08-13-2013 11:47 PM

sigh.

I too had the same kernel crash.

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...

guanx

08-14-2013 08:07 AM

Does it crash with 3.10.6?

GazL	08-15-2013 04:39 AM

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"?

Code:

3.10.1:  25 files changed,  108 insertions(+),  57 deletions(-)

3.10.2:  84 files changed,  675 insertions(+), 235 deletions(-)

3.10.3: 100 files changed, 1113 insertions(+), 411 deletions(-)

3.10.4:  77 files changed,  839 insertions(+), 437 deletions(-)

3.10.5: 111 files changed, 1120 insertions(+), 697 deletions(-)

3.10.6: 115 files changed, 1183 insertions(+), 753 deletions(-)

3.10.7:  74 files changed,  633 insertions(+), 390 deletions(-)

On the plus side 3.10.7 ought to be much better than 3.10.0 was after that little lot, but how bad must 3.10.0 have been to need all that!

hitest

08-15-2013 08:06 AM

Maybe you folks will have better luck with 3.10.6.

Code:

Thu Aug 15 03:46:12 UTC 2013

a/dialog-1.2_20130523-i486-1.txz:  Upgraded.

a/kernel-generic-smp-3.10.6_smp-i686-1.txz:  Upgraded.

a/kernel-generic-3.10.6-i486-1.txz:  Upgraded.

a/kernel-huge-smp-3.10.6_smp-i686-1.txz:  Upgraded.

a/kernel-huge-3.10.6-i486-1.txz:  Upgraded.

a/kernel-modules-smp-3.10.6_smp-i686-1.txz:  Upgraded.

a/kernel-modules-3.10.6-i486-1.txz:  Upgraded.

d/kernel-headers-3.10.6_smp-x86-1.txz:  Upgraded.

k/kernel-source-3.10.6_smp-noarch-1.txz:  Upgraded.

astrogeek

08-15-2013 05:39 PM

Quote:

Originally Posted by hitest (Post 5009725)

Maybe you folks will have better luck with 3.10.6.

Code:

Thu Aug 15 03:46:12 UTC 2013

a/dialog-1.2_20130523-i486-1.txz:  Upgraded.

a/kernel-generic-smp-3.10.6_smp-i686-1.txz:  Upgraded.

a/kernel-generic-3.10.6-i486-1.txz:  Upgraded.

a/kernel-huge-smp-3.10.6_smp-i686-1.txz:  Upgraded.

a/kernel-huge-3.10.6-i486-1.txz:  Upgraded.

a/kernel-modules-smp-3.10.6_smp-i686-1.txz:  Upgraded.

a/kernel-modules-3.10.6-i486-1.txz:  Upgraded.

d/kernel-headers-3.10.6_smp-x86-1.txz:  Upgraded.

k/kernel-source-3.10.6_smp-noarch-1.txz:  Upgraded.

Or 3.10.7...

Code:

Thu Aug 15 21:23:13 UTC 2013

a/bash-4.2.045-i486-1.txz:  Upgraded.

a/kernel-generic-3.10.7-i486-1.txz:  Upgraded.

a/kernel-generic-smp-3.10.7_smp-i686-1.txz:  Upgraded.

a/kernel-huge-3.10.7-i486-1.txz:  Upgraded.

a/kernel-huge-smp-3.10.7_smp-i686-1.txz:  Upgraded.

a/kernel-modules-3.10.7-i486-1.txz:  Upgraded.

a/kernel-modules-smp-3.10.7_smp-i686-1.txz:  Upgraded.

d/kernel-headers-3.10.7_smp-x86-1.txz:  Upgraded.

k/kernel-source-3.10.7_smp-noarch-1.txz:  Upgraded.

extra/bash-completion/bash-completion-2.1-noarch-1.txz:  Upgraded.

extra/linux-3.10.7-nosmp-sdk/*:  Upgraded.

isolinux/initrd.img:  Rebuilt.

kernels/*:  Upgraded.

usb-and-pxe-installers/usbboot.img:  Rebuilt.

hitest

08-15-2013 06:10 PM

Quote:

Originally Posted by astrogeek (Post 5010038)

Or 3.10.7...

Code:

Thu Aug 15 21:23:13 UTC 2013

a/bash-4.2.045-i486-1.txz:  Upgraded.

a/kernel-generic-3.10.7-i486-1.txz:  Upgraded.

a/kernel-generic-smp-3.10.7_smp-i686-1.txz:  Upgraded.

a/kernel-huge-3.10.7-i486-1.txz:  Upgraded.

a/kernel-huge-smp-3.10.7_smp-i686-1.txz:  Upgraded.

a/kernel-modules-3.10.7-i486-1.txz:  Upgraded.

a/kernel-modules-smp-3.10.7_smp-i686-1.txz:  Upgraded.

d/kernel-headers-3.10.7_smp-x86-1.txz:  Upgraded.

k/kernel-source-3.10.7_smp-noarch-1.txz:  Upgraded.

extra/bash-completion/bash-completion-2.1-noarch-1.txz:  Upgraded.

extra/linux-3.10.7-nosmp-sdk/*:  Upgraded.

isolinux/initrd.img:  Rebuilt.

kernels/*:  Upgraded.

usb-and-pxe-installers/usbboot.img:  Rebuilt.

Just upgraded. Running well here. :)

Code:

Linux odin 3.10.7-smp #2 SMP Thu Aug 15 05:32:49 CDT 2013 i686 Intel(R) Pentium(R) D CPU 3.20GHz GenuineIntel GNU/Linux

zakame

08-16-2013 12:18 PM

Kernels 3.10.5 to 3.10.7 are not resuming from suspend on my personal ThinkPad X200, while it runs fine on my work's T420. Seems to be an issue on Core 2 Duo ThinkPads: https://bugzilla.redhat.com/show_bug.cgi?id=989373

sardinha

08-16-2013 12:56 PM

interesting news

Not only the 3.10.x series was being marked as LTS but will have too the new features of 3.11 and 3.12.

http://www.linuxfoundation.org/news-...ether-ltsi-310

All times are GMT -5. The time now is 08:27 AM.

Page 2 of 4

Show 50 post(s) from this thread on one page