Re: AW: AW: MC7455 not listed as usb device any more after reboot

2017-03-21 Thread Bjørn Mork
Thomas Lang  writes:

> Coldstart:
>
> [  481.884820] ehci-pci: EHCI PCI platform driver
> [  481.885253] ehci-pci :00:13.0: EHCI Host Controller
> [  481.885308] ehci-pci :00:13.0: new USB bus registered, assigned bus 
> number 1
> [  481.885326] ehci-pci :00:13.0: applying AMD SB700/SB800/Hudson-2/3 
> EHCI dummy qh workaround
> [  481.885345] ehci-pci :00:13.0: debug port 2
> [  481.885486] ehci-pci :00:13.0: irq 18, io mem 0xfeb25400
> [  481.894640] ehci-pci :00:13.0: USB 2.0 started, EHCI 1.00
> [  481.894892] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
> [  481.894901] usb usb1: New USB device strings: Mfr=3, Product=2, 
> SerialNumber=1
> [  481.894908] usb usb1: Product: EHCI Host Controller
> [  481.894914] usb usb1: Manufacturer: Linux 4.6.2-040602-generic ehci_hcd
> [  481.894920] usb usb1: SerialNumber: :00:13.0
> [  481.895585] hub 1-0:1.0: USB hub found
> [  481.895643] hub 1-0:1.0: 2 ports detected
> [  482.206481] usb 1-1: new high-speed USB device number 2 using ehci-pci
> [  482.338995] usb 1-1: New USB device found, idVendor=0438, idProduct=7900
> [  482.339004] usb 1-1: New USB device strings: Mfr=0, Product=0, 
> SerialNumber=0
> [  482.340410] hub 1-1:1.0: USB hub found
> [  482.340597] hub 1-1:1.0: 4 ports detected
> [  482.638000] usb 1-1.3: new high-speed USB device number 3 using ehci-pci
> [  482.749626] usb 1-1.3: config 1 has an invalid interface number: 8 but max 
> is 4
> [  482.749649] usb 1-1.3: config 1 has an invalid interface number: 10 but 
> max is 4
> [  482.749658] usb 1-1.3: config 1 has no interface number 1
> [  482.749664] usb 1-1.3: config 1 has no interface number 4
> [  482.757858] usb 1-1.3: New USB device found, idVendor=1199, idProduct=9071
> [  482.757866] usb 1-1.3: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [  482.757873] usb 1-1.3: Product: Sierra Wireless MC7455 Qualcomm® 
> Snapdragon™ X7 LTE-A
> [  482.757880] usb 1-1.3: Manufacturer: Sierra Wireless, Incorporated
> [  482.757886] usb 1-1.3: SerialNumber: LQ61620344021006
> [  482.765172] qcserial 1-1.3:1.0: Qualcomm USB modem converter detected
> [  482.765591] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB0
> [  482.767049] qcserial 1-1.3:1.2: Qualcomm USB modem converter detected
> [  482.767338] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB1
> [  482.768308] qcserial 1-1.3:1.3: Qualcomm USB modem converter detected
> [  482.768641] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB2
> [  482.769810] qmi_wwan 1-1.3:1.8: cdc-wdm0: USB WDM device
> [  482.771427] qmi_wwan 1-1.3:1.8 wwan0: register 'qmi_wwan' at 
> usb-:00:13.0-1.3, WWAN/QMI device, 52:bb:8a:5e:bc:e4
> [  482.773220] qmi_wwan 1-1.3:1.10: cdc-wdm1: USB WDM device
> [  482.774975] qmi_wwan 1-1.3:1.10 wwan1: register 'qmi_wwan' at 
> usb-:00:13.0-1.3, WWAN/QMI device, 52:bb:8a:5e:bc:e4
> [  482.832446] qmi_wwan 1-1.3:1.10 wwp0s19u1u3i10: renamed from wwan1
> [  482.851723] qmi_wwan 1-1.3:1.8 wwp0s19u1u3i8: renamed from wwan0
>
> Everything is fine.
>
> After reboot:
>
> [   63.933614] ehci-pci :00:13.0: remove, state 4
> [   63.933678] usb usb3: USB disconnect, device number 1
> [   63.933686] usb 3-1: USB disconnect, device number 2
> [   63.935744] ehci-pci :00:13.0: USB bus 3 deregistered
> [   86.540041] ehci-pci: EHCI PCI platform driver
> [   86.540551] ehci-pci :00:13.0: EHCI Host Controller
> [   86.540577] ehci-pci :00:13.0: new USB bus registered, assigned bus 
> number 3
> [   86.540595] ehci-pci :00:13.0: applying AMD SB700/SB800/Hudson-2/3 
> EHCI dummy qh workaround
> [   86.540613] ehci-pci :00:13.0: debug port 2
> [   86.540698] ehci-pci :00:13.0: irq 18, io mem 0xfeb25400
> [   86.549905] ehci-pci :00:13.0: USB 2.0 started, EHCI 1.00
> [   86.550216] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
> [   86.550225] usb usb3: New USB device strings: Mfr=3, Product=2, 
> SerialNumber=1
> [   86.550232] usb usb3: Product: EHCI Host Controller
> [   86.550238] usb usb3: Manufacturer: Linux 4.6.2-040602-generic ehci_hcd
> [   86.550244] usb usb3: SerialNumber: :00:13.0
> [   86.550930] hub 3-0:1.0: USB hub found
> [   86.550959] hub 3-0:1.0: 2 ports detected
> [   86.861905] usb 3-1: new high-speed USB device number 2 using ehci-pci
> [   86.994337] usb 3-1: New USB device found, idVendor=0438, idProduct=7900
> [   86.994346] usb 3-1: New USB device strings: Mfr=0, Product=0, 
> SerialNumber=0
> [   86.995750] hub 3-1:1.0: USB hub found
> [   86.995929] hub 3-1:1.0: 4 ports detected
>
> Nothing the modem is not detected.

This looks like an issue with the 0438:7900 hub.  I guess this is an
internal hub ang all hardwired, so that you have no other option than
connecting the modem to port 3 of this hub?  Are any of the other ports
of this hub exposed?  If so, do they work with a device connected across
reboots?

If you do "lsusb -vd 

AW: AW: MC7455 not listed as usb device any more after reboot

2017-03-21 Thread Thomas Lang
ice found, idVendor=0438, idProduct=7900
[  482.339004] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  482.340410] hub 1-1:1.0: USB hub found
[  482.340597] hub 1-1:1.0: 4 ports detected
[  482.638000] usb 1-1.3: new high-speed USB device number 3 using ehci-pci
[  482.749626] usb 1-1.3: config 1 has an invalid interface number: 8 but max 
is 4
[  482.749649] usb 1-1.3: config 1 has an invalid interface number: 10 but max 
is 4
[  482.749658] usb 1-1.3: config 1 has no interface number 1
[  482.749664] usb 1-1.3: config 1 has no interface number 4
[  482.757858] usb 1-1.3: New USB device found, idVendor=1199, idProduct=9071
[  482.757866] usb 1-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[  482.757873] usb 1-1.3: Product: Sierra Wireless MC7455 Qualcomm® Snapdragon™ 
X7 LTE-A
[  482.757880] usb 1-1.3: Manufacturer: Sierra Wireless, Incorporated
[  482.757886] usb 1-1.3: SerialNumber: LQ61620344021006
[  482.765172] qcserial 1-1.3:1.0: Qualcomm USB modem converter detected
[  482.765591] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB0
[  482.767049] qcserial 1-1.3:1.2: Qualcomm USB modem converter detected
[  482.767338] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB1
[  482.768308] qcserial 1-1.3:1.3: Qualcomm USB modem converter detected
[  482.768641] usb 1-1.3: Qualcomm USB modem converter now attached to ttyUSB2
[  482.769810] qmi_wwan 1-1.3:1.8: cdc-wdm0: USB WDM device
[  482.771427] qmi_wwan 1-1.3:1.8 wwan0: register 'qmi_wwan' at 
usb-:00:13.0-1.3, WWAN/QMI device, 52:bb:8a:5e:bc:e4
[  482.773220] qmi_wwan 1-1.3:1.10: cdc-wdm1: USB WDM device
[  482.774975] qmi_wwan 1-1.3:1.10 wwan1: register 'qmi_wwan' at 
usb-:00:13.0-1.3, WWAN/QMI device, 52:bb:8a:5e:bc:e4
[  482.832446] qmi_wwan 1-1.3:1.10 wwp0s19u1u3i10: renamed from wwan1
[  482.851723] qmi_wwan 1-1.3:1.8 wwp0s19u1u3i8: renamed from wwan0

Everything is fine.

After reboot:

[   63.933614] ehci-pci :00:13.0: remove, state 4
[   63.933678] usb usb3: USB disconnect, device number 1
[   63.933686] usb 3-1: USB disconnect, device number 2
[   63.935744] ehci-pci :00:13.0: USB bus 3 deregistered
[   86.540041] ehci-pci: EHCI PCI platform driver
[   86.540551] ehci-pci :00:13.0: EHCI Host Controller
[   86.540577] ehci-pci :00:13.0: new USB bus registered, assigned bus 
number 3
[   86.540595] ehci-pci :00:13.0: applying AMD SB700/SB800/Hudson-2/3 EHCI 
dummy qh workaround
[   86.540613] ehci-pci :00:13.0: debug port 2
[   86.540698] ehci-pci :00:13.0: irq 18, io mem 0xfeb25400
[   86.549905] ehci-pci :00:13.0: USB 2.0 started, EHCI 1.00
[   86.550216] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[   86.550225] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   86.550232] usb usb3: Product: EHCI Host Controller
[   86.550238] usb usb3: Manufacturer: Linux 4.6.2-040602-generic ehci_hcd
[   86.550244] usb usb3: SerialNumber: :00:13.0
[   86.550930] hub 3-0:1.0: USB hub found
[   86.550959] hub 3-0:1.0: 2 ports detected
[   86.861905] usb 3-1: new high-speed USB device number 2 using ehci-pci
[   86.994337] usb 3-1: New USB device found, idVendor=0438, idProduct=7900
[   86.994346] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   86.995750] hub 3-1:1.0: USB hub found
[   86.995929] hub 3-1:1.0: 4 ports detected

Nothing the modem is not detected.

I came up with a workaround which currently work but is perhaps not the 
solution for the problem. I do an at!reset to the modem and do a reboot right 
after it. In this way the modem is detected and working after reboot.
Could it be that the modem is put in LPM mode and is not powered on again?

Thomas


-Ursprüngliche Nachricht-
Von: Dan Williams [mailto:d...@redhat.com] 
Gesendet: Montag, 20. März 2017 22:16
An: Thomas Lang <thomas.l...@tactilo.eu>; ModemManager (development) 
<modemmanager-devel@lists.freedesktop.org>
Betreff: Re: AW: MC7455 not listed as usb device any more after reboot

On Mon, 2017-03-20 at 09:45 +, Thomas Lang wrote:
> Hi Dan,
> thanks for your comments.
> I have included a trace of the working start and the reboot. I
> noticed that in the reboot case the usb 3-1.3 device is not detected
> anymore. The usb 3-1 is an ehci-pci. Would it help to reset the ehci-
> pci? And if so how would I do this.

If you rmmod anything related to ehci-hcd and then re-mode probe it and
anything else you unloaded, does that make it show up?  If so, that
would indicate a bug in the ehci driver and/or your platform support.

Dan

> Thanks a lot for any coment,
> Thomas
> 
> Cold Start
> PCEngines apu2
> coreboot build 20160311
> 4080 MB ECC DRAM
> 
> SeaBIOS (version ?-20160311_005214-0c3a223c2ee6)
> Found mainboard PC Engines PCEngines apu2
> multiboot: eax=0, ebx=0
> boot order:
> 1: /pci@i0cf8/usb@10/usb-*@1
> 2: /pci@i0cf8/usb@10/usb-*@2
> 3: /pci@

Re: AW: MC7455 not listed as usb device any more after reboot

2017-03-20 Thread Dan Williams
On Mon, 2017-03-20 at 09:45 +, Thomas Lang wrote:
> Hi Dan,
> thanks for your comments.
> I have included a trace of the working start and the reboot. I
> noticed that in the reboot case the usb 3-1.3 device is not detected
> anymore. The usb 3-1 is an ehci-pci. Would it help to reset the ehci-
> pci? And if so how would I do this.

If you rmmod anything related to ehci-hcd and then re-mode probe it and
anything else you unloaded, does that make it show up?  If so, that
would indicate a bug in the ehci driver and/or your platform support.

Dan

> Thanks a lot for any coment,
> Thomas
> 
> Cold Start
> PCEngines apu2
> coreboot build 20160311
> 4080 MB ECC DRAM
> 
> SeaBIOS (version ?-20160311_005214-0c3a223c2ee6)
> Found mainboard PC Engines PCEngines apu2
> multiboot: eax=0, ebx=0
> boot order:
> 1: /pci@i0cf8/usb@10/usb-*@1
> 2: /pci@i0cf8/usb@10/usb-*@2
> 3: /pci@i0cf8/usb@10/usb-*@3
> 4: /pci@i0cf8/usb@10/usb-*@4
> 5: /pci@i0cf8/*@14,7
> 6: /pci@i0cf8/*@11/drive@0/disk@0
> 7: /pci@i0cf8/*@11/drive@1/disk@0
> 8: /rom@genroms/pxe.rom
> 9: pxen0
> 10: scon1
> 11:
> Found 23 PCI devices (max PCI bus is 04)
> Copying SMBIOS entry point from 0xdffb7000 to 0x000f3110
> Copying ACPI RSDP from 0xdffb8000 to 0x000f30e0
> Copying MPTABLE from 0xdffdc000/dffdc010 to 0x000f2f30
> Copying PIR from 0xdffdd000 to 0x000f2f00
> Using pmtimer, ioport 0x818
> Scan for VGA option rom
> Running option rom at c000:0003
> 
> Google, Inc.
> Serial Graphics Adapter 08/22/15
> SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ (wiv@coreboot
> -Virtual-Machine) Sat Aug 22 09:25:30 UTC 2015
> Term: 80x24
> IO4 0
> Turning on vga text mode console
> SeaBIOS (version ?-20160311_005214-0c3a223c2ee6)
> XHCI init on dev 00:10.0: regs @ 0xfeb22000, 4 ports, 32 slots, 32
> byte contexts
> XHCIextcap 0x1 @ feb22500
> XHCIprotocol USB  3.00, 2 ports (offset 1), def 0
> XHCIprotocol USB  2.00, 2 ports (offset 3), def 10
> XHCIextcap 0xa @ feb22540
> Found 2 serial ports
> ATA controller 1 at 4010/4020/0 (irq 0 dev 88)
> EHCI init on dev 00:13.0 (regs=0xfeb25420)
> ATA controller 2 at 4018/4024/0 (irq 0 dev 88)
> Searching bootorder for: /pci@i0cf8/*@14,7
> Searching bootorder for: /rom@img/memtest
> Searching bootorder for: /rom@img/setup
> ata0-0: KINGSTON SMS200S3120G ATA-8 Hard-Disk (111 GiBytes)
> Searching bootorder for: /pci@i0cf8/*@11/drive@0/disk@0
> XHCI no devices found
> Initialized USB HUB (0 ports used)
> All threads complete.
> Scan for option roms
> Running option rom at c100:0003
> 
> 
> iPXE (http://ipxe.org) 00:00.0 C100 PCI2.10 PnP PMMpmm call arg1=1
> pmm call arg1=0
> +DFF49730pmm call arg1=1
> pmm call arg1=0
> +DFE89730 C100
> 
> 
> 
> Searching bootorder for: /rom@genroms/pxe.rom
> PCengines Press F10 key now for boot menu:
> Searching bootorder for: HALT
> drive 0x000f2e90: PCHS=16383/16/63 translation=lba LCHS=1024/255/63
> s=234441648
> Space available for UMB: c2000-ef000, f-f2e90
> Returned 262144 bytes of ZoneHigh
> e820 map has 7 items:
>   0:  - 0009f800 = 1 RAM
>   1: 0009f800 - 000a = 2 RESERVED
>   2: 000f - 0010 = 2 RESERVED
>   3: 0010 - dffae000 = 1 RAM
>   4: dffae000 - e000 = 2 RESERVED
>   5: f800 - fc00 = 2 RESERVED
>   6: 0001 - 00011f00 = 1 RAM
> enter handle_19:
>   NULL
> Booting from Hard Disk...
> Booting from :7c00
> [0.00] Linux version 4.6.2-040602-generic (kernel@gloin) (gcc
> version 5.3.1 20160528 (Ubuntu 5.3.1-21ubuntu11) ) #201606100516 SMP
> Fri Jun 10 09:18:34 UTC 2016
> [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.6.2-040602-
> generic root= UUID=474ac08c-0d55-4ac0-ad7e-b922152698e5 ro
> console=tty0 console=ttyS0,115200n8
> [0.00] KERNEL supported cpus:
> [0.00]   Intel GenuineIntel
> [0.00]   AMD AuthenticAMD
> [0.00]   Centaur CentaurHauls
> [0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
> [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: Supporting XSAVE feature 0x004: 'AVX
> registers'
> [0.00] x86/fpu: Enabled xstate features 0x7, context size is
> 832 bytes, using 'standard' format.
> [0.00] x86/fpu: Using 'eager' FPU context switches.
> [0.00] e820: BIOS-provided physical RAM map:
> [0.00] BIOS-e820: [mem 0x-0x0009f7ff] 
> usable
> [0.00] BIOS-e820: [mem 0x0009f800-0x0009] 
> reserved
> [0.00] BIOS-e820: [mem 0x000f-0x000f] 
> reserved
> [0.00] BIOS-e820: [mem 0x0010-0xdffadfff] 
> usable
> [0.00] BIOS-e820: [mem 0xdffae000-0xdfff] 
> reserved
> [0.00] BIOS-e820: [mem 

AW: MC7455 not listed as usb device any more after reboot

2017-03-20 Thread Thomas Lang
Hi Dan,
thanks for your comments.
I have included a trace of the working start and the reboot. I noticed that in 
the reboot case the usb 3-1.3 device is not detected anymore. The usb 3-1 is an 
ehci-pci. Would it help to reset the ehci-pci? And if so how would I do this.
Thanks a lot for any coment,
Thomas

Cold Start
PCEngines apu2
coreboot build 20160311
4080 MB ECC DRAM

SeaBIOS (version ?-20160311_005214-0c3a223c2ee6)
Found mainboard PC Engines PCEngines apu2
multiboot: eax=0, ebx=0
boot order:
1: /pci@i0cf8/usb@10/usb-*@1
2: /pci@i0cf8/usb@10/usb-*@2
3: /pci@i0cf8/usb@10/usb-*@3
4: /pci@i0cf8/usb@10/usb-*@4
5: /pci@i0cf8/*@14,7
6: /pci@i0cf8/*@11/drive@0/disk@0
7: /pci@i0cf8/*@11/drive@1/disk@0
8: /rom@genroms/pxe.rom
9: pxen0
10: scon1
11:
Found 23 PCI devices (max PCI bus is 04)
Copying SMBIOS entry point from 0xdffb7000 to 0x000f3110
Copying ACPI RSDP from 0xdffb8000 to 0x000f30e0
Copying MPTABLE from 0xdffdc000/dffdc010 to 0x000f2f30
Copying PIR from 0xdffdd000 to 0x000f2f00
Using pmtimer, ioport 0x818
Scan for VGA option rom
Running option rom at c000:0003

Google, Inc.
Serial Graphics Adapter 08/22/15
SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ 
(wiv@coreboot-Virtual-Machine) Sat Aug 22 09:25:30 UTC 2015
Term: 80x24
IO4 0
Turning on vga text mode console
SeaBIOS (version ?-20160311_005214-0c3a223c2ee6)
XHCI init on dev 00:10.0: regs @ 0xfeb22000, 4 ports, 32 slots, 32 byte contexts
XHCIextcap 0x1 @ feb22500
XHCIprotocol USB  3.00, 2 ports (offset 1), def 0
XHCIprotocol USB  2.00, 2 ports (offset 3), def 10
XHCIextcap 0xa @ feb22540
Found 2 serial ports
ATA controller 1 at 4010/4020/0 (irq 0 dev 88)
EHCI init on dev 00:13.0 (regs=0xfeb25420)
ATA controller 2 at 4018/4024/0 (irq 0 dev 88)
Searching bootorder for: /pci@i0cf8/*@14,7
Searching bootorder for: /rom@img/memtest
Searching bootorder for: /rom@img/setup
ata0-0: KINGSTON SMS200S3120G ATA-8 Hard-Disk (111 GiBytes)
Searching bootorder for: /pci@i0cf8/*@11/drive@0/disk@0
XHCI no devices found
Initialized USB HUB (0 ports used)
All threads complete.
Scan for option roms
Running option rom at c100:0003


iPXE (http://ipxe.org) 00:00.0 C100 PCI2.10 PnP PMMpmm call arg1=1
pmm call arg1=0
+DFF49730pmm call arg1=1
pmm call arg1=0
+DFE89730 C100



Searching bootorder for: /rom@genroms/pxe.rom
PCengines Press F10 key now for boot menu:
Searching bootorder for: HALT
drive 0x000f2e90: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=234441648
Space available for UMB: c2000-ef000, f-f2e90
Returned 262144 bytes of ZoneHigh
e820 map has 7 items:
  0:  - 0009f800 = 1 RAM
  1: 0009f800 - 000a = 2 RESERVED
  2: 000f - 0010 = 2 RESERVED
  3: 0010 - dffae000 = 1 RAM
  4: dffae000 - e000 = 2 RESERVED
  5: f800 - fc00 = 2 RESERVED
  6: 0001 - 00011f00 = 1 RAM
enter handle_19:
  NULL
Booting from Hard Disk...
Booting from :7c00
[0.00] Linux version 4.6.2-040602-generic (kernel@gloin) (gcc version 
5.3.1 20160528 (Ubuntu 5.3.1-21ubuntu11) ) #201606100516 SMP Fri Jun 10 
09:18:34 UTC 2016
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.6.2-040602-generic 
root= UUID=474ac08c-0d55-4ac0-ad7e-b922152698e5 ro console=tty0 
console=ttyS0,115200n8
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[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: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009f7ff] usable
[0.00] BIOS-e820: [mem 0x0009f800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000f-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xdffadfff] usable
[0.00] BIOS-e820: [mem 0xdffae000-0xdfff] reserved
[0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00011eff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.7 present.
[0.00] e820: last_pfn = 0x11f000 max_arch_pfn = 0x4
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT
[0.00] e820: last_pfn = 0xdffae max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000f2f30-0x000f2f3f] mapped at 
[880f2f30]
[0.00] Scanning 1 areas for low 

Re: MC7455 not listed as usb device any more after reboot

2017-03-17 Thread Dan Williams
On Fri, 2017-03-17 at 11:57 +, Thomas Lang wrote:
> Hi all,
> perhaps you have seen this bug before. I’m using the MC7455 with a
> linux system after normal power cycle (unplugged power) the mc 7455
> can be found  with lsusb:
> 
> 
> 
> go@ubuntu:~$ lsusb
> 
> Bus 003 Device 003: ID 1199:9071 Sierra Wireless, Inc.
> 
> Bus 003 Device 002: ID 0438:7900 Advanced Micro Devices, Inc.
> 
> 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
> 
> If I do a reboot, the mc7455 is not listed anymore.
> 
> Any ideas what might be the problem?

That's probably an issue with system BIOS or the kernel's USB stack,
unfortunately.  You'd want to enable debugging in the kernel drivers
for your USB HCI and then figure out why the device fails to be
enumerated.  There may even be logging for that already, check "dmesg"
for lines including "ehci" (USB 2), "ochi" (USB 1), and "xhci" (USB 3)
when the device fails to appear; perhaps something will show up for "3-
4", eg:

kernel: usb 3-4: new high-speed USB device number 2 using xhci_hcd

but if that device then fails to enumerate itself, the kernel won't
show it in lsusb since it can't get any information from it.

In any case, this sounds like a USB stack issue.

Dan
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel


MC7455 not listed as usb device any more after reboot

2017-03-17 Thread Thomas Lang
Hi all,
perhaps you have seen this bug before. I’m using the MC7455 with a linux system 
after normal power cycle (unplugged power) the mc 7455 can be found  with lsusb:



go@ubuntu:~$ lsusb

Bus 003 Device 003: ID 1199:9071 Sierra Wireless, Inc.

Bus 003 Device 002: ID 0438:7900 Advanced Micro Devices, Inc.

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

If I do a reboot, the mc7455 is not listed anymore.

Any ideas what might be the problem?

Kind regards,
Thomas
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel