https://bugzilla.kernel.org/show_bug.cgi?id=82431
Bug ID: 82431
Summary: Garbled screen on boot
Product: Drivers
Version: 2.5
Kernel Version: All after 3.13.6-20
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri(a)kernel-bugs.osdl.org
Reporter: fedevx(a)yahoo.com
Regression: No
When using any kernel higher than 3.13.6-20 (all the way to 3.16), my Toshiba
M840's screen gets garbled after Grub (grub itself is fine).
In particular, because my whole drive is encrypted, I see the garbled screen
when the prompt for the encryption key comes up.
I have the issue with my OpenSUSE installation and when booting off Archlinux's
installer.
I'm not sure if this is relevant but this happens on UEFI, if I change the
setting back to BIOS compatibility, at least on the Archlinux's installer, the
issue goes away. I can't test this on OpenSUSE since it is already set to UEFI
and will not boot on BIOS compatibility mode.
The issue has quite an impact since I can't bootup in a usable way, any Linux
distribution with a kernel newer than the one stated above.
I did a kernel bisect and found the below commit to be the cause of the issue:
[919cf555c04e16dafb1fba56904eb23889a812c3] drm/radeon: disable dpm on BTC
919cf555c04e16dafb1fba56904eb23889a812c3 is the first bad commit
commit 919cf555c04e16dafb1fba56904eb23889a812c3
Author: Alex Deucher <alexander.deucher(a)amd.com>
Date: Sat Jan 11 10:55:55 2014 -0500
drm/radeon: disable dpm on BTC
Still unstable on some boards.
Bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=73053https://bugzilla.kernel.org/show_bug.cgi?id=68571
Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com>
Cc: 3.13 <stable(a)vger.kernel.org> # 3.13
:040000 040000 c03cf693d8be0e49e0b431b968c4934324344d57
f4fa27f78f5ff03216036f8bcdc3978b274b812f M drivers
Thanks!
Details about my GFX card:
21: PCI 100.0: 0300 VGA compatible controller (VGA)
[Created at pci.319]
Unique ID: VCu0.dkF2+KIVH8C
Parent ID: vSkL.zuRwVyuZRN1
SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: graphics card
Model: "ATI VGA compatible controller"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0x6840
SubVendor: pci 0x1179 "Toshiba America Info Systems"
SubDevice: pci 0xfb81
Driver: "radeon"
Driver Modules: "drm"
Memory Range: 0xb0000000-0xbfffffff (ro,non-prefetchable)
Memory Range: 0xc0000000-0xc001ffff (rw,non-prefetchable)
I/O Ports: 0x3000-0x3fff (rw)
Memory Range: 0xc0040000-0xc005ffff (ro,non-prefetchable,disabled)
IRQ: 43 (76519 events)
Module Alias: "pci:v00001002d00006840sv00001179sd0000FB81bc03sc00i00"
Driver Info #0:
Driver Status: radeon is active
Driver Activation Cmd: "modprobe radeon"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #9 (PCI bridge)
-----------
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=50655
Bug #: 50655
Summary: ATI RV670 [Radeon HD 3870] Ioquake games causes GPU
lockup (waiting for 0x00003039 last fence id
0x00003030)
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: BryanQuigley(a)Ubuntu.com
Created attachment 62474
--> https://bugs.freedesktop.org/attachment.cgi?id=62474
kern.log
Tested and reproducible with Urban Terror, Warsow, and World of Padman. Used
phoronix test suite, and at some point during the run of each game, it would
either freeze or eventually display weird output to the screen (attached).
Occasionally a VT switch would let the game "appear" again. Other times you
can hear the sound of the game continue.
I am using the 3.4 kernel and drivers/X, etc from Xorg Edgers PPA, which for
the ati driver would be 6.14.99+git20120525.b1e9c308 and mesa is
8.1~git20120530.ff3eef1a.
You should be able to reproduce this by:
Installing phoronix test suite
(http://www.phoronix-test-suite.com/?k=downloads)
and then running: phoronix-test-suite benchmark urbanterror
(or warsow or padman)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=93821
Bug ID: 93821
Summary: radeonsi vaapi motion-adaptive deinterlace artifacts.
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: adf.lists(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 121204
--> https://bugs.freedesktop.org/attachment.cgi?id=121204&action=edit
highlighted artifacts.
Testing with mpv like -
mpv --hwdec=vaapi --vo=vaapi --vf=vavpp:deint=motion-adaptive ....
Produces artifacts which look like old buffers/pixels around the edges of
things get replayed in their old position if eg. the camera is panning.
The artifacts only appear in one field so those highlighted in the attached pic
would flash on/off if frame stepping with mpv.
The artifacts do not vary on a given sample whether it's frame stepped/slow
mo/normal speed.
Without pp or with deint=bob output is OK. (testing h264 as mpeg2 has it's own
issues).
Using motion-adaptive deint via vdpau does not have the issue.
Only mpv tested as I failed so far to get gstreamer to use pp.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=41503
Summary: Oops with Linux 3.0.0 and radeon driver:
shmem_truncate_range
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: paulepanter(a)users.sourceforge.net
Created an attachment (id=52032)
--> (https://bugs.freedesktop.org/attachment.cgi?id=52032)
Photo of monitor displaying Kernel messages like call trace
This report is a follow up for my message sent to the mailing list [1].
Unfortunately the Bugzilla instance of Linux [2] is still down due to the
security breach in August and therefore I am reporting this issue here in the
FreeDesktop Bugzilla [3].
Having a lot of windows open using the Awesome window manager [4] the X server
crashed printing the following to the monitor. Please see the attached image
for the complete message.
Pid: 1503, comm: Xorg Tainted: G C 3.0.0-1-amd64 #1 LENOVO
INVALID/Bali
[…]
Process Xorg (pid: 1503, threadinfo ffff88010c208000, task
ffff88011950d790
Stack:
[…]
Call Trace:
pagevec_move_tail+0x30/0x30
shmem_evict_inode+0x58/0xea
evict+0x7b/0x119
dentry_kill+0x136/0x155
dput+0xdb/0xea
fput+0x17b/0x1a2
remove_vma+0x3d/0x71
do_munmap+0x2da/0x2f3
sys_shmdt+0x9a/0x127
system_call_fastpath+0x16/0x1b
Code: 00 00 00 00 00 48 8b 94 24 a0 00 00 00 48 8d 45 28 48 ff 44 24 10
48 c7 44 24 50 00 00 …
RIP […] shmem_truncate_range+0x45c/0x6a1
RSP <ffff88010c209cf8>
Unfortunately for debugging this issue this is the first time it happened and
the issue is not reproducible.
Debian Wheezy/testing is running on this system with Linux 3.0.0-3 [5] and the
(non-free) firmware for the graphics card.
[1] http://lists.freedesktop.org/archives/dri-devel/2011-October/015011.html
[2] https://bugzilla.kernel.org/l
[3] https://bugs.freedesktop.org/
[4] http://awesome.naquadah.org/
[5]
http://packages.debian.org/changelogs/pool/main/l/linux-2.6/linux-2.6_3.0.0…
[6]
http://packages.debian.org/changelogs/pool/non-free/f/firmware-nonfree/firm…
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=62541
Bug ID: 62541
Summary: Kernel oops/panic during system boot with systemd -
"Unable to handle kernel NULL pointer dereference"
Product: Drivers
Version: 2.5
Kernel Version: 3.11
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri(a)kernel-bugs.osdl.org
Reporter: a.byszuk(a)elka.pw.edu.pl
Regression: No
Created attachment 110251
--> https://bugzilla.kernel.org/attachment.cgi?id=110251&action=edit
dmesg, lswh, .config outputs
Hello,
I have a bug (100 % repeatable) that prevents booting Linux when systemd is
used as an init system. However, booting with traditional init works fine.
I'm posting this bug to the DRI subsystem because I was (barely) able to
capture to capture kernel message before the screen becomes blank.
I can verify that this problem happens in all 3.11.x kernels and in Debian's
3.10 kernel.
The hardware is Dell Vostro 3560 - Intel Ivy Bridge, hybrid graphics (Intel +
Radeon), OCZ Vertex 4 SSD.
My suspicion is that maybe the system bootup is too fast for the kernel; I was
able to boot kernel once even with systemd, but that was when I turned on all
the debugging messages which flooded console a bit.
Photo of captured BUG message: http://s23.postimg.org/qgk843rzv/vga1.png
dmesg, lshw and .config outputs attached.
Kind regards,
Adrian
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73510
Priority: medium
Bug ID: 73510
Assignee: dri-devel(a)lists.freedesktop.org
Summary: ocl-toys smallptgpu example fails on r600
Severity: normal
Classification: Unclassified
OS: All
Reporter: fabian.deutsch(a)gmx.de
Hardware: Other
Status: NEW
Version: unspecified
Component: Drivers/Gallium/r600
Product: Mesa
The smallptgpu example from here ocltoys-linux64-v1.0.zip at
http://code.google.com/p/ocltoys/downloads/list
doesn't work:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6ab025d in clover::kernel::launch(clover::command_queue&,
std::vector<unsigned long, std::allocator<unsigned long> > const&,
std::vector<unsigned long, std::allocator<unsigned long> > const&,
std::vector<unsigned long, std::allocator<unsigned long> > const&) ()
from /usr/lib64/libMesaOpenCL.so.1
Missing separate debuginfos, use: debuginfo-install
elfutils-libelf-0.157-1.fc20.x86_64 expat-2.1.0-7.fc20.x86_64
libX11-1.6.1-1.fc20.x86_64 libXau-1.0.8-2.fc20.x86_64
libXdamage-1.1.4-4.fc20.x86_64 libXext-1.3.2-2.fc20.x86_64
libXfixes-5.0.1-2.fc20.x86_64 libXxf86vm-1.1.3-2.fc20.x86_64
libdrm-2.4.50-1.fc20.x86_64 libffi-3.0.13-5.fc20.x86_64
libgcc-4.8.2-7.fc20.x86_64 libselinux-2.2.1-6.fc20.x86_64
libstdc++-4.8.2-7.fc20.x86_64 libxcb-1.9.1-3.fc20.x86_64
llvm-libs-3.3-4.fc20.x86_64 mesa-dri-drivers-10.0.2-2.20140110.fc21.x86_64
mesa-libGL-10.0.2-2.20140110.fc21.x86_64
mesa-libOpenCL-10.0.2-2.20140110.fc21.x86_64
mesa-libOpenCL-devel-10.0.2-2.20140110.fc21.x86_64
mesa-libglapi-10.0.2-2.20140110.fc21.x86_64
ocl-icd-2.0.4-1.git20131001.4ee231e.fc20.x86_64 pcre-8.33-2.fc20.1.x86_64
systemd-libs-208-9.fc20.x86_64 xz-libs-5.1.2-6alpha.fc20.x86_64
zlib-1.2.8-3.fc20.x86_64
(gdb) bt
#0 0x00007ffff6ab025d in clover::kernel::launch(clover::command_queue&,
std::vector<unsigned long, std::allocator<unsigned long> > const&,
std::vector<unsigned long, std::allocator<unsigned long> > const&,
std::vector<unsigned long, std::allocator<unsigned long> > const&) ()
from /usr/lib64/libMesaOpenCL.so.1
#1 0x00007ffff6aab025 in clover::event::trigger() [clone .part.32] () from
/usr/lib64/libMesaOpenCL.so.1
#2 0x00007ffff6aabb48 in
clover::hard_event::hard_event(clover::command_queue&, unsigned int,
clover::ref_vector<clover::event> const&, std::function<void (clover::event&)>)
() from /usr/lib64/libMesaOpenCL.so.1
#3 0x00007ffff6acb8c9 in clEnqueueNDRangeKernel () from
/usr/lib64/libMesaOpenCL.so.1
#4 0x0000003eb62078ec in clEnqueueNDRangeKernel () from /lib64/libOpenCL.so.1
#5 0x0000000000454d7c in MandelGPU::UpdateMandel() ()
#6 0x0000000000455a84 in MandelGPU::RunToy() ()
#7 0x000000000045b1d6 in OCLToy::Run(int, char**) ()
#8 0x0000000000449057 in main ()
(gdb)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89282
Bug ID: 89282
Summary: new error messages 4.0-rc1 kernel
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: jarkko_korpi(a)hotmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
[ 17.407579] [drm] VGACON disable radeon kernel modesetting.
[ 17.407597] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon
module!
I don't know if those have impact, but they have never been there before.
r9 290
--
You are receiving this mail because:
You are the assignee for the bug.