(SOLVED, possible hardware problem) reboot required?

[kjpetrie]

Yep, also you can try nolapic. And you could also remove the invalid acpi=on as well.

Then again it's also possible whatever it was has sorted itself out, just to make you a liar!

[T6]

"Then again it's also possible whatever it was has sorted itself out, just to make you a liar!"

that or i haven't had enough time to test it     

[T6]

i'm not sure to follow you kjpetrie

the acpi from bios?

i tested noapic(no l) and system took 30 minutes to hang up but this time the mouse pointer wasn't moving slow so something happened

[kjpetrie]

According to dmesg, you have an entry in your menu.lst for "acpi=on". That's not a valid value and just generates an error message, so you might as well remove it.

You could try "acpi=off" to test whether that stops the lock-up, however it will mean your computer won't do any of the acpi stuff like turning itself off at shutdown, managing fan and clock speeds, etc. Might be an idea to open the case and make sure the fans are all running if you try it - and monitor the temperature.

If it doesn't affect the problem just remove the acpi entry from menu.lst completely.

If it does, you might need to experiment with the proper acpi setting from the list I posted earlier.

[T6]

i just done a full system clean, the cpu runs at a miserable 33.0 C°

i never use any of those options

in the dmesg, just delete the entry?

acpi turned off in bios, won't enter to desktop

[kjpetrie]

I didn't say turn it off in BIOS, just change the option in menu.lst. I suspect it won't make any difference, but it might be worth trying. Again, it might make things worse, in which case don't use that option.

However, the entry you currently have is wrong. The opposite of "acpi=off" is "acpi=force". There is no such option as "acpi=on", which is why dmesg reports it as an error. The fact the error is being detected suggests it will then be ignored. The dmesg entry will go when you correct or remove the option in menu.lst.

[T6]

i just watched boot in verbose, it seems to be something related to acpi, there was some retry count or something, it seems to be triggered by xorg, after the crash the acpi step didn't do any recount, it was a simple ok

i'm doing some tests before deleting the acpi=on, thanks a lot for your help kjpetrie

i haven't used xp in couple of days so i don't know what it triggers the problem, weird

[T6]

the changes to menu.lst didn't helped

the problem is acpi, the difference is a line saying "acpi even logging is off" or something like that, after the restart or reset the line is not showed during the boot in verbose mode

[kjpetrie]

What acpi options are there in your BIOS?

[T6]

acpi function: enabled/disabled(currently on)

acpi stand by state: auto/s3/s1(it was s3 but i set it to auto)

[T6]

since the update to kde4 anr any other change haven't fixed the problem i kept testing possible solutions but nothing worked

i just tested turn off apic local and apic in pclinux control center/boot

the problem is that music is doing lots of jumps/skip sections so this solution doesn't help either

n that same menu, there is a option for acpi, if i disable it, what could be the results?

[T6]

things seems the same here, still the same problem but i think it is firefox

i have replicated the problem many times when firefox is running, specially when i close a tab or i do something in firefox(just run seems to be enough)

i can't be sure but i hope that a new repartition of hard disk and a new kernel can create a more stable environment for me

[T6]

last update for this problem

i am using all days this machine and problem never occurred again

with the current state of system, current kernel and possibly the psu change i did problem vanished completely

unfortunately can't track exactly the reason of the problem because the original psu is in use in another place