I thought that i cured the freeze, but it striked again.
Here is mu drivers.txt
** Attachment added: drivers.txt
http://launchpadlibrarian.net/27719331/drivers.txt
--
Clocksource tsc unstable leads to lockups in Ubuntu Jaunty
https://bugs.launchpad.net/bugs/355155
You received this bug
I added clocksource=hpet
uptime
21:57:15 up 2 days, 8:06, 2 users, load average: 0.66, 0.45, 0.29
Seems to be pretty stable. :)
--
Clocksource tsc unstable leads to lockups in Ubuntu Jaunty
https://bugs.launchpad.net/bugs/355155
You received this bug notification because you are a member
I read another similar bug and there some guys got it fixed like that:
into /boot/grub/menu.lst on kernel line they added clocksource=tsc. I tried
that too, system was super slow on boot. So the other line was
clocksource=hpet. I am now running with that hpet line, had wireless
activity,
For few days it was rock stable. Now i had a crash while computer was on
screensaver.
18:39 I came and it was frozen. :(
cat /var/log/kern.log | grep -i tsc
May 21 18:06:07 Kompuuter kernel: [0.00] Fast TSC calibration using PIT
May 21 18:06:07 Kompuuter kernel: [0.468648] checking
With these acpi=off and noapic nolapic acpi=off my computer refuses
to boot. :/ acpi=off, then it just does nothing and when i put the other
one, then it says using some dummy acpi and connect to your hw vendor
and does not do anything more. :/
--
Computer hard locks randomly with ubuntu jaunty
Me too
At first it was pretty stable (using wicd), being in wifi it worked, but
after few hours i had to disconnect and connect to AP again.
Now yesterday crashes started, on all crashes i used torrents
(transmission).
Sometimes it's very stable for many hours.
System Specs:
JHL90; NV 9600M
