[Bug 195295] USB device insertion turns on discrete Radeon GPU
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Tue Apr 11 21:03:43 UTC 2017
https://bugzilla.kernel.org/show_bug.cgi?id=195295
--- Comment #3 from Eugene Shalygin (eugene.shalygin at gmail.com) ---
Tried 4.10.6, which was free of this bug at the time I used it, but now it show
the same behaviour. Here is a part from dmesg:
[ 21.074717] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[ 21.249295] usb 3-1: New USB device found, idVendor=13fe, idProduct=3600
[ 21.249299] usb 3-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 21.249300] usb 3-1: Product:
[ 21.249301] usb 3-1: Manufacturer:
[ 21.249302] usb 3-1: SerialNumber: 90B20A000FA260F6
[ 21.920245] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
[ 21.920250] [drm] PCIE gen 3 link speeds already enabled
[ 21.923553] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
[ 21.923706] radeon 0000:01:00.0: WB enabled
[ 21.923709] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000100000c00 and cpu addr 0xffff8807fc864c00
[ 21.923710] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr
0x0000000100000c04 and cpu addr 0xffff8807fc864c04
[ 21.923711] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr
0x0000000100000c08 and cpu addr 0xffff8807fc864c08
[ 21.923712] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000100000c0c and cpu addr 0xffff8807fc864c0c
[ 21.923713] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr
0x0000000100000c10 and cpu addr 0xffff8807fc864c10
[ 21.923917] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000075a18 and cpu addr 0xffffc9000ba35a18
[ 21.944050] radeon 0000:01:00.0: fence driver on ring 6 use gpu addr
0x0000000100000c18 and cpu addr 0xffff8807fc864c18
[ 21.944051] radeon 0000:01:00.0: fence driver on ring 7 use gpu addr
0x0000000100000c1c and cpu addr 0xffff8807fc864c1c
[ 22.091949] [drm] ring test on 0 succeeded in 2 usecs
[ 22.091954] [drm] ring test on 1 succeeded in 1 usecs
[ 22.091957] [drm] ring test on 2 succeeded in 1 usecs
[ 22.091962] [drm] ring test on 3 succeeded in 3 usecs
[ 22.091967] [drm] ring test on 4 succeeded in 3 usecs
[ 22.269145] [drm] ring test on 5 succeeded in 2 usecs
[ 22.269148] [drm] UVD initialized successfully.
[ 22.379257] [drm] ring test on 6 succeeded in 13 usecs
[ 22.379267] [drm] ring test on 7 succeeded in 4 usecs
[ 22.379268] [drm] VCE initialized successfully.
[ 22.379332] [drm] ib test on ring 0 succeeded in 0 usecs
[ 22.379356] [drm] ib test on ring 1 succeeded in 0 usecs
[ 22.379376] [drm] ib test on ring 2 succeeded in 0 usecs
[ 22.379394] [drm] ib test on ring 3 succeeded in 0 usecs
[ 22.379411] [drm] ib test on ring 4 succeeded in 0 usecs
[ 23.036811] [drm] ib test on ring 5 succeeded
[ 23.588821] [drm] ib test on ring 6 succeeded
[ 24.100855] [drm] ib test on ring 7 succeeded
[ 24.100915] switching from power state:
[ 24.100917] ui class:
[ 24.100918] none
[ 24.100921] internal class:
[ 24.100921] boot
[ 24.100925] caps:
[ 24.100929] uvd vclk: 0 dclk: 0
[ 24.100932] power level 0 sclk: 30000 mclk: 15000 vddc: 900
vddci: 850 pcie gen: 3
[ 24.100933] status:
[ 24.100934] c
[ 24.100935] b
[ 24.100939] switching to power state:
[ 24.100940] ui class:
[ 24.100941] performance
[ 24.100943] internal class:
[ 24.100944] none
[ 24.100948] caps:
[ 24.100951] uvd vclk: 0 dclk: 0
[ 24.100954] power level 0 sclk: 30000 mclk: 15000 vddc: 825
vddci: 850 pcie gen: 3
[ 24.100956] power level 1 sclk: 45000 mclk: 125000 vddc: 900
vddci: 975 pcie gen: 3
[ 24.100959] power level 2 sclk: 85000 mclk: 125000 vddc: 1000
vddci: 975 pcie gen: 3
[ 24.100961] power level 3 sclk: 90000 mclk: 125000 vddc: 1025
vddci: 975 pcie gen: 3
[ 24.100962] status:
[ 24.100963] r
[ 24.119263] usb-storage 3-1:1.0: USB Mass Storage device detected
[ 24.119319] usb-storage 3-1:1.0: Quirks match for vid 13fe pid 3600: 4000
[ 24.119348] scsi host6: usb-storage 3-1:1.0
[ 24.119413] usbcore: registered new interface driver usb-storage
[ 24.119899] usbcore: registered new interface driver uas
Probably, the problem is caused by another package? But how can I even guess
which one to check?
--
You are receiving this mail because:
You are watching the assignee of the bug.
More information about the dri-devel
mailing list