All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83708] New: mplayer plays video using gpu hardware acceleraing(vdpau,uvd) kernel panic, Unable to handle kernel paging request at virtual address
Date: Wed, 10 Sep 2014 11:02:53 +0000	[thread overview]
Message-ID: <bug-83708-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 6559 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=83708

          Priority: medium
            Bug ID: 83708
          Assignee: dri-devel@lists.freedesktop.org
           Summary: mplayer plays video using gpu hardware
                    acceleraing(vdpau,uvd) kernel panic, Unable to handle
                    kernel paging request at virtual address
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: zduo006@163.com
          Hardware: SPARC
            Status: NEW
           Version: 9.2
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

Created attachment 106051
  --> https://bugs.freedesktop.org/attachment.cgi?id=106051&action=edit
kernel panic messages

Hi, I try to using gpu hardware accelerate to play video from mplayer
(vdpau+uvd)  . The machine architecture is sparc64,video card is radeon
HD7450,OS version is redhat7,kernel version is 3.10.0, mplayer version is
1.1-21,mesa version is 9.2.5-6. But everything is ok on X86 platforms, all
versions are the same.
         The kernel panic occured when radeon call radeon_cs_ioctl to receive
the command stream from libdrm interface. and then radeon_cs_ib_chunk() call
radeon_uvd_cs_parse to parse the command.
         First I thought this error maybe occured in a permanent position and
maybe the ioctl data or size mismatch between user space and kernel space ，I
set 1 to /sys/module/drm/para... to open drm debug switch , after I catch the
messages, the panic occur  everywhere .the error context maybe after
RADEON_GEM_WAIT_IDLE? after RADEON_GEM_CREATE and so forth. so is not the data
stream error during ioctl.
        And I check the changelog from 3.10 to 3.15, no patch about this.
        Other, I run rpm -e mesa-vdpau-drivers to uninstall the devices driver
from mesa ,the mplayer can play video  stably using cpu , when I install this
package,the blue screen is come out . and I must run mplayer -vo x11 to solve
the blue screen problem.
       Because I am not clearly about the framework of the mesa-vdpau-driver
and uvd. Can anyone help me ? Thks 

the error messages is below:
pid=3037, dev=0xe200, auth=1, RADEON_GEM_WAIT_IDLE
Oct  8 21:43:26 localhost kernel: [17318.899669] pid=4483, dev=0xe200, auth=1,
RADEON_GEM_WAIT_IDLE
Oct  8 21:43:26 localhost kernel: [17318.902069] Unable to handle kernel paging
request at virtual address 000000ca14312000
Oct  8 21:43:26 localhost kernel: [17318.902090] tsk->{mm,active_mm}->context =
0000000000000a2b
Oct  8 21:43:26 localhost kernel: [17318.902104] tsk->{mm,active_mm}->pgd =
fffff80008f90000
Oct  8 21:43:26 localhost kernel: [17318.902119]               \|/ ____ \|/
Oct  8 21:43:26 localhost kernel: [17318.902119]               "@'/ .. \`@"
Oct  8 21:43:26 localhost kernel: [17318.902119]               /_| \__/ |_\
Oct  8 21:43:26 localhost kernel: [17318.902119]                  \__U_/
Oct  8 21:43:26 localhost kernel: [17318.902169] mplayer(4483): Oops [#1]
Oct  8 21:43:26 localhost kernel: [17318.902186] CPU: 28 PID: 4483 Comm:
mplayer Not tainted 3.10.0-54.0.1.el7.4ACL.sparc64 #1
Oct  8 21:43:26 localhost kernel: [17318.902201] task: fffff800faa2a200 ti:
fffff800fbec4000 task.ti: fffff800fbec4000
Oct  8 21:43:26 localhost kernel: [17318.902220] TSTATE: 0000004411001607 TPC:
00000000007f573c TNPC: 00000000007f5740 Y: 00000000    Not tainted
Oct  8 21:43:26 localhost kernel: [17318.902252] TPC:
<radeon_uvd_cs_parse+0x414/0x7b4>
Oct  8 21:43:26 localhost kernel: [17318.902267] g0: 0000000000083a15 g1:
000000ca14312000 g2: 000000ca14312000 g3: 0000000004314000
Oct  8 21:43:26 localhost kernel: [17318.902285] g4: fffff800faa2a200 g5:
fffff800fc2fe000 g6: fffff800fbec4000 g7: 0000000010000000
Oct  8 21:43:26 localhost kernel: [17318.902301] o0: 0000000000000000 o1:
fffff800fbec7860 o2: 0000000000000000 o3: 0000000004314000
Oct  8 21:43:26 localhost kernel: [17318.902317] o4: 0000000000000800 o5:
fffff800f62d4840 sp: fffff800fbec6f91 ret_pc: 00000000007f56f4
Oct  8 21:43:26 localhost kernel: [17318.902336] RPC:
<radeon_uvd_cs_parse+0x3cc/0x7b4>
Oct  8 21:43:26 localhost kernel: [17318.902352] l0: fffff80008dbbbc0 l1:
0000000000a213c8 l2: 0000000000000003 l3: 0000000000000001
Oct  8 21:43:26 localhost kernel: [17318.902366] l4: 000000000000ef10 l5:
0000000000d7fb10 l6: 0000000000d7fae8 l7: 0000000000d7fac8
Oct  8 21:43:26 localhost kernel: [17318.902382] i0: fffff800fbec7948 i1:
0000000000000000 i2: 000000000000ec00 i3: fffff800e30b9000
Oct  8 21:43:26 localhost kernel: [17318.902398] i4: 000000ca14312000 i5:
0000000000000000 i6: fffff800fbec7091 i7: 00000000007a1e5c
Oct  8 21:43:26 localhost kernel: [17318.902429] I7:
<radeon_cs_ioctl+0x394/0x930>
Oct  8 21:43:26 localhost kernel: [17318.902439] Call Trace:
Oct  8 21:43:26 localhost kernel: [17318.902458]  [00000000007a1e5c]
radeon_cs_ioctl+0x394/0x930
Oct  8 21:43:26 localhost kernel: [17318.902486]  [000000000073d1ac]
drm_ioctl+0x2fc/0x420
Oct  8 21:43:26 localhost kernel: [17318.902516]  [0000000000518c94]
vfs_ioctl+0x24/0x40
Oct  8 21:43:26 localhost kernel: [17318.902537]  [0000000000519518]
do_vfs_ioctl+0x440/0x4e0
Oct  8 21:43:26 localhost kernel: [17318.902560]  [00000000005195e4]
SyS_ioctl+0x2c/0x50
Oct  8 21:43:26 localhost kernel: [17318.902588]  [00000000004061b4]
linux_sparc_syscall+0x34/0x44
Oct  8 21:43:26 localhost kernel: [17318.902607] Disabling lock debugging due
to kernel taint
Oct  8 21:43:26 localhost kernel: [17318.902633] Caller[00000000007a1e5c]:
radeon_cs_ioctl+0x394/0x930
Oct  8 21:43:26 localhost kernel: [17318.902657] Caller[000000000073d1ac]:
drm_ioctl+0x2fc/0x420
Oct  8 21:43:26 localhost kernel: [17318.902681] Caller[0000000000518c94]:
vfs_ioctl+0x24/0x40
Oct  8 21:43:26 localhost kernel: [17318.902702] Caller[0000000000519518]:
do_vfs_ioctl+0x440/0x4e0
Oct  8 21:43:26 localhost kernel: [17318.902721] Caller[00000000005195e4]:
SyS_ioctl+0x2c/0x50
Oct  8 21:43:26 localhost kernel: [17318.902742] Caller[00000000004061b4]:
linux_sparc_syscall+0x34/0x44
Oct  8 21:43:26 localhost kernel: [17318.902757] Caller[fffff801086074ac]:
0xfffff801086074ac
Oct  8 21:43:26 localhost kernel: [17318.902765] Instruction DUMP: 913b6000 
c25fa7cf  b800401c <e0072008> 80a42000  12480007  fa072004  11002884  130035fe 
Oct  8 21:43:30 localhost kernel: [17323.141686] pid=3037, dev=0xe200, auth=1,
RADEON_GEM_CREATE

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 8171 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-09-10 11:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-10 11:02 bugzilla-daemon [this message]
2014-09-11  2:15 ` [Bug 83708] [vdpau,uvd] kernel oops, Unable to handle kernel paging request at virtual address bugzilla-daemon
2014-09-18  6:54 ` bugzilla-daemon
2014-09-18  6:55 ` bugzilla-daemon
2014-09-18  6:55 ` bugzilla-daemon
2014-09-18  6:56 ` bugzilla-daemon
2014-09-18  7:18 ` bugzilla-daemon
2014-09-18  7:28 ` bugzilla-daemon
2014-09-18 12:41 ` bugzilla-daemon
2014-09-20  4:09 ` bugzilla-daemon
2014-09-20  4:09 ` bugzilla-daemon
2014-09-20  4:10 ` bugzilla-daemon
2014-09-22  8:59 ` bugzilla-daemon
2014-09-23 13:00 ` bugzilla-daemon
2014-09-24  9:28 ` bugzilla-daemon
2014-09-24 15:18 ` bugzilla-daemon
2014-09-25  2:18 ` bugzilla-daemon
2014-09-25  7:26 ` bugzilla-daemon
2014-09-28 12:01 ` bugzilla-daemon
2014-09-29  7:16 ` bugzilla-daemon
2019-11-19  8:55 ` 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-83708-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.