LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-09-2013, 01:03 AM   #1
dr.s
Member
 
Registered: Feb 2010
Distribution: Slackware64
Posts: 134

Rep: Reputation: 20
Unhappy 3.10.5 kernel unstable?


Been running Slackware current on this desktop with different kernels, all very stable. I upgraded to the stock 3.10.5 kernel (Aug. 7) then applied the Aug. 8 updates. The system had a complete crash a few hours ago, out of the blue, while I was reading a webpage (only Firefox, Konqueror and Konsole were loaded).

I think this is the first time I've ever seen a total crash on Linux, don't know if it's the latest kernel or a combination of other factors, all I could do was take a snapshot of the screen and do a hard reboot.
Attached Images
File Type: jpg IMAG0016.jpg (284.6 KB, 166 views)
 
Old 08-09-2013, 02:19 AM   #2
danielldaniell
Member
 
Registered: Apr 2009
Location: Hungary
Distribution: Slackware, OpenBSD
Posts: 42

Rep: Reputation: 15
This happens for me also, on a Dell Inspiron 5110. It would help if your image would be a bit more clear, but the last line suggests (drm_kms_helper) that it has something to do with the DRM interface. The same goes for my laptop.

It crashes when playing YouTube videos, and suspend to ram also got broken, it just flashes the caps-lock key, and blanks the screen.
How ironic the Slackware changelog for the update:
"Looks like 3.10.x got LTS status, but more importantly fixes the power issue on resume with some Intel machines.".
 
Old 08-09-2013, 06:16 AM   #3
dunric
Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 457

Rep: Reputation: 68
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
 
Old 08-09-2013, 06:36 AM   #4
danielldaniell
Member
 
Registered: Apr 2009
Location: Hungary
Distribution: Slackware, OpenBSD
Posts: 42

Rep: Reputation: 15
Hey dunric, thanks for the tips. I'll try to remove the vbox drivers, and see if that makes any difference. Also, I've tested 3.11-rc4, but it also panics with the same symptoms.
I've managed to take a picture of the panic, too.
Attached Images
File Type: jpg slackware_3.10.5_kms_panic.jpg (213.3 KB, 68 views)
 
Old 08-09-2013, 08:15 AM   #5
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (3.17.1) UEFI enabled
Posts: 351

Rep: Reputation: 71
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
Of course the configuration of the kernel must include
Code:
CONFIG_INTEL_MEI=m
CONFIG_INTEL_MEI_ME=m
built as modules so's we can blacklist them.
Hope that helps
John

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

Last edited by AlleyTrotter; 08-10-2013 at 03:17 PM.
 
1 members found this post helpful.
Old 08-09-2013, 08:57 AM   #6
danielldaniell
Member
 
Registered: Apr 2009
Location: Hungary
Distribution: Slackware, OpenBSD
Posts: 42

Rep: Reputation: 15
The blacklisting doesn't solve the intermittent panics for me, unfortunatelly.
 
Old 08-09-2013, 09:18 AM   #7
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: linux (slackware-current)
Posts: 52

Rep: Reputation: 15
On my box [intel i7-3632QM quad core with intel HD4000 graphics] no panic problems but ran into this bug when attaching external mass-storage (my phone) via an USB-cable

Quote:
[33775.957272] usb 1-1.2: new full-speed USB device number 9 using ehci-pci
[33776.050735] usb 1-1.2: unable to read config index 0 descriptor/start: -32
[33776.050748] usb 1-1.2: chopping to 0 config(s)
[33776.056111] usb 1-1.2: New USB device found, idVendor=0471, idProduct=1201
[33776.056119] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[33776.056132] usb 1-1.2: Product: SAMSUNG Mobile USB Modem
[33776.056133] usb 1-1.2: Manufacturer: Samsung
[33776.056134] usb 1-1.2: SerialNumber: 000000-00-000000
[33776.056301] usb 1-1.2: no configuration chosen from 0 choices
[33778.338009] usb 1-1.2: USB disconnect, device number 9
[33779.537274] usb 1-1.2: new full-speed USB device number 10 using ehci-pci
[33779.631620] usb 1-1.2: New USB device found, idVendor=04e8, idProduct=675a
[33779.631627] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[33779.631631] usb 1-1.2: Product: SAMSUNG Mobile USB Modem
[33779.631634] usb 1-1.2: Manufacturer: Samsung
[33779.631637] usb 1-1.2: SerialNumber: 000000-00-000000
[33779.633531] usb-storage 1-1.2:2.0: USB Mass Storage device detected
[33779.633689] scsi11 : usb-storage 1-1.2:2.0
[33780.635592] scsi 11:0:0:0: Direct-Access SAMSUNG B2100 0 2.00 PQ: 0 ANSI: 0
[33780.640632] scsi 11:0:0:1: Direct-Access SAMSUNG B2100 1 2.00 PQ: 0 ANSI: 0
[33780.643666] sd 11:0:0:0: [sdc] 15685632 512-byte logical blocks: (8.03 GB/7.47 GiB)
[33780.651830] sd 11:0:0:0: [sdc] Test WP failed, assume Write Enabled
[33780.654840] sd 11:0:0:1: [sdd] 16508 512-byte logical blocks: (8.45 MB/8.06 MiB)
[33780.660970] sd 11:0:0:0: [sdc] Asking for cache data failed
[33780.660973] sd 11:0:0:0: [sdc] Assuming drive cache: write through
[33780.666820] sd 11:0:0:1: [sdd] Test WP failed, assume Write Enabled
[33811.448291] usb 1-1.2: reset full-speed USB device number 10 using ehci-pci
[33811.551675] sd 11:0:0:1: [sdd] Asking for cache data failed
[33811.551679] sd 11:0:0:1: [sdd] Assuming drive cache: write through
[33842.454272] usb 1-1.2: reset full-speed USB device number 10 using ehci-pci
[33873.332232] usb 1-1.2: reset full-speed USB device number 10 using ehci-pci
[33904.338228] usb 1-1.2: reset full-speed USB device number 10 using ehci-pci
[33935.280275] usb 1-1.2: reset full-speed USB device number 10 using ehci-pci
[33966.287082] usb 1-1.2: reset full-speed USB device number 10 using ehci-pci
[33997.292107] usb 1-1.2: reset full-speed USB device number 10 using ehci-pci
[34028.234144] usb 1-1.2: reset full-speed USB device number 10 using ehci-pci
[34028.396849] sd 11:0:0:0: [sdc] Attached SCSI removable disk
[34028.406809] sd 11:0:0:1: [sdd] Attached SCSI removable disk
[34028.419333] sd 11:0:0:0: [sdc] 15685632 512-byte logical blocks: (8.03 GB/7.47 GiB)
[34028.424955] sd 11:0:0:0: [sdc] Test WP failed, assume Write Enabled
[34028.431205] sd 11:0:0:0: [sdc] Asking for cache data failed
[34028.431207] sd 11:0:0:0: [sdc] Assuming drive cache: write through
[34059.176029] usb 1-1.2: reset full-speed USB device number 10 using ehci-pci
......
On an USB3 bus it appeared exactly as a bug reported for 3.10.3:
http://comments.gmane.org/gmane.linux.usb.general/91405

Now I am trying this patch --which did not make it to 3.10.5:
http://marc.info/?l=linux-usb&m=137523956310060&w=2

.....

Ok, recompiled and rebooted..
.....

Yes, with the lines
Quote:
if (sdev->skip_vpd_pages)
goto fail;
added to <path-to-kernel-source>/drivers/scsi/scsi.c as described in the patch-file, my phone is now recognised.

Last edited by brobr; 08-09-2013 at 10:49 AM.
 
Old 08-09-2013, 09:43 AM   #8
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 1,999

Rep: Reputation: Disabled
Quote:
Originally Posted by danielldaniell View Post
The blacklisting doesn't solve the intermittent panics for me, unfortunatelly.
From the screendump it seems the panic is related to the nouveau driver. I can't say I'm surprised, as several previous versions of that driver have caused hard lock-ups on some of my systems.

Have you tried the proprietary Nvidia drivers? The latest version should compile cleanly against a 3.10.5 kernel. Granted, these drivers have a few issues of their own, but that may not affect your particular card/chip.
 
Old 08-09-2013, 09:51 AM   #9
danielldaniell
Member
 
Registered: Apr 2009
Location: Hungary
Distribution: Slackware, OpenBSD
Posts: 42

Rep: Reputation: 15
This laptop has two graphic cards, a discrete NVIDIA and an integrated Intel. I'm turning off the NVIDIA card during boot as soon as I can (via the /sys/kernel/debug/vgaswitcheroo/switch file), and just using the Intel. I don't want to have anything to do with NVIDIA cards, or with its proprietary drivers; if I could, I'd take that video card off of the laptop...
 
Old 08-09-2013, 10:40 AM   #10
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current & "True Multilib." PC-BSD.
Posts: 2,238

Rep: Reputation: 176Reputation: 176
Quote:
Originally Posted by danielldaniell View Post
...I don't want to have anything to do with NVIDIA cards, or with its proprietary drivers; if I could, I'd take that video card off of the laptop...
Sounds like a personal problem. What did they do to you?

The 3.10.5 kernel, xorg 1.14.2, and the Nvidia 325.15 driver are working perfectly on this box (other than the audio volume problem that started after the 3.8.13 kernel).

Last edited by cwizardone; 08-09-2013 at 10:43 AM.
 
Old 08-09-2013, 11:43 AM   #11
dunric
Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 457

Rep: Reputation: 68
Heh, me crashing too. The `mei' module issue is not yet fixed even in the last 3.10.5 kernel.
There are mei init/reset/timeout patches do work for some people. Look innocent, trying myself.

Kernel development has got some twists, also do not remember so many issues or so frequent crashes for the long time. Not only kernel but also other popular software like Firefox or GNOME are getting crippled in the recent past.

Tough decisions for Pat to avoid carrying-in instabilities in otherwise rock-solid Slackware.
 
Old 08-09-2013, 12:33 PM   #12
Martinus2u
Member
 
Registered: Apr 2010
Distribution: Slackware
Posts: 345

Rep: Reputation: 56
fwiw, one of my machines occasionally panics after resume (sometimes immediately, sometimes a minute later), and has been doing so since 3.9. However, since i use kernel patches and proprietary modules i don't have anyone to complain to...

edit: intel core i7 (bloomfield) system with nvidia blob

Last edited by Martinus2u; 08-09-2013 at 02:56 PM.
 
Old 08-09-2013, 01:07 PM   #13
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,190

Rep: Reputation: 547Reputation: 547Reputation: 547Reputation: 547Reputation: 547Reputation: 547
The 3.10.5 kernel is running fine for me on three slackware-current boxes(32 bit). The boxes have Intel video cards. All is well here.
 
Old 08-09-2013, 02:00 PM   #14
Pentti Poytakangas
LQ Newbie
 
Registered: Mar 2011
Location: House
Distribution: S64-14.1/multilib
Posts: 18

Rep: Reputation: 1
Hi!
I use S64-14_current with vmlinuz-3.10.5 in Asus I5 PC...Works fine.
Intel stuff work too
First I use default .config file to compile.
So no problemas!
 
Old 08-09-2013, 03:14 PM   #15
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,382
Blog Entries: 15

Rep: Reputation: 934Reputation: 934Reputation: 934Reputation: 934Reputation: 934Reputation: 934Reputation: 934Reputation: 934
Both my Slackware and LFS partitions use 3.10.5 without any issues at the moment. I'm even using the Slackware 3.10.5 config for LFS too.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
ath9k driver unstable in kernel 2.6.38? MrCode Arch 0 04-13-2011 06:36 AM
Any later than kernel 2.6.23 stalls on boot, also quite unstable... doug2e Fedora 1 07-12-2008 05:24 PM
is ubuntu unstable less unstable than debian unstable? lefty.crupps Ubuntu 9 10-14-2005 01:38 PM
compiling kernel 2.5.70 (experimental-unstable) kazuni Slackware 12 07-11-2003 07:27 AM
unstable kernel? eagle0669 Linux - Newbie 7 08-09-2001 08:17 AM


All times are GMT -5. The time now is 11:06 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration