From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198511] lags in youtube videos 1080p 60fps with radeon hd4650 and kernel 4.15rc8
Date: Sat, 20 Jan 2018 15:59:29 +0000 [thread overview]
Message-ID: <bug-198511-2300-qsR7FmiVm7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198511-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198511
--- Comment #13 from Barto (mister.freeman@laposte.net) ---
the specs of my PC :
cpu : intel core 2 quad Q9650 ( 3 Ghz )
ram : 8 Gb DDR2
gpu : amd radeon HD4650 pcie
motherboard : gigabyte GA-P35-DS3L ( socket 775, chipset intel P35 )
window manager : plasma 5 ( kde )
OS : archlinux 64 bits
web browser : firefox 57.0.4 ( youtube in html5 mode, no flash plugin )
the output of "cat /proc/meminfo" when the bug occurs :
MemTotal: 8171844 kB
MemFree: 6188792 kB
MemAvailable: 6979356 kB
Buffers: 156940 kB
Cached: 780372 kB
SwapCached: 0 kB
Active: 1020160 kB
Inactive: 742148 kB
Active(anon): 647812 kB
Inactive(anon): 126472 kB
Active(file): 372348 kB
Inactive(file): 615676 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 5242876 kB
SwapFree: 5242876 kB
Dirty: 21768 kB
Writeback: 0 kB
AnonPages: 812840 kB
Mapped: 423408 kB
Shmem: 127600 kB
Slab: 73336 kB
SReclaimable: 46020 kB
SUnreclaim: 27316 kB
KernelStack: 6256 kB
PageTables: 29324 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 9328796 kB
Committed_AS: 2785064 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 0 kB
VmallocChunk: 0 kB
HardwareCorrupted: 0 kB
AnonHugePages: 145408 kB
ShmemHugePages: 0 kB
ShmemPmdMapped: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 187264 kB
DirectMap2M: 8200192 kB
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-01-20 15:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 19:54 [Bug 198511] New: lags in youtube videos 1080p 60fps with radeon hd4650 and kernel 4.15rc8 bugzilla-daemon
2018-01-18 19:56 ` [Bug 198511] " bugzilla-daemon
2018-01-18 19:57 ` bugzilla-daemon
2018-01-18 20:35 ` bugzilla-daemon
2018-01-18 20:58 ` bugzilla-daemon
2018-01-19 21:17 ` bugzilla-daemon
2018-01-19 21:18 ` bugzilla-daemon
2018-01-19 21:20 ` bugzilla-daemon
2018-01-19 22:09 ` bugzilla-daemon
2018-01-19 22:10 ` bugzilla-daemon
2018-01-20 1:26 ` bugzilla-daemon
2018-01-20 1:29 ` bugzilla-daemon
2018-01-20 4:11 ` bugzilla-daemon
2018-01-20 15:59 ` bugzilla-daemon [this message]
2018-01-20 17:33 ` bugzilla-daemon
2018-01-21 8:07 ` bugzilla-daemon
2018-01-21 9:50 ` bugzilla-daemon
2018-01-21 10:14 ` bugzilla-daemon
2018-01-21 15:06 ` bugzilla-daemon
2018-01-21 15:19 ` bugzilla-daemon
2018-01-21 15:50 ` bugzilla-daemon
2018-01-21 16:08 ` bugzilla-daemon
2018-01-21 16:35 ` bugzilla-daemon
2018-01-21 17:20 ` bugzilla-daemon
2018-01-21 17:48 ` bugzilla-daemon
2018-01-21 18:07 ` bugzilla-daemon
2018-01-21 19:17 ` bugzilla-daemon
2018-01-21 19:38 ` bugzilla-daemon
2018-01-22 3:01 ` bugzilla-daemon
2018-01-22 8:44 ` bugzilla-daemon
2018-02-10 23:28 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-198511-2300-qsR7FmiVm7@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.