Fedora keeps crashing, ran memtest +86 on both memory channels, and computer freezes
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
Fedora keeps crashing, ran memtest +86 on both memory channels, and computer freezes
I have a computer, I upgraded it from FC5 to Fedora 14. Thought at first I had a bad drive, as It kept crashing. After reformat & install of Fedora 14, continues to crash when doing high system resource type commands such as yum update. Thought I had bad memory, it has 4 memory slots, 4 GBs all the same brand model of memory, ran memtest +86 on first channel, and It froze in middle of the test. Removed that RAM and put in the other 2GBS in the other channel, and again it froze. So I dont think its the hard drive or RAM, Could it be the CPU?
nothing in /messages or dmesg. does not show any type of errors, It simple locks and freezes, not even ctrl-alt-del works have to hold power button to reboot.
Code:
[root@obelix ~]# less /var/log/messages
Dec 22 11:25:59 obelix kernel: [ 1.594181] system 00:0a: [io 0x6500-0x65fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594185] system 00:0a: [io 0x6600-0x66fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594188] system 00:0a: [io 0x6700-0x67fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594192] system 00:0a: [io 0x6800-0x68fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594196] system 00:0a: [io 0x6900-0x69fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594199] system 00:0a: [io 0x6a00-0x6afe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594203] system 00:0a: [io 0x6b00-0x6bfe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594207] system 00:0a: [io 0x6c00-0x6cfe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594210] system 00:0a: [io 0x6d00-0x6dfe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594214] system 00:0a: [io 0x6e00-0x6efe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594218] system 00:0a: [io 0x6f00-0x6ffe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594222] system 00:0a: [io 0xa000-0xa0fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594225] system 00:0a: [io 0xa100-0xa1fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594229] system 00:0a: [io 0xa200-0xa2fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594233] system 00:0a: [io 0xa300-0xa3fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594236] system 00:0a: [io 0xa400-0xa4fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594240] system 00:0a: [io 0xa500-0xa5fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594244] system 00:0a: [io 0xa600-0xa6fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594247] system 00:0a: [io 0xa700-0xa7fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594251] system 00:0a: [io 0xa800-0xa8fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594255] system 00:0a: [io 0xa900-0xa9fe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594259] system 00:0a: [io 0xaa00-0xaafe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594263] system 00:0a: [io 0xab00-0xabfe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594266] system 00:0a: [io 0xac00-0xacfe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594270] system 00:0a: [io 0xad00-0xadfe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594274] system 00:0a: [io 0xae00-0xaefe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594278] system 00:0a: [io 0xaf00-0xaffe] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594282] system 00:0a: [mem 0xe0000000-0xefffffff] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.594285] system 00:0a: [mem 0xfeda0000-0xfedacfff] has been reserved
Dec 22 11:25:59 obelix kernel: [ 1.601306] pci 0000:00:1c.0: BAR 15: assigned [mem 0xd0000000-0xd01fffff 64bit pref]
Dec 22 11:25:59 obelix kernel: [ 1.601311] pci 0000:00:1c.4: BAR 15: assigned [mem 0xd0200000-0xd03fffff 64bit pref]
Dec 22 11:25:59 obelix kernel: [ 1.601315] pci 0000:00:1c.0: BAR 13: assigned [io 0x1000-0x1fff]
Dec 22 11:25:59 obelix kernel: [ 1.601319] pci 0000:00:1c.4: BAR 13: assigned [io 0x3000-0x3fff]
Dec 22 11:25:59 obelix kernel: [ 1.601323] pci 0000:00:01.0: PCI bridge to [bus 01-01]
Dec 22 11:25:59 obelix kernel: [ 1.601326] pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
Dec 22 11:25:59 obelix kernel: [ 1.601331] pci 0000:00:01.0: bridge window [mem 0xdfd00000-0xdfefffff]
Dec 22 11:25:59 obelix kernel: [ 1.601335] pci 0000:00:01.0: bridge window [mem 0xc0000000-0xcfffffff 64bit pref]
Dec 22 11:25:59 obelix kernel: [ 1.601340] pci 0000:00:1c.0: PCI bridge to [bus 02-02]
Dec 22 11:25:59 obelix kernel: [ 1.601344] pci 0000:00:1c.0: bridge window [io 0x1000-0x1fff]
Dec 22 11:25:59 obelix kernel: [ 1.601349] pci 0000:00:1c.0: bridge window [mem 0xdfc00000-0xdfcfffff]
Dec 22 11:25:59 obelix kernel: [ 1.601354] pci 0000:00:1c.0: bridge window [mem 0xd0000000-0xd01fffff 64bit pref]
Dec 22 11:25:59 obelix kernel: [ 1.601360] pci 0000:00:1c.4: PCI bridge to [bus 03-03]
Dec 22 11:25:59 obelix kernel: [ 1.601364] pci 0000:00:1c.4: bridge window [io 0x3000-0x3fff]
Dec 22 11:25:59 obelix kernel: [ 1.601369] pci 0000:00:1c.4: bridge window [mem 0xdfb00000-0xdfbfffff]
Dec 22 11:25:59 obelix kernel: [ 1.601374] pci 0000:00:1c.4: bridge window [mem 0xd0200000-0xd03fffff 64bit pref]
Dec 22 11:25:59 obelix kernel: [ 1.601381] pci 0000:00:1e.0: PCI bridge to [bus 04-04]
Dec 22 11:25:59 obelix kernel: [ 1.601383] pci 0000:00:1e.0: bridge window [io disabled]
Dec 22 11:25:59 obelix kernel: [ 1.601389] pci 0000:00:1e.0: bridge window [mem 0xdfa00000-0xdfafffff]
Dec 22 11:25:59 obelix kernel: [ 1.601393] pci 0000:00:1e.0: bridge window [mem pref disabled]
Dec 22 11:25:59 obelix kernel: [ 1.601416] pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Dec 22 11:25:59 obelix kernel: [ 1.601430] pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Dec 22 11:25:59 obelix kernel: [ 1.601443] pci 0000:00:1c.4: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Code:
[ 17.199909] p4-clockmod: Warning: EST-capable CPU detected. The acpi-cpufreq module offers voltage scaling in addition of frequency scaling. You should use that instead of p4-clockmod, if possible.
[ 17.200190] p4-clockmod: Warning: EST-capable CPU detected. The acpi-cpufreq module offers voltage scaling in addition of frequency scaling. You should use that instead of p4-clockmod, if possible.
[ 17.200305] p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available
[ 20.108262] alloc irq_desc for 45 on node -1
[ 20.108266] alloc kstat_irqs on node -1
[ 20.108282] tg3 0000:03:00.0: irq 45 for MSI/MSI-X
[ 20.993648] NET: Registered protocol family 10
[ 20.994164] lo: Disabled Privacy Extensions
[ 20.994363] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 21.816740] tg3 0000:03:00.0: eth0: Link is up at 100 Mbps, full duplex
[ 21.816744] tg3 0000:03:00.0: eth0: Flow control is on for TX and on for RX
[ 21.817255] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 32.258036] eth0: no IPv6 routers present
[ 34.362642] readahead-collector: starting delayed service auditd
[ 34.815460] readahead-collector: sorting
[ 35.175859] readahead-collector: finished
i mean i see some wierd stuff but not really sure what it means
Only thing that comes to mind are hardware problems. Overheating? Can you check BIOS heat/fan settings? Incorrectly configured CPU/motherboard settings?
Perhaps try running the system in runlevel 3 (no X-server) and see if the problem persists?
Perhaps try updating the motherboard firmware/bios?
thats what i think it is but how do i trouble shoot it down to something specific? Dont think its RAM the computer is clean. I saw this
Quote:
p4-clockmod: Warning: EST-capable CPU detected. The acpi-cpufreq module offers voltage scaling in addition of frequency scaling. You should use that instead of p4-clockmod, if possible.
I think this is an inherent issue with dells. I have 2 other Dells with this same issue. Its like Dell Optiplex's are designed to self destruct after 4-5 years. We are replacing this machine with a rack mount virtual server. Which I am much more satisfied with
There is a deal with some dell servers. It was something like a legacy usb option in bios or usb keyboard pre os or something like that. Disable that setting and try again if it is even there. The option was to allow usb control before an install of like nt or some such stuff.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.