Like a few of the others, I'm getting rid of Jaunty and heading to
something else (not exactly sure what, yet). It's simply taken too long
for any real hint of a solution to appear (except perhaps downgrading
the X server from 1.6.0 -- I still haven't encountered any problems with
1.4.2 -- but tha
Just to add my own input and a few other things:
I've done two of the things suggested here that appear to have solved
this problem for me. I don't know if either of them alone would have
done it, since I made both changes at once. Basically, I upped my
"Virtual" size to 2048 2048, and I applied
@mnicky and others: I'm now basically certain that this bug has nothing
to do with the "Clocksource tsc unstable" messages; the title of the bug
should probably be changed. After I added "nohz=off" to the kernel boot
line, the freezes still occurred; others who followed suit had the same
results.
@Jamie: You (and other ATI users) might look here:
https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-
ati/+bug/348332.
I can confirm that both of the bug reports to which I recently linked
(including the one just linked) have solved the problems for me. One of
my machines uses xserver-
I believe that I suffered from this same bug (I suffered from a bug with
the same symptoms, anyway--though I didn't try XAA as the original
poster did). Like the rest of you, the problem disappeared when I
upgraded to a 2.6.29 kernel; for me, it was 2.6.29-020629-generic. (I
didn't try any others
Thanks for reporting this bug. I can confirm that it also exists in
Jaunty with Nautilus 2.26.2. Steps to reproduce are basically as you
described: go into a directory in Nautilus, right-click on a file and
select "Rename...", and then (without doing anything else) click "Up" to
enter the file's
** Bug watch added: GNOME Bug Tracker #584580
http://bugzilla.gnome.org/show_bug.cgi?id=584580
** Also affects: nautilus via
http://bugzilla.gnome.org/show_bug.cgi?id=584580
Importance: Unknown
Status: Unknown
--
Cursor becomes 'busy' in Nautilus when changing to parent directory
As requested, I've reported the bug upstream and linked to it.
--
Cursor becomes 'busy' in Nautilus when changing to parent directory while
renaming a file
https://bugs.launchpad.net/bugs/381824
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I just want to add my own confirmation, and the relevant files, here.
Like everyone else, I encounter seemingly random system freezes on
Jaunty. On the same machine on which I encounter these freezes, I have
no problems running Crunchbang 8.10, Debian Lenny, or ArchLinux -- the
issue occurs only w
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/27074630/dmesg.txt
--
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 of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "messages.txt"
http://launchpadlibrarian.net/27074670/messages.txt
--
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 of Ubuntu
Bugs, which is subscribed to Ubunt
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/27074636/lspci.txt
--
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 of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I do not use the nvidia drivers, so that isn't the issue in my case, at
least.
--
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 of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
I have no idea if this will actually be at all helpful, but I can tell
you that it removed the "clocksource tsc unstable" lines from dmesg for
me.
1) First, I checked the output of:
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
to see which clocksources I had available o
The last few comments (particularly Marc Domachowski's and
dannyboy1121's) suggest that the issue may not be with "clocksource tsc
unstable" after all (at least, not all by itself). I was going to
suggest that the issue may have something to do with Ubuntu's non-
vanilla kernels and their interact
Well, after days of uninterrupted use, I finally got a system freeze in
Xubuntu 9.04. For me, this seems to happen most often when I am quickly
moving between various open windows. Like alcCapone, my mouse typically
still moves when the freeze occurs. My keyboard does not respond to
CTRL+ALT+F1
Ugh... What's absolutely *awesome* is that there is apparently
also a bug in Ubuntu that prevents ALT+SysRq+K from working, even though
ALT+SysRq+REISUB does work!! See here:
https://bugs.launchpad.net/ubuntu/+bug/329644
So, unless the bug doesn't apply to you (you can test it while your X
server
Well, I never figured out how to get ALT+SysRq+K working, so I
downgraded the X server from 1.6.0 to 1.4.0.90 (the current X server for
Hardy Heron). I can't get any freezes to happen yet (doing the same
things that sometimes caused a freeze before), but I'll keep everyone
posted.
--
Clocksource
@alcCapone: You said, "ALT+SysRq+K does work for me. Tested is
yesterday." By this, do you mean that it worked to break you out of the
freeze? Or do you just mean that it works for you in general, but you
haven't been able to try it to break out of the freeze yet? If the
former is true, then thi
19 matches
Mail list logo
