Description of problem: After upgrade from F20 on F21 Huawei E3372 (3&4G USB stick) stopped working. I upgraded on F21 from 3.17.x kernel so it probably is not Fedora upgrade issue but kernel update issue. I connect USB stick, NetworkManager tries to connect using configured connection which worked in F20, new wwp0s26u1u1i2 device appears in ifconfig output, but NetworkManager stops trying after a while and wwp0s26u1u1i2 disappears from ifconfig. From ifconfig it seems that it sends and receives some bytes but connection fails and "kevent 12 may have been dropped" messages are in log. Version-Release number of selected component (if applicable): I tried it under 3.18.x and 3.19.x kernels with the same result. usb_modeswitch is in version 2.2.0-2.fc21, NetworkManager is 0.9.10.2-2.fc21, ModemManager is 1.4.4-2.fc21 How reproducible: Connect USB stick. Actual results: dmesg output: [112219.510480] usb 1-1.1: new high-speed USB device number 13 using ehci-pci [112219.598821] usb 1-1.1: New USB device found, idVendor=12d1, idProduct=1506 [112219.598831] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [112219.598836] usb 1-1.1: Product: HUAWEI_MOBILE [112219.598841] usb 1-1.1: Manufacturer: HUAWEI_MOBILE [112219.598845] usb 1-1.1: SerialNumber: 0123456789ABCDEF [112219.601478] option 1-1.1:1.0: GSM modem (1-port) converter detected [112219.602007] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB0 [112219.602317] option 1-1.1:1.1: GSM modem (1-port) converter detected [112219.602566] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB1 [112219.605526] huawei_cdc_ncm 1-1.1:1.2: MAC-Address: 00:1e:10:1f:00:00 [112219.605533] huawei_cdc_ncm 1-1.1:1.2: setting rx_max = 16384 [112219.606378] huawei_cdc_ncm 1-1.1:1.2: cdc-wdm0: USB WDM device [112219.606827] huawei_cdc_ncm 1-1.1:1.2 wwan0: register 'huawei_cdc_ncm' at usb-0000:00:1a.0-1.1, Huawei CDC NCM device, 00:1e:10:1f:00:00 [112220.302270] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: renamed from wwan0 [112229.129914] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112229.131469] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112274.239856] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112323.139357] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112323.140510] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112417.146561] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112417.147675] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112464.151418] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112464.152546] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112511.154987] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112511.156013] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112558.153668] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped [112558.154375] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped lsusb output: Bus 001 Device 013: ID 12d1:1506 Huawei Technologies Co., Ltd. Modem/Networkcard ifconfig output: wwp0s26u1u1i2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 00:1e:10:1f:00:00 txqueuelen 1000 (Ethernet) RX packets 465 bytes 21390 (20.8 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 156 bytes 51264 (50.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Expected results: Connect USB stick and NetworkManager is able to connect. Please help me what to do with that. Thanks, Lukas
Please provide the full output of dmesg from both a working and non-working kernel.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs. Fedora 21 has now been rebased to 3.19.5-200.fc21. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 22, and are still experiencing this issue, please change the version to Fedora 22. If you experience different issues, please open a new bug report for those.
Sorry, didn't intend to remove the needinfo flag.
(In reply to Bjørn Mork from comment #3) > Sorry, didn't intend to remove the needinfo flag. Any success with Huawei E3372 in the meantime. I have a similar problem with a Huawei E3372.
Yes, there is now a fix for E3372 modems in v4.2: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4a0e3e989d66bb7204b163d9cfaa7fa96d0f2023 It has been tested out with success in OpenWRT: https://lists.openwrt.org/pipermail/openwrt-devel/2015-July/034431.html I don't think it has been added to the stable queue just yet. But it is a nicely contained fix, so I believe this patch is a good stable candidate if it really fixes the problem.
Hi all, Sorry, I was not able to get E3372 working neither on F20 nor any router as I wrote at the beginning and thought that the modem is damaged. Many thanks to Bjørn for the info that the bug should be solved in kernel 4.2 and I confirms that it is really resolved there and this post is written from F22 with kernel 4.2.0-300.fc23.x86_64 using E3372 for connection. Messages like this still appears in dmesg but it works: [ 222.050238] huawei_cdc_ncm 1-1.1:1.2 wwp0s26u1u1i2: kevent 12 may have been dropped So this bug can be closed with "resolved in F23".
Thanks.
Sorry, I don't get it. What needs to be done or installed in Fedora 22 to get the E3372 working? Could you please give some advice? Regards, Harald (In reply to Bjørn Mork from comment #5) > Yes, there is now a fix for E3372 modems in v4.2: > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/ > ?id=4a0e3e989d66bb7204b163d9cfaa7fa96d0f2023 > > It has been tested out with success in OpenWRT: > https://lists.openwrt.org/pipermail/openwrt-devel/2015-July/034431.html > > I don't think it has been added to the stable queue just yet. But it is a > nicely contained fix, so I believe this patch is a good stable candidate if > it really fixes the problem.
Hi Harald, I did it using this command: dnf --releasever=23 --enablerepo=updates-testing update kernel* It installed 4.2 kernel which solved the issue for me. Lukas
Thanks, Harald