Comment # 190
on bug 79980
from Daniel Kozak
(In reply to agapito from comment #189) > This is strange because 5 days ago i was starting to use intel graphic card > because i had a lot of lock-ups with 3.17.1 and 3.18 rc1 kernels. When 3.18 > rc2 was launched i returned to radeon driver and this bug disappeared under > 3.18 rc2, but now i am using 3.17.1 and it seems stable... Maybe this bug is > a mesa problem, and not a kernel problem. Mesa 10.3.2 arrived to archlinux 3 > days ago. > > Changes from 10.3.1 to 10.3.2: > > Brian Paul (3): > mesa: fix spurious wglGetProcAddress / GL_INVALID_OPERATION error > st/wgl: add WINAPI qualifiers on wgl function typedefs > glsl: fix several use-after-free bugs > > Daniel Manjarres (1): > glx: Fix glxUseXFont for glxWindow and glxPixmaps > > Dave Airlie (1): > mesa: fix GetTexImage for 1D array depth textures > > Emil Velikov (3): > docs: Add sha256 sums for the 10.3.1 release > Update VERSION to 10.3.2 > Add release notes for the 10.3.2 release > > Ilia Mirkin (4): > gm107/ir: add dnz emission for fmul > gk110/ir: add dnz flag emission for fmul/fmad > nouveau: 3d textures are unsupported, limit 3d levels to 1 > st/gbm: fix order of arguments passed to is_format_supported > > Kenneth Graunke (3): > i965: Add a BRW_MOCS_PTE #define. > i965: Use BDW_MOCS_PTE for renderbuffers. > i965: Fix register write checks. > > Marek Olšák (2): > st/mesa: use pipe_sampler_view_release for releasing sampler views > glsl_to_tgsi: fix the value of gl_FrontFacing with native integers > > Michel Dänzer (4): > radeonsi: Clear sampler view flags when binding a buffer > r600g,radeonsi: Always use GTT again for PIPE_USAGE_STREAM buffers > winsys/radeon: Use separate caching buffer manager for each set of > flags > r600g: Drop references to destroyed blend state I don't think so. I try tio downgrade mesa, linux-firmware and lots of other packages, but even with vdpau vlc, html5 youtube videos or flash videos I am unable to frozen my system again (I really try it hard all day). It must be some HW problem or some wierd HW state or something completly different.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
