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.
https://bugs.freedesktop.org/show_bug.cgi?id=84836
Bug ID: 84836
Summary: VERDE lockup with Unigine Valley/Heaven if
ARB_sample_shading is enabled
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: alexander(a)tsoy.me
Created attachment 107614
--> https://bugs.freedesktop.org/attachment.cgi?id=107614&action=edit
dmesg output
Unigine Valley 1.0 and Heaven 4.0 cause VERDE GPU lockup when
ARB_sample_shading is enabled. With kernel 3.14.19 I got immediate lockup.
3.14.20 allows Valley and Heaven to run for up to 1 min. GPU fails to resume
after lockup, screen becomes corrupted and I need to reboot the system.
If I disable ARB_sample_shading (via env variable
MESA_EXTENSION_OVERRIDE=-GL_ARB_sample_shading) then VERDE GPU do not hang at
all (currently valley is running on my system for more than two hours without
lockups).
I also have BONAIRE GPU and it does not hang.
Software versions:
kernel-3.14.20
mesa-10.3.0
llvm-3.5
xf86-video-ati 7.4.0
libdrm-2.4.56
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76382
Priority: medium
Bug ID: 76382
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Mesa Gallium egllog _eglLog
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: f1r31c3r(a)gmail.com
Hardware: All
Status: NEW
Version: 9.0
Component: Drivers/Gallium/i915g
Product: Mesa
Hi all.
Sorry in advance for any spelling blurb as i am using match sticks to hold me
eyes open.
I found a bug in the mesa, particularly related to the include files used in
src/gallium/x11
files that contain the include egllog.h that define _elLog cant find the it.
Not sure if the environment variable set for the source code under the gallium
directory is not set right.
Put simply even though the include is specified in the source file it does not
actually include it and hence the compile fails due to "undefined reference
_eglLog"
Seems that it only ever fails to compile when gallium has been enabled. egl
enabled with gles1 and 2 is fine but enable gallium and the compile error
occurs.
Hope it helps.
--
You are receiving this mail because:
You are the assignee for the bug.