slackware-64 13.37 suddenly freezes ( logs included )
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
slackware-64 13.37 suddenly freezes ( logs included )
Hello, I have slackware 13.37-64 bit with nvidia gforce 210.
Since i did the installation and use the default graphic card driver (nouveau) i see that after some hours of using it suddenly freezes. I can't do anything, even use alt_ctl_backspace
or alt_ctl_del for reboot, so i use the button of the pc to reboot. The only thing that i have noticed is that it happens that every time it freezes i am using firefox. But i don't know if it has every relation with this.
Since i'm not very experienced user and can't understand the log files i have put here the pieces of /var/log/syslog and /var/log/messages related to the time that the freeze happens:
/var/log/syslog:
Code:
May 3 01:29:51 slaris udevd[1517]: bind failed: Address already in use
May 3 01:29:51 slaris kernel: [ 0.281291] ACPI: PCI Interrupt Link [LN0A] enabled at IRQ 19
May 3 01:29:51 slaris kernel: [ 0.281464] ACPI: PCI Interrupt Link [LN2A] enabled at IRQ 18
May 3 01:29:51 slaris kernel: [ 0.281631] ACPI: PCI Interrupt Link [LN3A] enabled at IRQ 17
May 3 01:29:51 slaris kernel: [ 0.281795] ACPI: PCI Interrupt Link [LN4A] enabled at IRQ 16
May 3 01:29:51 slaris kernel: [ 0.384550] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
May 3 01:29:51 slaris kernel: [ 0.389624] Console: switching to colour frame buffer device 128x48
May 3 01:29:51 slaris kernel: [ 3.657227] ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 23
May 3 01:29:51 slaris kernel: [ 4.011834] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
May 3 01:29:51 slaris kernel: [ 4.013527] registered taskstats version 1
May 3 01:29:51 slaris kernel: [ 7.013335] ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 22
May 3 01:29:51 slaris kernel: [ 7.032777] ACPI: PCI Interrupt Link [UB12] enabled at IRQ 21
May 3 01:29:51 slaris kernel: [ 7.084752] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 20
May 3 01:29:51 slaris kernel: [ 7.179571] ACPI: PCI Interrupt Link [LUB0] enabled at IRQ 23
May 3 01:29:51 slaris kernel: [ 7.243782] ACPI: resource nForce2_smbus [io 0x2e00-0x2e3f] conflicts with ACPI region SM00 [io 0x2e00-0x2e3f 64bit disabled]
May 3 01:29:51 slaris kernel: [ 7.246706] ACPI: PCI Interrupt Link [UB11] enabled at IRQ 22
May 3 01:29:51 slaris kernel: [ 7.417659] fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver
May 3 01:29:51 slaris kernel: [ 7.418542] Console: switching to colour dummy device 80x25
May 3 01:29:51 slaris kernel: [ 7.487352] [drm] nouveau 0000:02:00.0: Pointer to BIT loadval table invalid
May 3 01:29:51 slaris kernel: [ 7.528049] [drm] nouveau 0000:02:00.0: 0xD329: Condition still not met after 20ms, skipping following opcodes
May 3 01:29:51 slaris kernel: [ 7.549030] [drm] nouveau 0000:02:00.0: 0xD32D: Condition still not met after 20ms, skipping following opcodes
May 3 01:29:51 slaris kernel: [ 7.622036] [drm] nouveau 0000:02:00.0: 0xCF0C: Condition still not met after 20ms, skipping following opcodes
May 3 01:29:51 slaris kernel: [ 7.838180] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 21
May 3 01:29:51 slaris kernel: [ 8.059860] Console: switching to colour frame buffer device 210x65
May 3 01:29:51 slaris kernel: [ 8.182036] hda-codec: no NID for mapping control Independent HP:0:0
May 3 01:29:51 slaris kernel: [ 8.245406] ACPI: PCI Interrupt Link [LN0B] enabled at IRQ 19
May 3 01:29:51 slaris kernel: [ 12.612974] usbfs: unrecognised mount option "devgid=groupid" or missing value
May 3 01:29:51 slaris kernel: [ 12.613421] usbfs: mount parameter error.
May 3 01:29:51 slaris udevd[1517]: error binding control socket, seems udevd is already running
May 3 01:29:58 slaris console-kit-daemon[1838]: WARNING: Failed to acquire org.freedesktop.ConsoleKit
May 3 01:29:58 slaris console-kit-daemon[1838]: WARNING: Could not acquire name; bailing out
May 3 01:30:17 slaris python: hp-systray[2203]: warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Hello, I have slackware 13.37-64 bit with nvidia gforce 210.
Since i did the installation and use the default graphic card driver (nouveau) i see that after some hours of using it suddenly freezes. I can't do anything, even use alt_ctl_backspace or alt_ctl_del for reboot, so i use the button of the pc to reboot. The only thing that i have noticed is that it happens that every time it freezes i am using firefox. But i don't know if it has every relation with this.
Were you browsing a site that has mostly text (like the linuxquestions forums) or picture galleries ? I had what seems to be the same problem that when i opened tabs showing e.g wallpapers, firefox crashed the system or messed the screen up and artifacts were everywhere. The cause was hardware acceleration. I have the impression that Firefox enables it only for the binary nvidia driver because when i tested nouveau it never crashed, so your cause might be a different one, but disable hardware acceleration anyway and see if you can reproduce it (Edit-> Preferences-> Advanced-> General-> Use hardware acceleration when available).
This is the post i made here and the post in Greek. As i said it might be a different cause in your case since you use nouveau but it is easy to disable acceleration and test it.
I have tried it and have serious problem with high memory usage of X ( sometimes over 500 Mb ).
I have tried many things:
KDE + nvidia ( 256, 260-from slackbuilds, 270 )= high memory
KDE + nouveau = high memory
LXDE + nvidia ( 256, 260-from slackbuilds, 270 )= high memory
LXDE + nouveau = normal memory BUT freezes
Ofcaurse now i haven't KDE and it's libs installed ( did a clean installed with just LXDE ). Should i give another try? Would it make any difference?
Were you browsing a site that has mostly text (like the linuxquestions forums) or picture galleries ? I had what seems to be the same problem that when i opened tabs showing e.g wallpapers, firefox crashed the system or messed the screen up and artifacts were everywhere. The cause was hardware acceleration. I have the impression that Firefox enables it only for the binary nvidia driver because when i tested nouveau it never crashed, so your cause might be a different one, but disable hardware acceleration anyway and see if you can reproduce it (Edit-> Preferences-> Advanced-> General-> Use hardware acceleration when available).
This is the post i made here and the post in Greek. As i said it might be a different cause in your case since you use nouveau but it is easy to disable acceleration and test it.
I'm not sure i remember what i was browsing, only that once i was downloading a video attachment from an e-mail through my account with firefox. I also haven't had any artifacts - just the freezing. I now disabled the "hardware acceleration" as you said, and wait and see...
Hmm - I find it hard to believe that the binary driver causes huge memory usage. I would really like to see the open-source driver come to true fruition, but in the meantime we're a far way from that. So I'd also suggest sticking to the binary. After all, you probably paid a chunk of money to get a decent graphics card. If you were running with Intel graphics it would make great sense to stick with the open version.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.