does not seem to be any big errors.
]]>
The kernel.log, what to look for, theres alot of info. I found this, maby it is what im looking for.
May 8 05:43:25 NetBox ACPI: PCI Interrupt Routing Table [_SB_.PCI0._PRT]
May 8 05:43:25 NetBox ACPI: PCI Interrupt Routing Table [_SB_.PCI0.SLOT._PRT]
May 8 05:43:25 NetBox ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 *11 12 14 15)
May 8 05:43:25 NetBox ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 *9 10 11 12 14 15)
May 8 05:43:25 NetBox ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 9 10 11 12 14 15)
May 8 05:43:25 NetBox ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 *10 11 12 14 15)
May 8 05:43:25 NetBox ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 *11 12 14 15)
May 8 05:43:25 NetBox ACPI: PCI Interrupt Link [LNKF] (IRQs *3 4 5 7 9 10 11 12 14 15)
May 8 05:43:25 NetBox ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 *9 10 11 12 14 15)
May 8 05:43:25 NetBox ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 *9 10 11 12 14 15)
May 8 05:43:25 NetBox ACPI: PCI Interrupt Routing Table [_SB_.PCI0.AGP_._PRT]
but i have no idea... I gotta set the system clock right so that I can see the right time in the log, last time i set it wiuth date but it seems to change each time I reboot
]]>my computer 'crashed' for 10 minutes ago this is what happened when i tried rebooting
first it crashed, i rebooted and it stopped at hotplug , rebooted three times and this happened.
after that i stopped at the partition check and dit fsck -y ; reboot after that it said 'ARCH has gone 49709 days without beeing checked' <- thats a lot of days!
I copied all logs to another folder, wich log is theone i want to look in?
--edit-
crashed again, yay, maby it really is overheating. thistime i did fsck -y directly and it worked fine, saved logs into diffrent folder so now I maby could do diff or something.
To get lm_sensors working run and follow the instructions of sensors-detect. After that customize your /etc/sensors.conf if needed (if get get very weird results then change some thing until it gives reasonable output. For more info read the stuff in the config file).
But for now the output of the logfiles and dmesg are much more interesting.
]]>Weird, what cpu and other hardware do you have and do you have a temperature sensor in your pc? If so, look in the bios to see what the temperature is, or install and setup lm_sensors. I suspect a cpu cooler that gets stuck once in a while or something, causing the slowness. It may also be a broken harddisk, but then you'll see errors in the logs for sure.
Look in your logs and at dmesg output, if there's nothing interesting there try booting with acpi=off to see if that makes a difference. What kernel are you running? If something before 2.6.11 then upgrade. Also posting the dmesg output just when such sloweness begins would be very interesting.
[firedance@NetBox ~]$ uname -r
2.6.11.7-ARCH
but, if it was overheating wouldnt the slowness come slowly?
the computer goes slow like Poff!
[root@NetBox firedance]# pacman -S lm_sensors
:: lm_sensors-2.9.1-1: is up to date. Upgrade anyway? [Y/n] n
I haave lm_sensors, just dont know howto use it, il check with google.
]]>Look in your logs and at dmesg output, if there's nothing interesting there try booting with acpi=off to see if that makes a difference. What kernel are you running? If something before 2.6.11 then upgrade. Also posting the dmesg output just when such sloweness begins would be very interesting.
]]>Look at /var/log/kernel. Though if it's a real hard crash then either no info was generated or the data didn't made it to disk. But perhaps there is something interesting earlier on.
Since when do you have these problems? What changed?
I have had theese problems since I installed arch, never happened in fedora and happened once on the ubuntu live cd.
Im not sure if its a crash, the computer works, but VERY VERY slow (In the time of a beep i am able to go to the sofa , sit down and still hear the beep)
]]>Since when do you have these problems? What changed?
]]>I don't think it's a ram problem, memtest would have found it most likely. You don't have to run the cpuburn a whole week, just until it crashes (one hour should be plenty). Nothing funny in dmesg or logs after a crash?
Im sorry, where is the logs?
Im quite sure its not the ram. becouse I took out one ramstick a time and the computer crashed with all combinations (um, i mean like ram 1,2 & 1,3 & 3,2)