https://bugs.freedesktop.org/show_bug.cgi?id=71753
Priority: medium
Bug ID: 71753
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Radeon Audio clock running wrong speed
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: fritsch(a)xbmc.org
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
When syncing radeon audio to a systemclock one realizes that it goes wrong
approximately 10ms per 6 seconds.
For example with 60hz and 50hz the audio clock is 10ms / 6 seconds too fast,
which causes great issues, when watching e.g. LiveTV.
When displaying at 24hz the audio clock is approximately 10ms / 6 seconds too
slow, which can be workarounded by doubling packages.
You can only realize this problem, if you don't use any resample algorithms to
make audio fit.
Some output from an xbmc.log:
Configuration: 50hz no sync playback to display.
Kernel 3.12 (Pierre Ossmann patch applied) with mesa git
19:46:13 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 -
was:62710358734.243919, should be:62710332298.764549, error:-26435.479370
19:46:16 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 -
was:62712528103.582550, should be:62712508710.849106, error:-19392.733447
19:46:17 T:139718566078208 DEBUG: CPullupCorrection: detected pattern of
length 1: 40000.00, frameduration: 40000.000000
19:46:22 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 -
was:62718996472.639107, should be:62719007584.295349, error:11111.656243
19:46:28 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 -
was:62725295876.976349, should be:62725306470.191048, error:10593.214698
19:46:35 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 -
was:62731698477.715050, should be:62731709235.032417, error:10757.317365
19:46:38 T:139719056176896 DEBUG: Thread JobWorker 139719056176896
terminating (autodelete)
19:46:41 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 -
was:62738297284.064415, should be:62738308465.384331, error:11181.319916
19:46:48 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 -
was:62744796455.484329, should be:62744807397.750954, error:10942.266624
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=71697
Priority: medium
Bug ID: 71697
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [radeonsi] gtkperf hangs the system
Severity: normal
Classification: Unclassified
OS: All
Reporter: darkbasic(a)linuxsystems.it
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
HD 7950
drm-next-3.13 (agd5f tree)
libdrm git
mesa git
xf86-video-ati git
xorg-server-1.14.4 + DRI-loader-entrypoint
glamor git
llvm 3.4 git
The system hangs about a minute after gtkperf started, there is nothing in
/var/log/messages.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=71067
Priority: medium
Bug ID: 71067
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [drm:r600] UVD not responding OR failed testing IB on
GFX ring
Severity: normal
Classification: Unclassified
OS: All
Reporter: timothee.romain.ravier(a)gmail.com
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
When I boot 3.10 or 3.11 kernels, I get either one of those errors, apparently
at random :
* UVD not responding, trying to reset the VCPU
-> Full log attached: *freeze-boot-then-yellow.log
The display turns yellow when the X server starts. I can still use VT and
there is no corruption there. I made sure that I got the latest firmware and I
also checked my initrd (following instructions in 65270);
* GPU lockup CP stall for more than 10000msec
GPU lockup (waiting for 0x000000000000020e last fence id
0x00000000000001ec)
r600_ib_test] *ERROR* radeon: fence wait failed (-35)
radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35)
-> Full log attached: *freeze-cursor.log
I can log into my graphical session, but quickly after that, everything
freeze and I can only move the cursor which displays as a "corrupted" square.
Again VT are fine.
I filed only one bug report as I get both issue using the same software and
boot command line.
At the beginning I had bug 67994, which turned into this one. I tried
downgrading the kernel without much success for now.
Booting with nomodeset works perfectly (with no accel/KMS obviously) and
booting under Windows 7 too.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=70543
Priority: medium
Bug ID: 70543
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [r600g] HD5450 + uvd + hdmi flickers
Severity: normal
Classification: Unclassified
OS: All
Reporter: stompdagger1(a)yahoo.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 87753
--> https://bugs.freedesktop.org/attachment.cgi?id=87753&action=edit
X's session log
I have a HD5450 hooked up to my lcd tv as part of a multiseat setup.
every few seconds the feed flickers.
usually I use xbmc to view content but it happens with VBox too.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=70542
Priority: medium
Bug ID: 70542
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [r600g] HD5450 + uvd + hdmi flickers
Severity: normal
Classification: Unclassified
OS: All
Reporter: stompdagger1(a)yahoo.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 87752
--> https://bugs.freedesktop.org/attachment.cgi?id=87752&action=edit
seat
greetings,
I have a HD5450 hooked up to my lcd tv as part of a multiseat setup.
every few seconds the feed flickers.
usually I use xbmc to view content but it happens with VBox too.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=70514
Priority: medium
Bug ID: 70514
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Unresponsive system on boot with radeon + FireGL v7700
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: noryb009(a)gmail.com
Hardware: x86 (IA32)
Status: NEW
Version: 9.2
Component: Drivers/Gallium/r600
Product: Mesa
I'm using a FireGL V7700 with Arch Linux x64. When booting to a command line,
when drivers are loaded, the screen goes into power saving mode, and the system
becomes unresponsive.
Booting with `nomodeset' works OK. If I run "$ modprobe radeon modeset=1", the
screen goes power saving mode, the system stops responding to open ssh
session(s), and the caps lock key no longer works (kernel panic?).
I've also tested with a Puppy Linux Live-CD, with the same results
(unresponsive on driver load).
I've tested a HD 4650 in the same system, and everything works fine.
$ lspci -v | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV670
GL [FireGL V7700] (prog-if 00 [VGA controller])
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=70286
Priority: medium
Bug ID: 70286
Assignee: dri-devel(a)lists.freedesktop.org
Summary: X crashes when using Firefox with logout loop
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: xgt008(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: DRI CVS
Component: DRM/Radeon
Product: DRI
Created attachment 87293
--> https://bugs.freedesktop.org/attachment.cgi?id=87293&action=edit
syslog during crash
Firefox 24, with hardware acceleration on, X crashes and the whole desktop
enters a logout loop. Restarting is the only way out :(.
I am running Ubunut 13.04 (linux mint 15) with Linux Kernel 3.11.4 with
radeon.dpm=1 and oibaf ppa (mesa-9.3-git) and Xorg 1.13.4
Attached are my syslog and Xorg.0.log during the crash.
Please let me know if I need to attach any further logs.
Here are some error messages that I found in these logs :
syslog :
[ 1807.720765] [drm:radeon_crtc_page_flip] *ERROR* failed to pin new rbo buffer
before flip
[ 1810.600061] radeon 0000:01:00.0: ffff88008c51ac00 pin failed
from Xorg.0.log :
[ 1839.182] (WW) RADEON(0): flip queue failed: Invalid argument
[ 1839.182] (WW) RADEON(0): Page flip failed: Invalid argument
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=70219
Priority: medium
Bug ID: 70219
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [radeon] Cannot restore video mode after vt switch or
GPU lockup
Severity: minor
Classification: Unclassified
OS: Linux (All)
Reporter: pupykin.s(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Steps to reproduce:
- boot using "radeon.modeset=1 video=DIN-1:1024x768-24@60e"
- switch off S-Video: "xrandr --output DIN --off"
- Ctrl+Alt+F1 - vt1 console appears
- Ctrl+Alt+F7 - monitor shows no video input
Workaround:
- Ctrl+Alt+F1 again
- login and export proper DISPLAY
- xrandr --output DIN --auto
- Ctrl+Alt+F7 - Xorg works
Booting with forced S-Video and switching it off from Xorg makes problem. Also
video mode cannot be restored in this case after GPU lockup. Restarting Xorg
from vt1 helps too.
Environment:
Arch Linux x86_64
linux 3.11.3-1
xorg-server 1.14.3-1
libdrm 2.4.46-2
xf86-video-ati 1:7.2.0-1
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=70203
Priority: medium
Bug ID: 70203
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Mobility Radeon HD 5430 identified as generic hdmi
Severity: normal
Classification: Unclassified
OS: All
Reporter: stompdagger1(a)yahoo.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
I have the following card:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Park
[Mobility Radeon HD 5430]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio
[Radeon HD 5400/6300 Series]
aplay -l returns this:
**** List of PLAYBACK Hardware Devices ****
card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
playing sound to hw:2,3 doesn't outputs sound to the screen but hw:1,3 does.
according to the alsa devs, the intel hda c file lacks the PCI IDs of many ATI
HDMI HDA devices (for example aa50/aa58/aa60/aa68/aa80/aa88/aa90/aa98:
Cypress/Juniper/Redwood/Cedar/Cayman+Antilles/Barts/Turks/Caicos)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=70165
Priority: medium
Bug ID: 70165
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Two GPU RV790, three screen setup locks up with dpm=1
Severity: normal
Classification: Unclassified
OS: All
Reporter: Mathias.Froehlich(a)web.de
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Hi,
I have here a dual radeon RV790 gpu, three screen setup. Tried this out with
dpm=1 locks up the machine. The lockup happens either when X starts and lightdm
starts to paint the login widget or, if the machine survives this, it usually
occurs once the mouse crosses the borders of the two gpu's screens on the X
display.
I run fedora 19 with a recent patch level.
The kernel that runs in dpm mode is 7dee8dff47734ee52da2cd8b8ea9736e42c5062f
which is todays linus master tree and includes all of agd5f/drm-fixes-3.12.
Attached are, dmesg with and without dpm enabled, Xorg logs with these cases,
the xorg configuraton file for these three screens, and the video bioses of
these two only similar cards. The dpm variants are acquired logged in via ssh
on a session where lightdm did not manage to lock up the machine at the first
time but locked it when I moved the mouse across the screen borders.
Some observations when digging somehow into this problem:
1. The attached patch shows a minimal change to rv770_dpm_set_power_state that
makes the machine run as normal. I think that already narrows down the problem
a bit.
2. The pi->clk_regs.rv770.mpll_ss{1,2} values are set into the table that aims
to be activated above, but are never initialized like the other values beneath
on rv770. May be they need to be read initially from some gpu register?
3. Disabling aspm does not help.
4. Unplugging the second monitor on the second gpu makes the problem appear way
more seldom if it stays unplugged. Hotplugging this screen results in the same
reproducible lockup.
Greetings
Mathias
--
You are receiving this mail because:
You are the assignee for the bug.