SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
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.
Click Here to receive this Complete Guide absolutely free.
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.
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.".
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
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.
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
[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
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...
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.
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 03:56 PM.