(In reply to Mikhail Novosyolov from comment #59)
> You mean that when e.g. Chromium browser writes its cache, it loads IO "up
> to 10x higher than EXT4"
Yes. This is also true for read operations, not only for write.
> and, when IO is also loaded by swapping, it causes
> microfreezes?
Yes, prob
I have an idea why this bug is much worse with BTRFS than with EXT4:
BTRFS has much bigger read/write amplification, up to 10x higher than
EXT4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833281
T
Recently, about since kernel 5.2.7, the issue is either gone or present to much
less extent.
Right now I'm running kernel 5.2.11 and finally I can keel Firefox and
VirtualBox running at the same time, with 3G+ in swap, and the system does not
freeze.
Could anyone affected by this issue try newe
(In reply to Luca from comment #40)
> I switched from BTRFS to EXT4 and this did seem to solve the problem, at
> least for me.
Do you use swap file or swap partition? I use swap partition, so it
shouldn't matter, but I indeed have btrfs for /.
--
You received this bug notification because you ar
These lockups are probably not related to this bug. I've updated by Intel Sandy
Bridge laptop to 4.17.5 from Fedora 28 repository and now I have random CPU
lockups, too.
4.17.3 worked fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
For me, this fixes slowdown which I wrote in the first message. There is
2 other bugs: screen corruption with gles and incorrect screen
repainting with gl. And I don't know if it's MESA or KDE bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
(In reply to comment #83)
> In other news, I just noticed something: for some reason my video's were
> tearing even when using the vaapi and gl outputs just now. This was with
> kernel-3.4+drm-intel-next-2012-05-20.
> Toggling the resolution with xrandr fixed it. I don't know how or why it
> stoppe
(In reply to comment #81)
With this new version I have no tearing on 1366x768, 1024x768, 800x600
fullscreen. But, of course, still have in windowed mode. I have rc6 enabled,
and there is tearing on top of the screen. With rc6=0 I have only one top pixel
line tearing.
--
You received this bug n
(In reply to comment #78)
> As I expected, then.
>
> I picked 800x600 because every laptop should be able to set that mode, but by
> all means switch it around. :-)
There is tearing in fullscreen with 800x600. That's definitely 16:9
problem for me.
> In the meantime, maybe we should switch to us
(In reply to comment #76)
> Those are movies, and the test program I'm using that doesn't tear doesn't
> play
> any movies, it just does raw GL output. mplayer *does* tear in fullscreen, but
> that's because it doesn't actually set the fullscreen bit.
I have no tearing in mplayer in fullscreen if
(In reply to comment #74)
> I have no tearing on GL in fullscreen.
Please test it with tearing test 720x406 from
https://bugs.freedesktop.org/show_bug.cgi?id=43674
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
(In reply to comment #72)
> Just as an update from the past post.
>
> Unfortunately, all my attempts for fixing this properly have failed so far,
> the
> hardware does not wants to collaborate with the software for inter-ring
> synchronization.
>
> So the workaround I used previously still appli
(In reply to comment #68)
> Hello,
>
> I was unable to reproduce the bug on Fedora 17 with Gnome Shell.
Take a look
https://bugs.freedesktop.org/show_bug.cgi?id=43674
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Please take a look at this bug
https://bugs.freedesktop.org/show_bug.cgi?id=43674 and confirm it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/755841
Title:
[sandybridge] Graphics tearing when play
Public bug reported:
THing is yust fucked up!
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/create.py", line 302, in forward
if(self.validate(notebook.get_current_page()) != True):
File "/usr/share/virt-manager/virtManager/create.py", line 1005, in validate
15 matches
Mail list logo
