Find the answer to your Linux question:
Results 1 to 9 of 9
I'm not entirely new to linux but still have alot to learn so please be patient with me if a say something stupid. I'm having major probs I've been trying ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2010
    Posts
    34

    HELP!!! Stop the Restarts!


    I'm not entirely new to linux but still have alot to learn so please be patient with me if a say something stupid.

    I'm having major probs I've been trying to get a multiboot set up going with different linux distros and Windows 7.

    For some reason my computer is having random reboots. This happens with various distros so I don't think it specific to the distro. even booting to a live CD will do it sometimes. It doesn't appear to happen on Windows 7 though so I'm thinking it is one of three things;

    1)Faulty Hardware, have tested the RAM & CPU etc and found no prob plus can run demanding games on Windows 7 perfectly fine so am less inclined to think that this is it.
    2)Hardware incompatibility with Linux in general, not sure on this don't know a lot about it. Will list my hardware below.
    3)Problems with ext4 fs, I'm thinking this is unlikely but with Win 7 and my Linux Distros being partition separately on the same HDD the only difference I see is the fs (NTFS & ext4).

    I could be completely off on all of the above so if anyone can shed any light on to this please, help me. I really don't go back to just windows and let my windows only friends say I told you so...

    My hardware:
    Motherboard - Gigabyte GA-M55SLI-S4 F10
    AMD Athlon x2 64 Dual Core Processor
    Nvidea GeForce 8600 GT
    1x 320 GB SATA HDD
    1x 500 GB SATA HDD
    PATA DVD Reader/Writer

  2. #2
    Linux Engineer Freston's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    1,049
    I have no idea what could be causing this.

    But the first thing I thought was 'overheating'. You don't encounter it very often, but sometimes a machine can't get rid of the heat it's generating. The hardware will shutdown or reboot the system in order to prevent all kinds of nastiness.

    Do you have the impression that the fans are working properly under Linux?




    And of course try looking through dmesg... I have a feeling it's acpi related. Run something like:
    Code:
    dmesg|grep -i --color=auto acpi
    dmesg|grep -iv default|grep -i --color=auto fault
    dmesg|grep -iv debug|grep -i --color=auto bug
    dmesg|grep -i --color=auto not
    dmesg|grep -i --color=auto error
    dmesg|grep -i --color=auto bios
    dmesg|grep -i --color=auto temp
    dmesg|grep -i --color=auto problem

    Also:
    You can monitor the temperature of your machine with the `sensors` command, although this may not be enabled by default or even supported on your system (if indeed there lies the problem). I had to run `sensors-detect` on my system, and `modprobe coretemp` to get it to work. YMMV
    Last edited by Freston; 07-11-2010 at 11:15 AM. Reason: Added some detail
    Can't tell an OS by it's GUI

  3. #3
    Just Joined!
    Join Date
    Mar 2010
    Posts
    34
    Quote Originally Posted by Freston View Post
    I have no idea what could be causing this.

    But the first thing I thought was 'overheating'. You don't encounter it very often, but sometimes a machine can't get rid of the heat it's generating. The hardware will shutdown or reboot the system in order to prevent all kinds of nastiness.

    Do you have the impression that the fans are working properly under Linux?




    And of course try looking through dmesg... I have a feeling it's acpi related. Run something like:
    Code:
    dmesg|grep -i --color=auto acpi
    dmesg|grep -iv default|grep -i --color=auto fault
    dmesg|grep -iv debug|grep -i --color=auto bug
    dmesg|grep -i --color=auto not
    dmesg|grep -i --color=auto error
    dmesg|grep -i --color=auto bios
    dmesg|grep -i --color=auto temp
    dmesg|grep -i --color=auto problem

    Also:
    You can monitor the temperature of your machine with the `sensors` command, although this may not be enabled by default or even supported on your system (if indeed there lies the problem). I had to run `sensors-detect` on my system, and `modprobe coretemp` to get it to work. YMMV
    Now running Debian and still getting restart ran the dsmeg commands and got;
    Code:
    jonny-desktop:/home/jonny# dmesg|grep -i --color=auto acpi
    [    0.000000]  BIOS-e820: 000000007fff0000 - 000000007fff3000 (ACPI NVS)
    [    0.000000]  BIOS-e820: 000000007fff3000 - 0000000080000000 (ACPI data)
    [    0.000000] ACPI: RSDP 000F6360, 0014 (r0 GBT   )
    [    0.000000] ACPI: RSDT 7FFF3000, 0034 (r1 GBT    NVDAACPI 42302E31 NVDA  1010101)
    [    0.000000] ACPI: FACP 7FFF3040, 0074 (r1 GBT    NVDAACPI 42302E31 NVDA  1010101)
    [    0.000000] ACPI: DSDT 7FFF30C0, 42E3 (r1 GBT    NVDAACPI     1000 MSFT  100000C)
    [    0.000000] ACPI: FACS 7FFF0000, 0040
    [    0.000000] ACPI: SSDT 7FFF7440, 02CC (r1 PTLTD  POWERNOW        1  LTP        1)
    [    0.000000] ACPI: MCFG 7FFF7740, 003C (r1 GBT    NVDAACPI 42302E31 NVDA  1010101)
    [    0.000000] ACPI: APIC 7FFF73C0, 007C (r1 GBT    NVDAACPI 42302E31 NVDA  1010101)
    [    0.000000] Nvidia board detected. Ignoring ACPI timer override.
    [    0.000000] If you got timer trouble try acpi_use_timer_override
    [    0.000000] ACPI: PM-Timer IO Port: 0x1008
    [    0.000000] ACPI: Local APIC address 0xfee00000
    [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
    [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
    [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
    [    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [    0.000000] ACPI: BIOS IRQ0 pin2 override ignored.
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
    [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
    [    0.000000] ACPI: IRQ9 used by override.
    [    0.000000] ACPI: IRQ14 used by override.
    [    0.000000] ACPI: IRQ15 used by override.
    [    0.000000] Using ACPI (MADT) for SMP configuration information
    [    0.100769] ACPI: Core revision 20080321
    [    0.240015] ACPI: bus type pci registered
    [    0.244015] ACPI: EC: Look up EC in DSDT
    [    0.248015] ACPI: Interpreter enabled
    [    0.248015] ACPI: (supports S0 S1 S4 S5)
    [    0.248015] ACPI: Using IOAPIC for interrupt routing
    [    0.252016] ACPI: PCI Root Bridge [PCI0] (0000:00)
    [    0.252016] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    [    0.252016] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
    [    0.288411] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    [    0.288411] ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    [    0.288411] ACPI: PCI Interrupt Link [LNK3] (IRQs *3 4 5 7 9 10 11 12 14 15)
    [    0.288411] ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    [    0.288411] ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    [    0.288411] ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 *5 7 9 10 11 12 14 15)
    [    0.288411] ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    [    0.288411] ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 *5 7 9 10 11 12 14 15)
    [    0.288411] ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 7 9 10 *11 12 14 15)
    [    0.288411] ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    [    0.288524] ACPI: PCI Interrupt Link [LSMB] (IRQs *3 4 5 7 9 10 11 12 14 15)
    [    0.288635] ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 7 9 *10 11 12 14 15)
    [    0.292683] ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    [    0.292801] ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 5 7 9 10 *11 12 14 15)
    [    0.292917] ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 7 9 *10 11 12 14 15)
    [    0.293032] ACPI: PCI Interrupt Link [LPCA] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
    [    0.293156] ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled.
    [    0.293278] ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled.
    [    0.293399] ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0
    [    0.293518] ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled.
    [    0.293595] ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
    [    0.293721] ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0
    [    0.293846] ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0, disabled.
    [    0.293974] ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0
    [    0.294099] ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0
    [    0.294224] ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0, disabled.
    [    0.294349] ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0
    [    0.294475] ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0
    [    0.294601] ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
    [    0.294733] ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0
    [    0.294864] ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0
    [    0.294996] ACPI: PCI Interrupt Link [APCP] (IRQs 20 21 22 23) *0, disabled.
    [    0.295663] pnp: PnP ACPI init
    [    0.295668] ACPI: bus type pnp registered
    [    0.300351] pnp: PnP ACPI: found 12 devices
    [    0.300351] ACPI: ACPI bus type pnp unregistered
    [    0.300351] PnPBIOS: Disabled by ACPI PNP
    [    0.300351] PCI: Using ACPI for IRQ routing
    [    0.306408] ACPI: RTC can wake from S4
    [    1.156465] ACPI: ACPI0007:00 is registered as cooling_device0
    [    1.156465] ACPI: ACPI0007:01 is registered as cooling_device1
    [    1.371384] ACPI: PCI Interrupt Link [APCF] enabled at IRQ 23
    [    1.371384] ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 23 (level, low) -> IRQ 23
    [    1.538895] ACPI: PCI Interrupt Link [APCL] enabled at IRQ 22
    [    1.538895] ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCL] -> GSI 22 (level, low) -> IRQ 22
    [    1.653957] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 21
    [    1.653957] ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [APCH] -> GSI 21 (level, low) -> IRQ 21
    [    2.186947] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
    [    2.186947] ACPI: PCI Interrupt 0000:01:0a.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 18
    [    2.232732] ACPI: PCI Interrupt Link [APSI] enabled at IRQ 20
    [    2.232738] ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [APSI] -> GSI 20 (level, low) -> IRQ 20
    [    4.271326] ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 23
    [    4.271326] ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [APSJ] -> GSI 23 (level, low) -> IRQ 23
    [   10.801433] ACPI: Power Button (FF) [PWRF]
    [   10.862431] ACPI: Power Button (CM) [PWRB]
    [   11.281620] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22
    [   11.281620] ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCJ] -> GSI 22 (level, low) -> IRQ 22
    [   11.377621] parport_pc 00:09: reported by Plug and Play ACPI
    jonny-desktop:/home/jonny# dmesg|grep -iv default|grep -i --color=auto fault
    jonny-desktop:/home/jonny# dmesg|grep -iv debug|grep -i --color=auto bug
    jonny-desktop:/home/jonny# dmesg|grep -i --color=auto not
    [    0.310395] system 00:02: ioport range 0x294-0x297 could not be reserved
    [    0.310403] system 00:0a: iomem range 0xd0000000-0xdfffffff could not be reserved
    [    0.310413] system 00:0b: iomem range 0xf0000-0xfbfff could not be reserved
    [    0.310416] system 00:0b: iomem range 0xfc000-0xfffff could not be reserved
    [    0.310418] system 00:0b: iomem range 0x7fff0000-0x7fffffff could not be reserved
    [    0.310420] system 00:0b: iomem range 0xffff0000-0xffffffff could not be reserved
    [    0.310423] system 00:0b: iomem range 0x0-0x9ffff could not be reserved
    [    0.310425] system 00:0b: iomem range 0x100000-0x7ffeffff could not be reserved
    [    0.310427] system 00:0b: iomem range 0xfec00000-0xfec00fff could not be reserved
    [    0.310430] system 00:0b: iomem range 0xfee00000-0xfee00fff could not be reserved
    [    1.538895] PCI: cache line size of 64 is not supported by device 0000:00:02.1
    [    6.570850] NFORCE-CK804: not 100% native mode: will probe irqs later
    [    7.145690] usb 1-3: not running at top speed; connect to a high speed hub
    jonny-desktop:/home/jonny# dmesg|grep -i --color=auto error
    [   12.468188] ata1: SError: { PHYRdyChg Dispar LinkSeq TrStaTrns }
    [   12.468188]          res d0/00:01:fa:46:48/00:01:fa:46:48/e0 Emask 0x12 (ATA bus error)
    jonny-desktop:/home/jonny# dmesg|grep -i --color=auto bios
    [    0.000000] BIOS-provided physical RAM map:
    [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
    [    0.000000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
    [    0.000000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    [    0.000000]  BIOS-e820: 0000000000100000 - 000000007fff0000 (usable)
    [    0.000000]  BIOS-e820: 000000007fff0000 - 000000007fff3000 (ACPI NVS)
    [    0.000000]  BIOS-e820: 000000007fff3000 - 0000000080000000 (ACPI data)
    [    0.000000]  BIOS-e820: 00000000d0000000 - 00000000e0000000 (reserved)
    [    0.000000]  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
    [    0.000000] ACPI: BIOS IRQ0 pin2 override ignored.
    [    0.300351] PnPBIOS: Disabled by ACPI PNP
    jonny-desktop:/home/jonny# dmesg|grep -i --color=auto temp
    jonny-desktop:/home/jonny# dmesg|grep -i --color=auto problem
    jonny-desktop:/home/jonny#
    Don't know enough to know if theres anything there that explains it. Pleas if theres a way to fix it I would love to here it.

  4. #4
    Just Joined!
    Join Date
    Mar 2010
    Posts
    34
    Please can anyone give me some advice on this? I've already lost count of the amount of restarts I've had today. And yet it ran fine all night running a compression of a large folder.

    I'm so frustrated with this that I'm about to scrap the whole thing and go to just Windows which I really don't want to do as I'm loving Linux when its going.

    This is the only computer I had trouble with Linux on. Any other has worked fine, and thats often running the exact same copy of a distro, so I know its not the distro.

    If it's faulty hardware, how can I tell? I've ran memtest and a CPU stress test and still found no problem.

    Please I'm at my wits end with the thing...

  5. #5
    Just Joined!
    Join Date
    Mar 2010
    Posts
    34
    Here is some more info on my system if anyone can spot anything.
    Code:
    [Jonny@localhost ~]$ cat /proc/meminfo
    MemTotal:        2062380 kB
    MemFree:         1489000 kB
    Buffers:           23480 kB
    Cached:           324372 kB
    SwapCached:            0 kB
    Active:           296036 kB
    Inactive:         199612 kB
    Active(anon):     151984 kB
    Inactive(anon):       16 kB
    Active(file):     144052 kB
    Inactive(file):   199596 kB
    Unevictable:           0 kB
    Mlocked:               0 kB
    HighTotal:       1191880 kB
    HighFree:         692292 kB
    LowTotal:         870500 kB
    LowFree:          796708 kB
    SwapTotal:       4128760 kB
    SwapFree:        4128760 kB
    Dirty:                92 kB
    Writeback:             0 kB
    AnonPages:        147788 kB
    Mapped:            69636 kB
    Shmem:              4212 kB
    Slab:              40968 kB
    SReclaimable:      19240 kB
    SUnreclaim:        21728 kB
    KernelStack:        2120 kB
    PageTables:         5004 kB
    NFS_Unstable:          0 kB
    Bounce:                0 kB
    WritebackTmp:          0 kB
    CommitLimit:     5159948 kB
    Committed_AS:     718792 kB
    VmallocTotal:     122880 kB
    VmallocUsed:       55976 kB
    VmallocChunk:      48284 kB
    HardwareCorrupted:     0 kB
    HugePages_Total:       0
    HugePages_Free:        0
    HugePages_Rsvd:        0
    HugePages_Surp:        0
    Hugepagesize:       4096 kB
    DirectMap4k:       16376 kB
    DirectMap4M:      888832 kB
    [Jonny@localhost ~]$ cat /proc/cpuinfo
    processor	: 0
    vendor_id	: AuthenticAMD
    cpu family	: 15
    model		: 67
    model name	: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+
    stepping	: 3
    cpu MHz		: 1000.000
    cache size	: 1024 KB
    physical id	: 0
    siblings	: 2
    core id		: 0
    cpu cores	: 2
    apicid		: 0
    initial apicid	: 0
    fdiv_bug	: no
    hlt_bug		: no
    f00f_bug	: no
    coma_bug	: no
    fpu		: yes
    fpu_exception	: yes
    cpuid level	: 1
    wp		: yes
    flags		: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy
    bogomips	: 2010.24
    clflush size	: 64
    cache_alignment	: 64
    address sizes	: 40 bits physical, 48 bits virtual
    power management: ts fid vid ttp tm stc
    
    processor	: 1
    vendor_id	: AuthenticAMD
    cpu family	: 15
    model		: 67
    model name	: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+
    stepping	: 3
    cpu MHz		: 1000.000
    cache size	: 1024 KB
    physical id	: 0
    siblings	: 2
    core id		: 1
    cpu cores	: 2
    apicid		: 1
    initial apicid	: 1
    fdiv_bug	: no
    hlt_bug		: no
    f00f_bug	: no
    coma_bug	: no
    fpu		: yes
    fpu_exception	: yes
    cpuid level	: 1
    wp		: yes
    flags		: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy
    bogomips	: 2010.24
    clflush size	: 64
    cache_alignment	: 64
    address sizes	: 40 bits physical, 48 bits virtual
    power management: ts fid vid ttp tm stc
    
    [Jonny@localhost ~]$ lspci
    00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3)
    00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
    00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
    00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2)
    00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3)
    00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2)
    00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
    00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
    00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
    00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
    00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev a3)
    00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
    00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
    00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
    00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
    00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
    00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
    00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
    00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
    01:0a.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)
    05:00.0 VGA compatible controller: nVidia Corporation G84 [GeForce 8600 GT] (rev a1)
    I'm currently running fedora13 from a different HDD and have disconceted other HDDs incase it is they were the problem. This is only a temp situation as this HDD is coming up as failing. But so far so good (touch wood).

    If it is the one of the HDD that is the problem, are there any commands that could help with this to either fix or diagnose this?

  6. #6
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,568
    From what you are describing, I think you have a hardware problem, probably related to the hardware interrupt (NMI) circuitry. Some of these sort of problems Windows will mask - Linux is somewhat more demanding of the hardware in some respects. You need to run the diagnostics in a continual loop at least overnight, and possibly longer. A single pass is not adequate to trace these sort of subtle problems.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  7. #7
    Just Joined!
    Join Date
    Mar 2010
    Posts
    34
    Quote Originally Posted by Rubberman View Post
    From what you are describing, I think you have a hardware problem, probably related to the hardware interrupt (NMI) circuitry. Some of these sort of problems Windows will mask - Linux is somewhat more demanding of the hardware in some respects. You need to run the diagnostics in a continual loop at least overnight, and possibly longer. A single pass is not adequate to trace these sort of subtle problems.
    What diagnostic are you talking about? The memtest i left running all day while I was at my course and checked it that evening and it had done alot of passes (I forget how many).

    Is it possible that it's the HDD that I've been running linux off? I ask because SMART hasn't brought up any warnings or anything. And in refernce to my last post, after submiting that post I brought up and started every appliction that I could, ran heaps of tabs in the web browser and still no restarting. So I shut the system down pluged the other HDD back in and booted in to Debain and started writing an email to my Dad to explain how to do something (thats all I was doing on it), all was working fine and the moment I went to take a sreenshot the thing restarted once again. Disconected that HDD and have reconected the other HDD and now running from Fedora 13 again and have no issue yet. If thats the case I try another HDD that I got there.

    So if I change HDD and install Debain on it again, will I be able to restore things back to the way they were by copying the partions over to the new one and or will I have to start from sratch? I dont want to have to redownload stuff as my internet quota is just about out.

  8. #8
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,568
    Memtest isn't enough. You need to get the diagnostics from the board vendor/manufacturer to exercise the entire board. All memtest does is check memory. I doubt that is your problem. Since it is apparently (from what you said) random, yet affects more than one Linux distribution, including live CD versions, then it almost has to be a hardware issue, although it may be some motherboard issue aside from a failure scenario, such as ACPI not being properly implemented (just an example). In any case, do make sure you have installed the latest BIOS on the system.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  9. #9
    Penguin of trust elija's Avatar
    Join Date
    Jul 2004
    Location
    Either at home or at work or down the pub
    Posts
    3,565
    When booting Debian

    At the grub screen press e
    On the second line press e again
    add "noapic" (without the quotes) to the end of line
    Press Enter
    Press b to boot

    If that doesn't work try

    At the grub screen press e
    On the second line press e again
    add "acpi=off" (without the quotes) to the end of line
    Press Enter
    Press b to boot

    If one of these stops the reboots then we can look at adding it as a permenant grub option
    What do we want?
    Time machines!

    When do we want 'em?
    Doesn't really matter does it!?


    The Fifth Continent

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •