So... two years and no one really cares? I mean, the patch is already
there, published by Debian people, why not bring it over?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331630
Title:
Creates
Greetings,
People, have any of you verified if it fixes the issue for you to
disable power management? .. I know it is not a *fix*, specially for
a laptop (battery life would suffer a lot), but I just want to know if
we are having the same issue.
Ildefonso.
--
You received this bug
://code.google.com/p/avr-uip/
It would be good to either upgrade the version, or backport the patch.
Thanks!
Ildefonso Camargo
** Affects: gcc-avr (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: GCC Bugzilla #49487
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49487
--
You
Sorry, pasted the wrong URL:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49487
That's the bug on gcc. Well, the link was on the other bug too, but
here is the direct link just in case.
Also, the patch seems to be this one:
http://gcc.gnu.org/viewcvs?view=revisionrevision=176277
Ildefonso.
Hi Hansen,
No, my CPU is A8-3850 (no external video card, just the included HD
6550D). Also, I have to inform that after almost 7 hours idle the
machine didn't crashed. I disabled power management (ie, left only the
screen saver, but screen is never put to sleep).
Also, before the update to
Greetings,
Another update: almost 3 hours after moving again to Ubuntu kernel, with
disabled display power management, the system is working just fine.
I think the problem shows itself when the video card goes into energy
save mode.
Ildefonso.
--
You received this bug notification because you
Greetings,
I seem to be having the same problem. While using 11.10 (ie, before
updating) this problem used to happen under two situations:
1. If I used a low-latency kernel (ie: fully preemptive). I switched to
voluntary preemption.
2. If I enabled V-Sync + Escritorio libre de fragmentaciones
Greetings,
Even more information:
I turned off vsync, and the freeze happened again, this happens after
some time idle (maybe related to power management).
On other information, now I tried from the ssh session to kill X server
and kdm (yes, I'm using kde), first with signal 15, then with
