Hi. This is already since quite a while. My Fujitsu Lifebook E782 has a (presumably) Gobi 3000 UMTS modem. It's enabled in the BIOS, a SIM card is plugged... and it actually worked before (unfortunately I don't remember in which kernel version, but it must be something before 3.10, since I've did that report before: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721005 Currently I run $ uname -a Linux heisenberg 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64 GNU/Linux and everything else is Debian sid. In the meantime the thing doesn't even show up anymore in: $ lsusb Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 009: ID 04f2:b2fc Chicony Electronics Co., Ltd Bus 003 Device 004: ID 0489:e052 Foxconn / Hon Hai Bus 003 Device 010: ID 0b97:7772 O2 Micro, Inc. OZ776 CCID Smartcard Reader Bus 003 Device 003: ID 0b97:7761 O2 Micro, Inc. Oz776 1.1 Hub Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub or: $ lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) 00:1c.7 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 8 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 0a:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34) 0b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) Any ideas? Cheers, Chris.
Still in 3.19
That seems to work again since some versions: $ lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 008: ID 04f2:b2fc Chicony Electronics Co., Ltd Bus 001 Device 007: ID 1199:9011 Sierra Wireless, Inc. Bus 001 Device 005: ID 0489:e052 Foxconn / Hon Hai Bus 001 Device 006: ID 0b97:7772 O2 Micro, Inc. OZ776 CCID Smartcard Reader Bus 001 Device 003: ID 0b97:7761 O2 Micro, Inc. Oz776 1.1 Hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub It's the 1199:9011 Sierra Wireless, Inc..
(at least since kernel 4.2.5)
And the problem is back with 4.2.6
Taking that with the regression back... I booted again with 4.2.5 an the problem remained there as well. So it must have been something else that I did, which had solved the problems for a few boots (though I cannot think of anything that could be)... or there's simply something racy. Attached is a kernel.log from when it worked... with several boots... at one of them it failed and then one sees these: Nov 6 02:07:31 heisenberg kernel: [ 2.365832] usb 1-1.5: new full-speed USB device number 5 using ehci-pci Nov 6 02:07:31 heisenberg kernel: [ 2.437874] usb 1-1.5: device descriptor read/64, error -32 Nov 6 02:07:31 heisenberg kernel: [ 2.613975] usb 1-1.5: device descriptor read/64, error -32 Nov 6 02:07:31 heisenberg kernel: [ 2.774938] scsi 6:0:0:0: Direct-Access JetFlash Transcend 8GB 8.07 PQ: 0 ANSI: 2 Nov 6 02:07:31 heisenberg kernel: [ 2.776289] sd 6:0:0:0: [sdb] 15687678 512-byte logical blocks: (8.03 GB/7.47 GiB) Nov 6 02:07:31 heisenberg kernel: [ 2.776578] sd 6:0:0:0: [sdb] Write Protect is off Nov 6 02:07:31 heisenberg kernel: [ 2.776663] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00 Nov 6 02:07:31 heisenberg kernel: [ 2.776924] sd 6:0:0:0: [sdb] No Caching mode page found Nov 6 02:07:31 heisenberg kernel: [ 2.776996] sd 6:0:0:0: [sdb] Assuming drive cache: write through Nov 6 02:07:31 heisenberg kernel: [ 2.790075] usb 1-1.5: new full-speed USB device number 6 using ehci-pci Nov 6 02:07:31 heisenberg kernel: [ 2.862110] usb 1-1.5: device descriptor read/64, error -32 Nov 6 02:07:31 heisenberg kernel: [ 3.038213] usb 1-1.5: device descriptor read/64, error -32 Nov 6 02:07:31 heisenberg kernel: [ 3.126525] clocksource: Switched to clocksource tsc Nov 6 02:07:31 heisenberg kernel: [ 3.208589] sdb: sdb1 sdb2 sdb3 Nov 6 02:07:31 heisenberg kernel: [ 3.210394] sd 6:0:0:0: [sdb] Attached SCSI removable disk Nov 6 02:07:31 heisenberg kernel: [ 3.214232] usb 1-1.5: new full-speed USB device number 7 using ehci-pci Nov 6 02:07:31 heisenberg kernel: [ 3.622509] usb 1-1.5: device not accepting address 7, error -32 Nov 6 02:07:31 heisenberg kernel: [ 3.694575] usb 1-1.5: new full-speed USB device number 8 using ehci-pci Nov 6 02:07:31 heisenberg kernel: [ 4.102771] usb 1-1.5: device not accepting address 8, error -32 1-1.5 is apparently the Gobi device,.. in the cases it worked, these "not accepting address" messages didn't appear. Chris.
Created attachment 195251 [details] kern.log
From my side, the bug can be closed as I no longer use the specific piece of hardware (I do still have it, if someone wants me to test something).
Closing this now as obsolete since I don't use the laptop in question anymore (though the problem was never really fixed and in fact even on my new Fujitsu laptop the WWAN modem isn't detected either, but I'd open a separate issue for that in cases I need it).