Hi, I have no idea on these output, how can I help to reproduce the error?
I'm not sure how it occurs, it just come up with a dialog, and I just submit the report. On Mon, Oct 8, 2012 at 7:24 PM, Marlon Costa <marlo...@gmail.com> wrote: > Hi, > > I can't reproduce these error in newer versions, my syslog output: > > Oct 8 08:13:41 note26 kernel: [53285.178035] usb 2-1.1: >USB disconnect, > device number 6 > Oct 8 08:13:42 note26 kernel: [53285.378752] usb 2-1.1: >new high-speed > USB device number 7 using ehci_hcd > Oct 8 08:13:42 note26 kernel: [53285.472354] usb 2-1.1: >New USB device > found, idVendor=04e8, idProduct=6860 > Oct 8 08:13:42 note26 kernel: [53285.472368] usb 2-1.1: >New USB device > strings: Mfr=2, Product=3, SerialNumber=4 > Oct 8 08:13:42 note26 kernel: [53285.472376] usb 2-1.1: >Product: > SAMSUNG_Android > Oct 8 08:13:42 note26 kernel: [53285.472383] usb 2-1.1: >Manufacturer: > SAMSUNG > Oct 8 08:13:42 note26 kernel: [53285.472389] usb 2-1.1: > >SerialNumber:ZZZZZZZZZZZZZ > Oct 8 08:13:42 note26 kernel: [53285.473610] cdc_acm 2-1.1:1.1: >This > device cannot do calls on its own. It is not a modem. > Oct 8 08:13:42 note26 kernel: [53285.473657] cdc_acm 2-1.1:1.1: >ttyACM0: > USB ACM device > > Oct 8 08:13:54 note26 modem-manager[1621]: <info> (ttyACM0) closing > serial port... > Oct 8 08:13:54 note26 modem-manager[1621]: <info> (ttyACM0) serial port > closed > Oct 8 08:13:54 note26 modem-manager[1621]: <info> (ttyACM0) opening > serial port... > Oct 8 08:14:00 note26 modem-manager[1621]: <info> (ttyACM0) closing > serial port... > Oct 8 08:14:00 note26 modem-manager[1621]: <info> (ttyACM0) serial port > closed > Oct 8 08:14:00 note26 modem-manager[1621]: <info> (ttyACM0) opening > serial port... > Oct 8 08:14:12 note26 modem-manager[1621]: <info> (ttyACM0) closing > serial port... > Oct 8 08:14:12 note26 modem-manager[1621]: <info> (ttyACM0) serial port > closed > Oct 8 08:14:12 note26 modem-manager[1621]: <info> (ttyACM0) opening > serial port... > Oct 8 08:14:18 note26 modem-manager[1621]: <info> (ttyACM0) closing > serial port... > Oct 8 08:14:18 note26 modem-manager[1621]: <info> (ttyACM0) serial port > closed > > But I can't see the modem of the celular. > > But the USB thetering worked well: > > Oct 8 08:21:03 note26 modem-manager[1621]: <info> (ttyACM0) closing > serial port... > Oct 8 08:21:03 note26 modem-manager[1621]: <info> (ttyACM0) serial port > closed > Oct 8 08:21:03 note26 modem-manager[1621]: <warn> Couldn't probe for > capabilities, probably not a GSM or CDMA modem > Oct 8 08:21:03 note26 kernel: [53721.942643] usb 2-1.1: >USB disconnect, > device number 10 > Oct 8 08:21:04 note26 kernel: [53722.142704] usb 2-1.1: >new high-speed > USB device number 11 using ehci_hcd > Oct 8 08:21:04 note26 kernel: [53722.236646] usb 2-1.1: >New USB device > found, idVendor=04e8, idProduct=6864 > Oct 8 08:21:04 note26 kernel: [53722.236650] usb 2-1.1: >New USB device > strings: Mfr=2, Product=3, SerialNumber=4 > Oct 8 08:21:04 note26 kernel: [53722.236652] usb 2-1.1: >Product: > SAMSUNG_Android > Oct 8 08:21:04 note26 kernel: [53722.236653] usb 2-1.1: >Manufacturer: > SAMSUNG > Oct 8 08:21:04 note26 kernel: [53722.236655] usb 2-1.1: >SerialNumber: > ZZZZZZZZZZZ > Oct 8 08:21:04 note26 vmnet-natd: RTM_NEWLINK: name:usb0 index:8 > flags:0x00001002 > Oct 8 08:21:04 note26 vmnetBridge: RTM_NEWLINK: name:usb0 index:8 > flags:0x00001002 > Oct 8 08:21:04 note26 kernel: [53722.239779] rndis_host 2-1.1:1.0: >usb0: > register 'rndis_host' at usb-0000:00:1d.0-1.1, RNDIS device, > 02:01:3d:61:61:6f > Oct 8 08:21:04 note26 NetworkManager[1783]: <warn> failed to allocate > link cache: (-10) Operation not supported > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): carrier is OFF > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): new Ethernet > device (driver: 'rndis_host' ifindex: 8) > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): exported as > /org/freedesktop/NetworkManager/Devices/3 > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): now managed > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): device state > change: unmanaged -> unavailable (reason 'managed') [10 20 2] > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): bringing up > device. > Oct 8 08:21:04 note26 vmnet-natd: RTM_NEWLINK: name:usb0 index:8 > flags:0x00011043 > Oct 8 08:21:04 note26 vmnetBridge: RTM_NEWLINK: name:usb0 index:8 > flags:0x00011043 > Oct 8 08:21:04 note26 vmnetBridge: Adding interface usb0 index:8 > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): carrier now ON > (device state 20) > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): preparing > device. > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): deactivating > device (reason 'managed') [2] > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Added default wired > connection 'Conexão cabeada 2' for > /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/net/usb0 > Oct 8 08:21:04 note26 NetworkManager[1783]: SCPlugin-Ifupdown: devices > added (path: > /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/net/usb0, > iface: usb0) > Oct 8 08:21:04 note26 NetworkManager[1783]: SCPlugin-Ifupdown: device > added (path: > /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/net/usb0, > iface: usb0): no ifupdown configuration found. > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): device state > change: unavailable -> disconnected (reason 'none') [20 30 0] > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Auto-activating > connection 'Conexão cabeada 2'. > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > starting connection 'Conexão cabeada 2' > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): device state > change: disconnected -> prepare (reason 'none') [30 40 0] > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 1 of 5 (Device Prepare) scheduled... > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 1 of 5 (Device Prepare) started... > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 2 of 5 (Device Configure) scheduled... > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 1 of 5 (Device Prepare) complete. > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 2 of 5 (Device Configure) starting... > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): device state > change: prepare -> config (reason 'none') [40 50 0] > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 2 of 5 (Device Configure) successful. > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 3 of 5 (IP Configure Start) scheduled. > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 2 of 5 (Device Configure) complete. > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 3 of 5 (IP Configure Start) started... > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): device state > change: config -> ip-config (reason 'none') [50 70 0] > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Beginning DHCPv4 transaction (timeout in 45 seconds) > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> dhclient started with > pid 32644 > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Beginning IP6 addrconf. > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 3 of 5 (IP Configure Start) complete. > Oct 8 08:21:04 note26 laptop-mode: Warning: Configuration file > /etc/laptop-mode/conf.d/board-specific/*.conf is not readable, skipping. > Oct 8 08:21:04 note26 dhclient: Internet Systems Consortium DHCP Client > 4.2.4 > Oct 8 08:21:04 note26 dhclient: Copyright 2004-2012 Internet Systems > Consortium. > Oct 8 08:21:04 note26 dhclient: All rights reserved. > Oct 8 08:21:04 note26 dhclient: For info, please visit > https://www.isc.org/software/dhcp/ > Oct 8 08:21:04 note26 dhclient: > Oct 8 08:21:04 note26 laptop-mode: Warning: Configuration file > /etc/laptop-mode/conf.d/board-specific/*.conf is not readable, skipping. > Oct 8 08:21:04 note26 laptop-mode: Warning: Configuration file > /etc/laptop-mode/conf.d/board-specific/*.conf is not readable, skipping. > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): DHCPv4 state > changed nbi -> preinit > Oct 8 08:21:04 note26 laptop-mode: Warning: Configuration file > /etc/laptop-mode/conf.d/board-specific/*.conf is not readable, skipping. > Oct 8 08:21:04 note26 dhclient: Listening on LPF/usb0/02:01:3d:61:61:6f > Oct 8 08:21:04 note26 dhclient: Sending on LPF/usb0/02:01:3d:61:61:6f > Oct 8 08:21:04 note26 dhclient: Sending on Socket/fallback > Oct 8 08:21:04 note26 dhclient: DHCPDISCOVER on usb0 to 255.255.255.255 > port 67 interval 3 > Oct 8 08:21:04 note26 dhclient: DHCPREQUEST of 192.168.42.245 on usb0 to > 255.255.255.255 port 67 > Oct 8 08:21:04 note26 dhclient: DHCPOFFER of 192.168.42.245 from > 192.168.42.129 > Oct 8 08:21:04 note26 laptop-mode: Laptop mode > Oct 8 08:21:04 note26 laptop-mode: enabled, not active > Oct 8 08:21:04 note26 laptop-mode: Laptop mode > Oct 8 08:21:04 note26 laptop-mode: enabled, not active > Oct 8 08:21:04 note26 dhclient: DHCPACK of 192.168.42.245 from > 192.168.42.129 > Oct 8 08:21:04 note26 dhclient: bound to 192.168.42.245 -- renewal in > 1753 seconds. > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> (usb0): DHCPv4 state > changed preinit -> bound > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> address > 192.168.42.245 > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> prefix 24 > (255.255.255.0) > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> gateway > 192.168.42.129 > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> hostname 'note26' > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> nameserver > '192.168.42.129' > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 5 of 5 (IPv4 Configure Commit) scheduled... > Oct 8 08:21:04 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 5 of 5 (IPv4 Commit) started... > Oct 8 08:21:04 note26 vmnet-natd: RTM_NEWADDR: index:8, > addr:192.168.42.245 > Oct 8 08:21:04 note26 avahi-daemon[1662]: Joining mDNS multicast group on > interface usb0.IPv4 with address 192.168.42.245. > Oct 8 08:21:04 note26 avahi-daemon[1662]: New relevant interface > usb0.IPv4 for mDNS. > Oct 8 08:21:04 note26 avahi-daemon[1662]: Registering new address record > for 192.168.42.245 on usb0.IPv4. > Oct 8 08:21:04 note26 kernel: [53722.462497] userif-3: sent link down > event. > Oct 8 08:21:05 note26 NetworkManager[1783]: <info> (usb0): device state > change: ip-config -> activated (reason 'none') [70 100 0] > Oct 8 08:21:05 note26 NetworkManager[1783]: <info> ((null)): writing > resolv.conf to /sbin/resolvconf > Oct 8 08:21:05 note26 dnsmasq[2230]: configurando servidores upstream do > DBus > Oct 8 08:21:05 note26 dnsmasq[2230]: usando nome de servidor > 192.168.42.129#53 > Oct 8 08:21:05 note26 NetworkManager[1783]: <info> Policy set 'Conexão > cabeada 2' (usb0) as default for IPv4 routing and DNS. > Oct 8 08:21:05 note26 NetworkManager[1783]: <info> Activation (usb0) > successful, device activated. > Oct 8 08:21:05 note26 vmnet-natd: RTM_NEWROUTE: index:8 > Oct 8 08:21:05 note26 vmnetBridge: RTM_NEWROUTE: index:8 > Oct 8 08:21:05 note26 vmnetBridge: Stopped bridge ham0 to virtual network > 0. > Oct 8 08:21:05 note26 vmnetBridge: Started bridge usb0 to virtual network > 0. > Oct 8 08:21:05 note26 kernel: [53722.462500] userif-3: sent link up > event.<7>[53723.417372] bridge-ham0: disabling the bridge on dev down > Oct 8 08:21:05 note26 kernel: [53723.417407] bridge-ham0: down > Oct 8 08:21:05 note26 kernel: [53723.417412] bridge-ham0: detached > Oct 8 08:21:05 note26 kernel: [53723.417442] /dev/vmnet: open called by > PID 2119 (vmnet-bridge) > Oct 8 08:21:05 note26 kernel: [53723.417452] /dev/vmnet: hub 0 does not > exist, allocating memory. > Oct 8 08:21:05 note26 kernel: [53723.417473] /dev/vmnet: port on hub 0 > successfully opened > Oct 8 08:21:05 note26 kernel: [53723.417484] bridge-usb0: can't bridge > with usb0, bad header length 58 > Oct 8 08:21:05 note26 kernel: [53723.417486] bridge-usb0: enabling the > bridge on dev up > Oct 8 08:21:05 note26 kernel: [53723.417488] bridge-usb0: can't bridge > with usb0, bad header length 58 > Oct 8 08:21:05 note26 kernel: [53723.417489] bridge-usb0: interface usb0 > is not a valid Ethernet interface > Oct 8 08:21:05 note26 kernel: [53723.417491] bridge-usb0: attached > Oct 8 08:21:05 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 5 of 5 (IPv4 Commit) complete. > Oct 8 08:21:05 note26 dbus[1595]: [system] Activating service > name='org.freedesktop.nm_dispatcher' (using servicehelper) > Oct 8 08:21:05 note26 dbus[1595]: [system] Successfully activated service > 'org.freedesktop.nm_dispatcher' > Oct 8 08:21:05 note26 kernel: [53723.616724] userif-3: sent link down > event. > Oct 8 08:21:05 note26 avahi-daemon[1662]: Joining mDNS multicast group on > interface usb0.IPv6 with address fe80::1:3dff:fe61:616f. > Oct 8 08:21:05 note26 avahi-daemon[1662]: New relevant interface > usb0.IPv6 for mDNS. > Oct 8 08:21:05 note26 avahi-daemon[1662]: Registering new address record > for fe80::1:3dff:fe61:616f on usb0.*. > Oct 8 08:21:14 note26 ntpdate[349]: adjust time server 91.189.94.4 offset > 0.024260 sec > Oct 8 08:21:24 note26 NetworkManager[1783]: <info> (usb0): IP6 addrconf > timed out or failed. > Oct 8 08:21:24 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 4 of 5 (IPv6 Configure Timeout) scheduled... > Oct 8 08:21:24 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 4 of 5 (IPv6 Configure Timeout) started... > Oct 8 08:21:24 note26 NetworkManager[1783]: <info> Activation (usb0) > Stage 4 of 5 (IPv6 Configure Timeout) complete. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1063148). > https://bugs.launchpad.net/bugs/1036788 > > Title: > modem-manager crashed with SIGSEGV in supports_port() > > Status in “modemmanager” package in Ubuntu: > Incomplete > > Bug description: > Android connected (Samsung Galaxy SIII) > > ProblemType: Crash > DistroRelease: Ubuntu 12.10 > Package: modemmanager 0.6~git201206221719.8289a64-0ubuntu1 > ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0 > Uname: Linux 3.5.0-9-generic x86_64 > ApportVersion: 2.4-0ubuntu6 > Architecture: amd64 > Date: Tue Aug 14 15:58:25 2012 > ExecutablePath: /usr/sbin/modem-manager > InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 > (20120720.1) > ProcCmdline: /usr/sbin/modem-manager > ProcEnviron: > PATH=(custom, no user) > TERM=linux > SegvAnalysis: > Segfault happened at: 0x7f9faf55c69b: cmpb $0x74,(%rax) > PC (0x7f9faf55c69b) ok > source "$0x74" ok > destination "(%rax)" (0x00000000) not located in a known VMA region > (needed writable region)! > SegvReason: writing NULL VMA > Signal: 11 > SourcePackage: modemmanager > StacktraceTop: > ?? () from /usr/lib/ModemManager/libmm-plugin-iridium.so > ?? () > ?? () > mm_plugin_base_supports_task_complete () > g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 > Title: modem-manager crashed with SIGSEGV in > mm_plugin_base_supports_task_complete() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1036788/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036788 Title: modem-manager crashed with SIGSEGV in supports_port() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1036788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
