Slackware freezes after certain screensavers operate for a while

daidoji · 11-07-2010, 06:55 PM

So I've been using Slackware for a long time but I'm not really sure where to start with this bug. Basically I'm on an old P4 Dell system that I just got for free (so semi-old hardware)

Code:

bash-4.1# lspci
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 05)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 05)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller (rev 05)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 05)
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1 (rev 05)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev b2)
02:09.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
02:09.1 Input device controller: Creative Labs SB Live! Game Port (rev 07)
02:0a.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem (rev 01)
02:0b.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet (rev 31)
02:0c.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

Anyways, its a stock Slackware install, I'm running Slackware-current (as of a week ago) and don't have problems with anything else. Basically certain screensavers come up, then I get a total freeze. Can't restart X (via Ctrl-Alt-backspace) can't switch to a virtual console, can't do anything other than hard reboot. I'm not really sure where to start since this seems like a weird issue. Here's the syslog and the error I think is causing this. Any systems people know where I can begin with something like this since google has so far failed me?

Code:

Nov  7 16:41:15 darkstar kernel: [16464.160691] BUG: unable to handle kernel paging request at 7cda2d8b
Nov  7 16:41:15 darkstar kernel: [16464.160705] IP: [<7cda2d8b>] 0x7cda2d8b
Nov  7 16:41:15 darkstar kernel: [16464.160718] *pde = 00000000 
Nov  7 16:41:15 darkstar kernel: [16464.160724] Oops: 0000 [#1] SMP 
Nov  7 16:41:15 darkstar kernel: [16464.160729] last sysfs file: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/boot_vga
Nov  7 16:41:15 darkstar kernel: [16464.160736] Modules linked in: snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss ipv6 lp fuse b43 mac80211 snd_emu10k1 cfg80211 snd_rawmidi snd_ac97_codec rfkill led_class ac97_bus ssb snd_pcm usbhid snd_seq_device snd_timer rtc_cmos i2c_i801 ppdev intel_agp mmc_core snd_page_alloc snd_util_mem processor rtc_core rtc_lib parport_pc agpgart evdev pcmcia psmouse pcmcia_core i2c_core parport hid thermal thermal_sys dcdbas emu10k1_gp snd_hwdep button hwmon gameport serio_raw snd soundcore shpchp sg
Nov  7 16:41:15 darkstar kernel: [16464.160794] 
Nov  7 16:41:15 darkstar kernel: [16464.160800] Pid: 1712, comm: X Not tainted 2.6.35.7-smp #2 D845PT                         /DIM4400                        
Nov  7 16:41:15 darkstar kernel: [16464.160806] EIP: 0060:[<7cda2d8b>] EFLAGS: 00013246 CPU: 0
Nov  7 16:41:15 darkstar kernel: [16464.160812] EIP is at 0x7cda2d8b
Nov  7 16:41:15 darkstar kernel: [16464.160816] EAX: f39ffe00 EBX: c1a25040 ECX: f6967bd0 EDX: f2df9980
Nov  7 16:41:15 darkstar kernel: [16464.160820] ESI: 40000000 EDI: f39ffe00 EBP: f6967b44 ESP: f6967b3c
Nov  7 16:41:15 darkstar kernel: [16464.160825]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Nov  7 16:41:15 darkstar kernel: [16464.160830] Process X (pid: 1712, ti=f6966000 task=f68970c0 task.ti=f6966000)
Nov  7 16:41:15 darkstar kernel: [16464.160833] Stack:
Nov  7 16:41:15 darkstar kernel: [16464.160836]  c18a2694 0000001e f6967e44 c10ef3f3 00000000 c3008600 f6967b98 c105e162
Nov  7 16:41:15 darkstar kernel: [16464.160848] <0> 5b7473a1 00000ef9 00ffffff f68970c0 00000000 00000000 f6967bd0 00000000
Nov  7 16:41:15 darkstar kernel: [16464.160859] <0> 00000000 f6967f00 f6967ee0 f6967ec0 f6967f60 f6967ea0 f6967e80 f6967e60
Nov  7 16:41:15 darkstar kernel: [16464.160872] Call Trace:
Nov  7 16:41:15 darkstar kernel: [16464.160884]  [<c18a2694>] ? sock_poll+0x14/0x20
Nov  7 16:41:15 darkstar kernel: [16464.160895]  [<c10ef3f3>] ? do_select+0x363/0x640
Nov  7 16:41:15 darkstar kernel: [16464.160902]  [<c105e162>] ? sched_clock_local+0xb2/0x1a0
Nov  7 16:41:15 darkstar kernel: [16464.160909]  [<c10eeef0>] ? __pollwait+0x0/0xd0
Nov  7 16:41:15 darkstar kernel: [16464.160915]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160920]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160925]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160931]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160936]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160941]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160947]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160952]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160957]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160963]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160968]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160973]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160979]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160984]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160989]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.160994]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.161000]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.161003]  [<c10eefc0>] ? pollwake+0x0/0x60
Nov  7 16:41:15 darkstar kernel: [16464.161003]  [<c10ef81b>] ? core_sys_select+0x14b/0x2a0
Nov  7 16:41:15 darkstar kernel: [16464.161003]  [<c105bbac>] ? hrtimer_try_to_cancel+0x3c/0xb0
Nov  7 16:41:15 darkstar kernel: [16464.161003]  [<c104253e>] ? do_setitimer+0xbe/0x1e0
Nov  7 16:41:15 darkstar kernel: [16464.161003]  [<c10ef9a1>] ? sys_select+0x31/0xb0
Nov  7 16:41:15 darkstar kernel: [16464.161003]  [<c198404c>] ? syscall_call+0x7/0xb
Nov  7 16:41:15 darkstar kernel: [16464.161003]  [<c1980000>] ? migration_call+0x120/0x28f
Nov  7 16:41:15 darkstar kernel: [16464.161003] Code:  Bad EIP value.
Nov  7 16:41:15 darkstar kernel: [16464.161003] EIP: [<7cda2d8b>] 0x7cda2d8b SS:ESP 0068:f6967b3c
Nov  7 16:41:15 darkstar kernel: [16464.161003] CR2: 000000007cda2d8b
Nov  7 16:41:15 darkstar kernel: [16464.161101] ---[ end trace 90442964f14a1650 ]---

frankbell · 11-07-2010, 08:20 PM

I don't have an answer, but maybe some relevant experience.

Last Thursday, I decided to upgrade my Dell P4 from Slackware 13.0, which it had been running like a champ, to 13.1. I backed up all my crucial files to external media and set off to upgrade per the instructions on the CD (I have a subscription).

I had some initial trouble, because my MBR apparently got messed up (when I rebooted, LILO didn't load). I formatted the MBR and installed from scratch, including reformatting not only the MBR but also the HDD.

Everything seemed to be going great. I was in the middle of configuring stuff to my taste when my computer froze. I lost all mouse and keyboard function in the GUI. When I booted to the text interface, I had functionality, but, as soon as I started a GUI (KDE, Fluxbox, XFCE), it frizzed right up.

I rebooted multiple times and reinstalled twice. Same thing.

Now I'm running Debian 5.0.6 on that--actually, this--box (Slack is my favorite; Debian is probably my second favorite).

Here's some information about my computer, in case it helps you in your troubleshooting:

Code:

  Name  Intel(R) Pentium(R) 4 CPU 3.40GHz
  Family, model, stepping  15, 3, 4 (Pentium 4)
  Vendor  Intel Corp.
  Kernel 2.6.26-2-686

As I recall, Slackware 13.1 installed Linux kernel 2.6.33, for what it's worth.

daidoji · 11-07-2010, 08:48 PM

Thanks Frank. Actually I think I might have found out the issue. Word on the street is that OpenGL drivers/video firmware/video libraries might be buggy in Slackware-current (is that what you were running or base 13.1?) I'm not sure what causes it but sucks that you went to Debian instead. I'm sure this issue isn't too big a deal. If I find anything more out I'll let you know.

frankbell · 11-07-2010, 09:06 PM

I was running 13.1 from the CDs.

I actually like Debian, though I prefer Slackware; Debian is solid and stable.

When my Slack 14.0 CDs arrive (as I said, I have a subscription--it's a way to support Pat), I'll see about moving this box back to Slack.

Frankly, after getting spoiled by the flexibility of Slackware, nothing else feels like computing to my fingers.

Slackware expects you to know what you are doing. I like that.

willysr · 11-07-2010, 10:44 PM

I think the next release will be 13.2, not 14.0

frankbell · 11-08-2010, 08:33 PM

Quote:

Originally Posted by willysr

I think the next release will be 13.2, not 14.0

Whatever it is, it will arrive in my mailbox automatically.

UZ64 · 11-19-2010, 08:26 PM

I just did a Google search for something along the lines of "Slackware screensaver freeze" because I realized a few minutes ago it did the same thing to me. It led me to this thread. I have totally different hardware, and you could argue different distribution though.

The machine is a few years old--a Dell Inspiron 531 with an AMD64 processor. The OS itself is 64-bit and Slackware-based, SalixOS 13.1. Graphics card is an nVidia, using the nv drivers.

I have no clue when it froze, because I haven't used it all day; I have this machine and another one hooked up to the same monitor, and I happened to notice that it froze probably hours after it actually did when I switched the input to do something on the other machine. This is a 100% fresh installation, formatted / and /home partitions and did the installation just yesterday. Needless to say, a crash on the first day of operation while away from the machine is pretty disappointing.

I recall this happening before with other distros, and possibly on my other machine. Unfortunately, I can't remember what they were, but I bet they were Slack derivatives. I have yet to run into this problem with OpenSUSE or Ubuntu 10.04.

Scott271 · 11-19-2010, 08:58 PM

I have had this happen to me at some point with Slack and Zenwalk. I forget what the exact screensaver is, but it will freeze the whole system on both my machines - Dell Dimension 4300(desktop) and Toshiba Satellite L305D(laptop), running Xfce. My wife has never had it happen on her laptop running Vector.

I end up setting my screensaver to just use one, as opposed to random ones. If you want to know which one it is that is causing it, scroll through each screensaver. The preview alone with cause it to freeze. Also, I believe that more than one may cause it - don't quote me on it though.

astanton · 11-28-2010, 12:39 PM

Quote:

Originally Posted by Scott271

"Never run Gparted and apply changes after drinking Daiquiris all day long" - me, as a note to self...

My Gawd, Man!

I've got a couple of post-it's on my monitors reminding me of pretty much the same thing, all tattered and torn, coz it "NEVER" happens to me anymore - except for sometimes LOL!

Well I'm going out onto the highway for a couple of hours, gotta go to L.A. for the day, and your tagline just provided me with the chuckle I needed to leave Starbucks w/a smile on my face for the long drive.

Kindest regards,

Scott271 · 11-29-2010, 04:32 PM

lol.... for the record, the daiquiris that day were strawberry, and 50% rum.

Back on topic, after a recent install of Zenwalk 6.4, and leaving the machine running all night, the screensaver "Molecules" is the one that notoriously freezes the comp.