I have a node with a GPP device and PICOFLEXOR_1 device. I can shut down both devices successfully if I do not start a waveform that uses the PICOFLEXOR_1. However, if I start a waveform, release the waveform and then shutdown the node I get a signal 6 on the PICOFLEXOR device. It appears there is no deviceIOR for the PICOFLEXOR_1 device. Below is the trace from the good shutdown and the bad shutdown.
#
Here is a good shutdown of the node, a waveform was not allocated
root#atlas-i-z7e:~# INFO:DeviceManager_impl - shutting down DeviceManager
TRACE:DeviceManager_impl - unregistering DeviceManager
TRACE:DeviceManager_impl - Releasing device GPP_1
TRACE:DeviceManager_impl - Comparing tmpDeviceIOR to deviceIOR IOR:0100000025000
00049444c3a43462f41676772656761746545786563757461626c654465766963653a312e3000000
000010000000000000064000000010102000d0000003137322e32322e32342e383800009e950e000
000fed2a3c754000005a900000000000000020000000000000008000000010000000054544101000
0001c00000001000000010001000100000001000105090101000100000009010100 IOR:01000000
2500000049444c3a43462f41676772656761746545786563757461626c654465766963653a312e30
00000000010000000000000064000000010102000d0000003137322e32322e32342e383800009e95
0e000000fed2a3c754000005a9000000000000000200000000000000080000000100000000545441
010000001c00000001000000010001000100000001000105090101000100000009010100
TRACE:DeviceManager_impl - Matched device IOR
TRACE:DeviceManager_impl - Not unregistering device GPP_1 from domain manager be
cause we are shutting down
TRACE:DeviceManager_impl - Releasing device PICOFLEXOR_1
TRACE:DeviceManager_impl - Comparing tmpDeviceIOR to deviceIOR IOR:0100000012000
00049444c3a43462f4465766963653a312e30000000010000000000000064000000010102000d000
0003137322e32322e32342e3838000085a80e000000fed8a3c754000005bd0000000004000002000
00000000000080000000100000000545441010000001c00000001000000010001000100000001000
105090101000100000009010100 IOR:010000001200000049444c3a43462f4465766963653a312e
30000000010000000000000064000000010102000d0000003137322e32322e32342e3838000085a8
0e000000fed8a3c754000005bd000000000400000200000000000000080000000100000000545441
010000001c00000001000000010001000100000001000105090101000100000009010100
TRACE:DeviceManager_impl - Matched device IOR
TRACE:DeviceManager_impl - Not unregistering device PICOFLEXOR_1 from domain man
ager because we are shutting down
TRACE:DeviceManager_impl - Sending SIGTERM to device process 0x5a9
TRACE:DeviceManager_impl - Sending SIGTERM to device process 0x5bd
INFO:DeviceManager_impl - Child process GPP_1 (pid 0x5a9) has exited with status
0
TRACE:DeviceManager_impl - Sending SIGTERM to device process 0x5bd
TRACE:DeviceManager_impl - Sending SIGKILL to device process 0x5bd
TRACE:DeviceManager_impl - Unbinding device manager context
TRACE:DeviceManager_impl - Unregistering file systems
TRACE:DeviceManager_impl - Deleting file systems
TRACE:DeviceManager_impl - Deleted file systems
INFO:DeviceManager_impl - done shutting down DeviceManager
TRACE:DeviceManager_impl - shutting down ORB
WARN:DeviceManager_impl - Child process PICOFLEXOR_1 (pid 0x5bd) has terminated
with signal 0x9
INFO:DeviceManager - Goodbye!
DEBUG:DeviceManager - Farewell!
[1]+ Done nodeBooter -debug 5 -d /var/redhawk/sdr/dev/nodes/
PICOFLEXOR/DeviceManager.dcd.xml
root#atlas-i-z7e:~#
root#atlas-i-z7e:~#
root#atlas-i-z7e:~# #########################
root#atlas-i-z7e:~#root#atlas-i-z7e:~#
#
now shutdown after waveform allocated
root#atlas-i-z7e:~# TRACE:PropertySet_impl - Query all properties
TRACE:PropertySet_impl - Query returning 2 properties
TRACE:PropertySet_impl - Query all properties
TRACE:PropertySet_impl - Query returning 2 properties
INFO:DeviceManager_impl - shutting down DeviceManager
TRACE:DeviceManager_impl - unregistering DeviceManager
TRACE:DeviceManager_impl - Releasing device GPP_1
TRACE:DeviceManager_impl - Comparing tmpDeviceIOR to deviceIOR IOR:0100000025000
00049444c3a43462f41676772656761746545786563757461626c654465766963653a312e3000000
000010000000000000064000000010102000d0000003137322e32322e32342e383800003cea0e000
000fefcaac754000005e600000000000000020000000000000008000000010000000054544101000
0001c00000001000000010001000100000001000105090101000100000009010100 IOR:01000000
2500000049444c3a43462f41676772656761746545786563757461626c654465766963653a312e30
00000000010000000000000064000000010102000d0000003137322e32322e32342e383800003cea
0e000000fefcaac754000005e6000000000000000200000000000000080000000100000000545441
010000001c00000001000000010001000100000001000105090101000100000009010100
TRACE:DeviceManager_impl - Matched device IOR
TRACE:DeviceManager_impl - Not unregistering device GPP_1 from domain manager be
cause we are shutting down
TRACE:DeviceManager_impl - Releasing device PICOFLEXOR_1
glibc detected /var/redhawk/sdr/dev/devices/PICOFLEXOR/cpp/PICOFLEXOR: d
ouble free or corruption (out): 0x000b23e0 *
ERROR:DeviceManager_impl - CORBA COMM_FAILURE exception calling releaseObject on
PICOFLEXOR_1
TRACE:DeviceManager_impl - Sending SIGTERM to device process 1510
TRACE:DeviceManager_impl - Sending SIGTERM to device process 1529
WARN:DeviceManager_impl - Child process PICOFLEXOR_1 (pid 1529) has terminated w
ith signal 6**
INFO:DeviceManager_impl - Child process GPP_1 (pid 1510) has exited with status
0
TRACE:DeviceManager_impl - Unbinding device manager context
TRACE:DeviceManager_impl - Unregistering file systems
TRACE:DeviceManager_impl - Deleting file systems
TRACE:DeviceManager_impl - Deleted file systems
INFO:DeviceManager_impl - done shutting down DeviceManager
TRACE:DeviceManager_impl - shutting down ORB
INFO:DeviceManager - Goodbye!
DEBUG:DeviceManager - Farewell!
How are you launching the waveform? Looks like you are running nodebooter as root. Have you tried running nodebooter as a regular user or as a redhawk user?
Related
I am running Android Studio on Windows 8.1. When I try to run simple Hello World on a virtual device, it shows briefly then exits with dialog "The emulator process for AVD [device] has terminated.
Here is the output from the idea.log:
INFO - manager.EmulatorProcessHandler - Emulator: C:\Users\[my_username]\AppData\Local\Android\sdk\emulator\emulator.exe -netdelay none -netspeed full -avd Nexus_4_API_22
INFO - manager.EmulatorProcessHandler - Emulator: WARNING | encryption is off
INFO - manager.EmulatorProcessHandler - Emulator: Warning: Quick Boot / Snapshots not supported on this machine. A CPU with EPT + UG features is currently needed. We will address this in a future release.
INFO - manager.EmulatorProcessHandler - Emulator: WARNING | Not all modern X86 virtualization features supported, which introduces problems with slowdown when running Android on multicore vCPUs. Setting AVD to run with 1 vCPU core only.
INFO - manager.EmulatorProcessHandler - Emulator: WARNING | cannot add library vulkan-1.dll: failed
INFO - manager.EmulatorProcessHandler - Emulator: WARNING | cannot add library vulkan-1.dll: failed
INFO - manager.EmulatorProcessHandler - Emulator: INFO | configAndStartRenderer: setting vsync to 60 hz
INFO - manager.EmulatorProcessHandler - Emulator: INFO | added library C:\Users\[my_username]\AppData\Local\Android\sdk\emulator\lib64\vulkan\vulkan-1.dll
INFO - manager.EmulatorProcessHandler - Emulator: HAX is working and emulator runs in fast virt mode.
INFO - b.PhysicalDeviceChangeListener - emulator-5554 connected
INFO - manager.EmulatorProcessHandler - Emulator: INFO | Started GRPC server at 127.0.0.1:8554, security: Local
INFO - manager.EmulatorProcessHandler - Emulator: INFO | Advertising in: C:\Users\[my_username]\AppData\Local\Temp\avd\running\pid_1072.ini
INFO - b.PhysicalDeviceChangeListener - emulator-5554 state changed to ONLINE
INFO - b.PhysicalDeviceChangeListener - emulator-5554 state changed to OFFLINE
WARN - #com.android.ddmlib - Failed to start monitoring emulator-5554
INFO - manager.EmulatorProcessHandler - Emulator: INFO | Android emulator version 31.2.8.0 (build_id 8143646) (CL:N/A)
INFO - manager.EmulatorProcessHandler - Emulator: Process finished with exit code -1073741819 (0xC0000005)
WARN - manager.EmulatorProcessHandler - Emulator terminated with exit code -1073741819
INFO - b.PhysicalDeviceChangeListener - emulator-5554 disconnected
However, I am able to run it from the command line successfully. The log is nearly identical:
I have searched these forums and tried everything:
Change Graphics Performance option to "Software"
Cold Boot Now option
Wipe Data option
Delete .android folder
Delete, create multiple different virtual devices
Run as Administrator
Install, reinstall Android Emulator
Increase IDE memory to max (2GB)
Reboot machine
I am out of ideas. Has anyone been able to solve this?
Android Studio Bumblebee | 2021.1.1 Patch 2
Build #AI-211.7628.21.2111.8193401, built on February 16, 2022
Runtime version: 11.0.11+9-b1341.60 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 8.1 6.3
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Registry: external.system.auto.import.disabled=true
Non-Bundled Plugins: mobi.hsz.idea.gitignore (4.1.0), org.intellij.plugins.markdown (211.7142.37)
I want to make work mt7622 soc's ethernet controller and faced with this issue. I've compiled mtk_soc_eth driver as mkt_eth module and I have an entry in mt7622-bananapi-bpi-r64.dts device tree for device, compatible with driver.
During boot this module is loaded into system automatically (I think after mounting rootfs):
[root#nixos:~]# lsmod | grep mtk_eth
mtk_eth 69632 0
dsa_core 98304 1 mtk_eth
And it seems registered as platform driver:
[root#nixos:~]# ls /sys/bus/platform/drivers/mtk_soc_eth
bind module uevent unbind
Also after boot I have an platform device:
[root#nixos:~]# ls /sys/bus/platform/devices/1b100000.ethernet
driver_override
modalias
of_node
power
subsystem
supplier:platform:10006000.power-controller
supplier:platform:10209000.apmixedsys
supplier:platform:10210000.topckgen
supplier:platform:10211000.pinctrl
supplier:platform:1b000000.syscon
supplier:platform:1b128000.sgmiisys
uevent
waiting_for_supplier
However they are not binded for some reason. Moreover, when I try to bind them manually, I get an error:
[root#nixos:~]# echo '1b100000.ethernet' > /sys/bus/platform/drivers/mtk_soc_eth/bind
-bash: echo: write error: Resource temporarily unavailable
How can I understand why ethernet device doesn't bind with driver?
Well, it seems that I figured out where is the problem. It seems that linux kernel have rich debug options) I've enabled dynamic debug to track which happens inside __driver_probe_device https://github.com/torvalds/linux/blob/master/drivers/base/dd.c#L730 function:
[root#nixos:~]# echo 'file dd.c +p'>/sys/kernel/debug/dynamic_debug/control
[root#nixos:~]# echo 'file core.c +p'>/sys/kernel/debug/dynamic_debug/control
And then tried to bind device driver and device:
[root#nixos:~]# echo '1b100000.ethernet' >/sys/bus/platform/drivers/mtk_soc_eth/bind
-bash: echo: write error: Resource temporarily unavailable
[root#nixos:~]# dmesg -T | tail
...
[Sat Jan 1 00:03:27 2000] bus: 'platform': __driver_probe_device: matched device 1b100000.ethernet with driver mtk_soc_eth
[Sat Jan 1 00:03:27 2000] platform 1b100000.ethernet: error -EPROBE_DEFER: supplier 1b000000.syscon not ready
It seems that one of the dependent devices (1b000000.syscon) is not ready (at the same time /sys/bus/platform/devices/1b100000.ethernet/waiting_for_supplier was still 0 for some reason). I need to load clk-mt7622-eth driver as well.
Hardware/IDE Context:
Part/board: Genuine STM32F103C8 (BluePill)
Programmer: ST-Link V2
IDE: STM32CubeIDE 1.5.1 on fully-updated Windows 10
Flashing utility/debugger: OpenOCD
In attempting to build/flash a simple PC_13 LED blinky program to my BluePill board, I experience errors from OpenOCD like so:
Open On-Chip Debugger 0.10.0+dev-01288-g7491fb4 (2020-10-27-17:36)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : STLINK V2J37S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.256346
Info : Unable to match requested speed 8000 kHz, using 4000 kHz
Info : Unable to match requested speed 8000 kHz, using 4000 kHz
Info : clock speed 4000 kHz
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x1ba01477
Info : STM32F103C8Tx.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : STM32F103C8Tx.cpu: external reset detected
Info : starting gdb server for STM32F103C8Tx.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Error: timed out while waiting for target halted
Error executing event gdb-attach on target STM32F103C8Tx.cpu:
TARGET: STM32F103C8Tx.cpu - Not halted
Info : device id = 0x20036410
Info : flash size = 64kbytes
Info : accepting 'gdb' connection on tcp/3333
Error: timed out while waiting for target halted
Error executing event gdb-attach on target STM32F103C8Tx.cpu:
TARGET: STM32F103C8Tx.cpu - Not halted
Error: timed out while waiting for target halted
Error executing event gdb-flash-erase-start on target STM32F103C8Tx.cpu:
TARGET: STM32F103C8Tx.cpu - Not halted
Error: Target not halted
Error: failed erasing sectors 0 to 5
Error: flash_erase returned -304
shutdown command invoked
Info : dropped 'gdb' connection
shutdown command invoked
I'm interested in using OpenOCD-based flashing for my project to make use of some STM32F103C8 clone boards I have lying around, but the upload process works again when I switch the flashing mode/"Debug Probe" in STM32CubeIDE back to ST-Link (ST-Link GDB Server) from ST-Link (OpenOCD).
This is a peculiar error to me, especially since I specifically remember this exact configuration (STM32CubeIDE + OpenOCD + ST-Link + STM32F103C8) working a couple of months ago. Does anyone have any ideas as to what this could be caused by? I have the OpenOCD debugger to use the standard auto-generated config file.
Also please let me know if there is any more information/details you'd need to help diagnose this issue. I'd be happy to provide anything necessary.
EDIT 2/22/2021:
Here is a copy of the auto-generated (by STM32CubeIDE) OpenOCD .cfg file:
# This is an genericBoard board with a single STM32F103C8Tx chip
#
# Generated by STM32CubeIDE
# Take care that such file, as generated, may be overridden without any early notice. Please have a look to debug launch configuration setup(s)
source [find interface/stlink-dap.cfg]
set WORKAREASIZE 0x5000
transport select "dapdirect_swd"
set CHIPNAME STM32F103C8Tx
set BOARDNAME genericBoard
# Enable debug when in low power modes
set ENABLE_LOW_POWER 1
# Stop Watchdog counters when halt
set STOP_WATCHDOG 1
# STlink Debug clock frequency
set CLOCK_FREQ 8000
# Reset configuration
# use hardware reset, connect under reset
# connect_assert_srst needed if low power mode application running (WFI...)
reset_config srst_only srst_nogate connect_assert_srst
set CONNECT_UNDER_RESET 1
set CORE_RESET 0
# ACCESS PORT NUMBER
set AP_NUM 0
# GDB PORT
set GDB_PORT 3333
# BCTM CPU variables
source [find target/stm32f1x.cfg]
#SWV trace
tpiu config disable
Ultimately, after some further research and trial & error, I settled on a fix that seems to work for me. I noticed that when the error with halting the CPU came up, the correct program seemed to have been loaded and the RESET button just needed to be toggled manually. These are the OpenOCD settings I ended up settling on:
Changes from the default configuration:
SWD Frequency: 8 → 4 MHz
This is technically not required to work, but OpenOCD will automatically revert back to 4 MHz during the upload anyway
Reset Mode: Connect Under Reset → None
This works for me with the following output:
Open On-Chip Debugger 0.10.0+dev-01288-g7491fb4 (2020-10-27-17:36)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : STLINK V2J37S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.254751
Info : clock speed 4000 kHz
Info : stlink_dap_op_connect(connect)
Info : SWD DPIDR 0x1ba01477
Info : STM32F103C8Tx.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : STM32F103C8Tx.cpu: external reset detected
Info : starting gdb server for STM32F103C8Tx.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Info : device id = 0x20036410
Info : flash size = 64kbytes
undefined debug reason 8 - target needs reset
Info : accepting 'gdb' connection on tcp/3333
undefined debug reason 8 - target needs reset
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08000474 msp: 0x20005000
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08000474 msp: 0x20005000
shutdown command invoked
Info : dropped 'gdb' connection
shutdown command invoked
I'm trying to setup a gridgain cluster in a cloud environment (opensciencedatacloud.org).
I've verified that UDP multicast is available and port 47400 is open in this environment, but unfortunately GridGain is unable to find the other nodes when they are launched. Do you have clue why it is not working.
Following you can find below the a cluster node log:
INFO o.g.grid.kernal.GridKernal%nextflow - Config URL: n/a
INFO o.g.grid.kernal.GridKernal%nextflow - Daemon mode: off
INFO o.g.grid.kernal.GridKernal%nextflow - OS: Linux 2.6.32-358.2.1.el6.x86_64 amd64
INFO o.g.grid.kernal.GridKernal%nextflow - OS user: root
INFO o.g.grid.kernal.GridKernal%nextflow - Language runtime: Groovy
INFO o.g.grid.kernal.GridKernal%nextflow - VM information: Java(TM) SE Runtime Environment 1.7.0_51-b13 Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 24.51-b03
INFO o.g.grid.kernal.GridKernal%nextflow - VM total memory: 0.83GB
INFO o.g.grid.kernal.GridKernal%nextflow - Remote Management [restart: off, REST: on, JMX (remote: off)]
INFO o.g.grid.kernal.GridKernal%nextflow - GRIDGAIN_HOME=/root
INFO o.g.grid.kernal.GridKernal%nextflow - VM arguments: [-Djava.awt.headless=true]
WARN o.g.grid.kernal.GridKernal%nextflow - SMTP is not configured - email notifications are off.
INFO o.g.grid.kernal.GridKernal%nextflow - Configured caches ['allSessions']
INFO o.g.grid.kernal.GridKernal%nextflow - 3-rd party licenses can be found at: /root/libs/licenses
INFO o.g.grid.kernal.GridKernal%nextflow - Local node user attribute [ROLE=worker]
[gridgain-#5%pub-nextflow%] WARN o.g.grid.kernal.GridDiagnostic - Initial heap size is less than 512MB (59MB). It is highly recommended to allocate at least 512MB of initial heap to run GridGain. Use -Xms512m -Xmx512m to set initial heap size.
INFO o.g.grid.kernal.GridKernal%nextflow - Non-loopback local IPs: 172.16.1.98, fe80:0:0:0:78b5:53ff:fe01:643b%3, fe80:0:0:0:f816:3eff:fe54:f4e8%2, 172.17.42.1
INFO o.g.grid.kernal.GridKernal%nextflow - Enabled local MACs: FA163E54F4E8, 7AB55301643B
INFO o.g.g.s.c.t.GridTcpCommunicationSpi - IPC shared memory server endpoint started [port=48100, tokDir=/root/work/ipc/shmem/cf5dbd14-4bb8-420b-998f-820056aa6d1c-2646]
INFO o.g.g.s.c.t.GridTcpCommunicationSpi - Successfully bound shared memory communication to TCP port [port=48100, locHost=0.0.0.0/0.0.0.0]
INFO o.g.g.s.c.t.GridTcpCommunicationSpi - Successfully bound to TCP port [port=47100, locHost=0.0.0.0/0.0.0.0]
WARN o.g.g.s.c.noop.GridNoopCheckpointSpi - Checkpoints are disabled (to enable configure any GridCheckpointSpi implementation)
INFO o.g.grid.kernal.GridKernal%nextflow - Security status [authentication=off, secure-session=off]
WARN o.g.g.k.p.cache.GridCacheProcessor - Cache write synchronization mode is set to FULL_ASYNC. All single-key 'put' and 'remove' operations will return 'null', all 'putx' and 'removex' operations will return 'true'.
WARN o.g.g.k.p.cache.GridCacheProcessor - Automatically set write order mode to PRIMARY for write synchronization mode [writeSynchronizationMode=FULL_ASYNC, cacheName=allSessions]
WARN o.g.g.k.p.cache.GridCacheProcessor - Query indexing is disabled (queries will not work) for cache: 'allSessions'. To enable change GridCacheConfiguration.isQueryIndexEnabled() property.
INFO o.g.g.k.p.cache.GridCacheDgcManager - <allSessions> DGC trace log disabled.
INFO o.g.g.k.p.cache.GridCacheProcessor - Started cache [name=allSessions, mode=REPLICATED]
INFO org.eclipse.jetty.server.Server - jetty-9.0.5.v20130815
INFO o.e.jetty.server.ServerConnector - Started ServerConnector#7b9617a0{HTTP/1.1}{0.0.0.0:8080}
INFO o.g.g.k.p.r.p.h.j.GridJettyRestProtocol - Command protocol successfully started [name=Jetty REST, host=/0.0.0.0, port=8080]
INFO o.g.g.k.p.r.p.t.GridTcpRestProtocol - Command protocol successfully started [name=TCP binary, host=0.0.0.0/0.0.0.0, port=11211]
INFO o.g.g.s.d.tcp.GridTcpDiscoverySpi - Successfully bound to TCP port [port=47500, localHost=/172.16.1.98]
WARN o.g.g.s.d.t.i.m.GridTcpDiscoveryMulticastIpFinder - GridTcpDiscoveryMulticastIpFinder has no pre-configured addresses (it is recommended in production to specify at least one address in GridTcpDiscoveryMulticastIpFinder.getAddresses() configuration property)
>>> +------------------------------------------------------------------------------------+
>>> GridGain ver. platform-os-6.0.2#20140323-sha1:f9c796a1b29d2d7ce2737e681cbe578b5315d79f
>>> +------------------------------------------------------------------------------------+
>>> OS name: Linux 2.6.32-358.2.1.el6.x86_64 amd64
>>> CPU(s): 2
>>> Heap: 0.83GB
>>> VM name: 2646#node.novalocal
>>> Grid name: nextflow
>>> Local node [ID=CF5DBD14-4BB8-420B-998F-820056AA6D1C, order=1]
>>> Local node addresses: [node.novalocal/172.16.1.98]
>>> Local ports: TCP:8080 TCP:11211 TCP:47100 TCP:47500 TCP:48100
>>> GridGain documentation: http://www.gridgain.com/documentation
INFO o.g.g.k.m.d.GridDiscoveryManager - Topology snapshot [ver=1, nodes=1, CPUs=2, heap=0.83GB]
Usually software firewalls prevent multicast packets. Can you try with firewall disabled on your system?
I am trying to fix a problem I am having on Ubuntu (tried different versions including the latest 13.10) with a USB device talking CDC/ACM on one of its interfaces. The kernel module handling this kind of devices only reports
cdc_acm 6-2:1.1: This device cannot do calls on its own. It is not a modem.
cdc_acm: probe of 6-2:1.1 failed with error -22
in dmesg and that is it. Nothing about "Zero length descriptor references" or similar stuff that other people report on the web. So I wanted to find out what the problem might be. I followed the description in http://www.silly-science.co.uk/2012/06/23/lenovo-usb-modem-in-linux-ubuntu-10-04 to compile and load a custom cdc-acm module. First, I changed the two #undefs for debug to #defines in cdc-acm.c, but I am still not getting any additional output in dmesg.
Changing the version string in cdc-acm.c's DRIVER_VERSION define to something else, I can verify that my modified module is indeed loaded. Am I looking for the debug output in the wrong place?
I managed to get debug info from cdc_acm in dmesg, and even though I don't have something special to share, these were my steps, using latest kernel as of today 4.2-rc5:
Change DEBUG and VERBOSE_DEBUG #undefs to #defines in cdc-acm.c.
make -C /lib/modules/$(uname -r)/build M=$(pwd)/drivers/usb/class modules
modprobe -r cdc_acm; insmod $(pwd)/drivers/usb/class/cdc-acm.ko
dmesg after plugging a compatible device
[...]
[14035.355036] cdc_acm 2-2:1.1: acm_tty_write - write 1
[14035.368040] cdc_acm 2-2:1.1: acm_softint
[14038.156445] cdc_acm 2-2:1.0: acm_tty_close
[14038.173054] cdc_acm 2-2:1.0: acm_ctrl_msg - rq 0x22, val 0x0, len 0x0, result 0
[14038.173059] cdc_acm 2-2:1.0: acm_port_shutdown
[14038.173640] cdc_acm 2-2:1.0: acm_ctrl_irq - urb shutting down with status: -2
[14038.174636] cdc_acm 2-2:1.1: acm_read_bulk_callback - urb 0, len 0
[...]