Hi,
network manager's modemmanager crashed when i've inserted my openmoko
freerunner while an 3g usb device driven by the option driver was
already connected.
These are the last bits in messages:
[20462.652083] usb 6-1: new full speed USB device number 4 using uhci_hcd
[20462.836424] usb 6-1: New USB device found, idVendor=1d50, idProduct=5119
[20462.836440] usb 6-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[20462.836447] usb 6-1: Product: Neo1973 Bootloader U-Boot
1.3.2-dirty-moko12
[20462.836454] usb 6-1: Manufacturer: OpenMoko, Inc
[20462.836459] usb 6-1: SerialNumber: 0000000
mtp-probe: checking bus 6, device 4:
"/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-1"
mtp-probe: bus: 6, device: 4 was not an MTP device
[20462.901834] cdc_acm 6-1:1.0: ttyACM0: USB ACM device
[20462.904417] usbcore: registered new interface driver cdc_acm
[20462.904420] cdc_acm: v0.26:USB Abstract Control Model driver for USB
modems and ISDN adapters
[20463.624142] usb 6-1: USB disconnect, device number 4
[20463.641859] CPU 0
This is the stracktrace:
acm_ctrl_msg+0x16/0x59
mutex_lock+0x13/0x2a
acm_port_down+0x4c/0xcb
acm_tty_close+0x75/0x93
tty_release+0x1b5/0x47c
? compat_do_readv_write+0x199/0x1ae
fput+0xf8/0x1ad
filp_close+0x69/0x75
sys_close+0x8a/0xea
sysenter_dispatch+0x07/0x32
Config attached.
The 3g device is:
Bus 006 Device 002: ID 12d1:1003 Huawei Technologies Co., Ltd. E220
HSDPA Modem / E230/E270 HSDPA/HSUPA Modem
Thanks,
riccardo
Am Sonntag, 29. Mai 2011, 16:04:02 schrieb Riccardo Magliocchetti:
> mtp-probe: bus: 6, device: 4 was not an MTP device
> [20462.901834] cdc_acm 6-1:1.0: ttyACM0: USB ACM device
> [20462.904417] usbcore: registered new interface driver cdc_acm
> [20462.904420] cdc_acm: v0.26:USB Abstract Control Model driver for USB
> modems and ISDN adapters
> [20463.624142] usb 6-1: USB disconnect, device number 4
> [20463.641859] CPU 0
>
> This is the stracktrace:
>
> acm_ctrl_msg+0x16/0x59
> mutex_lock+0x13/0x2a
> acm_port_down+0x4c/0xcb
> acm_tty_close+0x75/0x93
> tty_release+0x1b5/0x47c
> ? compat_do_readv_write+0x199/0x1ae
> fput+0xf8/0x1ad
> filp_close+0x69/0x75
> sys_close+0x8a/0xea
> sysenter_dispatch+0x07/0x32
So we are trying to talk to a device that is already gone.
Is there anything unusual about your device? Could you
post "lsusb -v"?
Regards
Oliver
--
- - -
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
Maxfeldstra?e 5
90409 N?rnberg
Germany
- - -
Hi,
Il 30/05/2011 07:54, Oliver Neukum ha scritto:
> Am Sonntag, 29. Mai 2011, 16:04:02 schrieb Riccardo Magliocchetti:
>
>> mtp-probe: bus: 6, device: 4 was not an MTP device
>> [20462.901834] cdc_acm 6-1:1.0: ttyACM0: USB ACM device
>> [20462.904417] usbcore: registered new interface driver cdc_acm
>> [20462.904420] cdc_acm: v0.26:USB Abstract Control Model driver for USB
>> modems and ISDN adapters
>> [20463.624142] usb 6-1: USB disconnect, device number 4
>> [20463.641859] CPU 0
>>
>> This is the stracktrace:
>>
>> acm_ctrl_msg+0x16/0x59
>> mutex_lock+0x13/0x2a
>> acm_port_down+0x4c/0xcb
>> acm_tty_close+0x75/0x93
>> tty_release+0x1b5/0x47c
>> ? compat_do_readv_write+0x199/0x1ae
>> fput+0xf8/0x1ad
>> filp_close+0x69/0x75
>> sys_close+0x8a/0xea
>> sysenter_dispatch+0x07/0x32
>
> So we are trying to talk to a device that is already gone.
> Is there anything unusual about your device? Could you
> post "lsusb -v"?
Yes, the unusual thing is that is very prone to freezing when booting,
in fact it freezed when i got the crash in the laptop. Will post lsusb
output later in the day.
thanks,
riccardo
Il 30/05/2011 11:19, Riccardo Magliocchetti ha scritto:
> Hi,
>
> Il 30/05/2011 07:54, Oliver Neukum ha scritto:
>> Am Sonntag, 29. Mai 2011, 16:04:02 schrieb Riccardo Magliocchetti:
>>
>>> mtp-probe: bus: 6, device: 4 was not an MTP device
>>> [20462.901834] cdc_acm 6-1:1.0: ttyACM0: USB ACM device
>>> [20462.904417] usbcore: registered new interface driver cdc_acm
>>> [20462.904420] cdc_acm: v0.26:USB Abstract Control Model driver for USB
>>> modems and ISDN adapters
>>> [20463.624142] usb 6-1: USB disconnect, device number 4
>>> [20463.641859] CPU 0
>>>
>>> This is the stracktrace:
>>>
>>> acm_ctrl_msg+0x16/0x59
>>> mutex_lock+0x13/0x2a
>>> acm_port_down+0x4c/0xcb
>>> acm_tty_close+0x75/0x93
>>> tty_release+0x1b5/0x47c
>>> ? compat_do_readv_write+0x199/0x1ae
>>> fput+0xf8/0x1ad
>>> filp_close+0x69/0x75
>>> sys_close+0x8a/0xea
>>> sysenter_dispatch+0x07/0x32
>>
>> So we are trying to talk to a device that is already gone.
>> Is there anything unusual about your device? Could you
>> post "lsusb -v"?
>
> Yes, the unusual thing is that is very prone to freezing when booting,
> in fact it freezed when i got the crash in the laptop. Will post lsusb
> output later in the day.
Here's the lsusb -v
Bus 006 Device 003: ID 1457:5122 First International Computer, Inc.
OpenMoko Neo1973 / Neo Freerunner kernel cdc_ether USB network
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x1457 First International Computer, Inc.
idProduct 0x5122 OpenMoko Neo1973 / Neo Freerunner kernel
cdc_ether USB network
bcdDevice 3.12
iManufacturer 1 Linux 2.6.29-20100313.git973a41fc with
s3c2410_ud
iProduct 2 RNDIS/Ethernet Gadget
iSerial 0
bNumConfigurations 2
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 2
bConfigurationValue 2
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 255 Vendor Specific (MSFT RNDIS?)
iInterface 3 RNDIS Communications Control
CDC Header:
bcdCDC 1.10
CDC Call Management:
bmCapabilities 0x00
bDataInterface 1
CDC ACM:
bmCapabilities 0x00
CDC Union:
bMasterInterface 0
bSlaveInterface 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 32
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 4 RNDIS Ethernet Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 80
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 6 Ethernet Networking
bInterfaceProtocol 0
iInterface 5 CDC Ethernet Control Model (ECM)
CDC Header:
bcdCDC 1.10
CDC Union:
bMasterInterface 0
bSlaveInterface 1
CDC Ethernet:
iMacAddress 7 DA51BC59708F
bmEthernetStatistics 0x00000000
wMaxSegmentSize 1514
wNumberMCFilters 0x0000
bNumberPowerFilters 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 32
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 6 CDC Ethernet Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0001
Self Powered
thanks,
riccardo
Am Montag, 30. Mai 2011, 21:32:54 schrieb Riccardo Magliocchetti:
> >> So we are trying to talk to a device that is already gone.
> >> Is there anything unusual about your device? Could you
> >> post "lsusb -v"?
> >
> > Yes, the unusual thing is that is very prone to freezing when booting,
> > in fact it freezed when i got the crash in the laptop. Will post lsusb
> > output later in the day.
>
> Here's the lsusb -v
There is something strange going on. This is a cdc-ether device.
Are you using any additional patches?
Regards
Oliver
--
- - -
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
Maxfeldstra?e 5
90409 N?rnberg
Germany
- - -
Il 31/05/2011 10:37, Oliver Neukum ha scritto:
> Am Montag, 30. Mai 2011, 21:32:54 schrieb Riccardo Magliocchetti:
>>>> So we are trying to talk to a device that is already gone.
>>>> Is there anything unusual about your device? Could you
>>>> post "lsusb -v"?
>>>
>>> Yes, the unusual thing is that is very prone to freezing when booting,
>>> in fact it freezed when i got the crash in the laptop. Will post lsusb
>>> output later in the day.
>>
>> Here's the lsusb -v
>
> There is something strange going on. This is a cdc-ether device.
> Are you using any additional patches?
I'm using a vanilla 2.6.39. I can get only lsusb when the phone is
booted and in that case it is recgnized as cdc-ether.
This is what i got when i attached the phone switched off like when i
got the crash:
usb 6-1: new full speed USB device number 3 using uhci_hcd
usb 6-1: New USB device found, idVendor=1d50, idProduct=5119
usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 6-1: Product: Neo1973 Bootloader U-Boot 1.3.2-dirty-moko12
usb 6-1: Manufacturer: OpenMoko, Inc
usb 6-1: SerialNumber: 0000000
cdc_acm 6-1:1.0: This device cannot do calls on its own. It is not a modem.
cdc_acm 6-1:1.0: ttyACM0: USB ACM device
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN
adapters
hub 6-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
usb 6-1: USB disconnect, device number 3
usb 6-1: new full speed USB device number 4 using uhci_hcd
usb 6-1: device descriptor read/64, error -71
usb 6-1: device descriptor read/64, error -71
usb 6-1: new low speed USB device number 5 using uhci_hcd
usb 6-1: device descriptor read/64, error -71
usb 6-1: new full speed USB device number 6 using uhci_hcd
usb 6-1: device not accepting address 6, error -71
usb 6-1: new full speed USB device number 7 using uhci_hcd
usb 6-1: device not accepting address 7, error -71
hub 6-0:1.0: unable to enumerate USB device on port 1
thanks,
riccardo
Am Mittwoch, 1. Juni 2011, 09:05:44 schrieb Riccardo Magliocchetti:
> >> Here's the lsusb -v
> >
> > There is something strange going on. This is a cdc-ether device.
> > Are you using any additional patches?
>
> I'm using a vanilla 2.6.39. I can get only lsusb when the phone is
> booted and in that case it is recgnized as cdc-ether.
>
> This is what i got when i attached the phone switched off like when i
> got the crash:
Then please post lsusb -v of that state. This is a log of a connection
going wrong due to a bad cable or interference. Does that always happen?
Regards
Oliver
--
- - -
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imend?rffer, HRB 16746 (AG N?rnberg)
Maxfeldstra?e 5
90409 N?rnberg
Germany
- - -
Hi,
Il 01/06/2011 09:34, Oliver Neukum ha scritto:
> Am Mittwoch, 1. Juni 2011, 09:05:44 schrieb Riccardo Magliocchetti:
>>>> Here's the lsusb -v
>>>
>>> There is something strange going on. This is a cdc-ether device.
>>> Are you using any additional patches?
>>
>> I'm using a vanilla 2.6.39. I can get only lsusb when the phone is
>> booted and in that case it is recgnized as cdc-ether.
>>
>> This is what i got when i attached the phone switched off like when i
>> got the crash:
>
> Then please post lsusb -v of that state. This is a log of a connection
> going wrong due to a bad cable or interference. Does that always happen?
yes it does always happen because (i think) the device hangs, so lsusb
does not show the device.
thanks,
riccardo
Am Mittwoch, 1. Juni 2011, 20:04:38 schrieb Riccardo Magliocchetti:
> Il 01/06/2011 09:34, Oliver Neukum ha scritto:
> > Am Mittwoch, 1. Juni 2011, 09:05:44 schrieb Riccardo Magliocchetti:
> >>>> Here's the lsusb -v
> >>>
> >>> There is something strange going on. This is a cdc-ether device.
> >>> Are you using any additional patches?
> >>
> >> I'm using a vanilla 2.6.39. I can get only lsusb when the phone is
> >> booted and in that case it is recgnized as cdc-ether.
> >>
> >> This is what i got when i attached the phone switched off like when i
> >> got the crash:
> >
> > Then please post lsusb -v of that state. This is a log of a connection
> > going wrong due to a bad cable or interference. Does that always happen?
>
> yes it does always happen because (i think) the device hangs, so lsusb
> does not show the device.
Hm. Now I am completely disoriented. Could you please explain in which modi
the device can be connected and which of them work?
TIA
Oliver
Hi,
Il 02/06/2011 21:34, Oliver Neukum ha scritto:
> Am Mittwoch, 1. Juni 2011, 20:04:38 schrieb Riccardo Magliocchetti:
>> Il 01/06/2011 09:34, Oliver Neukum ha scritto:
>>> Am Mittwoch, 1. Juni 2011, 09:05:44 schrieb Riccardo Magliocchetti:
>>>>>> Here's the lsusb -v
>>>>>
>>>>> There is something strange going on. This is a cdc-ether device.
>>>>> Are you using any additional patches?
>>>>
>>>> I'm using a vanilla 2.6.39. I can get only lsusb when the phone is
>>>> booted and in that case it is recgnized as cdc-ether.
>>>>
>>>> This is what i got when i attached the phone switched off like when i
>>>> got the crash:
>>>
>>> Then please post lsusb -v of that state. This is a log of a connection
>>> going wrong due to a bad cable or interference. Does that always happen?
>>
>> yes it does always happen because (i think) the device hangs, so lsusb
>> does not show the device.
>
> Hm. Now I am completely disoriented. Could you please explain in which modi
> the device can be connected and which of them work?
if the device is already booted when connected to the laptop it is shown
as cdc-ether and works fine.
if the device is switched off when connected to the laptop i get a crash
/ the usb errors i posted in the last mail.
But let me say again that it well may be that the device is at fault,
i'm only interested in not having it crash the laptop and not on having
it work properly as cdc-acm.
thanks,
riccardo