[Bug 58354] [bisected] r600g: use DMA engine for VM page table updates on cayman locks in Unigine Tropics

bugzilla-daemon@xxxxxxxxxxxxxxx · Sun, 23 Dec 2012 07:23:43 +0000

            Comment # 10
              on bug 58354
              from  Alexandre Demers

        (In reply to comment #9)
> Doesn't fix it, it locks as before. Sadly, dmesg seems to loose the count
> because of another bug introduced in 3.8-rc1. Now that I moved to 3.8-rc1,
> there is a huge amount of messages appearing in errors.log and dmesg (when
> typed in the terminal):
> ...
> [ 6223.054880] radeon 0000:01:00.0: GPU fault detected: 146 0x00239514
> [ 6223.054882] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054883] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054885] radeon 0000:01:00.0: GPU fault detected: 146 0x00135514
> [ 6223.054887] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054889] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054891] radeon 0000:01:00.0: GPU fault detected: 146 0x00239514
> [ 6223.054893] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054895] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054897] radeon 0000:01:00.0: GPU fault detected: 146 0x0033a514
> [ 6223.054899] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054900] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054902] radeon 0000:01:00.0: GPU fault detected: 146 0x00136514
> [ 6223.054904] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054906] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054908] radeon 0000:01:00.0: GPU fault detected: 146 0x0033a514
> [ 6223.054910] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054912] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054914] radeon 0000:01:00.0: GPU fault detected: 146 0x0033a514
> [ 6223.054916] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054918] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054920] radeon 0000:01:00.0: GPU fault detected: 146 0x00232514
> [ 6223.054922] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054923] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054925] radeon 0000:01:00.0: GPU fault detected: 146 0x00232514
> [ 6223.054927] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054930] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054932] radeon 0000:01:00.0: GPU fault detected: 146 0x0033d514
> [ 6223.054934] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054936] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054938] radeon 0000:01:00.0: GPU fault detected: 146 0x0033d514
> [ 6223.054940] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054942] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054944] radeon 0000:01:00.0: GPU fault detected: 146 0x00235514
> [ 6223.054946] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054948] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054950] radeon 0000:01:00.0: GPU fault detected: 146 0x00235514
> [ 6223.054952] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054954] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054956] radeon 0000:01:00.0: GPU fault detected: 146 0x0033e514
> [ 6223.054958] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054960] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054962] radeon 0000:01:00.0: GPU fault detected: 146 0x0033e514
> [ 6223.054963] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054965] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054967] radeon 0000:01:00.0: GPU fault detected: 146 0x00339514
> [ 6223.054969] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054971] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054973] radeon 0000:01:00.0: GPU fault detected: 146 0x00339514
> [ 6223.054975] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054977] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> [ 6223.054979] radeon 0000:01:00.0: GPU fault detected: 146 0x00236514
> [ 6223.054980] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_ADDR  
> 0x00000000
> [ 6223.054982] radeon 0000:01:00.0:   VM_CONTEXT1_PROTECTION_FAULT_STATUS
> 0x00000000
> ...
> 
> I'm sure it is a different bug, can you confirm? dmesg.log stops to be
> populated when X/Gnome start, but typing dmesg in a terminal outputs tons of
> the reported messages. Should I open a new bug for it or has it been already
> reported?

Found something similar, it looks bug 58667.

      You are receiving this mail because:

          You are the assignee for the bug.

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