commit a481daa88fd (drm/radeon: always apply pci shutdown callbacks) breaks reboot

2016-10-12 Thread Markus Trippelsdorf
Since: commit a481daa88fd4d6b54f25348972bba10b5f6a84d0 Author: Alex Deucher Date: Thu Sep 22 14:43:50 2016 -0400 drm/radeon: always apply pci shutdown callbacks We can't properly detect all hypervisors and we need this to properly tear down the hardware. I cannot reboot my machin

Re: [git pull] drm fixes for 4.10-rc6 (just missed rc5 tagging :-)

2017-01-25 Thread Markus Trippelsdorf
On 2017.01.23 at 09:38 +1000, Dave Airlie wrote: > > Alex Deucher (8): > drm/radeon/si: load special ucode for certain MC configs > drm/amdgpu/si: load special ucode for certain MC configs > drm/amdgpu: drop oland qu

Commit f5d9b7f0f9 (fix r600_enable_sclk_control()) causes kexec issues

2013-07-29 Thread Markus Trippelsdorf
On my test machine Xorg doesn't start anymore when I kexec into a 3.11.0-rc3 kernel. On cold boot everything is fine: [drm] Initialized drm 1.1.0 20060810 [drm] radeon kernel modesetting enabled. [drm] initializing kernel modesetting (RS780 0x1002:0x9614 0x1043:0x834D). [drm] register mmio base: 0

Re: Commit f5d9b7f0f9 (fix r600_enable_sclk_control()) causes kexec issues

2013-07-29 Thread Markus Trippelsdorf
On 2013.07.29 at 09:58 -0400, Alex Deucher wrote: > On Mon, Jul 29, 2013 at 3:51 AM, Markus Trippelsdorf > wrote: > > On my test machine Xorg doesn't start anymore when I kexec into a > > 3.11.0-rc3 kernel. > > With kexec, dpm doesn't get torn down properly wh

Re: Commit f5d9b7f0f9 (fix r600_enable_sclk_control()) causes kexec issues

2013-07-29 Thread Markus Trippelsdorf
On 2013.07.29 at 18:14 +0200, Joshua C. wrote: > > This error message seems similar to mine "[drm:r600_uvd_ring_test] > *ERROR* radeon: ring 5 test failed (0xCAFEDEAD)" Bugzilla: > https://bugs.freedesktop.org/show_bug.cgi?id=67276 In my case I blame > another commit for this. Are these bugs relat

Re: Commit f5d9b7f0f9 (fix r600_enable_sclk_control()) causes kexec issues

2013-07-29 Thread Markus Trippelsdorf
> Alex Deucher wrote: > >>>>On Mon, Jul 29, 2013 at 10:09 AM, Markus Trippelsdorf > >>>> wrote: > >>>>> On 2013.07.29 at 09:58 -0400, Alex Deucher wrote: > >>>>>> On Mon, Jul 29, 2013 at 3:51 AM, Markus Trippelsdorf > >&g

Re: Commit f5d9b7f0f9 (fix r600_enable_sclk_control()) causes kexec issues

2013-07-30 Thread Markus Trippelsdorf
> Alex Deucher wrote: > >>>>On Mon, Jul 29, 2013 at 10:09 AM, Markus Trippelsdorf > >>>> wrote: > >>>>> On 2013.07.29 at 09:58 -0400, Alex Deucher wrote: > >>>>>> On Mon, Jul 29, 2013 at 3:51 AM, Markus Trippelsdorf > >&g

Re: Commit f5d9b7f0f9 (fix r600_enable_sclk_control()) causes kexec issues

2013-07-30 Thread Markus Trippelsdorf
On 2013.07.30 at 13:27 +0200, Markus Trippelsdorf wrote: > On 2013.07.29 at 15:53 -0400, Alex Deucher wrote: > > On Mon, Jul 29, 2013 at 2:10 PM, Eric W. Biederman > > wrote: > > > Alex Deucher writes: > > > > > >> On Mon, Jul 29, 2013

Re: Commit f5d9b7f0f9 (fix r600_enable_sclk_control()) causes kexec issues

2013-07-30 Thread Markus Trippelsdorf
On 2013.07.30 at 10:53 -0400, Alex Deucher wrote: > On Tue, Jul 30, 2013 at 7:27 AM, Markus Trippelsdorf > wrote: > > On 2013.07.29 at 15:53 -0400, Alex Deucher wrote: > >> On Mon, Jul 29, 2013 at 2:10 PM, Eric W. Biederman > >> wrote: > >> > Alex Deuc

Re: Commit f5d9b7f0f9 (fix r600_enable_sclk_control()) causes kexec issues

2013-07-30 Thread Markus Trippelsdorf
On 2013.07.30 at 20:46 +0200, Markus Trippelsdorf wrote: > On 2013.07.30 at 10:53 -0400, Alex Deucher wrote: > > On Tue, Jul 30, 2013 at 7:27 AM, Markus Trippelsdorf > > wrote: > > > On 2013.07.29 at 15:53 -0400, Alex Deucher wrote: > > >> On Mon, Jul 29

[PATCH 0/3] drm/radeon kexec fixes

2013-09-08 Thread Markus Trippelsdorf
Here are a couple of patches that get kexec working with radeon devices. I've tested this on my RS780. Comments or flames are welcome. Thanks. Markus Trippelsdorf (3): kexec: get rid of late printk drm/radeon: Implement radeon_pci_shutdown drm/radeon: get rid of r100_restore_sanity

[PATCH 1/3] kexec: get rid of late printk

2013-09-08 Thread Markus Trippelsdorf
kexec calls: printk(KERN_EMERG "Starting new kernel\n"); late before calling machine_shutdown(). However at this point the underlying fb device may have already been shutdown. This causes the kernel to hang. Fix by simply getting rid of the printk call. Signed-off-by: Markus Tr

[PATCH 2/3] drm/radeon: Implement radeon_pci_shutdown

2013-09-08 Thread Markus Trippelsdorf
Currently radeon devices are not properbly shutdown during kexec. This cases a varity of issues, e.g. dpm initialization failures. Fix this by implementing a radeon_pci_shutdown function, that unloads the driver cleanly. Signed-off-by: Markus Trippelsdorf --- drivers/gpu/drm/radeon/radeon_drv.c

[PATCH 3/3] drm/radeon: get rid of r100_restore_sanity hack

2013-09-08 Thread Markus Trippelsdorf
Now that radeon devices are properly shutdown during kexec, we can get rid of r100_restore_sanity. Signed-off-by: Markus Trippelsdorf --- drivers/gpu/drm/radeon/r100.c| 27 --- drivers/gpu/drm/radeon/r300.c| 2 -- drivers/gpu/drm/radeon/r420.c

Re: [PATCH 0/3] drm/radeon kexec fixes

2013-09-09 Thread Markus Trippelsdorf
On 2013.09.08 at 17:32 -0700, Eric W. Biederman wrote: > Markus Trippelsdorf writes: > > > Here are a couple of patches that get kexec working with radeon devices. > > I've tested this on my RS780. > > Comments or flames are welcome. > > Thanks. > > A

Re: [PATCH 0/3] drm/radeon kexec fixes

2013-09-11 Thread Markus Trippelsdorf
On 2013.09.10 at 16:40 -0400, Alex Deucher wrote: > On Tue, Sep 10, 2013 at 2:27 PM, Eric W. Biederman > wrote: > > Alex Deucher writes: > > > >> On Mon, Sep 9, 2013 at 5:21 AM, Markus Trippelsdorf > >> wrote: > >> > >>> IIRC Alex sa

Re: [PATCH 0/3] drm/radeon kexec fixes

2013-09-11 Thread Markus Trippelsdorf
On 2013.09.09 at 11:38 +0200, Christian König wrote: > Am 09.09.2013 11:21, schrieb Markus Trippelsdorf: > > On 2013.09.08 at 17:32 -0700, Eric W. Biederman wrote: > >> Markus Trippelsdorf writes: > >> > >>> Here are a couple of patches that get kexec

[no subject]

2014-09-07 Thread Markus Trippelsdorf
On 2014.08.25 at 11:10 +0200, Christian K?nig wrote: > Let me know if it works for you, cause we don't really have any hardware > any more to test it. I've tested your patch series today (using drm-next-3.18 from ~agd5f/linux) on a RS780D/Radeon HD 3300 system with a couple of H264 videos. While

[no subject]

2014-09-08 Thread Markus Trippelsdorf
On 2014.09.07 at 23:47 -0400, Alex Deucher wrote: > On Sun, Sep 7, 2014 at 9:24 AM, Markus Trippelsdorf > wrote: > > On 2014.08.25 at 11:10 +0200, Christian K?nig wrote: > >> Let me know if it works for you, cause we don't really have any hardware > >> any m

Re: [PATCH wq#for-linus] drm: fix a fallout from slow-work -> wq conversion

2018-06-19 Thread Markus Trippelsdorf
k and error message. > > Signed-off-by: Tejun Heo > Reported-by: Markus Trippelsdorf > Cc: David Airlie > Cc: dri-devel@lists.freedesktop.org > --- > Markus, it's almost trivial but it would be great if you can test this > one too. Looks good, but drm_kms_helper_poll

Can no longer shutdown after drm/radeon: Implement radeon_pci_shutdown

2013-12-11 Thread Markus Trippelsdorf
On 2013.12.11 at 11:37 +1100, Peter Chubb wrote: > On my HP Elitebook 8740w qith a Mobility Radeon HD 5870 > commit 846ae41ae99d314bf2a02784152208a6ddf7eddc > breaks shutdown. The machine hangs when trying to shutdown, kexec or > hibernate, before seeing the usual `machine halted' (or whatever) me

Can no longer shutdown after drm/radeon: Implement radeon_pci_shutdown

2013-12-12 Thread Markus Trippelsdorf
On 2013.12.11 at 23:46 +, Deucher, Alexander wrote: > > -Original Message- > > From: Peter Chubb [mailto:peter.chubb at nicta.com.au] > > Sent: Wednesday, December 11, 2013 5:11 PM > > To: Markus Trippelsdorf > > Cc: Peter Chubb; Deucher, Alexander; airli

Can no longer shutdown after drm/radeon: Implement radeon_pci_shutdown

2013-12-12 Thread Markus Trippelsdorf
On 2013.12.12 at 03:27 +, Deucher, Alexander wrote: > > On 2013.12.11 at 23:46 +, Deucher, Alexander wrote: > > > > -Original Message- > > > > From: Peter Chubb [mailto:peter.chubb at nicta.com.au] > > > > Sent: Wednesday, December 11, 20

Monitor sync out of range with current Linux git tree

2012-10-05 Thread Markus Trippelsdorf
When I cold start my machine I see the following error message on my monitor: Out of Range 48.2kHz / 44Hz I have to reboot on older kernel and kexec to the current one to get it working again. [drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to kernel modesetting. [drm] radeon kern

Monitor sync out of range with current Linux git tree

2012-10-05 Thread Markus Trippelsdorf
On 2012.10.05 at 09:14 -0400, Alex Deucher wrote: > On Fri, Oct 5, 2012 at 8:37 AM, Markus Trippelsdorf > wrote: > > When I cold start my machine I see the following error message on my > > monitor: > > > > Out of Range > > 48.2kHz / 44Hz > > > &g

Monitor sync out of range with current Linux git tree

2012-10-05 Thread Markus Trippelsdorf
On 2012.10.05 at 10:02 -0400, Alex Deucher wrote: > On Fri, Oct 5, 2012 at 9:38 AM, Markus Trippelsdorf > wrote: > > On 2012.10.05 at 09:14 -0400, Alex Deucher wrote: > >> On Fri, Oct 5, 2012 at 8:37 AM, Markus Trippelsdorf > >> wrote: > >> > When I

Monitor sync out of range with current Linux git tree

2012-10-05 Thread Markus Trippelsdorf
On 2012.10.05 at 10:25 -0400, Alex Deucher wrote: > On Fri, Oct 5, 2012 at 10:15 AM, Markus Trippelsdorf > wrote: > > On 2012.10.05 at 10:02 -0400, Alex Deucher wrote: > >> On Fri, Oct 5, 2012 at 9:38 AM, Markus Trippelsdorf > >> wrote: > >> > On 201

GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-17 Thread Markus Trippelsdorf
As soon as I open the following website: http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_i.html my Radeon RS780 stalls (GPU lockup) leaving the machine unusable: Dec 17 17:41:39 x4 kernel: [drm] Initialized drm 1.1.0 20060810 Dec 17 17:41:39 x4 kernel: [drm] radeon defaulting

Re: GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-17 Thread Markus Trippelsdorf
On 2012.12.17 at 16:32 -0500, Alex Deucher wrote: > On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf > wrote: > > As soon as I open the following website: > > http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_i.html > > > > my Radeon RS780 s

Re: GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-17 Thread Markus Trippelsdorf
On 2012.12.17 at 22:48 +0100, Markus Trippelsdorf wrote: > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote: > > On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf > > wrote: > > > As soon as I open the following website: > > > http://

Re: GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-17 Thread Markus Trippelsdorf
On 2012.12.17 at 17:00 -0500, Alex Deucher wrote: > On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf > wrote: > > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote: > >> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf > >> wrote: > >> &g

Re: GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-17 Thread Markus Trippelsdorf
On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote: > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote: > > On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf > > wrote: > > > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote: > > >> On Mon, Dec 17,

Re: GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-18 Thread Markus Trippelsdorf
On 2012.12.18 at 12:20 +0100, Michel Dänzer wrote: > On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote: > > On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote: > > > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote: > > > > On Mon, Dec 17, 2012 a

Re: GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-18 Thread Markus Trippelsdorf
On 2012.12.18 at 14:38 +0100, Markus Trippelsdorf wrote: > On 2012.12.18 at 12:20 +0100, Michel Dänzer wrote: > > On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote: > > > On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote: > > > > On 2012.12.17 at 1

Re: GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-18 Thread Markus Trippelsdorf
On 2012.12.18 at 16:24 +0100, Maarten Lankhorst wrote: > Op 18-12-12 14:38, Markus Trippelsdorf schreef: > > On 2012.12.18 at 12:20 +0100, Michel Dänzer wrote: > >> On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote: > >>> On 2012.12.17 at 23:25 +0

Re: GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-19 Thread Markus Trippelsdorf
On 2012.12.19 at 14:57 +0100, Maarten Lankhorst wrote: > Op 18-12-12 17:12, Markus Trippelsdorf schreef: > > With your supposed debugging BUG_ONs added I still get: > > > > Dec 18 17:01:15 x4 kernel: [ cut here ] > > Dec 18 17:01:15 x4 kernel

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2012-12-19 Thread Markus Trippelsdorf
atch. > > > > Also please add the commit summary to make the commit message self > > contained? > > > > The problem description would also be nice. > > > >> Signed-off-by: Maarten Lankhorst > >> Reported-by: Markus Trippelsdorf > > Message-I

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2012-12-19 Thread Markus Trippelsdorf
On 2012.12.19 at 15:54 +0100, Markus Trippelsdorf wrote: > On 2012.12.19 at 09:47 -0500, Alex Deucher wrote: > > And the pictures get distorted on the test-webpage when I scroll up and > down, see: > http://trippelsdorf.de/bad.png The picture distortion issue is cau

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2012-12-20 Thread Markus Trippelsdorf
On 2012.12.20 at 08:30 -0500, Alex Deucher wrote: > On Wed, Dec 19, 2012 at 9:33 AM, Markus Trippelsdorf > wrote: > > On 2012.12.19 at 15:18 +0100, Maarten Lankhorst wrote: > >> Fix regression introduced by 85b144f860176 > > > > Thanks. This fixes the kernel BUG

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2012-12-20 Thread Markus Trippelsdorf
On 2012.12.20 at 14:45 +0100, Markus Trippelsdorf wrote: > On 2012.12.20 at 08:30 -0500, Alex Deucher wrote: > > On Wed, Dec 19, 2012 at 9:33 AM, Markus Trippelsdorf > > wrote: > > > On 2012.12.19 at 15:18 +0100, Maarten Lankhorst wrote: > > >> Fix re

Re: GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-23 Thread Markus Trippelsdorf
On 2012.12.22 at 20:46 -0500, Alex Deucher wrote: > On Mon, Dec 17, 2012 at 5:25 PM, Markus Trippelsdorf > wrote: > > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote: > >> On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf > >> wrote: > >> > On 201

Re: GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-23 Thread Markus Trippelsdorf
On 2012.12.23 at 10:09 +, Andy Furniss wrote: > Markus Trippelsdorf wrote: > > >> Does booting with radeon.wb=0 fix the issue? Please make sure your > >> kernel has this patch: > >> http://git.kernel.org/?p=linux/kernel/git/

Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec

2012-12-23 Thread Markus Trippelsdorf
On 2012.12.23 at 12:31 +0100, Borislav Petkov wrote: > On Sun, Dec 23, 2012 at 11:19:00AM +, Andy Furniss wrote: > > modinfo radeon > > > > will give a list assuming you use modules, I think all of them need =. > > Yep, that is one way of getting that info, thanks. I always go and look > at D

Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec

2013-01-02 Thread Markus Trippelsdorf
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 i

Re: radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec

2013-01-03 Thread Markus Trippelsdorf
On 2013.01.02 at 18:37 -0500, 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/0

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2013-01-05 Thread Markus Trippelsdorf
On 2012.12.20 at 14:58 +0100, Markus Trippelsdorf wrote: > On 2012.12.20 at 14:45 +0100, Markus Trippelsdorf wrote: > > On 2012.12.20 at 08:30 -0500, Alex Deucher wrote: > > > On Wed, Dec 19, 2012 at 9:33 AM, Markus Trippelsdorf > > > wrote: > > > > On 2012.

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2013-01-15 Thread Markus Trippelsdorf
On 2013.01.15 at 15:43 +0100, Michel Dänzer wrote: > On Sam, 2013-01-05 at 11:41 +0100, Markus Trippelsdorf wrote: > > On 2012.12.20 at 14:58 +0100, Markus Trippelsdorf wrote: > > > > > > And just in case it got lost in the noise yesterday: > > > The image c

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2013-01-15 Thread Markus Trippelsdorf
On 2013.01.15 at 16:26 +0100, Michel Dänzer wrote: > On Die, 2013-01-15 at 16:23 +0100, Markus Trippelsdorf wrote: > > On 2013.01.15 at 15:43 +0100, Michel Dänzer wrote: > > > On Sam, 2013-01-05 at 11:41 +0100, Markus Trippelsdorf wrote: > > > > On 2012.12.20 at 14

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2013-01-15 Thread Markus Trippelsdorf
On 2013.01.15 at 17:32 +0100, Markus Trippelsdorf wrote: > On 2013.01.15 at 16:26 +0100, Michel Dänzer wrote: > > On Die, 2013-01-15 at 16:23 +0100, Markus Trippelsdorf wrote: > > > On 2013.01.15 at 15:43 +0100, Michel Dänzer wrote: > > > > On Sam, 2013-01-05 at 11

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2013-01-16 Thread Markus Trippelsdorf
On 2013.01.16 at 17:36 -0500, Alex Deucher wrote: > On Tue, Jan 15, 2013 at 12:03 PM, Markus Trippelsdorf > wrote: > > On 2013.01.15 at 17:32 +0100, Markus Trippelsdorf wrote: > >> On 2013.01.15 at 16:26 +0100, Michel Dänzer wrote: > >> > On Die, 2013-01-15 at

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2013-01-17 Thread Markus Trippelsdorf
On 2013.01.16 at 19:18 -0500, Jerome Glisse wrote: > On Wed, Jan 16, 2013 at 6:10 PM, Markus Trippelsdorf > wrote: > > On 2013.01.16 at 17:36 -0500, Alex Deucher wrote: > >> On Tue, Jan 15, 2013 at 12:03 PM, Markus Trippelsdorf > >> wrote: > >> > On 2013

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2013-01-17 Thread Markus Trippelsdorf
On 2013.01.17 at 10:44 -0500, Jerome Glisse wrote: > On Thu, Jan 17, 2013 at 3:46 AM, Markus Trippelsdorf > wrote: > > On 2013.01.16 at 19:18 -0500, Jerome Glisse wrote: > >> On Wed, Jan 16, 2013 at 6:10 PM, Markus Trippelsdorf > >> wrote: > >> > On 201

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2013-01-17 Thread Markus Trippelsdorf
On 2013.01.17 at 12:55 -0500, Jerome Glisse wrote: > On Thu, Jan 17, 2013 at 11:10 AM, Markus Trippelsdorf > wrote: > > On 2013.01.17 at 10:44 -0500, Jerome Glisse wrote: > >> On Thu, Jan 17, 2013 at 3:46 AM, Markus Trippelsdorf > >> wrote: > >> > O

Re: [PATCH] drm/ttm: fix delayed ttm_bo_cleanup_refs_and_unlock delayed handling

2013-01-17 Thread Markus Trippelsdorf
On 2013.01.17 at 13:28 -0500, Jerome Glisse wrote: > On Thu, Jan 17, 2013 at 11:10 AM, Markus Trippelsdorf > wrote: > > On 2013.01.17 at 10:44 -0500, Jerome Glisse wrote: > >> On Thu, Jan 17, 2013 at 3:46 AM, Markus Trippelsdorf > >> wrote: > >> > O

/dev/dri/card0 sometimes vanishes when I exit Xorg (Radeon RS780)

2012-09-29 Thread Markus Trippelsdorf
Hi, since a few weeks the /dev/dri/card0 entry sometimes vanishes when I exit Xorg. When I want to start Xorg again I get the following error message: ... [ 12711.547] (II) [KMS] Kernel modesetting enabled. [ 12711.548] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 12711.5

Re: [Solved] /dev/dri/card0 sometimes vanishes when I exit Xorg (Radeon RS780)

2012-09-30 Thread Markus Trippelsdorf
On 2012.09.29 at 20:38 +0200, Markus Trippelsdorf wrote: > since a few weeks the /dev/dri/card0 entry sometimes vanishes when I > exit Xorg. When I want to start Xorg again I get the following error > message: > > ... > [ 12711.547] (II) [KMS] Kernel modesetting enabled. >

Monitor sync out of range with current Linux git tree

2012-10-05 Thread Markus Trippelsdorf
When I cold start my machine I see the following error message on my monitor: Out of Range 48.2kHz / 44Hz I have to reboot on older kernel and kexec to the current one to get it working again. [drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to kernel modesetting. [drm] radeon kern

Re: Monitor sync out of range with current Linux git tree

2012-10-05 Thread Markus Trippelsdorf
On 2012.10.05 at 09:14 -0400, Alex Deucher wrote: > On Fri, Oct 5, 2012 at 8:37 AM, Markus Trippelsdorf > wrote: > > When I cold start my machine I see the following error message on my > > monitor: > > > > Out of Range > > 48.2kHz / 44Hz > > > &g

Re: Monitor sync out of range with current Linux git tree

2012-10-05 Thread Markus Trippelsdorf
On 2012.10.05 at 10:02 -0400, Alex Deucher wrote: > On Fri, Oct 5, 2012 at 9:38 AM, Markus Trippelsdorf > wrote: > > On 2012.10.05 at 09:14 -0400, Alex Deucher wrote: > >> On Fri, Oct 5, 2012 at 8:37 AM, Markus Trippelsdorf > >> wrote: > >> > When I

Re: Monitor sync out of range with current Linux git tree

2012-10-05 Thread Markus Trippelsdorf
On 2012.10.05 at 10:25 -0400, Alex Deucher wrote: > On Fri, Oct 5, 2012 at 10:15 AM, Markus Trippelsdorf > wrote: > > On 2012.10.05 at 10:02 -0400, Alex Deucher wrote: > >> On Fri, Oct 5, 2012 at 9:38 AM, Markus Trippelsdorf > >> wrote: > >> > On 201

Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-11-23 Thread Markus Trippelsdorf
On 2011.11.21 at 16:36 +0100, Markus Trippelsdorf wrote: > On 2011.11.21 at 15:16 +0100, Eric Dumazet wrote: > > Le lundi 21 novembre 2011 à 14:15 +0100, Markus Trippelsdorf a écrit : > > > > > I've enabled CONFIG_SLUB_DEBUG_ON and this is what happend: > >

Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-11-24 Thread Markus Trippelsdorf
On 2011.11.23 at 10:06 -0600, Christoph Lameter wrote: > On Wed, 23 Nov 2011, Markus Trippelsdorf wrote: > > > > FIX idr_layer_cache: Marking all objects used > > > > Yesterday I couldn't reproduce the issue at all. But today I've hit > > exact

Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-12-01 Thread Markus Trippelsdorf
On 2011.11.24 at 09:50 +0100, Markus Trippelsdorf wrote: > On 2011.11.23 at 10:06 -0600, Christoph Lameter wrote: > > On Wed, 23 Nov 2011, Markus Trippelsdorf wrote: > > > > > > FIX idr_layer_cache: Marking all objects used > > > > > > Yesterday I c

Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-12-02 Thread Markus Trippelsdorf
On 2011.12.02 at 14:43 -0500, Jerome Glisse wrote: > On Thu, Dec 01, 2011 at 09:44:37AM +0100, Markus Trippelsdorf wrote: > > On 2011.11.24 at 09:50 +0100, Markus Trippelsdorf wrote: > > > On 2011.11.23 at 10:06 -0600, Christoph Lameter wrote: > > > > On Wed, 23 Nov 2

Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-12-02 Thread Markus Trippelsdorf
On 2011.12.02 at 21:06 +0100, Markus Trippelsdorf wrote: > On 2011.12.02 at 14:43 -0500, Jerome Glisse wrote: > > On Thu, Dec 01, 2011 at 09:44:37AM +0100, Markus Trippelsdorf wrote: > > > On 2011.11.24 at 09:50 +0100, Markus Trippelsdorf wrote: > > > > On 2011.1

Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-12-03 Thread Markus Trippelsdorf
On 2011.12.03 at 12:20 +, Dave Airlie wrote: > >> > > > > FIX idr_layer_cache: Marking all objects used > >> > > > > >> > > > Yesterday I couldn't reproduce the issue at all. But today I've hit > >> > > > exactly the same spot again. (CCing the drm list) > > If I had to guess it looks like 0 i

Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-12-03 Thread Markus Trippelsdorf
On 2011.12.03 at 14:31 -0500, Jerome Glisse wrote: > On Sat, Dec 3, 2011 at 7:29 AM, Markus Trippelsdorf > wrote: > > On 2011.12.03 at 12:20 +, Dave Airlie wrote: > >> >> > > > > FIX idr_layer_cache: Marking all objects used > >> >> > &

Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-12-05 Thread Markus Trippelsdorf
On 2011.12.05 at 12:10 -0500, Jerome Glisse wrote: > On Sun, Dec 04, 2011 at 02:02:00AM +0100, Markus Trippelsdorf wrote: > > On 2011.12.03 at 14:31 -0500, Jerome Glisse wrote: > > > On Sat, Dec 3, 2011 at 7:29 AM, Markus Trippelsdorf > > > wrote: > > > > On

Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-12-05 Thread Markus Trippelsdorf
On 2011.12.05 at 14:11 -0500, Jerome Glisse wrote: > On Mon, Dec 05, 2011 at 07:15:49PM +0100, Markus Trippelsdorf wrote: > > On 2011.12.05 at 12:10 -0500, Jerome Glisse wrote: > > > On Sun, Dec 04, 2011 at 02:02:00AM +0100, Markus Trippelsdorf wrote: > > > > On 201

Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-12-07 Thread Markus Trippelsdorf
On 2011.12.07 at 15:32 +0100, Robert Richter wrote: > On 02.12.11 21:48:20, Markus Trippelsdorf wrote: > > BTW I always see (mostly only on screen, sometimes in the logs): > > > > [Firmware Bug]: cpu 2, try to use APIC500 (LVT offset 0) for vector > > 0x10400, but the

Re: 3.2-rc6+: Reported regressions from 3.0 and 3.1

2011-12-20 Thread Markus Trippelsdorf
On 2011.12.21 at 00:54 +0100, Rafael J. Wysocki wrote: > Subject: WARNING: at fs/sysfs/sysfs.h:195 (during boot) > Submitter : Markus Trippelsdorf > > Date : 2011-11-13 19:24 > Message-ID : 2013192417.ga1659-tlcgzgx+ij+kxvt8iv0...@public.gmane.org > References

radeon_gem_object_create:69 alloc size 139Mb bigger than 128Mb limit (RS780)

2013-02-28 Thread Markus Trippelsdorf
Running the latest Linus git kernel I occasionally see the following warning: radeon_gem_object_create:69 alloc size 139Mb bigger than 128Mb limit >From dmesg: [drm] Initialized drm 1.1.0 20060810 [drm] radeon kernel modesetting enabled. [drm] initializing kernel modesetting (RS780 0x1002:0x9614

Re: [pull] radeon drm-next-3.11

2013-07-01 Thread Markus Trippelsdorf
On 2013.07.01 at 17:01 -0400, alexdeuc...@gmail.com wrote: > From: Alex Deucher > > Hi Dave, > > A few more patches for 3.11: > - add debugfs interface to check current DPM state > - Fix a bug that caused problems with DPM on BTC+ asics. > > The following changes since commit f7d452f4fd5d86f764

Commit ecff665f5e3f (drm/ttm: make ttm reservation calls...) causes system hang on Radeon RS780

2013-07-10 Thread Markus Trippelsdorf
By simply copy/pasting a big document under LibreOffice my system hangs itself up. Only a hard reset gets it working again. see also: https://bugs.freedesktop.org/show_bug.cgi?id=66551 I've bisected the issue to: commit ecff665f5e3f1c6909353e00b9420e45ae23d995 Author: Maarten Lankhorst Date: T

Re: Commit ecff665f5e3f (drm/ttm: make ttm reservation calls...) causes system hang on Radeon RS780

2013-07-10 Thread Markus Trippelsdorf
On 2013.07.10 at 11:29 +0200, Maarten Lankhorst wrote: > Op 10-07-13 11:22, Markus Trippelsdorf schreef: > > By simply copy/pasting a big document under LibreOffice my system hangs > > itself up. Only a hard reset gets it working again. > > see also: https://bugs.freedeskto

Re: Commit ecff665f5e3f (drm/ttm: make ttm reservation calls...) causes system hang on Radeon RS780

2013-07-10 Thread Markus Trippelsdorf
On 2013.07.10 at 11:56 +0200, Maarten Lankhorst wrote: > Op 10-07-13 11:46, Markus Trippelsdorf schreef: > > On 2013.07.10 at 11:29 +0200, Maarten Lankhorst wrote: > >> Op 10-07-13 11:22, Markus Trippelsdorf schreef: > >>> By simply copy/pasting a big document und

Re: WARNING: at drivers/gpu/drm/ttm/ttm_page_alloc.c:758

2011-04-06 Thread Markus Trippelsdorf
On 2011.04.05 at 18:31 +0200, Markus Trippelsdorf wrote: > On 2011.03.29 at 16:56 +0200, Markus Trippelsdorf wrote: > > Just came across this WARNING (running latest git kernel): > > > > Mar 29 09:14:39 gentoo kernel: udev[888]:

Re: WARNING: at drivers/gpu/drm/ttm/ttm_page_alloc.c:758 .. [GIT PULL] stable/ttm.pci-api-rc2 for 2.6.39-rc2

2011-04-06 Thread Markus Trippelsdorf
On 2011.04.06 at 08:27 -0400, Konrad Rzeszutek Wilk wrote: > On Wed, Apr 06, 2011 at 11:13:59AM +0200, Thomas Hellstrom wrote: > > Dave, Konrad > > > > I think we need to back out this change as soon as possible. I will > > follow up the discussion with Konrad on how we should attempt to > > handl

Re: kernel 2.6.39-rc3 drm, radeon: device driver tries to free DMA memory it has not allocated

2011-04-12 Thread Markus Trippelsdorf
On 2011.04.12 at 21:09 +0200, Stefan Richter wrote: > Hi, > > I just switched from 2.6.38-rc7 to 2.6.39-rc3 and got this at some point > during userland startup: > > WARNING: at lib/dma-debug.c:803 check_unmap+0x19a/0x696() > Hardware name: System Product Name > NULL NULL: DMA-API: device driver

Re: drm-radeon failures on R600: patches still don't work

2011-06-12 Thread Markus Trippelsdorf
On 2011.06.12 at 13:48 +0300, Jaroslaw Fedewicz wrote: > > There was a recent thread as found on > https://lkml.org/lkml/2011/6/8/17, started by Markus Trippelsdorf: > > > The merge of the 'drm-radeon' branch by Linus yesterday breaks my setup > > (RS780). The

Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference

2010-11-08 Thread Markus Trippelsdorf
I can trigger a kernel crash on my system by simply loading this png image with firefox: http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg The system has an embedded RS780 and is running the latest git kernel. (Xorg.0.log is attached) The

Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference

2010-11-08 Thread Markus Trippelsdorf
On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: > I can trigger a kernel crash on my system by simply loading this png > image with firefox: > http://mediaarchive.cern.ch/MediaArchive/Photo/Public/2010/1011251/1011251_01/1011251_01-A4-at-144-dpi.jpg Sorry the abov

Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference

2010-11-08 Thread Markus Trippelsdorf
On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: > On Mon, Nov 08, 2010 at 06:07:37PM +0100, Markus Trippelsdorf wrote: > > On Mon, Nov 08, 2010 at 06:02:21PM +0100, Markus Trippelsdorf wrote: > > > I can trigger a kernel crash on my system by simpl

Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference

2010-11-09 Thread Markus Trippelsdorf
On Mon, Nov 08, 2010 at 11:29:16PM +0100, Thomas Hellstrom wrote: > On 11/08/2010 09:53 PM, Jerome Glisse wrote: > >On Mon, Nov 8, 2010 at 2:02 PM, Markus Trippelsdorf > > wrote: > >>On Mon, Nov 08, 2010 at 07:43:02PM +0100, Markus Trippelsdorf wrote: > >>>On M

Re: Radeon RS780 - BUG: unable to handle kernel NULL pointer dereference

2010-11-09 Thread Markus Trippelsdorf
On Tue, Nov 09, 2010 at 11:32:57AM +0100, Michel Dänzer wrote: > On Die, 2010-11-09 at 11:07 +0100, Thomas Hellstrom wrote: > > On 11/09/2010 10:53 AM, Thomas Hellstrom wrote: > > > On 11/09/2010 10:29 AM, Markus Trippelsdorf wrote: > > >> OK I've

Re: Radeon RS780 - BUG: at drivers/gpu/drm/ttm/ttm_bo.c:1134!

2010-11-27 Thread Markus Trippelsdorf
I've hit a new BUG using the same trigger (huge png image in firefox, zoom in and zoom out while the picture is loading): Nov 27 09:56:14 [kernel] kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:1134! Nov 27 09:56:14 [kernel] CPU 3 Nov 27 09:56:14 [kernel] Pid: 1867, comm: X Not tainted 2.6.37-rc3-002

WARNING: at drivers/gpu/drm/ttm/ttm_page_alloc.c:758

2011-03-29 Thread Markus Trippelsdorf
Just came across this WARNING (running latest git kernel): Mar 29 09:14:39 gentoo kernel: udev[888]: starting version 164 Mar 29 15:45:45 gentoo kernel: [ cut here ]

Re: [PATCH RESEND block#for-2.6.36] block_dev: always serialize exclusive open attempts

2010-08-05 Thread Markus Trippelsdorf
> bd_prepare_to_claim() and attempting to mount two partitions of a > > disk. > > > > stable: only applicable to v2.6.35 > > > > Signed-off-by: Tejun Heo > > Reported-by: Markus Trippelsdorf > > Cc: sta...@kernel.org > > Thanks Tejun, appli

Re: [PATCH wq#for-linus] drm: fix a fallout from slow-work -> wq conversion

2010-08-09 Thread Markus Trippelsdorf
k and error message. > > Signed-off-by: Tejun Heo > Reported-by: Markus Trippelsdorf > Cc: David Airlie > Cc: dri-devel@lists.freedesktop.org > --- > Markus, it's almost trivial but it would be great if you can test this > one too. Looks good, but drm_kms_helper_poll

Re: Intel graphics CPU usage - SDVO detect bogosity?

2010-08-15 Thread Markus Trippelsdorf
On Sun, Aug 15, 2010 at 07:32:15PM -0700, Linus Torvalds wrote: > I started wondering why 'top' was showing an otherwise idle system as > having a load average of 0.5+, and worker threads constantly using the > CPU. > > So I did a system-wide profile, and got the attached output (look at > it in a

Re: REGRESSION 2.6.36: radeon KMS console switch broken

2010-10-10 Thread Markus Trippelsdorf
On Sun, Oct 10, 2010 at 02:30:00PM +0200, Andi Kleen wrote: > > Hi, > > I see a radeon regression here with 2.6.36-rc7. > > I updated a system from 2.6.35 to 2.6.36-rc7. Now I cannot > switch to the text console from the X server anymore; the screen just > keeps displaying the X desktop. Event

Re: REGRESSION 2.6.36: radeon KMS console switch broken

2010-10-10 Thread Markus Trippelsdorf
On Sun, Oct 10, 2010 at 04:09:08PM +0200, Andi Kleen wrote: > On Sun, Oct 10, 2010 at 03:44:29PM +0200, Markus Trippelsdorf wrote: > > On Sun, Oct 10, 2010 at 02:30:00PM +0200, Andi Kleen wrote: > > > > > > Hi, > > > > > > I see a radeon regression h

WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-11-23 Thread Markus Trippelsdorf
On 2011.11.21 at 16:36 +0100, Markus Trippelsdorf wrote: > On 2011.11.21 at 15:16 +0100, Eric Dumazet wrote: > > Le lundi 21 novembre 2011 ? 14:15 +0100, Markus Trippelsdorf a ?crit : > > > > > I've enabled CONFIG_SLUB_DEBUG_ON and this is what happend: > >

WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

2011-11-24 Thread Markus Trippelsdorf
On 2011.11.23 at 10:06 -0600, Christoph Lameter wrote: > On Wed, 23 Nov 2011, Markus Trippelsdorf wrote: > > > > FIX idr_layer_cache: Marking all objects used > > > > Yesterday I couldn't reproduce the issue at all. But today I've hit > > exact

GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-17 Thread Markus Trippelsdorf
As soon as I open the following website: http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_i.html my Radeon RS780 stalls (GPU lockup) leaving the machine unusable: Dec 17 17:41:39 x4 kernel: [drm] Initialized drm 1.1.0 20060810 Dec 17 17:41:39 x4 kernel: [drm] radeon defaulting

GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-17 Thread Markus Trippelsdorf
On 2012.12.17 at 16:32 -0500, Alex Deucher wrote: > On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf > wrote: > > As soon as I open the following website: > > http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_i.html > > > > my Radeon RS780 s

GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-17 Thread Markus Trippelsdorf
On 2012.12.17 at 22:48 +0100, Markus Trippelsdorf wrote: > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote: > > On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf > > wrote: > > > As soon as I open the following website: > > > http://

GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-17 Thread Markus Trippelsdorf
On 2012.12.17 at 17:00 -0500, Alex Deucher wrote: > On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf > wrote: > > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote: > >> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf > >> wrote: > >> &g

GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-17 Thread Markus Trippelsdorf
On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote: > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote: > > On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf > > wrote: > > > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote: > > >> On Mon, Dec 17,

GPU lockup CP stall for more than 10000msec on latest vanilla git

2012-12-18 Thread Markus Trippelsdorf
On 2012.12.18 at 12:20 +0100, Michel D?nzer wrote: > On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote: > > On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote: > > > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote: > > > > On Mon, Dec 17, 2012 a

  1   2   >