Am Mittwoch, den 05.10.2011, 11:21 +0200 schrieb Michel Dänzer:
On Mit, 2011-10-05 at 10:54 +0200, Paul Menzel wrote:
the Linux kernel showed an Oops with the following call trace, which I copied from a picture taken from the screen.
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>The machine runs Debian Wheezy/testing.
Could you please point me to the right platform to report this? Is that a Linux Kernel issue or a Freedesktop issue?
The above looks like the former.
Thank you. Unfortunately my question was rather pointless as the Bugzilla instance at kernel.org still has not been set up again after the security breach in August.
Therefore I reported this issue to FreeDesktop’s Bugzilla as #41503 [1].
What component should I file this against?
I'm not sure, but I wouldn't start with the radeon driver; why do you think it's related to that?
I do not know. I though when the X server crashes or causes a Linux oops then it is most likely a driver issue.
It would be great if someone with more insight can set the meta tags appropriately and I am sorry for having to ignore your advise twice.
Thanks,
Paul