Why is linux kernel not using my driver - module

I have tried to write a simple linux char device driver using this tutorial: http://matthias.vallentin.net/blog/2007/04/writing-a-linux-kernel-driver-for-an-unknown-usb-device/
I am using slightly newer device and slightly newer kernel. So I used their code changing product and vendor id and I am just trying to make kernel call probe function when device is attached which I failed to do looking at my /var/log/messages. Driver loads successfully:
Sep 5 18:32:43 manticore kernel: [10673.664884] usbcore: deregistering interface driver missile_launcher
Sep 5 18:32:43 manticore kernel: [10673.664908] [info] usb_ml_exit(661): module deregistered
Sep 5 18:32:43 manticore kernel: [10673.666314] usbcore: registered new interface driver missile_launcher
Sep 5 18:32:43 manticore kernel: [10673.666317] [info] usb_ml_init(651): driver registered successfully
But when device is attached the driver is not used:
Sep 5 17:58:12 manticore kernel: [ 8607.295688] usb 3-1.1: New USB device found, idVendor=2123, idProduct=1010
Sep 5 17:58:12 manticore kernel: [ 8607.295689] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 5 17:58:12 manticore kernel: [ 8607.295691] usb 3-1.1: Product: USB Missile Launcher
Sep 5 17:58:12 manticore kernel: [ 8607.295693] usb 3-1.1: Manufacturer: Syntek
Sep 5 17:58:12 manticore kernel: [ 8607.295789] usb 3-1.1: usb_probe_device
Sep 5 17:58:12 manticore kernel: [ 8607.295791] usb 3-1.1: configuration #1 chosen from 1 choice
Sep 5 17:58:12 manticore kernel: [ 8607.295797] usb 3-1.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
Sep 5 17:58:12 manticore kernel: [ 8607.295855] usb 3-1.1: Successful Endpoint Configure command
Sep 5 17:58:12 manticore kernel: [ 8607.296132] usb 3-1.1: adding 3-1.1:1.0 (config #1, interface 0)
Sep 5 17:58:12 manticore kernel: [ 8607.296173] usbhid 3-1.1:1.0: usb_probe_interface
Sep 5 17:58:12 manticore kernel: [ 8607.296174] usbhid 3-1.1:1.0: usb_probe_interface - got id
Sep 5 17:58:12 manticore kernel: [ 8607.298577] usbhid 3-1.1:1.0: looking for a minor, starting at 96
Sep 5 17:58:12 manticore kernel: [ 8607.298697] generic-usb 0003:2123:1010.0008: hiddev0,hidraw2: USB HID v1.10 Device [Syntek USB Missile Launcher] on usb-0000:00:14.0-1.1/input0
Sep 5 17:58:12 manticore kernel: [ 8607.298712] drivers/usb/core/inode.c: creating file '016'
Sep 5 17:58:12 manticore kernel: [ 8607.298754] hub 3-1:1.0: port 2, status 0101, change 0000, 12 Mb/s
Sep 5 17:58:12 manticore kernel: [ 8607.310627] hub 3-1:1.0: port 2 not reset yet, waiting 10ms
Sep 5 17:58:12 manticore kernel: [ 8607.372509] usb 3-1.2: new high-speed USB device number 17 using xhci_hcd
Sep 5 17:58:12 manticore kernel: [ 8607.418456] usb 3-1.2: skipped 1 descriptor after configuration
Sep 5 17:58:12 manticore kernel: [ 8607.418460] usb 3-1.2: skipped 6 descriptors after interface
Sep 5 17:58:12 manticore kernel: [ 8607.418462] usb 3-1.2: skipped 1 descriptor after endpoint
Sep 5 17:58:12 manticore kernel: [ 8607.418463] usb 3-1.2: skipped 9 descriptors after interface
Sep 5 17:58:12 manticore kernel: [ 8607.419100] usb 3-1.2: default language 0x0409
Sep 5 17:58:12 manticore kernel: [ 8607.421607] usb 3-1.2: udev 17, busnum 3, minor = 272
The code I have that is responsible for making this association is:
#define ML_VENDOR_ID 0x2123
#define ML_PRODUCT_ID 0x1010
static struct usb_device_id ml_table [] = {
{ USB_DEVICE(ML_VENDOR_ID, ML_PRODUCT_ID) },
{ }
};
static struct usb_driver ml_driver = {
.name = "missile_launcher",
.id_table = ml_table,
.probe = ml_probe,
.disconnect = ml_disconnect,
};
My kernel version is 3.3.8
Any ideas what might be wrong?
BTW. I am completely new at this so it is very likely that I skipped some relevant information please ask me if something more is needed.

Related

Buildroot - Hang at Starting Kernel

I'm trying to use Buildroot to create a linux image for my Banana Pi M2M. My issue is that when I power it up, the system hangs at "Starting kernel..." indefinitely.
Here is the log:
U-Boot 2021.10 (Nov 11 2021 - 11:29:29 +0000) Allwinner Technology
CPU: Allwinner A33 (SUN8I 1667)
Model: BananaPi M2 Magic
DRAM: 512 MiB
MMC: mmc#1c0f000: 0, mmc#1c10000: 2, mmc#1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1... Unknown monitor
Unknown monitor
In: serial
Out: serial
Err: serial
Allwinner mUSB OTG (Peripheral)
Net: eth0: usb_ether
starting USB...
Bus usb#1c1a000: USB EHCI 1.00
Bus usb#1c1a400: USB OHCI 1.0
scanning bus usb#1c1a000 for devices... 1 USB Device(s) found
scanning bus usb#1c1a400 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
306 bytes read in 1 ms (298.8 KiB/s)
## Executing script at 43100000
23186 bytes read in 2 ms (11.1 MiB/s)
4882032 bytes read in 205 ms (22.7 MiB/s)
Kernel image # 0x46000000 [ 0x000000 - 0x4a7e70 ]
## Flattened Device Tree blob at 49000000
Booting using the fdt blob at 0x49000000
Using Device Tree in place at 49000000, end 49008a91
DE is present but not probed
Starting kernel ...
As there is no buildroot defconfig for the BananaPi M2M, I'm working from a modified olimex_a33_olinuxino_defconfig (Both boards use the Allwinner A33 processor). I am, however, using both the Bananapi_m2m_defconfig and sun8i-r16-bananapi-m2m.dts from u-boot.
My modified olimex defconfig:
# Architecture
BR2_arm=y
BR2_cortex_a7=y
BR2_ARM_FPU_NEON_VFPV4=y
# Linux headers same as kernel, a 5.14 series
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_14=y
# System configuration
BR2_TARGET_GENERIC_HOSTNAME="bananapi-m2m"
BR2_TARGET_GENERIC_ISSUE="Welcome to Bananapi M2M"
BR2_TARGET_GENERIC_GETTY=y
BR2_TARGET_GENERIC_GETTY_PORT="ttyS2"
# Bootloaders
BR2_TARGET_UBOOT=y
BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
BR2_TARGET_UBOOT_CUSTOM_VERSION=y
BR2_TARGET_UBOOT_CUSTOM_VERSION_VALUE="2021.10"
BR2_TARGET_UBOOT_BOARD_DEFCONFIG="Bananapi_m2m"
BR2_TARGET_UBOOT_NEEDS_DTC=y
BR2_TARGET_UBOOT_NEEDS_PYTHON3=y
BR2_TARGET_UBOOT_NEEDS_PYLIBFDT=y
BR2_TARGET_UBOOT_NEEDS_OPENSSL=y
BR2_TARGET_UBOOT_FORMAT_BIN=y
BR2_TARGET_UBOOT_SPL=y
BR2_TARGET_UBOOT_SPL_NAME="u-boot-sunxi-with-spl.bin"
BR2_PACKAGE_HOST_UBOOT_TOOLS=y
BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT=y
BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT_SOURCE="$(BR2_EXTERNAL_BANANAPI_M2M_PATH)/board/bananapi-m2m/boot.cmd"
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.14.13"
BR2_LINUX_KERNEL_USE_DEFCONFIG=y
BR2_LINUX_KERNEL_DEFCONFIG="sunxi"
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="sun8i-r16-bananapi-m2m.dts"
BR2_LINUX_KERNEL_INSTALL_TARGET=y
# Filesystem
BR2_TARGET_ROOTFS_EXT2=y
BR2_TARGET_ROOTFS_EXT2_4=y
BR2_ROOTFS_POST_BUILD_SCRIPT="$(BR2_EXTERNAL_BANANAPI_M2M_PATH)/board/bananapi-m2m/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
BR2_ROOTFS_POST_SCRIPT_ARGS="-c $(BR2_EXTERNAL_BANANAPI_M2M_PATH)/board/bananapi-m2m/genimage.cfg"
# Additional tools
BR2_PACKAGE_HOST_DOSFSTOOLS=y
BR2_PACKAGE_HOST_GENIMAGE=y
BR2_PACKAGE_HOST_UBOOT_TOOLS=y
BR2_PACKAGE_HOST_MTOOLS=y
The specific tweaks I made:
Changed the getty port to ttyS2 (the default debug uart for the m2m is uart2)
Swapped to the pre-existing uboot defconfig for Bananapi_m2m
Swapped to the pre-existing device tree file from u-boot
Redirected boot.cmd to an external package
Redirected post-build.sh and genimage.cfg to an external package
At the moment, boot.cmd, post-build.sh and genimage.cfg are unmodified copies of the olimex versions. I'll include boot.cmd for reference.
boot.cmd:
setenv bootargs console=ttyS2,115200 root=/dev/mmcblk0p1 rootwait panic=10 ${extra}
ext4load mmc 0 0x49000000 /boot/${fdtfile}
ext4load mmc 0 0x46000000 /boot/zImage
env set fdt_high ffffffff
bootz 0x46000000 - 0x49000000
I'm somewhat of a novice, so apologies if I've shared too much irrelevant information. If anyone has any insight I'd greatly appreciate it, I feel a little blind with the only output being "Starting Kernel..."
EDIT: I reverted the boot argument back to ttyS0 and it got over the initial hang. I'm not sure what part it's hanging at now, is it failing to run the Getty?
U-Boot 2021.10 (Nov 12 2021 - 12:27:32 +0000) Allwinner Technology
CPU: Allwinner A33 (SUN8I 1667)
Model: BananaPi M2 Magic
DRAM: 512 MiB
MMC: mmc#1c0f000: 0, mmc#1c10000: 2, mmc#1c11000: 1
Loading Environment from FAT... Unable to use mmc 0:1... Unknown monitor
Unknown monitor
In: serial
Out: serial
Err: serial
Allwinner mUSB OTG (Peripheral)
Net: eth0: usb_ether
starting USB...
Bus usb#1c1a000: USB EHCI 1.00
Bus usb#1c1a400: USB OHCI 1.0
scanning bus usb#1c1a000 for devices... 1 USB Device(s) found
scanning bus usb#1c1a400 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
294 bytes read in 1 ms (287.1 KiB/s)
## Executing script at 43100000
23186 bytes read in 3 ms (7.4 MiB/s)
4882032 bytes read in 204 ms (22.8 MiB/s)
Kernel image # 0x46000000 [ 0x000000 - 0x4a7e70 ]
## Flattened Device Tree blob at 49000000
Booting using the fdt blob at 0x49000000
Using Device Tree in place at 49000000, end 49008a91
DE is present but not probed
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.14.13 (ryan#ryan-VirtualBox) (arm-buildroot-linux-uclibcgnueabihf-gcc.br_real (Buildroot 2021.11-rc1-106-g827bd376e3) 10.3.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP Fri Nov 12 11:27:52 GMT 2021
[ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: BananaPi M2 Magic
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 16 MiB at 0x5f000000
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000040000000-0x000000005fffffff]
[ 0.000000] HighMem empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000040000000-0x000000005fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000005fffffff]
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: Using PSCI v0.1 Function IDs from DT
[ 0.000000] percpu: Embedded 15 pages/cpu s31628 r8192 d21620 u61440
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 130048
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p1 rootwait panic=10
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 490592K/524288K available (7168K kernel code, 910K rwdata, 1984K rodata, 1024K init, 231K bss, 17312K reserved, 16384K cma-reserved, 0K highmem)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] GIC: Using split EOI/Deactivate mode
[ 0.000000] random: get_random_bytes called from start_kernel+0x484/0x638 with crng_init=0
[ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000002] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[ 0.000019] Switching to timer-based delay loop, resolution 41ns
[ 0.000232] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.000684] Console: colour dummy device 80x30
[ 0.000745] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000)
[ 0.000767] pid_max: default: 32768 minimum: 301
[ 0.000897] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.000916] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.001619] CPU: Testing write buffer coherency: ok
[ 0.001938] /cpus/cpu#0 missing clock-frequency property
[ 0.001977] /cpus/cpu#1 missing clock-frequency property
[ 0.001998] /cpus/cpu#2 missing clock-frequency property
[ 0.002021] /cpus/cpu#3 missing clock-frequency property
[ 0.002036] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.002531] Setting up static identity map for 0x40100000 - 0x40100060
[ 0.002655] rcu: Hierarchical SRCU implementation.
[ 0.003134] smp: Bringing up secondary CPUs ...
[ 0.003873] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.004705] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.005469] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.005563] smp: Brought up 1 node, 4 CPUs
[ 0.005594] SMP: Total of 4 processors activated (192.00 BogoMIPS).
[ 0.005606] CPU: All CPU(s) started in HYP mode.
[ 0.005613] CPU: Virtualization extensions available.
[ 0.006185] devtmpfs: initialized
[ 0.011678] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
[ 0.011896] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.011926] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.012703] pinctrl core: initialized pinctrl subsystem
[ 0.013768] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.015138] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.016103] thermal_sys: Registered thermal governor 'step_wise'
[ 0.016635] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.016662] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.023731] platform 1e60000.display-backend: Fixing up cyclic dependency with 1e00000.display-frontend
[ 0.024061] platform 1e70000.drc: Fixing up cyclic dependency with 1e60000.display-backend
[ 0.035542] SCSI subsystem initialized
[ 0.035979] usbcore: registered new interface driver usbfs
[ 0.036030] usbcore: registered new interface driver hub
[ 0.036074] usbcore: registered new device driver usb
[ 0.036247] mc: Linux media interface: v0.10
[ 0.036283] videodev: Linux video capture interface: v2.00
[ 0.036381] pps_core: LinuxPPS API ver. 1 registered
[ 0.036392] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti#linux.it>
[ 0.036414] PTP clock support registered
[ 0.036775] Advanced Linux Sound Architecture Driver Initialized.
[ 0.037608] clocksource: Switched to clocksource arch_sys_counter
[ 0.044554] NET: Registered PF_INET protocol family
[ 0.044741] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.045332] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 0.045370] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[ 0.045416] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.045483] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.045606] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.045657] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.045833] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.046512] RPC: Registered named UNIX socket transport module.
[ 0.046534] RPC: Registered udp transport module.
[ 0.046542] RPC: Registered tcp transport module.
[ 0.046549] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.047978] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[ 0.053618] NFS: Registering the id_resolver key type
[ 0.053671] Key type id_resolver registered
[ 0.053680] Key type id_legacy registered
[ 0.053769] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 0.053783] io scheduler mq-deadline registered
[ 0.053794] io scheduler kyber registered
[ 0.057821] sun8i-a33-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[ 0.104123] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[ 0.105906] sun8i-a33-pinctrl 1c20800.pinctrl: supply vcc-pb not found, using dummy regulator
[ 0.106801] printk: console [ttyS0] disabled
[ 0.127056] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 41, base_baud = 1500000) is a U6_16550A
[ 0.791590] printk: console [ttyS0] enabled
[ 0.796249] sun8i-a33-pinctrl 1c20800.pinctrl: supply vcc-pg not found, using dummy regulator
[ 0.825603] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 42, base_baud = 1500000) is a U6_16550A
[ 0.842426] lima 1c40000.gpu: gp - mali400 version major 1 minor 1
[ 0.848709] lima 1c40000.gpu: pp0 - mali400 version major 1 minor 1
[ 0.855018] lima 1c40000.gpu: pp1 - mali400 version major 1 minor 1
[ 0.861333] lima 1c40000.gpu: l2 cache 64K, 4-way, 64byte cache line, 64bit external bus
[ 0.869824] lima 1c40000.gpu: bus rate = 200000000
[ 0.874621] lima 1c40000.gpu: mod rate = 384000000
[ 0.879511] lima 1c40000.gpu: dev_pm_opp_set_regulators: no regulator (mali) found: -19
[ 0.887881] lima 1c40000.gpu: Failed to register cooling device
[ 0.894173] [drm] Initialized lima 1.1.0 20191231 for 1c40000.gpu on minor 0
[ 0.904373] libphy: Fixed MDIO Bus: probed
[ 0.909324] CAN device driver interface
[ 0.913799] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.920352] ehci-platform: EHCI generic platform driver
[ 0.925697] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.931896] ohci-platform: OHCI generic platform driver
[ 0.938647] sun6i-rtc 1f00000.rtc: registered as rtc0
[ 0.943732] sun6i-rtc 1f00000.rtc: setting system clock to 1970-01-01T00:00:06 UTC (6)
[ 0.951685] sun6i-rtc 1f00000.rtc: RTC enabled
[ 0.956410] i2c /dev entries driver
[ 0.961594] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, nowayout=0)
[ 0.970388] sun8i-a33-pinctrl 1c20800.pinctrl: supply vcc-pc not found, using dummy regulator
[ 0.979609] sun4i-ss 1c15000.crypto-engine: Die ID 5
[ 0.986353] usbcore: registered new interface driver usbhid
[ 0.991972] usbhid: USB HID core driver
[ 0.998190] cedrus 1c0e000.video-codec: Device registered as /dev/video0
[ 1.007831] NET: Registered PF_PACKET protocol family
[ 1.012914] can: controller area network core
[ 1.017335] NET: Registered PF_CAN protocol family
[ 1.022157] can: raw protocol
[ 1.025131] can: broadcast manager protocol
[ 1.029335] can: netlink gateway - max_hops=1
[ 1.033886] Key type dns_resolver registered
[ 1.038244] Registering SWP/SWPB emulation handler
[ 1.052575] sun8i-a23-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver
[ 1.061524] sun8i-a23-r-pinctrl 1f02c00.pinctrl: supply vcc-pl not found, using dummy regulator
[ 1.071777] sun8i-a33-pinctrl 1c20800.pinctrl: supply vcc-pc not found, using dummy regulator
[ 1.081200] sunxi-rsb 1f03400.rsb: RSB running at 3000000 Hz
[ 1.087266] axp20x-rsb sunxi-rsb-3a3: AXP20x variant AXP223 found
[ 1.095175] input: axp20x-pek as /devices/platform/soc/1f03400.rsb/sunxi-rsb-3a3/axp221-pek/input/input0
[ 1.106201] axp20x-adc axp22x-adc: DMA mask not set
[ 1.111766] vcc-3v0: supplied by regulator-dummy
[ 1.116741] vdd-sys: supplied by regulator-dummy
[ 1.121703] vdd-cpu: supplied by regulator-dummy
[ 1.126699] dcdc4: supplied by regulator-dummy
[ 1.131331] vcc-dram: supplied by regulator-dummy
[ 1.136344] vcc-lcd: supplied by vcc-3v0
[ 1.140440] vdd-cpus: supplied by vcc-dram
[ 1.144842] vcc-io: supplied by regulator-dummy
[ 1.149665] vdd-dll: supplied by regulator-dummy
[ 1.154568] avcc: supplied by regulator-dummy
[ 1.159328] eldo1: supplied by vcc-3v0
[ 1.163327] eldo2: supplied by vcc-3v0
[ 1.167310] eldo3: supplied by vcc-3v0
[ 1.171207] vcc-wifi0: Bringing 700000uV into 3300000-3300000uV
[ 1.177225] vcc-wifi0: supplied by regulator-dummy
[ 1.182335] vcc-wifi1: Bringing 700000uV into 3300000-3300000uV
[ 1.188345] vcc-wifi1: supplied by regulator-dummy
[ 1.193532] dldo3: supplied by regulator-dummy
[ 1.198268] dldo4: supplied by regulator-dummy
[ 1.202824] vcc-rtc: supplied by regulator-dummy
[ 1.207817] ldo_io0: supplied by regulator-dummy
[ 1.212658] ldo_io1: supplied by regulator-dummy
[ 1.217553] usb0-vbus: supplied by regulator-dummy
[ 1.222918] axp20x-ac-power-supply axp20x-ac-power-supply: DMA mask not set
[ 1.231521] axp20x-usb-power-supply axp20x-usb-power-supply: DMA mask not set
[ 1.239730] axp20x-rsb sunxi-rsb-3a3: AXP20X driver loaded
[ 1.245511] sun8i-a33-pinctrl 1c20800.pinctrl: supply vcc-ph not found, using dummy regulator
[ 1.255424] ehci-platform 1c1a000.usb: EHCI Host Controller
[ 1.261062] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1
[ 1.269432] ehci-platform 1c1a000.usb: irq 35, io mem 0x01c1a000
[ 1.297627] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00
[ 1.304497] hub 1-0:1.0: USB hub found
[ 1.308306] hub 1-0:1.0: 1 port detected
[ 1.313249] ohci-platform 1c1a400.usb: Generic Platform OHCI controller
[ 1.319904] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2
[ 1.327926] ohci-platform 1c1a400.usb: irq 36, io mem 0x01c1a400
[ 1.402286] hub 2-0:1.0: USB hub found
[ 1.406074] hub 2-0:1.0: 1 port detected
[ 1.411055] usb_phy_generic usb_phy_generic.1.auto: supply vcc not found, using dummy regulator
[ 1.420687] musb-hdrc musb-hdrc.2.auto: MUSB HDRC host driver
[ 1.426451] musb-hdrc musb-hdrc.2.auto: new USB bus registered, assigned bus number 3
[ 1.435350] hub 3-0:1.0: USB hub found
[ 1.439160] hub 3-0:1.0: 1 port detected
[ 1.449278] sun8i-a33-pinctrl 1c20800.pinctrl: supply vcc-pf not found, using dummy regulator
[ 1.461544] sunxi-mmc 1c10000.mmc: allocated mmc-pwrseq
[ 1.461712] ALSA device list:
[ 1.469798] No soundcards found.
[ 1.476675] sunxi-mmc 1c0f000.mmc: Got CD GPIO
[ 1.495095] sunxi-mmc 1c10000.mmc: initialized, max. request size: 16384 KB
[ 1.501801] sunxi-mmc 1c11000.mmc: initialized, max. request size: 16384 KB
[ 1.513285] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB
[ 1.520626] Waiting for root device /dev/mmcblk0p1...
[ 1.538171] mmc0: queuing unknown CIS tuple 0x80 (2 bytes)
[ 1.545246] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.553349] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
[ 1.562819] mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
[ 1.571394] random: fast init done
[ 1.574859] mmc2: host does not support reading read-only switch, assuming write-enable
[ 1.583265] mmc0: queuing unknown CIS tuple 0x81 (9 bytes)
[ 1.589182] mmc2: new high speed SDHC card at address aaaa
[ 1.600494] mmcblk2: mmc2:aaaa SB16G 14.8 GiB
[ 1.616008] mmcblk2: p1
[ 1.710991] mmc0: new high speed SDIO card at address 0001
[ 31.848045] vcc-lcd: disabling
EDIT 2: I'm a dumb, the root filesystem isn't being mounted. Have changed to root=/dev/mmcblk2p1 in boot.cmd and now it works.

Automated Testing with Project Piper

We are currently in the process of setting up a CI/CD pipeline for our SCP CF environment based on Project Piper. After a lot of trial & error, we have made significant process, however we are still not able to run our karma tests.
We understood that we need to use the karma-webdriver-launcher, however we are not able to start/connect to Chrome in the sidecar container.
Relevant logs:
[Pipeline] sh
+ cd ./nodejs
+ npm test
> nodejs#1.0.0 test /var/jenkins_home/workspace/CICD_Multibranch_master/nodejs
> karma start ./karma.conf.js
10 07 2019 14:42:53.897:DEBUG [config]: Loading config /var/jenkins_home/workspace/CICD_Multibranch_master/nodejs/karma.conf.js
10 07 2019 14:42:53.906:DEBUG [karma-server]: Final config [{"LOG_DISABLE":"1","LOG_ERROR":"2","LOG_WARN":"3","LOG_INFO":"4","LOG_DEBUG":"5","frameworks":"6","protocol":"7","port":9876,"listenAddress":"8","hostname":"9","httpsServerConfig":"10","basePath":"11","files":"12","browserConsoleLogOptions":"13","customContextFile":null,"customDebugFile":null,"customClientContextFile":null,"exclude":"14","logLevel":"5","colors":false,"autoWatch":false,"autoWatchBatchDelay":250,"restartOnFileChange":false,"usePolling":true,"reporters":"15","singleRun":true,"browsers":"16","captureTimeout":60000,"proxies":"17","proxyValidateSSL":true,"preprocessors":"18","urlRoot":"19","reportSlowerThan":0,"loggers":"20","transports":"21","forceJSONP":false,"plugins":"22","client":"23","defaultClient":"23","browserDisconnectTimeout":2000,"browserDisconnectTolerance":0,"browserNoActivityTimeout":30000,"processKillTimeout":2000,"concurrency":null,"failOnEmptyTestSuite":true,"retryLimit":2,"detached":false,"crossOriginAttribute":true,"browserSocketTimeout":20000,"cmd":"24","configFile":"25","customLaunchers":"26","junitReporter":"27"},"OFF","ERROR","WARN","INFO","DEBUG",["28"],"http:","0.0.0.0","localhost",{},"/var/jenkins_home/workspace/CICD_Multibranch_master/nodejs",["29","30"],{"level":"31","format":"32","terminal":true},["25"],["33"],["34"],{},{},"/",["35"],["36","37"],["38","39","40","41","42"],{"args":"43","useIframe":true,"runInParent":false,"captureConsole":true,"clearContext":true},"start","/var/jenkins_home/workspace/CICD_Multibranch_master/nodejs/karma.conf.js",{"chromeSel":"44"},{"outputFile":"45","suite":"46"},"qunit",{"pattern":"47","served":true,"included":true,"watched":true,"nocache":false,"weight":"48"},{"pattern":"49","served":true,"included":true,"watched":true,"nocache":false,"weight":"50"},"debug","%b %T: %m","junit","chromeSel",{"type":"51","layout":"52"},"polling","websocket","karma-qunit","karma-junit-reporter","karma-chrome-launcher","karma-webdriver-launcher",{"launcher:chromeSel":"53"},[],{"base":"54","config":"55","browserName":"56"},"test-results-karma.xml","","/var/jenkins_home/workspace/CICD_Multibranch_master/nodejs/server.js",[1,0,0,0,0,0],"/var/jenkins_home/workspace/CICD_Multibranch_master/nodejs/tests/sampleTest.spec.js",[1,0,0,0,0,0],"console",{"type":"57","pattern":"58"},["59",null],"WebDriver",{"hostname":"60","port":4444},"chrome","pattern","%d{DATE}:%p [%c]: %m","factory","selenium"]
10 07 2019 14:42:53.907:DEBUG [plugin]: Loading plugin karma-qunit.
10 07 2019 14:42:53.908:DEBUG [plugin]: Loading plugin karma-junit-reporter.
10 07 2019 14:42:53.923:DEBUG [plugin]: Loading plugin karma-chrome-launcher.
10 07 2019 14:42:53.931:DEBUG [plugin]: Loading plugin karma-webdriver-launcher.
10 07 2019 14:42:54.179:DEBUG [plugin]: Loading inlined plugin (defining launcher:chromeSel).
10 07 2019 14:42:54.193:DEBUG [web-server]: Instantiating middleware
10 07 2019 14:42:54.194:DEBUG [reporter]: Trying to load reporter: junit
10 07 2019 14:42:54.195:DEBUG [reporter]: Trying to load color-version of reporter: junit (junit_color)
10 07 2019 14:42:54.195:DEBUG [reporter]: Couldn't load color-version.
10 07 2019 14:42:54.224:INFO [karma-server]: Karma v4.1.0 server started at http://0.0.0.0:9876/
10 07 2019 14:42:54.225:INFO [launcher]: Launching browsers chromeSel with concurrency unlimited
10 07 2019 14:42:54.231:INFO [launcher]: Starting browser chrome via Remote WebDriver
10 07 2019 14:42:54.232:DEBUG [launcher]: null -> BEING_CAPTURED
10 07 2019 14:42:54.232:DEBUG [temp-dir]: Creating temp dir at /tmp/karma-89562642
10 07 2019 14:42:54.235:DEBUG [WebDriver]: WebDriver config: {"hostname":"selenium","port":4444}
10 07 2019 14:42:54.235:DEBUG [WebDriver]: Browser capabilities: {"platform":"ANY","testName":"Karma test","tags":[],"version":"","base":"WebDriver","browserName":"chrome"}
10 07 2019 14:43:54.281:WARN [launcher]: chrome via Remote WebDriver have not captured in 60000 ms, killing.
10 07 2019 14:43:54.286:DEBUG [launcher]: BEING_CAPTURED -> BEING_KILLED
10 07 2019 14:43:54.355:INFO [WebDriver]: Killed Karma test.
10 07 2019 14:43:54.355:DEBUG [launcher]: Process chrome via Remote WebDriver exited with code -1 and signal timeout
10 07 2019 14:43:54.356:DEBUG [temp-dir]: Cleaning temp dir /tmp/karma-89562642
10 07 2019 14:43:54.358:INFO [launcher]: Trying to start chrome via Remote WebDriver again (1/2).
karma.conf.js:
// Karma configuration
module.exports = function(config) {
var webdriverConfig = {
hostname: 'selenium',
port: 4444
}
config.set({
// base path that will be used to resolve all patterns (eg. files, exclude)
basePath: '',
// frameworks to use
// available frameworks: https://npmjs.org/browse/keyword/karma-adapter
frameworks: ['qunit'],
plugins: ['karma-qunit','karma-junit-reporter','karma-chrome-launcher', 'karma-webdriver-launcher'],
// list of files / patterns to load in the browser
files: [
'server.js',
'tests/sampleTest.spec.js'
],
// list of files to exclude
exclude: [
],
// preprocess matching files before serving them to the browser
// available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
preprocessors: {
},
// test results reporter to use
// possible values: 'dots', 'progress'
// available reporters: https://npmjs.org/browse/keyword/karma-reporter
reporters: ['junit'],
// web server port
//port: 9876,
//hostname: localhost,
// enable / disable colors in the output (reporters and logs)
colors: false,
// level of logging
// possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
logLevel: config.LOG_DEBUG,
// enable / disable watching file and executing tests whenever any file changes
autoWatch: false,
customLaunchers: {
'chromeSel': {
base: 'WebDriver',
config: webdriverConfig,
browserName: 'chrome'
}
},
// start these browsers
// available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
browsers: ['chromeSel'],
// Continuous Integration mode
// if true, Karma captures browsers, runs the tests and exits
singleRun: true,
junitReporter: {
outputFile: 'test-results-karma.xml',
suite: ''
}
});
};
Jenkinsfile:
#!groovy
#Library('piper-lib-os') _
node(){
stage('Prepare') {
deleteDir()
checkout scm
setupCommonPipelineEnvironment
}
stage('Build') {
karmaExecuteTests script: this, modules: ['./nodejs'],
installCommand: "npm install karma karma-qunit karma-junit-reporter karma-chrome-launcher qunit karma-webdriver-launcher",
runCommand: 'npm test'
mtaBuild script:this, buildTarget: 'CF', applicationName: 'appLibrary'
}
stage('Deploy to QA') {
testsPublishResults script: this, junit: [updateResults: true, archive: true]
cloudFoundryDeploy(
script: this,
cloudFoundry: [apiEndpoint: 'https://api.cf.eu10.hana.ondemand.com', manifest: 'manifest.yml', org:'xxx', space:'xxx', credentialsId: 'xxx'],
deployTool: 'mtaDeployPlugin'
)
}
}
Thanks a lot,
Nico
To run the karmaExecuteTests step on your Jenkins, you need a Docker deamon installed. I assume this is the case.
In the Docker sidecar pattern the containers can talk to each other using their container names (karma & selenium). So for the browser (config.customLaunchers.chromeSel.config.hostname) you set the hostname correctly to selenium but you also need to set config.hostname to karma.

React native app is stuck at splashscreen

I have one react native app coded with Ignite Red Boilerplate and app sometimes stuck at Launch screen (Splash screen) only. Then I go back to previous commit and start the app again, and it starts working as expected.
To help you to find out the solution:
I am using this splash screen module : React native splash screen
Ignite red comes with one Login Saga and I have added another signup saga, and it was working fine till the time I actual uninstall the app and reinstall it, and then when App get installed, it never pass the splash screen.
I am not seeing any log any where, tried to run it in Xcode as well but no debug log, how ever I can see following things in Simulator system log and I am pasting some things here. Hope some body can help me to decode it.
Feb 16 09:46:11 MAC009s-Mac-mini NyteVibe[1709]: Running application NyteVibe ({
initialProps = {
};
rootTag = 1;
})
Feb 16 09:46:11 MAC009s-Mac-mini NyteVibe[1709]: Running application "NyteVibe" with appParams: {"rootTag":1,"initialProps":{}}. __DEV__ === true, development-level warning are ON, performance optimizations are OFF
Feb 16 09:46:12 MAC009s-Mac-mini NyteVibe[1709]: undefined is not an object (evaluating 'el.props.component')
Feb 16 09:46:12 MAC009s-Mac-mini NyteVibe[1709]: Unhandled JS Exception: undefined is not an object (evaluating 'el.props.component')
Feb 16 09:46:12 MAC009s-Mac-mini NyteVibe[1709]: action # 09:46:12.030 STARTUP
Feb 16 09:46:12 MAC009s-Mac-mini NyteVibe[1709]: '%c prev state', 'color: #9E9E9E; font-weight: bold', { temperature: { temperature: null, fetching: null, error: null, city: null },
login: { user: null, error: null, fetching: false },
Feb 16 09:46:12 MAC009s-Mac-mini NyteVibe[1709]: —— log end ——
Feb 16 09:46:12 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 7 Connection has no connected handler
Feb 16 09:46:13 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 8 Connection has no connected handler
Feb 16 09:46:14 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 9 Connection has no connected handler
Feb 16 09:46:16 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 10 Connection has no connected handler
Feb 16 09:46:16 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 11 Connection has no connected handler
Feb 16 09:46:18 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 12 Connection has no connected handler
Feb 16 09:46:20 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 13 Connection has no connected handler
Feb 16 09:46:21 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 14 Connection has no connected handler
Feb 16 09:46:22 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 15 Connection has no connected handler
Feb 16 09:46:24 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 16 Connection has no connected handler
Feb 16 09:46:26 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 17 Connection has no connected handler
Feb 16 09:46:26 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 18 Connection has no connected handler
Feb 16 09:46:28 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 19 Connection has no connected handler
Feb 16 09:46:30 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 20 Connection has no connected handler
Feb 16 09:46:31 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 21 Connection has no connected handler
Feb 16 09:46:32 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 22 Connection has no connected handler
Feb 16 09:46:34 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 23 Connection has no connected handler
Feb 16 09:46:36 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 24 Connection has no connected handler
Feb 16 09:46:36 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 25 Connection has no connected handler
Feb 16 09:46:38 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 26 Connection has no connected handler
Feb 16 09:46:40 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 27 Connection has no connected handler
Feb 16 09:46:41 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 28 Connection has no connected handler
Feb 16 09:46:42 MAC009s-Mac-mini NyteVibe[1709]: [] __nw_connection_get_connected_socket_block_invoke 29 Connection has no connected handler
As you can see in system log, First 6 entries are my start up actions that are getting fired perfectly. And then this no connected handler.
You have an exception:
undefined is not an object (evaluating 'el.props.component')
Search your project for el.props.component - it's going to be a component which is mounted during start-up more than likely. Either that or you're misusing a 3rd-party component which has that code.

Debian Jessie not working hot plug with usb modem sierra 802

When I connect modem befour PC start all works fine. But when connect to working PC have bug.
Have no use any drivers from other place all work on default debian jessie repositories.
Here dmesg:
171.342776] usbcore: registered new interface driver usb-storage
[ 171.528837] usb 2-5: USB disconnect, device number 2
[ 171.998784] usb 2-5: new high-speed USB device number 3 using ehci-pci
[ 172.131651] usb 2-5: New USB device found, idVendor=1199, idProduct=0029
[ 172.131658] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 172.131664] usb 2-5: Product: Sierra Wireless Tethered Hotspot
[ 172.131668] usb 2-5: Manufacturer: Linux 2.6.28.10-arm1 with pxa3xx_u2d
[ 172.185784] usbcore: registered new interface driver usbserial
[ 172.185822] usbcore: registered new interface driver usbserial_generic
[ 172.185851] usbserial: USB Serial support registered for generic
[ 172.210624] usbcore: registered new interface driver sierra
[ 172.210668] usbserial: USB Serial support registered for Sierra USB modem
[ 172.210734] sierra 2-5:1.0: Sierra USB modem converter detected
[ 172.211174] usb 2-5: Sierra USB modem converter now attached to ttyUSB0
[ 172.211984] sierra 2-5:1.1: Sierra USB modem converter detected
[ 172.212400] usb 2-5: Sierra USB modem converter now attached to ttyUSB1
[ 172.277188] usbcore: registered new interface driver cdc_ether
[ 172.285339] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.285346] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.285350] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.285354] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.285827] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.285831] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.285835] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.285838] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286198] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286202] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286205] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286208] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286601] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286608] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286612] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286615] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286947] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286953] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286958] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.286963] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.287325] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.287333] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.287338] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
[ 172.287343] sierra ttyUSB0: sierra_submit_rx_urbs: submit urb failed: -8
Have found this article:
In the good sequence, cdc_ether is loaded first and lays claim to the
device. The new eth1 interface is configured and all is well. After
doing some research, I decided to give something a go. What if we just
disabled the sierra driver? It seemed like this latest Sierra Wireless
device didn’t really need that driver as it could communicate via USB
CDC. What could it hurt? Nothing, I figured, so I opened up
/etc/modeprobe.d/blacklist.conf (don’t forget to invoke vi with sudo!)
and went to work. Here’s what I added at the bottom.
# added 2012-12-04 - prevent sierra USB driver from loading
blacklist sierra

Splunk prop Config issue

I currently writing prop configure to validate my event
Events
Feb 03 13:22:23 Jessica-Ubuntu kernel: [ 7098.424722] usb 1-1: Manufacturer: SanDisk Feb 3 13:22:23 Jessica-Ubuntu kernel: [ 7098.424725] usb 1-1: SerialNumber: 200522427013E6812147 Feb 4 22:11:46 Jessica-Ubuntu kernel: [ 2.710593] usb 2-2.1: Product: Virtual Bluetooth Adapter Feb 4 22:11:46 Jessica-Ubuntu kernel: [ 2.710597] usb 2-2.1: SerialNumber: 000650268328
Prop.Config Settings
[source::linuxusb]
SHOULD_LINEMERGE = true
BREAK_ONLY_BEFORE = Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec
EXTRACT-date = (?i) .*? (?P<date>\w+\s+\d+\s+\d+:\d+:\d+)\s+\w+
EXTRACT-description = (?i) Product: (?P<description>.+?)\s+\w+\s+\d+
EXTRACT-device_mfg = (?i) Manufacturer: (?P<device_mfg>[^ ]+)
EXTRACT-serial_number = (?i) SerialNumber: (?P<serial_number>.+)
Result for SerialNumber
200522427013E6812147 Feb 4 22:11:46 Jessica-Ubuntu kernel: [ 2.710593] usb 2-2.1: Product: Virtual Bluetooth Adapter Feb 4 22:11:46 Jessica-Ubuntu kernel: [ 2.710597] usb 2-2.1: SerialNumber: 000650268328`
I only wan 200522427013E6812147. How do i grab this data only. Please help
Assuming the events provided are 4 separate events (looking at the timestamps):
Feb 03 13:22:23 Jessica-Ubuntu kernel: [ 7098.424722] usb 1-1: Manufacturer: SanDisk
Feb 3 13:22:23 Jessica-Ubuntu kernel: [ 7098.424725] usb 1-1: SerialNumber: 200522427013E6812147
Feb 4 22:11:46 Jessica-Ubuntu kernel: [ 2.710593] usb 2-2.1: Product: Virtual Bluetooth Adapter
Feb 4 22:11:46 Jessica-Ubuntu kernel: [ 2.710597] usb 2-2.1: SerialNumber: 000650268328
Edit EXTRACT-serial_number, changing it to:
EXTRACT-serial_number = (?i) SerialNumber: (?P<serial_number>[^ ]+)
Also, if Splunk does not recognize the above 4 events (based on timestamp) as 4 separate events, try changing SHOULD_LINEMENRGE to false.