Advertisement
Guest User

Untitled

a guest
Jul 19th, 2018
169
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.41 KB | None | 0 0
  1. To: linux-usb@vger.kernel.org
  2. From: Hal Emmerich <hal@halemmerich.com>
  3. Subject: PROBLEM: Regression, USB devices not recognized if plugged in after
  4. system boots
  5. Message-ID: <aa549aed-b070-f7f0-655d-d61b5ca43284@halemmerich.com>
  6. Date: Thu, 19 Jul 2018 12:03:29 -0500
  7. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
  8. Thunderbird/52.9.1
  9. MIME-Version: 1.0
  10. Content-Type: text/plain; charset=UTF-8; format=flowed
  11. Content-Transfer-Encoding: 8bit
  12. Content-Language: en-US
  13.  
  14. [1.] One line summary of the problem: Regression, USB devices not
  15. recognized if plugged in after system boots
  16. [2.] Full description of the problem/report:
  17.  
  18. If a usb device is plugged in before system begins booting into the
  19. kernel, it will be recognized once boot completes.
  20. However, if a usb device is plugged in once boot completes the
  21. system will not recognized it, no messages are added to dmesg.
  22. If CONFIG_USB_DWC2_DEBUG is set to yes, two messages are added to
  23. dmesg when a usb device is plugged in:
  24. dwc2 ff580000.usb: gintsts=40000001 gintmsk=f0000000
  25. dwc2 ff580000.usb: Session request interrupt - lx_state=2
  26. ##Reverting the merge made at commit
  27. 6d23ee9caa6790aea047f9aca7f3c03cb8d96eb6 (The main 4.17 merge) fixes the
  28. issue##
  29.  
  30. [3.] Keywords (i.e., modules, networking, kernel): usb, dwc2, kernel, arm
  31. [4.] Kernel information:
  32.  
  33. [4.1.] Kernel version (from /proc/version):
  34. Linux version 4.17.6 (root@debian-build) (gcc version 5.4.1 20160919
  35. (15:5.4.1+svn241155-1)) #1 SMP PREEMPT Thu Jul 12 21:40:35 CDT 2018
  36.  
  37. [4.2.] Kernel .config file:
  38.  
  39. [5.] Most recent kernel version which did not have the bug: 4.16.18
  40.  
  41.  
  42. [6.] Output of Oops.. message (if applicable) with symbolic information
  43. resolved (see Documentation/admin-guide/bug-hunting.rst)
  44. [7.] A small shell script or example program which triggers the
  45. problem (if possible)
  46. [8.] Environment
  47. [8.1.] Software (add the output of the ver_linux script here)
  48.  
  49. [8.2.] Processor information (from /proc/cpuinfo):
  50.  
  51. processor : 0
  52. model name : ARMv7 Processor rev 1 (v7l)
  53. BogoMIPS : 48.00
  54. Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4
  55. idiva idivt vfpd32 lpae evtstrm
  56. CPU implementer : 0x41
  57. CPU architecture: 7
  58. CPU variant : 0x0
  59. CPU part : 0xc0d
  60. CPU revision : 1
  61.  
  62. processor : 1
  63. model name : ARMv7 Processor rev 1 (v7l)
  64. BogoMIPS : 48.00
  65. Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4
  66. idiva idivt vfpd32 lpae evtstrm
  67. CPU implementer : 0x41
  68. CPU architecture: 7
  69. CPU variant : 0x0
  70. CPU part : 0xc0d
  71. CPU revision : 1
  72.  
  73. processor : 2
  74. model name : ARMv7 Processor rev 1 (v7l)
  75. BogoMIPS : 48.00
  76. Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4
  77. idiva idivt vfpd32 lpae evtstrm
  78. CPU implementer : 0x41
  79. CPU architecture: 7
  80. CPU variant : 0x0
  81. CPU part : 0xc0d
  82. CPU revision : 1
  83.  
  84. processor : 3
  85. model name : ARMv7 Processor rev 1 (v7l)
  86. BogoMIPS : 48.00
  87. Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4
  88. idiva idivt vfpd32 lpae evtstrm
  89. CPU implementer : 0x41
  90. CPU architecture: 7
  91. CPU variant : 0x0
  92. CPU part : 0xc0d
  93. CPU revision : 1
  94.  
  95. Hardware : Rockchip (Device Tree)
  96. Revision : 0000
  97. Serial : 0000000000000000
  98.  
  99.  
  100. [8.3.] Module information (from /proc/modules):
  101.  
  102. vfat 20480 1 - Live 0xbf16f000
  103. fat 65536 1 vfat, Live 0xbf158000
  104. ath9k_htc 65536 0 - Live 0xbf140000
  105. ath9k_common 16384 1 ath9k_htc, Live 0xbf137000
  106. ath9k_hw 360448 2 ath9k_htc,ath9k_common, Live 0xbf0d1000
  107. ath 24576 3 ath9k_htc,ath9k_common,ath9k_hw, Live 0xbf0c7000
  108. mac80211 561152 1 ath9k_htc, Live 0xbf00f000
  109. autofs4 36864 2 - Live 0xbf000000
  110.  
  111.  
  112. [8.4.] Loaded driver and hardwar
  113. e information (/proc/ioports, /proc/iomem)
  114. 00000000-feefffff : System RAM
  115. 00008000-00dfffff : Kernel code
  116. 01000000-011008f3 : Kernel data
  117. ff0c0000-ff0c3fff : dwmmc@ff0c0000
  118. ff0d0000-ff0d3fff : dwmmc@ff0d0000
  119. ff0f0000-ff0f3fff : dwmmc@ff0f0000
  120. ff110000-ff110fff : spi@ff110000
  121. ff130000-ff130fff : spi@ff130000
  122. ff140000-ff140fff : i2c@ff140000
  123. ff160000-ff160fff : i2c@ff160000
  124. ff170000-ff170fff : i2c@ff170000
  125. ff180000-ff18001f : serial
  126. ff190000-ff19001f : serial
  127. ff250000-ff253fff : dma-controller@ff250000
  128. ff250000-ff253fff : dma-controller@ff250000
  129. ff280000-ff2800ff : tsadc@ff280000
  130. ff500000-ff5000ff : usb@ff500000
  131. ff540000-ff57ffff : usb@ff540000
  132. ff580000-ff5bffff : usb@ff580000
  133. ff650000-ff650fff : i2c@ff650000
  134. ff660000-ff660fff : i2c@ff660000
  135. ff680000-ff68000f : pwm@ff680000
  136. ff680010-ff68001f : pwm@ff680010
  137. ff690000-ff69001f : serial
  138. ff700000-ff717fff : ff700000.bus_intmem
  139. ff720000-ff720fff : ff720000.sram
  140. ff750000-ff7500ff : gpio0@ff750000
  141. ff780000-ff7800ff : gpio1@ff780000
  142. ff790000-ff7900ff : gpio2@ff790000
  143. ff7a0000-ff7a00ff : gpio3@ff7a0000
  144. ff7b0000-ff7b00ff : gpio4@ff7b0000
  145. ff7c0000-ff7c00ff : gpio5@ff7c0000
  146. ff7d0000-ff7d00ff : gpio6@ff7d0000
  147. ff7e0000-ff7e00ff : gpio7@ff7e0000
  148. ff7f0000-ff7f00ff : gpio8@ff7f0000
  149. ff800000-ff8000ff : watchdog@ff800000
  150. ff890000-ff89ffff : i2s@ff890000
  151. ff8a0000-ff8a3fff : cypto-controller@ff8a0000
  152. ff930000-ff93019b : vop@ff930000
  153. ff930300-ff9303ff : iommu@ff930300
  154. ff940000-ff94019b : vop@ff940000
  155. ff940300-ff9403ff : iommu@ff940300
  156. ff970000-ff973fff : dp@ff970000
  157. ff980000-ff99ffff : hdmi@ff980000
  158. ffb20000-ffb23fff : dma-controller@ffb20000
  159. ffb20000-ffb23fff : dma-controller@ffb20000
  160. ffb40000-ffb4001f : efuse@ffb40000
  161.  
  162. [8.5.] PCI information ('lspci -vvv' as root) N/A
  163. [8.6.] SCSI information (from /proc/scsi/scsi) N/A
  164. [8.7.] Other information that might be relevant to the problem
  165. (please look in /proc and include all information that you
  166. think to be relevant):
  167. [X.] Other notes, patches, fixes, workarounds:
  168.  
  169. Reverting the merge made at commit
  170. 6d23ee9caa6790aea047f9aca7f3c03cb8d96eb6 fixes the issue
  171.  
  172. Walking through the dmesg logs with and without that commit I found this
  173. difference at the same point in the boot process:
  174.  
  175. dwc2 ff540000.usb: In host mode, hprt0=00001501
  176. With the non-functional commit
  177. dwc2 ff540000.usb: In host mode, hprt0=00001101
  178.  
  179. This difference corresponds to bit 10 being set in the hprt0 register,
  180. but I can’t tell what this bits function is in hw.h
  181.  
  182. disabling power_down and lpm in dwc2_set_his_params in params.c (like
  183. this
  184. https://github.com/torvalds/linux/commit/d98c624ab3bf9c3c988c3b7d0f24e703061a172f#diff-3a905b19fc3744269a82aeec54a7e405)
  185. did not help.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement