Re: rtlwifi oops
On 10/31/2017 06:11 AM, Barry Day wrote: On Sun, Oct 29, 2017 at 01:08:24AM +0300, nirinA raseliarison wrote: [ 145.966016] usb 2-1.4: new high-speed USB device number 4 using ehci-pci [ 146.045808] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8178 [ 146.045811] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 146.045812] usb 2-1.4: Product: 802.11n WLAN Adapter [ 146.045813] usb 2-1.4: Manufacturer: Realtek [ 146.045814] usb 2-1.4: SerialNumber: 00e04c01 [ 146.202043] rtl8192cu: Chip version 0x11 [ 146.278549] rtl8192cu: Board Type 0 [ 146.278790] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [ 146.278823] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin [ 146.278938] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' [ 146.279113] usbcore: registered new interface driver rtl8192cu [ 146.281706] usbcore: registered new interface driver rtl8xxxu -- nirinA It appears that both rtl8192cu and rtl8xxxu are being loaded for the one device. Try blacklisting one of them. both seem to work fine; i'll use rtl8192cu and blacklist rtl8xxxu. thanks, Barry -- nirinA
Re: rtlwifi oops
On Sun, Oct 29, 2017 at 01:08:24AM +0300, nirinA raseliarison wrote: > [ 145.966016] usb 2-1.4: new high-speed USB device number 4 using ehci-pci > [ 146.045808] usb 2-1.4: New USB device found, idVendor=0bda, > idProduct=8178 > [ 146.045811] usb 2-1.4: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 146.045812] usb 2-1.4: Product: 802.11n WLAN Adapter > [ 146.045813] usb 2-1.4: Manufacturer: Realtek > [ 146.045814] usb 2-1.4: SerialNumber: 00e04c01 > [ 146.202043] rtl8192cu: Chip version 0x11 > [ 146.278549] rtl8192cu: Board Type 0 > [ 146.278790] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 > [ 146.278823] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin > [ 146.278938] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' > [ 146.279113] usbcore: registered new interface driver rtl8192cu > [ 146.281706] usbcore: registered new interface driver rtl8xxxu > -- > nirinA It appears that both rtl8192cu and rtl8xxxu are being loaded for the one device. Try blacklisting one of them. Barry
Re: rtlwifi oops
On 10/28/2017 01:57 AM, James Cameron wrote: [snip] Your dmesg shows the mouse is discovered, then disconnects, then reconnects. I can't tell if your mouse normally does this. Can you also test for the wireless problem without the USB mouse, or with a different mouse? a new dmesg below with another usb mouse. Your dmesg also shows "cannot get freq" for USB audio device endpoints, but I'm not sure what this means. it seems that this device does not support reading the sample rate. i added its usb id in sound/usb/quirks.c:snd_usb_get_sample_rate_quirk so that this "cannot get freq" is not logged anymore. [snip] thanks, [0.00] random: get_random_bytes called from start_kernel+0x2a/0x413 with crng_init=0 [0.00] Linux version 4.13.8.20171019 (root@supernova) (gcc version 7.2.0 (GCC)) #2 SMP Sat Oct 28 16:27:44 EAT 2017 [0.00] Command line: BOOT_IMAGE=nirinA ro root=802 vt.default_utf8=0 console=tty0 raid=noautodetect [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009d7ff] usable [0.00] BIOS-e820: [mem 0x0009d800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x1fff] usable [0.00] BIOS-e820: [mem 0x2000-0x201f] reserved [0.00] BIOS-e820: [mem 0x2020-0x40003fff] usable [0.00] BIOS-e820: [mem 0x40004000-0x40004fff] reserved [0.00] BIOS-e820: [mem 0x40005000-0xcdf30fff] usable [0.00] BIOS-e820: [mem 0xcdf31000-0xce25afff] reserved [0.00] BIOS-e820: [mem 0xce25b000-0xce25bfff] ACPI data [0.00] BIOS-e820: [mem 0xce25c000-0xce373fff] ACPI NVS [0.00] BIOS-e820: [mem 0xce374000-0xce6d8fff] reserved [0.00] BIOS-e820: [mem 0xce6d9000-0xce6d9fff] usable [0.00] BIOS-e820: [mem 0xce6da000-0xce71cfff] ACPI NVS [0.00] BIOS-e820: [mem 0xce71d000-0xcee19fff] usable [0.00] BIOS-e820: [mem 0xcee1a000-0xceff1fff] reserved [0.00] BIOS-e820: [mem 0xceff2000-0xceff] usable [0.00] BIOS-e820: [mem 0xcf80-0xdf9f] reserved [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00021f5f] usable [0.00] NX (Execute Disable) protection: active [0.00] random: fast init done [0.00] SMBIOS 2.7 present. [0.00] DMI: To be filled by O.E.M. To be filled by O.E.M./ONDA H61V Ver:4.01, BIOS 4.6.5 01/07/2013 [0.00] tsc: Fast TSC calibration using PIT [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] e820: last_pfn = 0x21f600 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-D3FFF write-protect [0.00] D4000-E7FFF uncachable [0.00] E8000-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask E write-back [0.00] 1 base 2 mask FE000 write-back [0.00] 2 base 0E000 mask FE000 uncachable [0.00] 3 base 0D000 mask FF000 uncachable [0.00] 4 base 0CF80 mask FFF80 uncachable [0.00] 5 base 21F80 mask FFF80 uncachable [0.00] 6 base 21F60 mask FFFE0 uncachable [0.00] 7 disabled [0.00] 8 disabled [0.00] 9 disabled [0.00] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT [0.00] e820: update [mem 0xcf80-0x] usable ==> reserved [0.00] e820: last_pfn = 0xcf000 max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000fd6f0-0x000fd6ff] mapped at
Re: rtlwifi oops
On Sat, Oct 28, 2017 at 12:02:30AM +0300, nirinA raseliarison wrote: > On 10/27/2017 07:57 AM, James Cameron wrote: > >On Fri, Oct 27, 2017 at 04:08:48AM +0300, nirinA raseliarison wrote: > >>hi all, > >>i applied the patch against 4.13.8. i still got some trouble, dmesg > >>is below. > > > >As this new event does not have "disabled by hub (EMI?)", it is a > >different problem to your 19th October post, so I don't think the > >patch is relevant. > > > >>after i plugged the device, it seems to be detected and all modules > >>loaded, but when i tried to connect to an access point, by using > >>wicd, it halted after a while. at this point, all usb ports are > >>broken, there was no more log in dmesg, > > > >If the other USB ports are not responding, then your problem is > >probably wider than the wireless device, and the wireless device > >is acting as the "canary in the mine"; failing first because it is > >the most active. > > > >Can you test to exclude possibility of damaged USB host controller or > >hub? > > yes, dmesg below with an usb audio adapter and a usb mouse plugged at > boot time. then the rtl8192cu plugged, and i'm using it to retrieve > and send this mail. Thanks. Your dmesg shows the mouse is discovered, then disconnects, then reconnects. I can't tell if your mouse normally does this. Can you also test for the wireless problem without the USB mouse, or with a different mouse? Your dmesg also shows "cannot get freq" for USB audio device endpoints, but I'm not sure what this means. > my first guess was also about a damaged device or usb port > as those random crashes are recent. > note that the device i'm using here is not the same as the one > that triggered the previous errors. > > >>lsusb still showed the device even after being unplugged. it got > >>even worse as reboot failed. > > > >Yes, once a USB host controller is failed, organised reboot can be > >difficult. lsusb not updated confirms host controller not responding. > > > >>i cannot really trace the error as right now all thing works fine. > > > >Your dmesg looks like you removed and reinserted the wireless device > >several times. Did you do that, or did the system do it without any > >physical action? > > no, the device was always connected. i've only removed it long after > i noticed something went wrong and just before i tried reboot. Okay, thanks. I'm worried that unexpected disconnect suggests a USB host or hub problem. > >A full dmesg from boot may be interesting, at least to better > >understand the USB host controller. > > > > here it is. > thanks, > [...] -- James Cameron http://quozl.netrek.org/
Re: rtlwifi oops
On 10/27/2017 07:57 AM, James Cameron wrote: On Fri, Oct 27, 2017 at 04:08:48AM +0300, nirinA raseliarison wrote: hi all, i applied the patch against 4.13.8. i still got some trouble, dmesg is below. As this new event does not have "disabled by hub (EMI?)", it is a different problem to your 19th October post, so I don't think the patch is relevant. after i plugged the device, it seems to be detected and all modules loaded, but when i tried to connect to an access point, by using wicd, it halted after a while. at this point, all usb ports are broken, there was no more log in dmesg, If the other USB ports are not responding, then your problem is probably wider than the wireless device, and the wireless device is acting as the "canary in the mine"; failing first because it is the most active. Can you test to exclude possibility of damaged USB host controller or hub? yes, dmesg below with an usb audio adapter and a usb mouse plugged at boot time. then the rtl8192cu plugged, and i'm using it to retrieve and send this mail. my first guess was also about a damaged device or usb port as those random crashes are recent. note that the device i'm using here is not the same as the one that triggered the previous errors. lsusb still showed the device even after being unplugged. it got even worse as reboot failed. Yes, once a USB host controller is failed, organised reboot can be difficult. lsusb not updated confirms host controller not responding. i cannot really trace the error as right now all thing works fine. Your dmesg looks like you removed and reinserted the wireless device several times. Did you do that, or did the system do it without any physical action? no, the device was always connected. i've only removed it long after i noticed something went wrong and just before i tried reboot. A full dmesg from boot may be interesting, at least to better understand the USB host controller. here it is. thanks, ## [0.00] random: get_random_bytes called from start_kernel+0x2a/0x413 with crng_init=0 [0.00] Linux version 4.13.8.20171019 (root@supernova) (gcc version 7.2.0 (GCC)) #1 SMP Thu Oct 19 03:53:05 EAT 2017 [0.00] Command line: BOOT_IMAGE=nirinA ro root=802 vt.default_utf8=0 console=tty0 raid=noautodetect [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009d7ff] usable [0.00] BIOS-e820: [mem 0x0009d800-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x1fff] usable [0.00] BIOS-e820: [mem 0x2000-0x201f] reserved [0.00] BIOS-e820: [mem 0x2020-0x40003fff] usable [0.00] BIOS-e820: [mem 0x40004000-0x40004fff] reserved [0.00] BIOS-e820: [mem 0x40005000-0xcdf30fff] usable [0.00] BIOS-e820: [mem 0xcdf31000-0xce25afff] reserved [0.00] BIOS-e820: [mem 0xce25b000-0xce25bfff] ACPI data [0.00] BIOS-e820: [mem 0xce25c000-0xce373fff] ACPI NVS [0.00] BIOS-e820: [mem 0xce374000-0xce6d8fff] reserved [0.00] BIOS-e820: [mem 0xce6d9000-0xce6d9fff] usable [0.00] BIOS-e820: [mem 0xce6da000-0xce71cfff] ACPI NVS [0.00] BIOS-e820: [mem 0xce71d000-0xcee19fff] usable [0.00] BIOS-e820: [mem 0xcee1a000-0xceff1fff] reserved [0.00] BIOS-e820: [mem 0xceff2000-0xceff] usable [0.00] BIOS-e820: [mem 0xcf80-0xdf9f] reserved [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00021f5f] usable [0.00] NX (Execute Disable) protection: active [0.00] random: fast init done [0.00] SMBIOS 2.7 present. [0.00] DMI: To be filled by O.E.M. To be filled by O.E.M./ONDA H61V Ver:4.01, BIOS 4.6.5 01/07/2013 [0.00] tsc: Fast TSC calibration using PIT [0.00] e820: update [mem
Re: rtlwifi oops
On Fri, Oct 27, 2017 at 04:08:48AM +0300, nirinA raseliarison wrote: > hi all, > i applied the patch against 4.13.8. i still got some trouble, dmesg > is below. As this new event does not have "disabled by hub (EMI?)", it is a different problem to your 19th October post, so I don't think the patch is relevant. > after i plugged the device, it seems to be detected and all modules > loaded, but when i tried to connect to an access point, by using > wicd, it halted after a while. at this point, all usb ports are > broken, there was no more log in dmesg, If the other USB ports are not responding, then your problem is probably wider than the wireless device, and the wireless device is acting as the "canary in the mine"; failing first because it is the most active. Can you test to exclude possibility of damaged USB host controller or hub? > lsusb still showed the device even after being unplugged. it got > even worse as reboot failed. Yes, once a USB host controller is failed, organised reboot can be difficult. lsusb not updated confirms host controller not responding. > i cannot really trace the error as right now all thing works fine. Your dmesg looks like you removed and reinserted the wireless device several times. Did you do that, or did the system do it without any physical action? A full dmesg from boot may be interesting, at least to better understand the USB host controller. -- James Cameron http://quozl.netrek.org/
Re: rtlwifi oops
hi all, i applied the patch against 4.13.8. i still got some trouble, dmesg is below. after i plugged the device, it seems to be detected and all modules loaded, but when i tried to connect to an access point, by using wicd, it halted after a while. at this point, all usb ports are broken, there was no more log in dmesg, lsusb still showed the device even after being unplugged. it got even worse as reboot failed. i cannot really trace the error as right now all thing works fine. ## [101297.29] usb 2-1.4: new high-speed USB device number 6 using ehci-pci [101297.290836] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8178 [101297.290839] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [101297.290840] usb 2-1.4: Product: 802.11n WLAN Adapter [101297.290841] usb 2-1.4: Manufacturer: Realtek [101297.290842] usb 2-1.4: SerialNumber: 00e04c01 [101297.841845] rtl8192cu: Chip version 0x11 [101297.97] rtl8192cu: Board Type 0 [101297.973581] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [101297.973621] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin [101297.973743] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' [101297.973923] usbcore: registered new interface driver rtl8192cu [101298.013513] usbcore: registered new interface driver rtl8xxxu [101298.113014] rtl8192cu 2-1.4:1.0 wlan125: renamed from wlan0 [101298.116255] rtl8192cu 2-1.4:1.0 wlan4: renamed from wlan125 [101298.319580] usb 2-1.4: USB disconnect, device number 6 [101298.508120] usb 2-1.4: new high-speed USB device number 7 using ehci-pci [101298.748134] usb 2-1.4: new high-speed USB device number 8 using ehci-pci [101298.827700] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8178 [101298.827702] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [101298.827703] usb 2-1.4: Product: 802.11n WLAN Adapter [101298.827704] usb 2-1.4: Manufacturer: Realtek [101298.827705] usb 2-1.4: SerialNumber: 00e04c01 [101298.828320] rtl8192cu: Chip version 0x11 [101298.907705] rtl8192cu: Board Type 0 [101298.907945] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [101298.907976] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin [101298.908145] ieee80211 phy1: Selected rate control algorithm 'rtl_rc' [101298.922774] rtl8192cu 2-1.4:1.0 wlan124: renamed from wlan0 [101298.926242] rtl8192cu 2-1.4:1.0 wlan4: renamed from wlan124 [101312.904723] rtl8192cu: MAC auto ON okay! [101312.939101] rtl8192cu: Tx queue select: 0x05 [101313.541630] IPv6: ADDRCONF(NETDEV_UP): wlan4: link is not ready [101322.297910] rtl8192cu: MAC auto ON okay! [101322.331036] rtl8192cu: Tx queue select: 0x05 [101322.933065] IPv6: ADDRCONF(NETDEV_UP): wlan4: link is not ready [101323.089905] rtl8192cu: MAC auto ON okay! [101323.122907] rtl8192cu: Tx queue select: 0x05 [101323.730181] IPv6: ADDRCONF(NETDEV_UP): wlan4: link is not ready [101325.455267] usb 2-1.4: USB disconnect, device number 8 [101325.460166] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffed value=0xf9 [101325.460168] rtl_usb: reg 0x422, usbctrl_vendorreq TimeOut! status:0xffed value=0x100 [101325.460171] rtl_usb: reg 0x542, usbctrl_vendorreq TimeOut! status:0xffed value=0x3fd [101325.460186] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffed value=0xf9 [101325.655146] usb 2-1.4: new high-speed USB device number 9 using ehci-pci [101325.734893] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8178 [101325.734897] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [101325.734898] usb 2-1.4: Product: 802.11n WLAN Adapter [101325.734899] usb 2-1.4: Manufacturer: Realtek [101325.734900] usb 2-1.4: SerialNumber: 00e04c01 [101325.735636] rtl8192cu: Chip version 0x11 [101325.812035] rtl8192cu: Board Type 0 [101325.812394] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [101325.812470] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin [101325.812725] ieee80211 phy2: Selected rate control algorithm 'rtl_rc' [101325.827120] rtl8192cu 2-1.4:1.0 wlan123: renamed from wlan0 [101325.832254] rtl8192cu 2-1.4:1.0 wlan4: renamed from wlan123 [101332.879463] usb 2-1.4: USB disconnect, device number 9 [101333.072149] usb 2-1.4: new high-speed USB device number 10 using ehci-pci [101333.151841] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8178 [101333.151843] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [101333.151845] usb 2-1.4: Product: 802.11n WLAN Adapter [101333.151846] usb 2-1.4: Manufacturer: Realtek [101333.151847] usb 2-1.4: SerialNumber: 00e04c01 [101333.152585] rtl8192cu: Chip version 0x11 [101333.229738] rtl8192cu: Board Type 0 [101333.229963] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [101333.230038] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin [101333.230298] ieee80211 phy3: Selected rate control algorithm 'rtl_rc' [101333.49] rtl8192cu 2-1.4:1.0 wlan122: renamed
Re: rtlwifi oops
Larry Finger wrote: On 10/18/2017 08:40 PM, nirinA wrote: i checked my dmesg and have this similar log, i think when i unplugged the device. [ 5640.100541] usb 2-1.4: USB disconnect, device number 5 [ 5640.104108] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 [ 5640.104110] rtl_usb: reg 0x422, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 [ 5640.104113] rtl_usb: reg 0x542, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 [ 5640.104127] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffed value=0xd38000 i will apply the patch and will see if i still get this. As I said in the response to your private message: sorry for the private mail, i press reply button instead of reply-all. No, that is a different error. You need to check for the USB disconnect when starting, but no rtl_usb errors. up to now, i have no error when plugging the device with the same machine. the message above only appears from time to time, not always when i unplugged. i also use 2 other rtl8192cu with a raspberry pi and a beaglebone black, but never checked any log when the connection with the devices failed; i just shut down and restart. i'll try to get more detail if some failure will occur with these devices. Larry thanks, --- nirinA
Re: rtlwifi oops
On 10/18/2017 08:40 PM, nirinA wrote: i checked my dmesg and have this similar log, i think when i unplugged the device. [ 5640.100541] usb 2-1.4: USB disconnect, device number 5 [ 5640.104108] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 [ 5640.104110] rtl_usb: reg 0x422, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 [ 5640.104113] rtl_usb: reg 0x542, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 [ 5640.104127] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffed value=0xd38000 i will apply the patch and will see if i still get this. As I said in the response to your private message: No, that is a different error. You need to check for the USB disconnect when starting, but no rtl_usb errors. Larry
Re: rtlwifi oops
i checked my dmesg and have this similar log, i think when i unplugged the device. [ 5640.100541] usb 2-1.4: USB disconnect, device number 5 [ 5640.104108] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 [ 5640.104110] rtl_usb: reg 0x422, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 [ 5640.104113] rtl_usb: reg 0x542, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 [ 5640.104127] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffed value=0xd38000 i will apply the patch and will see if i still get this. thanks, -- nirinA Larry Finger wrote: On 10/18/2017 06:18 PM, nirinA wrote: not really a rtlwifi oops then. maybe issue with udev as that also disabled the usb mouse. but i have no problem since. i will report if i will catch it again. thanks, -- nirinA James Cameron wrote: On Thu, Oct 19, 2017 at 01:31:43AM +0300, nirinA wrote: hello there, i got the oops below with a rtl8192cu:0bda:8178 and kernel 4.13.6, but cannot reproduce it. i use this device since 4.3 or so without noticing any issue. nirinA [ 239.338040] usb 2-1.3: new high-speed USB device number 4 using ehci-pci [ 239.417728] usb 2-1.3: New USB device found, idVendor=0bda, idProduct=8178 [ 239.417730] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 239.417731] usb 2-1.3: Product: 802.11n WLAN Adapter [ 239.417732] usb 2-1.3: Manufacturer: Realtek [ 239.417733] usb 2-1.3: SerialNumber: 00e04c01 [ 239.578100] rtl8192cu: Chip version 0x11 [ 239.678225] usb 2-1-port3: disabled by hub (EMI?), re-enabling... Just prior to the oops, your USB hub disabled the port being used by the wireless device. While the response of the driver seems wrong, it is a difficult condition to reproduce; one must either force or forge the disabling by the hub. [ 239.678230] usb 2-1.3: USB disconnect, device number 4 [ 239.679128] rtl_usb: reg 0x30, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 This sequence of events is unusual. A driver should be able to trust that the platform is behaving correctly and normally. In reviewing the USB probe routine, the only thing I could see is that one returned value is not being checked. If the problem happens again, please try the following patch: diff --git a/drivers/net/wireless/realtek/rtlwifi/usb.c b/drivers/net/wireless/realtek/rtlwifi/usb.c index 5590d07d0918..092cd2da15f6 100644 --- a/drivers/net/wireless/realtek/rtlwifi/usb.c +++ b/drivers/net/wireless/realtek/rtlwifi/usb.c @@ -1082,6 +1082,8 @@ int rtl_usb_probe(struct usb_interface *intf, init_completion(>firmware_loading_complete); SET_IEEE80211_DEV(hw, >dev); udev = interface_to_usbdev(intf); + if (!udev) + return -ENODEV; usb_get_dev(udev); usb_priv = rtl_usbpriv(hw); memset(usb_priv, 0, sizeof(*usb_priv)); I will test and push this patch because that value should be checked, but I'm not sure it would correct your problem. Larry
Re: rtlwifi oops
On 10/18/2017 06:18 PM, nirinA wrote: not really a rtlwifi oops then. maybe issue with udev as that also disabled the usb mouse. but i have no problem since. i will report if i will catch it again. thanks, -- nirinA James Cameron wrote: On Thu, Oct 19, 2017 at 01:31:43AM +0300, nirinA wrote: hello there, i got the oops below with a rtl8192cu:0bda:8178 and kernel 4.13.6, but cannot reproduce it. i use this device since 4.3 or so without noticing any issue. nirinA [ 239.338040] usb 2-1.3: new high-speed USB device number 4 using ehci-pci [ 239.417728] usb 2-1.3: New USB device found, idVendor=0bda, idProduct=8178 [ 239.417730] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 239.417731] usb 2-1.3: Product: 802.11n WLAN Adapter [ 239.417732] usb 2-1.3: Manufacturer: Realtek [ 239.417733] usb 2-1.3: SerialNumber: 00e04c01 [ 239.578100] rtl8192cu: Chip version 0x11 [ 239.678225] usb 2-1-port3: disabled by hub (EMI?), re-enabling... Just prior to the oops, your USB hub disabled the port being used by the wireless device. While the response of the driver seems wrong, it is a difficult condition to reproduce; one must either force or forge the disabling by the hub. [ 239.678230] usb 2-1.3: USB disconnect, device number 4 [ 239.679128] rtl_usb: reg 0x30, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 This sequence of events is unusual. A driver should be able to trust that the platform is behaving correctly and normally. In reviewing the USB probe routine, the only thing I could see is that one returned value is not being checked. If the problem happens again, please try the following patch: diff --git a/drivers/net/wireless/realtek/rtlwifi/usb.c b/drivers/net/wireless/realtek/rtlwifi/usb.c index 5590d07d0918..092cd2da15f6 100644 --- a/drivers/net/wireless/realtek/rtlwifi/usb.c +++ b/drivers/net/wireless/realtek/rtlwifi/usb.c @@ -1082,6 +1082,8 @@ int rtl_usb_probe(struct usb_interface *intf, init_completion(>firmware_loading_complete); SET_IEEE80211_DEV(hw, >dev); udev = interface_to_usbdev(intf); + if (!udev) + return -ENODEV; usb_get_dev(udev); usb_priv = rtl_usbpriv(hw); memset(usb_priv, 0, sizeof(*usb_priv)); I will test and push this patch because that value should be checked, but I'm not sure it would correct your problem. Larry
Re: rtlwifi oops
not really a rtlwifi oops then. maybe issue with udev as that also disabled the usb mouse. but i have no problem since. i will report if i will catch it again. thanks, -- nirinA James Cameron wrote: On Thu, Oct 19, 2017 at 01:31:43AM +0300, nirinA wrote: hello there, i got the oops below with a rtl8192cu:0bda:8178 and kernel 4.13.6, but cannot reproduce it. i use this device since 4.3 or so without noticing any issue. nirinA [ 239.338040] usb 2-1.3: new high-speed USB device number 4 using ehci-pci [ 239.417728] usb 2-1.3: New USB device found, idVendor=0bda, idProduct=8178 [ 239.417730] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 239.417731] usb 2-1.3: Product: 802.11n WLAN Adapter [ 239.417732] usb 2-1.3: Manufacturer: Realtek [ 239.417733] usb 2-1.3: SerialNumber: 00e04c01 [ 239.578100] rtl8192cu: Chip version 0x11 [ 239.678225] usb 2-1-port3: disabled by hub (EMI?), re-enabling... Just prior to the oops, your USB hub disabled the port being used by the wireless device. While the response of the driver seems wrong, it is a difficult condition to reproduce; one must either force or forge the disabling by the hub. [ 239.678230] usb 2-1.3: USB disconnect, device number 4 [ 239.679128] rtl_usb: reg 0x30, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 [ 239.679131] rtl_usb: reg 0x32, usbctrl_vendorreq TimeOut! status:0xffed value=0x20 [ 239.679133] rtl_usb: reg 0x33, usbctrl_vendorreq TimeOut! status:0xffed value=0x80 [ 239.679134] rtl_usb: reg 0x30, usbctrl_vendorreq TimeOut! status:0xffed value=0x80206f30 [ 239.700640] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [ 239.700648] BUG: unable to handle kernel NULL pointer dereference at (null) [ 239.700682] IP: rtl_deinit_core+0x2e/0x90 [rtlwifi] [ 239.700693] PGD 1c5d5d067 [ 239.700694] P4D 1c5d5d067 [ 239.700701] PUD 1c5d9b067 [ 239.700708] PMD 0 [ 239.700727] Oops: [#1] SMP [ 239.700735] Modules linked in: rtl8192cu(+) rtl_usb rtl8192c_common rtlwifi mac80211 cfg80211 rfkill appletalk ipx p8023 p8022 psnap llc nct6775 hwmon_vid ipv6 hid_generic usbhid hid coretemp hwmon x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic kvm_intel i915 kvm drm_kms_helper evdev i2c_dev irqbypass syscopyarea sysfillrect sysimgblt r8169 crc32_pclmul serio_raw crc32c_intel mii snd_pcsp fb_sys_fops drm fan thermal button battery 8250 8250_base serial_core mei_me snd_hda_intel mei intel_gtt snd_hda_codec video agpgart ehci_pci ehci_hcd lpc_ich snd_hwdep snd_hda_core snd_pcm i2c_algo_bit snd_timer i2c_i801 i2c_core snd soundcore fuse [ 239.700875] CPU: 0 PID: 1174 Comm: udevd Not tainted 4.13.6.20171012 #1 [ 239.700889] Hardware name: To be filled by O.E.M. To be filled by O.E.M./ONDA H61V Ver:4.01, BIOS 4.6.5 01/07/2013 [ 239.700909] task: 8801c5fbc980 task.stack: c99a [ 239.700924] RIP: 0010:rtl_deinit_core+0x2e/0x90 [rtlwifi] [ 239.700936] RSP: :c99a3b40 EFLAGS: 00010207 [ 239.700947] RAX: 0282 RBX: 8801b9440780 RCX: ffea [ 239.700962] RDX: 0001 RSI: 0282 RDI: [ 239.700977] RBP: 8801b944b070 R08: 0001 R09: 02b0 [ 239.700991] R10: ea0008473480 R11: R12: 8801b9441560 [ 239.701006] R13: 8801b944b880 R14: R15: 8801b9441560 [ 239.701021] FS: 7f3eb636e7c0() GS:88021f20() knlGS: [ 239.701037] CS: 0010 DS: ES: CR0: 80050033 [ 239.701050] CR2: CR3: 0001c5d99000 CR4: 001406f0 [ 239.701064] Call Trace: [ 239.701074] ? rtl_usb_probe+0x6b6/0xc50 [rtl_usb] [ 239.701088] ? usb_probe_interface+0xe2/0x2a0 [ 239.701100] ? driver_probe_device+0x21d/0x2d0 [ 239.70] ? __driver_attach+0x8a/0x90 [ 239.701121] ? driver_probe_device+0x2d0/0x2d0 [ 239.701133] ? bus_for_each_dev+0x5c/0x90 [ 239.701143] ? bus_add_driver+0x196/0x220 [ 239.701154] ? driver_register+0x57/0xc0 [ 239.701165] ? usb_register_driver+0x7c/0x140 [ 239.701175] ? 0xa064e000 [ 239.701185] ? do_one_initcall+0x4b/0x190 [ 239.701197] ? kmem_cache_alloc_trace+0xe4/0x1c0 [ 239.701208] ? do_init_module+0x22/0x1e1 [ 239.701219] ? do_init_module+0x5b/0x1e1 [ 239.701229] ? load_module+0x21ff/0x2760 [ 239.701239] ? SYSC_finit_module+0x90/0xb0 [ 239.701249] ? SYSC_finit_module+0x90/0xb0 [ 239.701261] ? entry_SYSCALL_64_fastpath+0x1a/0xa5 [ 239.701272] Code: 00 00 41 57 31 f6 41 56 41 55 41 54 55 53 48 89 fb e8 e7 fe ff ff 4c 8b 7b 48 49 8b bf 10 9b 00 00 49 8d af 10 9b 00 00 48 39 ef <48> 8b 1f 74 44 49 bd 00 01 00 00 00 00 ad de 49 89 de 49 bc 00 [ 239.701327] RIP: rtl_deinit_core+0x2e/0x90 [rtlwifi] RSP: c99a3b40 [ 239.702028] CR2: [ 239.705370] ---[ end trace 6ec9029c0d9c0e13 ]--- [ 239.706311] udevd[528]: worker [1174] failed while handling '/d
Re: rtlwifi oops
On Thu, Oct 19, 2017 at 01:31:43AM +0300, nirinA wrote: > hello there, > i got the oops below with a rtl8192cu:0bda:8178 and kernel 4.13.6, but > cannot reproduce it. > i use this device since 4.3 or so without noticing any issue. > > nirinA > > [ 239.338040] usb 2-1.3: new high-speed USB device number 4 using ehci-pci > [ 239.417728] usb 2-1.3: New USB device found, idVendor=0bda, > idProduct=8178 > [ 239.417730] usb 2-1.3: New USB device strings: Mfr=1, Product=2, > SerialNumber=3 > [ 239.417731] usb 2-1.3: Product: 802.11n WLAN Adapter > [ 239.417732] usb 2-1.3: Manufacturer: Realtek > [ 239.417733] usb 2-1.3: SerialNumber: 00e04c01 > [ 239.578100] rtl8192cu: Chip version 0x11 > [ 239.678225] usb 2-1-port3: disabled by hub (EMI?), re-enabling... Just prior to the oops, your USB hub disabled the port being used by the wireless device. While the response of the driver seems wrong, it is a difficult condition to reproduce; one must either force or forge the disabling by the hub. > [ 239.678230] usb 2-1.3: USB disconnect, device number 4 > [ 239.679128] rtl_usb: reg 0x30, usbctrl_vendorreq TimeOut! > status:0xffed value=0x0 > [ 239.679131] rtl_usb: reg 0x32, usbctrl_vendorreq TimeOut! > status:0xffed value=0x20 > [ 239.679133] rtl_usb: reg 0x33, usbctrl_vendorreq TimeOut! > status:0xffed value=0x80 > [ 239.679134] rtl_usb: reg 0x30, usbctrl_vendorreq TimeOut! > status:0xffed value=0x80206f30 > [ 239.700640] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 > [ 239.700648] BUG: unable to handle kernel NULL pointer dereference at > (null) > [ 239.700682] IP: rtl_deinit_core+0x2e/0x90 [rtlwifi] > [ 239.700693] PGD 1c5d5d067 > [ 239.700694] P4D 1c5d5d067 > [ 239.700701] PUD 1c5d9b067 > [ 239.700708] PMD 0 > > [ 239.700727] Oops: [#1] SMP > [ 239.700735] Modules linked in: rtl8192cu(+) rtl_usb rtl8192c_common > rtlwifi mac80211 cfg80211 rfkill appletalk ipx p8023 p8022 psnap llc nct6775 > hwmon_vid ipv6 hid_generic usbhid hid coretemp hwmon x86_pkg_temp_thermal > intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek > snd_hda_codec_generic kvm_intel i915 kvm drm_kms_helper evdev i2c_dev > irqbypass syscopyarea sysfillrect sysimgblt r8169 crc32_pclmul serio_raw > crc32c_intel mii snd_pcsp fb_sys_fops drm fan thermal button battery 8250 > 8250_base serial_core mei_me snd_hda_intel mei intel_gtt snd_hda_codec video > agpgart ehci_pci ehci_hcd lpc_ich snd_hwdep snd_hda_core snd_pcm > i2c_algo_bit snd_timer i2c_i801 i2c_core snd soundcore fuse > [ 239.700875] CPU: 0 PID: 1174 Comm: udevd Not tainted 4.13.6.20171012 #1 > [ 239.700889] Hardware name: To be filled by O.E.M. To be filled by > O.E.M./ONDA H61V Ver:4.01, BIOS 4.6.5 01/07/2013 > [ 239.700909] task: 8801c5fbc980 task.stack: c99a > [ 239.700924] RIP: 0010:rtl_deinit_core+0x2e/0x90 [rtlwifi] > [ 239.700936] RSP: :c99a3b40 EFLAGS: 00010207 > [ 239.700947] RAX: 0282 RBX: 8801b9440780 RCX: > ffea > [ 239.700962] RDX: 0001 RSI: 0282 RDI: > > [ 239.700977] RBP: 8801b944b070 R08: 0001 R09: > 02b0 > [ 239.700991] R10: ea0008473480 R11: R12: > 8801b9441560 > [ 239.701006] R13: 8801b944b880 R14: R15: > 8801b9441560 > [ 239.701021] FS: 7f3eb636e7c0() GS:88021f20() > knlGS: > [ 239.701037] CS: 0010 DS: ES: CR0: 80050033 > [ 239.701050] CR2: CR3: 0001c5d99000 CR4: > 001406f0 > [ 239.701064] Call Trace: > [ 239.701074] ? rtl_usb_probe+0x6b6/0xc50 [rtl_usb] > [ 239.701088] ? usb_probe_interface+0xe2/0x2a0 > [ 239.701100] ? driver_probe_device+0x21d/0x2d0 > [ 239.70] ? __driver_attach+0x8a/0x90 > [ 239.701121] ? driver_probe_device+0x2d0/0x2d0 > [ 239.701133] ? bus_for_each_dev+0x5c/0x90 > [ 239.701143] ? bus_add_driver+0x196/0x220 > [ 239.701154] ? driver_register+0x57/0xc0 > [ 239.701165] ? usb_register_driver+0x7c/0x140 > [ 239.701175] ? 0xa064e000 > [ 239.701185] ? do_one_initcall+0x4b/0x190 > [ 239.701197] ? kmem_cache_alloc_trace+0xe4/0x1c0 > [ 239.701208] ? do_init_module+0x22/0x1e1 > [ 239.701219] ? do_init_module+0x5b/0x1e1 > [ 239.701229] ? load_module+0x21ff/0x2760 > [ 239.701239] ? SYSC_finit_module+0x90/0xb0 > [ 239.701249] ? SYSC_finit_module+0x90/0xb0 > [ 239.701261] ? entry_SYSCALL_64_fastpath+0x1a/0xa5 > [ 239.701272] Code: 00 00 41 57 31 f6 41 56 41 55 41 54 55 53 48 89 fb e8 > e7 fe ff ff 4c 8b 7b 48 49 8b bf 10 9b 00 00 49 8d af 10 9b 00 00 48 39 ef > <48> 8b 1f 74 44 49 bd 00 01 00 00 00 00 ad de 49 89 de 49 bc 00 > [ 239.701327] RIP: rtl_deinit_core+0x2e/0x90 [rtlwifi] RSP: > c99a3b40 > [ 239.702028] CR2: > [ 239.705370] ---[ end trace 6ec9029c0d9c0e13 ]--- > [ 239.706311] udevd[528]: worker [1174] failed while handling >
rtlwifi oops
hello there, i got the oops below with a rtl8192cu:0bda:8178 and kernel 4.13.6, but cannot reproduce it. i use this device since 4.3 or so without noticing any issue. nirinA [ 239.338040] usb 2-1.3: new high-speed USB device number 4 using ehci-pci [ 239.417728] usb 2-1.3: New USB device found, idVendor=0bda, idProduct=8178 [ 239.417730] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 239.417731] usb 2-1.3: Product: 802.11n WLAN Adapter [ 239.417732] usb 2-1.3: Manufacturer: Realtek [ 239.417733] usb 2-1.3: SerialNumber: 00e04c01 [ 239.578100] rtl8192cu: Chip version 0x11 [ 239.678225] usb 2-1-port3: disabled by hub (EMI?), re-enabling... [ 239.678230] usb 2-1.3: USB disconnect, device number 4 [ 239.679128] rtl_usb: reg 0x30, usbctrl_vendorreq TimeOut! status:0xffed value=0x0 [ 239.679131] rtl_usb: reg 0x32, usbctrl_vendorreq TimeOut! status:0xffed value=0x20 [ 239.679133] rtl_usb: reg 0x33, usbctrl_vendorreq TimeOut! status:0xffed value=0x80 [ 239.679134] rtl_usb: reg 0x30, usbctrl_vendorreq TimeOut! status:0xffed value=0x80206f30 [ 239.700640] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [ 239.700648] BUG: unable to handle kernel NULL pointer dereference at (null) [ 239.700682] IP: rtl_deinit_core+0x2e/0x90 [rtlwifi] [ 239.700693] PGD 1c5d5d067 [ 239.700694] P4D 1c5d5d067 [ 239.700701] PUD 1c5d9b067 [ 239.700708] PMD 0 [ 239.700727] Oops: [#1] SMP [ 239.700735] Modules linked in: rtl8192cu(+) rtl_usb rtl8192c_common rtlwifi mac80211 cfg80211 rfkill appletalk ipx p8023 p8022 psnap llc nct6775 hwmon_vid ipv6 hid_generic usbhid hid coretemp hwmon x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic kvm_intel i915 kvm drm_kms_helper evdev i2c_dev irqbypass syscopyarea sysfillrect sysimgblt r8169 crc32_pclmul serio_raw crc32c_intel mii snd_pcsp fb_sys_fops drm fan thermal button battery 8250 8250_base serial_core mei_me snd_hda_intel mei intel_gtt snd_hda_codec video agpgart ehci_pci ehci_hcd lpc_ich snd_hwdep snd_hda_core snd_pcm i2c_algo_bit snd_timer i2c_i801 i2c_core snd soundcore fuse [ 239.700875] CPU: 0 PID: 1174 Comm: udevd Not tainted 4.13.6.20171012 #1 [ 239.700889] Hardware name: To be filled by O.E.M. To be filled by O.E.M./ONDA H61V Ver:4.01, BIOS 4.6.5 01/07/2013 [ 239.700909] task: 8801c5fbc980 task.stack: c99a [ 239.700924] RIP: 0010:rtl_deinit_core+0x2e/0x90 [rtlwifi] [ 239.700936] RSP: :c99a3b40 EFLAGS: 00010207 [ 239.700947] RAX: 0282 RBX: 8801b9440780 RCX: ffea [ 239.700962] RDX: 0001 RSI: 0282 RDI: [ 239.700977] RBP: 8801b944b070 R08: 0001 R09: 02b0 [ 239.700991] R10: ea0008473480 R11: R12: 8801b9441560 [ 239.701006] R13: 8801b944b880 R14: R15: 8801b9441560 [ 239.701021] FS: 7f3eb636e7c0() GS:88021f20() knlGS: [ 239.701037] CS: 0010 DS: ES: CR0: 80050033 [ 239.701050] CR2: CR3: 0001c5d99000 CR4: 001406f0 [ 239.701064] Call Trace: [ 239.701074] ? rtl_usb_probe+0x6b6/0xc50 [rtl_usb] [ 239.701088] ? usb_probe_interface+0xe2/0x2a0 [ 239.701100] ? driver_probe_device+0x21d/0x2d0 [ 239.70] ? __driver_attach+0x8a/0x90 [ 239.701121] ? driver_probe_device+0x2d0/0x2d0 [ 239.701133] ? bus_for_each_dev+0x5c/0x90 [ 239.701143] ? bus_add_driver+0x196/0x220 [ 239.701154] ? driver_register+0x57/0xc0 [ 239.701165] ? usb_register_driver+0x7c/0x140 [ 239.701175] ? 0xa064e000 [ 239.701185] ? do_one_initcall+0x4b/0x190 [ 239.701197] ? kmem_cache_alloc_trace+0xe4/0x1c0 [ 239.701208] ? do_init_module+0x22/0x1e1 [ 239.701219] ? do_init_module+0x5b/0x1e1 [ 239.701229] ? load_module+0x21ff/0x2760 [ 239.701239] ? SYSC_finit_module+0x90/0xb0 [ 239.701249] ? SYSC_finit_module+0x90/0xb0 [ 239.701261] ? entry_SYSCALL_64_fastpath+0x1a/0xa5 [ 239.701272] Code: 00 00 41 57 31 f6 41 56 41 55 41 54 55 53 48 89 fb e8 e7 fe ff ff 4c 8b 7b 48 49 8b bf 10 9b 00 00 49 8d af 10 9b 00 00 48 39 ef <48> 8b 1f 74 44 49 bd 00 01 00 00 00 00 ad de 49 89 de 49 bc 00 [ 239.701327] RIP: rtl_deinit_core+0x2e/0x90 [rtlwifi] RSP: c99a3b40 [ 239.702028] CR2: [ 239.705370] ---[ end trace 6ec9029c0d9c0e13 ]--- [ 239.706311] udevd[528]: worker [1174] failed while handling '/devices/pci:00/:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0'
