Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
On 12/25/2012 06:50 AM, Shuah Khan wrote: On Sun, Dec 23, 2012 at 6:31 AM, Borislav Petkov wrote: On Sun, Dec 23, 2012 at 01:22:12PM +0100, Borislav Petkov wrote: Right, let me try that and report back. Yep, looks like reverting the above commit fixes it - the boston.com website loads just fine. Thanks. -- Regards/Gruss, Boris. Saw the same error and after reading this thread, reverted the Commit 2d6cc7296d4ee128ab0fa3b715f0afde511f49c2. drm/radeon: use async dma for ttm buffer moves on 6xx-SI and the problem is gone. In my case, it is a solid hang right after system switches to vga. I was able to login on console once or twice. But dmesg showed the same message reported in this thread: [ 35.812085] radeon :01:00.0: GPU lockup CP stall for more than 1msec [ 35.812091] radeon :01:00.0: GPU lockup (waiting for 0x0002 last fence id 0x0001) My system has: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] I ended up also that same commit after bisecting from current 3.8 master. 01:05.0 VGA compatible controller: ATI Technologies Inc 760G [Radeon 3000] It is ASUS M5A78L-M/USB3 with integrated GPU. I cannot even boot unless graphical boot is removed from Fedora 17 boot options (rhgb quiet). Random GPU crashes still. regards Antti -- http://palosaari.fi/ ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
On 01/02/2013 07:19 PM, Jerome Glisse wrote: On Wed, Jan 2, 2013 at 7:02 AM, Borislav Petkov wrote: On Wed, Jan 02, 2013 at 03:42:20AM +0200, Antti Palosaari wrote: I ended up also that same commit after bisecting from current 3.8 master. 01:05.0 VGA compatible controller: ATI Technologies Inc 760G [Radeon 3000] It is ASUS M5A78L-M/USB3 with integrated GPU. I cannot even boot unless graphical boot is removed from Fedora 17 boot options (rhgb quiet). Random GPU crashes still. You could try the temporary R600-only fix although I can't see whether your GPU is also an R600 ASIC or something different by staring at the model string above: http://marc.info/?l=dri-devel&m=135628734704029 HTH. -- Regards/Gruss, Boris. How do you trigger the issue ? Does it happens right away on boot ? Cheers, Jerome Sorry for utterly unclear description. I meant it randomly crashes desktop in case I got it booting by removing graphical boot option. In that case Cinnamon desktop "freezes", I was able to move mouse cursor but clicking buttons or moving windows etc. didn't worked at all. Only mouse cursor moves. It was possible to switch to console by ctrl+alt+fN. When Fedora graphical boot was enabled (options rhgb quiet) and I selected Kernel from the grub, it makes just blank screen and after 10sec or so monitor switches off saying "no signal". Nothing happened after that, boot was forced. I use dm-crypt and normally about the first thing is to show is graphical lock screen asking passphrase. I did some grepping from the syslog and that same message is seen: Jan 2 03:35:34 localhost kernel: [ 1164.433117] radeon :01:05.0: GPU lockup CP stall for more than 1msec Jan 2 03:35:34 localhost kernel: [ 1164.433121] radeon :01:05.0: GPU lockup (waiting for 0x0003 last fence id 0x0002) After I reverted bisected patch it has been working just fine. I has been running whole day without problems. regards Antti -- http://palosaari.fi/ ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
On 01/03/2013 01:59 AM, Alex Deucher wrote: On Wed, Jan 2, 2013 at 6:58 PM, Shuah Khan wrote: On Wed, Jan 2, 2013 at 4:37 PM, Alex Deucher wrote: On Wed, Jan 2, 2013 at 5:38 PM, Markus Trippelsdorf wrote: On 2013.01.02 at 17:31 -0500, Jerome Glisse wrote: Please affected people can you test if patch : http://people.freedesktop.org/~glisse/0003-drm-radeon-fix-dma-copy-on-r6xx-r7xx-evergen-ni-si-g.patch Fix the issue, you need to make sure you don't have the patch that disable dma on r6xx ie that line 977-978 & 1061-1062 in radeon_asic.c is : .copy = &r600_copy_dma, .copy_ring_index = R600_RING_TYPE_DMA_INDEX, It fixes the issue for me. Thanks. The count is actually the count, not count - 1. The real fix seems to be that r6xx requires 2 dw aligned transfers. The attached patch fixes the issue for me. Catching up with this thread. I reverted the drm/radeon: use async dma for ttm buffer moves on 6xx-SI commit id: 2d6cc7296d4ee128ab0fa3b715f0afde511f49c2 Do I need to apply this patch without reverting 2d6cc7296d4ee128ab0fa3b715f0afde511f49c2? Correct. Don't revert anything. Just apply this patch. Tested, it is working. I didn't revert anything, just added that latest patch. regards Antti -- http://palosaari.fi/ ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: radeon regression 3.11.0-rc2+
On 07/24/2013 04:24 PM, Alex Deucher wrote: On Tue, Jul 23, 2013 at 6:22 PM, Antti Palosaari wrote: Hello I just upgraded Kernel from 3.10.0-rc6+ to 3.11.0-rc2+ and ran serious problems. That Kernel is current Linux Media master, which contains some upcoming media stuff that should not still has any effect, but lets mention for sure. Display started freezing and gone black, I think two times. Next freeze led to effect screen was full of very colourful boxes. It recognized mouse moves but text was unable to read so I was forced to hard boot to old Kernel. Attached log contains stuff I found from the debug log. Can you try my latest fixes branch: http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-fixes-3.11 If that doesn't help, can you bisect? It has been running that branch 4 hours without errors. Bug seems to be fixed! regards Antti -- http://palosaari.fi/ ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] drm/kms: add a module param to disable strict EDID checking
Hey, Could you say what's status of fixing that problem? I see Alex patch is not included to the Kernel for the some reason. Could you point out what is recommended workaround for that bug as now? I have that known bad behaving Acer AL2216W monitor... regards Antti -- http://palosaari.fi/ ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] drm/kms: add a module param to disable strict EDID checking
Hey, Could you say what's status of fixing that problem? I see Alex patch is not included to the Kernel for the some reason. Could you point out what is recommended workaround for that bug as now? I have that known bad behaving Acer AL2216W monitor... regards Antti -- http://palosaari.fi/
radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
On 12/25/2012 06:50 AM, Shuah Khan wrote: > On Sun, Dec 23, 2012 at 6:31 AM, Borislav Petkov wrote: >> On Sun, Dec 23, 2012 at 01:22:12PM +0100, Borislav Petkov wrote: >>> Right, let me try that and report back. >> >> Yep, looks like reverting the above commit fixes it - the boston.com >> website loads just fine. >> >> Thanks. >> >> -- >> Regards/Gruss, >> Boris. > > Saw the same error and after reading this thread, reverted the > > Commit 2d6cc7296d4ee128ab0fa3b715f0afde511f49c2. > > drm/radeon: use async dma for ttm buffer moves on 6xx-SI > > and the problem is gone. In my case, it is a solid hang right after > system switches to vga. I was able to login on console once or twice. > But dmesg showed the same message reported in this thread: > > [ 35.812085] radeon :01:00.0: GPU lockup CP stall for more than > 1msec > [ 35.812091] radeon :01:00.0: GPU lockup (waiting for > 0x0002 last fence id 0x0001) > > > My system has: > 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee > ATI RV620 [Mobility Radeon HD 3400 Series] I ended up also that same commit after bisecting from current 3.8 master. 01:05.0 VGA compatible controller: ATI Technologies Inc 760G [Radeon 3000] It is ASUS M5A78L-M/USB3 with integrated GPU. I cannot even boot unless graphical boot is removed from Fedora 17 boot options (rhgb quiet). Random GPU crashes still. regards Antti -- http://palosaari.fi/
radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
On 01/02/2013 07:19 PM, Jerome Glisse wrote: > On Wed, Jan 2, 2013 at 7:02 AM, Borislav Petkov wrote: >> On Wed, Jan 02, 2013 at 03:42:20AM +0200, Antti Palosaari wrote: >>> I ended up also that same commit after bisecting from current 3.8 >>> master. >>> >>> 01:05.0 VGA compatible controller: ATI Technologies Inc 760G [Radeon >>> 3000] It is ASUS M5A78L-M/USB3 with integrated GPU. >>> >>> I cannot even boot unless graphical boot is removed from Fedora 17 >>> boot options (rhgb quiet). Random GPU crashes still. >> >> You could try the temporary R600-only fix although I can't see whether >> your GPU is also an R600 ASIC or something different by staring at the >> model string above: >> >> http://marc.info/?l=dri-devel&m=135628734704029 >> >> HTH. >> >> -- >> Regards/Gruss, >> Boris. > > How do you trigger the issue ? Does it happens right away on boot ? > > Cheers, > Jerome Sorry for utterly unclear description. I meant it randomly crashes desktop in case I got it booting by removing graphical boot option. In that case Cinnamon desktop "freezes", I was able to move mouse cursor but clicking buttons or moving windows etc. didn't worked at all. Only mouse cursor moves. It was possible to switch to console by ctrl+alt+fN. When Fedora graphical boot was enabled (options rhgb quiet) and I selected Kernel from the grub, it makes just blank screen and after 10sec or so monitor switches off saying "no signal". Nothing happened after that, boot was forced. I use dm-crypt and normally about the first thing is to show is graphical lock screen asking passphrase. I did some grepping from the syslog and that same message is seen: Jan 2 03:35:34 localhost kernel: [ 1164.433117] radeon :01:05.0: GPU lockup CP stall for more than 1msec Jan 2 03:35:34 localhost kernel: [ 1164.433121] radeon :01:05.0: GPU lockup (waiting for 0x0003 last fence id 0x0002) After I reverted bisected patch it has been working just fine. I has been running whole day without problems. regards Antti -- http://palosaari.fi/
radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec
On 01/03/2013 01:59 AM, Alex Deucher wrote: > On Wed, Jan 2, 2013 at 6:58 PM, Shuah Khan wrote: >> On Wed, Jan 2, 2013 at 4:37 PM, Alex Deucher >> wrote: >>> On Wed, Jan 2, 2013 at 5:38 PM, Markus Trippelsdorf >>> wrote: On 2013.01.02 at 17:31 -0500, Jerome Glisse wrote: > Please affected people can you test if patch : > http://people.freedesktop.org/~glisse/0003-drm-radeon-fix-dma-copy-on-r6xx-r7xx-evergen-ni-si-g.patch > > Fix the issue, you need to make sure you don't have the patch that > disable dma on r6xx ie that line 977-978 & 1061-1062 in radeon_asic.c > is : > .copy = &r600_copy_dma, > .copy_ring_index = R600_RING_TYPE_DMA_INDEX, It fixes the issue for me. Thanks. >>> >>> The count is actually the count, not count - 1. The real fix seems to >>> be that r6xx requires 2 dw aligned transfers. The attached patch >>> fixes the issue for me. >>> >> >> Catching up with this thread. I reverted the >> >> drm/radeon: use async dma for ttm buffer moves on 6xx-SI >> commit id: 2d6cc7296d4ee128ab0fa3b715f0afde511f49c2 >> >> Do I need to apply this patch without reverting >> 2d6cc7296d4ee128ab0fa3b715f0afde511f49c2? > > Correct. Don't revert anything. Just apply this patch. Tested, it is working. I didn't revert anything, just added that latest patch. regards Antti -- http://palosaari.fi/
[PATCH 4/4] media: cxd2820r: use DIV_ROUND_CLOSEST_ULL()
On 03/20/2015 01:14 PM, Javi Merino wrote:
> Now that the kernel provides DIV_ROUND_CLOSEST_ULL(), drop the internal
> implementation and use the kernel one.
>
> Cc: Antti Palosaari
> Cc: Mauro Carvalho Chehab
> Signed-off-by: Javi Merino
Acked-by: Antti Palosaari
Reviewed-by: Antti Palosaari
Antti
> ---
> I've only compile-tested it, I don't have the hardware to run it.
>
> drivers/media/dvb-frontends/cxd2820r_c.c| 2 +-
> drivers/media/dvb-frontends/cxd2820r_core.c | 6 --
> drivers/media/dvb-frontends/cxd2820r_priv.h | 2 --
> drivers/media/dvb-frontends/cxd2820r_t.c| 2 +-
> drivers/media/dvb-frontends/cxd2820r_t2.c | 2 +-
> 5 files changed, 3 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/media/dvb-frontends/cxd2820r_c.c
> b/drivers/media/dvb-frontends/cxd2820r_c.c
> index 149fdca3fb44..72b0e2db3aab 100644
> --- a/drivers/media/dvb-frontends/cxd2820r_c.c
> +++ b/drivers/media/dvb-frontends/cxd2820r_c.c
> @@ -79,7 +79,7 @@ int cxd2820r_set_frontend_c(struct dvb_frontend *fe)
>
> num = if_freq / 1000; /* Hz => kHz */
> num *= 0x4000;
> - if_ctl = 0x4000 - cxd2820r_div_u64_round_closest(num, 41000);
> + if_ctl = 0x4000 - DIV_ROUND_CLOSEST_ULL(num, 41000);
> buf[0] = (if_ctl >> 8) & 0x3f;
> buf[1] = (if_ctl >> 0) & 0xff;
>
> diff --git a/drivers/media/dvb-frontends/cxd2820r_core.c
> b/drivers/media/dvb-frontends/cxd2820r_core.c
> index 422e84bbb008..490e090048ef 100644
> --- a/drivers/media/dvb-frontends/cxd2820r_core.c
> +++ b/drivers/media/dvb-frontends/cxd2820r_core.c
> @@ -244,12 +244,6 @@ error:
> return ret;
> }
>
> -/* 64 bit div with round closest, like DIV_ROUND_CLOSEST but 64 bit */
> -u32 cxd2820r_div_u64_round_closest(u64 dividend, u32 divisor)
> -{
> - return div_u64(dividend + (divisor / 2), divisor);
> -}
> -
> static int cxd2820r_set_frontend(struct dvb_frontend *fe)
> {
> struct cxd2820r_priv *priv = fe->demodulator_priv;
> diff --git a/drivers/media/dvb-frontends/cxd2820r_priv.h
> b/drivers/media/dvb-frontends/cxd2820r_priv.h
> index 7ff5f60c83e1..4b428959b16e 100644
> --- a/drivers/media/dvb-frontends/cxd2820r_priv.h
> +++ b/drivers/media/dvb-frontends/cxd2820r_priv.h
> @@ -64,8 +64,6 @@ int cxd2820r_wr_reg_mask(struct cxd2820r_priv *priv, u32
> reg, u8 val,
> int cxd2820r_wr_regs(struct cxd2820r_priv *priv, u32 reginfo, u8 *val,
> int len);
>
> -u32 cxd2820r_div_u64_round_closest(u64 dividend, u32 divisor);
> -
> int cxd2820r_wr_regs(struct cxd2820r_priv *priv, u32 reginfo, u8 *val,
> int len);
>
> diff --git a/drivers/media/dvb-frontends/cxd2820r_t.c
> b/drivers/media/dvb-frontends/cxd2820r_t.c
> index 51401d036530..008cb2ac8480 100644
> --- a/drivers/media/dvb-frontends/cxd2820r_t.c
> +++ b/drivers/media/dvb-frontends/cxd2820r_t.c
> @@ -103,7 +103,7 @@ int cxd2820r_set_frontend_t(struct dvb_frontend *fe)
>
> num = if_freq / 1000; /* Hz => kHz */
> num *= 0x100;
> - if_ctl = cxd2820r_div_u64_round_closest(num, 41000);
> + if_ctl = DIV_ROUND_CLOSEST_ULL(num, 41000);
> buf[0] = ((if_ctl >> 16) & 0xff);
> buf[1] = ((if_ctl >> 8) & 0xff);
> buf[2] = ((if_ctl >> 0) & 0xff);
> diff --git a/drivers/media/dvb-frontends/cxd2820r_t2.c
> b/drivers/media/dvb-frontends/cxd2820r_t2.c
> index 9c0c4f42175c..35fe364c7182 100644
> --- a/drivers/media/dvb-frontends/cxd2820r_t2.c
> +++ b/drivers/media/dvb-frontends/cxd2820r_t2.c
> @@ -120,7 +120,7 @@ int cxd2820r_set_frontend_t2(struct dvb_frontend *fe)
>
> num = if_freq / 1000; /* Hz => kHz */
> num *= 0x100;
> - if_ctl = cxd2820r_div_u64_round_closest(num, 41000);
> + if_ctl = DIV_ROUND_CLOSEST_ULL(num, 41000);
> buf[0] = ((if_ctl >> 16) & 0xff);
> buf[1] = ((if_ctl >> 8) & 0xff);
> buf[2] = ((if_ctl >> 0) & 0xff);
>
--
http://palosaari.fi/
radeon regression 3.11.0-rc2+
Hello I just upgraded Kernel from 3.10.0-rc6+ to 3.11.0-rc2+ and ran serious problems. That Kernel is current Linux Media master, which contains some upcoming media stuff that should not still has any effect, but lets mention for sure. Display started freezing and gone black, I think two times. Next freeze led to effect screen was full of very colourful boxes. It recognized mouse moves but text was unable to read so I was forced to hard boot to old Kernel. Attached log contains stuff I found from the debug log. OS Fedora 17 01:05.0 VGA compatible controller: ATI Technologies Inc 760G [Radeon 3000] regards Antti -- http://palosaari.fi/ -- next part -- Jul 23 23:22:28 localhost kernel: imklog 5.8.10, log source = /proc/kmsg started. Jul 23 23:22:28 localhost kernel: [0.00] Initializing cgroup subsys cpuset Jul 23 23:22:28 localhost kernel: [0.00] Initializing cgroup subsys cpu Jul 23 23:22:28 localhost kernel: [0.00] Initializing cgroup subsys cpuacct Jul 23 23:22:28 localhost kernel: [0.00] Linux version 3.11.0-rc2+ (crope at localhost.localdomain) (gcc version 4.7.2 20120921 (Red Hat 4.7.2-2) (GCC) ) #59 SMP Tue Jul 23 22:50:55 EEST 2013 Jul 23 23:22:28 localhost kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.11.0-rc2+ root=/dev/mapper/luks-cca8d466-f3e4-4c07-abb1-c1d6c21fde81 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=fi rd.luks.uuid=luks-cca8d466-f3e4-4c07-abb1-c1d6c21fde81 LANG=en_US.UTF-8 rhgb quiet Jul 23 23:22:28 localhost kernel: [0.00] e820: BIOS-provided physical RAM map: Jul 23 23:22:28 localhost kernel: [0.00] BIOS-e820: [mem 0x-0x0009efff] usable Jul 23 23:22:28 localhost kernel: [0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved Jul 23 23:22:28 localhost kernel: [0.00] BIOS-e820: [mem 0x000e4000-0x000f] reserved Jul 23 23:22:28 localhost kernel: [0.00] BIOS-e820: [mem 0x0010-0xcfe7] usable Jul 23 23:22:28 localhost kernel: [0.00] BIOS-e820: [mem 0xcfe8-0xcfe97fff] ACPI data Jul 23 23:22:28 localhost kernel: [0.00] BIOS-e820: [mem 0xcfe98000-0xcfeb] ACPI NVS Jul 23 23:22:28 localhost kernel: [0.00] BIOS-e820: [mem 0xcfec-0xcfef] reserved Jul 23 23:22:28 localhost kernel: [0.00] BIOS-e820: [mem 0xffe0-0x] reserved Jul 23 23:22:28 localhost kernel: [0.00] BIOS-e820: [mem 0x0001-0x00031fff] usable Jul 23 23:22:28 localhost kernel: [0.00] NX (Execute Disable) protection: active Jul 23 23:22:28 localhost kernel: [0.00] SMBIOS 2.5 present. Jul 23 23:22:28 localhost kernel: [0.00] DMI: System manufacturer System Product Name/M5A78L-M/USB3, BIOS 150311/14/2012 Jul 23 23:22:28 localhost kernel: [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved Jul 23 23:22:28 localhost kernel: [0.00] e820: remove [mem 0x000a-0x000f] usable Jul 23 23:22:28 localhost kernel: [0.00] No AGP bridge found Jul 23 23:22:28 localhost kernel: [0.00] e820: last_pfn = 0x32 max_arch_pfn = 0x4 Jul 23 23:22:28 localhost kernel: [0.00] MTRR default type: uncachable Jul 23 23:22:28 localhost kernel: [0.00] MTRR fixed ranges enabled: Jul 23 23:22:28 localhost kernel: [0.00] 0-9 write-back Jul 23 23:22:28 localhost kernel: [0.00] A-E uncachable Jul 23 23:22:28 localhost kernel: [0.00] F-F write-protect Jul 23 23:22:28 localhost kernel: [0.00] MTRR variable ranges enabled: Jul 23 23:22:28 localhost kernel: [0.00] 0 base mask 8000 write-back Jul 23 23:22:28 localhost kernel: [0.00] 1 base 8000 mask C000 write-back Jul 23 23:22:28 localhost kernel: [0.00] 2 base C000 mask F000 write-back Jul 23 23:22:28 localhost kernel: [0.00] 3 disabled Jul 23 23:22:28 localhost kernel: [0.00] 4 disabled Jul 23 23:22:28 localhost kernel: [0.00] 5 disabled Jul 23 23:22:28 localhost kernel: [0.00] 6 disabled Jul 23 23:22:28 localhost kernel: [0.00] 7 disabled Jul 23 23:22:28 localhost kernel: [0.00] TOM2: 00033000 aka 13056M Jul 23 23:22:28 localhost kernel: [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 Jul 23 23:22:28 localhost kernel: [0.00] e820: update [mem 0xd000-0x] usable ==> reserved Jul 23 23:22:28 localhost kernel: [0.00] e820: last_pfn = 0xcfe80 max_arch_pfn = 0x4 Jul 23 23:22:28 localhost kernel: [0.00] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [880ff780] Jul 23 23:22:28 localhost kernel: [0.00] Base memory trampoline at [fff
radeon regression 3.11.0-rc2+
On 07/24/2013 04:24 PM, Alex Deucher wrote: > On Tue, Jul 23, 2013 at 6:22 PM, Antti Palosaari wrote: >> Hello >> I just upgraded Kernel from 3.10.0-rc6+ to 3.11.0-rc2+ and ran serious >> problems. That Kernel is current Linux Media master, which contains some >> upcoming media stuff that should not still has any effect, but lets mention >> for sure. >> >> Display started freezing and gone black, I think two times. Next freeze led >> to effect screen was full of very colourful boxes. It recognized mouse moves >> but text was unable to read so I was forced to hard boot to old Kernel. >> Attached log contains stuff I found from the debug log. > > Can you try my latest fixes branch: > http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-fixes-3.11 > > If that doesn't help, can you bisect? It has been running that branch 4 hours without errors. Bug seems to be fixed! regards Antti -- http://palosaari.fi/
