I've just find, that on my newly installed Debian Lenny dmesg shows
"Clocksource tsc unstable (delta = -233324728 ns)". But I have no real
problems, no lockups etc. So I've started thinking that maybe
"Clocksource tsc unstable" isn't connected with this bug (and freezes)
in no way...
This would al
I am using Ubuntu Jaunty 9.04. The freezes have begun just after fresh
installation... I thought they are connected with Jaunty problems on Intel
graphic cards... but after reading this...
Dmesg reveals "Clocksource tsc unstable (delta = -184814454 ns)"
I have also Debian Lenny on other PC - no
Looks like a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355155
--
AJP M3000N siezes up after a random period since upgrade to Jaunty
https://bugs.launchpad.net/bugs/375072
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
My mouse is also working and ALT+SysRq+K works for me, but I didn't tested it
with freeze yet...
I also tried "clocksource=hpet" boot option and dmesg still gives "tsc
unstable"... Im gonna to try "nohz=off"...
--
Clocksource tsc unstable leads to lockups in Ubuntu Jaunty
https://bugs.launchpad
Firstly, I dont know what to think about this, because yesterday I was
getting freezes every few minutes and today I wasn't able to get any
(only dmesg shows "tsc unstable")...
Now, with "nohz=off" option, dmesg shows no tsc unstability and no hpet
errors. I also wasn't able to get to freeze even
So it's here: "nohz=off" option doesn't work for me :-(
Few minutes ago I had lockup again. And I've found out, that "ALT+SysRq+K"
doesn't solve the problem - it only brings up the blank black screen...
--
Clocksource tsc unstable leads to lockups in Ubuntu Jaunty
https://bugs.launchpad.net/bugs
To avoid misunderstanding: "nohz=off" option doesn't work for me as a
workaround - it only causes no tsc unstability reported.
However, I find it interesting that my last freeze happened without tsc
unstability reported, so I add my var/log/messages from time of booting
till the lockup (and then "
My another questions are:
- Is there ANY DEVELOPER who is interesting in FIXING THIS BUG???
- Shouldn't be importance of this bug marked as CRITICAL?
--
Clocksource tsc unstable leads to lockups in Ubuntu Jaunty
https://bugs.launchpad.net/bugs/355155
You received this bug notification because yo
Computer on which I encountered this bug belongs to my friend... If he
wasn't a linux newbie, I would install him Debian... But now, I'm forced
to revert it back to Intrepid unless this bug is solved... Bye Jaunty!
It's a shame for Canonical. To me it seems like they aren't interested
in fixing th
Maybe I will consider installing him another distro (we have here also
Fedora, Mint, PCLinuxOS, OpenSUSE ... and linux has always been the
freedom of choice ;-) if things like this will happen also in the future
Ubuntu releases...
Canonical should be very, very careful not to make users of Ubuntu
10 matches
Mail list logo
