12.10 has been trouble-free for me. I have attempted to duplicate the
exact conditions that would reliably crash 12.04 on my T520, and so far,
the system has resolutely failed to fail :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Nothing's holding me back...not sure what you mean by that?
If you look through all the comments in this bug, you'll see that the
variety of systems and symptoms is so varied that it's difficult for the
developers to find anything common. Some people experience complete and
total freezes, where
@Steve Hayes (#361): unfortunately, in its present state, this bug
report has become unmanageable. There are too many variations in systems
and reported symptoms for anyone to try to make sense of out what's
here. Bug 10 is tracking a similar issue, but ONLY for:
* systems that freeze
@milton (#318): Yes, the freeze happens in other flavors. I'm running
Kubuntu and it happens on my T520.
Since you can move your mouse cursor, your problem is a different one
than the complete freeze reported here (and also in bug 10).
--
You received this bug notification because you are a
Hey... I know that two anecdotes don't make for good data, but it sure
looks like Willem's experience matches mine. I wonder if the root cause
is somehow USB-related?
I hope more people experiment with this. Let's see if we can figure out
a trend!
--
You received this bug notification because
Well, on day five with kernel 3.5rc2 (and _rc6=0 and _fbc=0), I finally
experienced a freeze. During the middle a VoIP call. So the root cause
of this nasty bug *still* appears unsolved.
QUESTION FOR ALL: has anyone experienced this problem while using a
machine that has *no* external USB devices
Well, I'm not sure we can know that the issue is confined to an
interaction between some X update and kernel 3.2. Many of us have tried
later kernels and still experience the problem.
I was planning to delay writing about my next experiment, but since the
issue of kernel versions came up again,
So today I went dockless... actually the only external device connected
was my USB headset. And I had yet another freeze. Curiously, it was
during a VoIP call.
Perhaps this bug is some nasty regression that gets triggered when an
external device is in use on systems with Intel graphics? I find it
@Danny Goodall (#279): Indeed, my freeze experiences have been only with
the laptop that I regularly dock, my ThinkPad T520. Connected to that
are an external monitor, mouse, and keyboard. I'd have to say I wouldn't
have thought to consider this arrangement to be a contributor to the
problem, but
Grr *@#$%! Moments after I typed #281, my T520 froze up. Again, during a
mouse movement. Thus, on the third day of my experiment, using kernel
3.4.1 as an attempt to expunge this problem has failed. Sigh.
I'll try disabling FBC now. I really don't want to give up the dock just
yet.
---
Holy
I just endured freeze #3 today. I wasn't even moving the mouse! I was on
a VoIP call (with Twinkle) and the audio went away. I knew the cause was
the same crash because all the other symptoms were present: mouse cursor
won't move, second hand on clock was stopped, no TTY switching, and
magic SysRq
@pureblood: I wish I could answer your questions, but alas, I cannot. I
can report that I enjoyed no crashes today. Two full days of no crashing
is a welcome relief. But like many folks chiming in here, I am at a loss
to understand the causes of these crashes, so I can't explain why 3.4.1
appears
There are muliple RC6 modes. From modinfo i915:
+
| parm: i915_enable_rc6:Enable power-saving render C-state 6.
Different stages
| can be selected via bitmask values (0 = disable; 1 = enable rc6; 2 = enable
deep rc6;
| 4 = enable deepest rc6). For example, 3 would enable
I see this bug is now filed under xserver-xorg-video-intel. Given that
the reports include all matter of graphics equipment, is that assignment
correct?
Anyway...given that I'm not sure, at this point, where else to report
some potential success, I thought I'd offer something here. This morning
I
More follow-up. Today, before starting my VM, I changed the VM's
settings. I selected Disable acceleration for binary translation and I
deselected Virtualize Intel VT-x/EPT or AMD-V/RVI.
And good news: no freezes! I've been moving my mouse about the desktop
with reckless abandon all day, and
I'm experiencing the total freeze bug. And it appears not to be Unity-
related, as I'm running Kubuntu. The complete freeze (no mouse, no
REISUB, no nothing) occurs with three different kernels:
* 3.2.0-25
* 3.4.0-030400 (Ubuntu mainline)
* 3.4.0-3 (from Xorg-Edgers)
I'm running the Xorg-Edgers
Following up to my #207... nope, changing mice didn't help. Just
experienced another complete freeze. Absolutely zero response, even
magic SysRq failed. This particular time I was on the 3.4.0-030400
kernel, had my VM open, and was dragging the mouse inside a Rekonq
window.
--
You received this
Public bug reported:
After updating to the latest packages in xorg-edgers, the KCM for the
touchpad crashes -- or, more precisely, causes a segfault 11 in
kcmshell4. I had to revert to an earlier version of the driver. Also,
tap-to-click doesn't work.
Broken version:
18 matches
Mail list logo
