All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 41503] New: Oops with Linux 3.0.0 and radeon driver: shmem_truncate_range
Date: Thu,  6 Oct 2011 02:06:41 -0700 (PDT)	[thread overview]
Message-ID: <bug-41503-502@http.bugs.freedesktop.org/> (raw)

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@lists.freedesktop.org
        ReportedBy: paulepanter@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-3/changelog#version3.0.0-3
[6]
http://packages.debian.org/changelogs/pool/non-free/f/firmware-nonfree/firmware-nonfree_0.33/changelog#version0.33

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2011-10-06  9:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06  9:06 bugzilla-daemon [this message]
2011-10-06 10:28 ` [Bug 41503] Oops with Linux 3.0.0 and radeon driver: shmem_truncate_range bugzilla-daemon
2011-10-06 10:32 ` bugzilla-daemon
2017-08-05 13:02 ` 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-41503-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.