Buildroot - Hang at Starting Kernel - embedded
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.
Related
How to properly use eglfs on Beaglebone Black?
Project description I am using Yocto to build my embedded Linux for Beaglebone Black. Embedded Linux will be used to host my Qt5 graphicall application. Embedded Linux image is build for MACHINE defined in poky/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf and not for the one from the repository meta-ti (this one gave me problems). In the embedded Linux image that I am building I already managed to add (a) Qt5 libraries that my application needs to compile with bitbake and (b) my Qt5 application which sucessfully compiles with bitbake. Qt5 libraries were appended to the image like this: IMAGE_INSTALL += "qtbase qwt-qt5" And my Qt application was appended like this: IMAGE_INSTALL += "application" So libraries are installed through recipes qtbase and qwt-qt5 while my application was installed through recipe application which I wrote myself. I can post a list of files that each recipe installs on the target's root file system: ┌───┐ │ $ │ ziga > ziga--hypervisor > build--beaglbone_black_c2 └─┬─┘ /dev/pts/1 └─> oe-pkgdata-util list-pkg-files qtbase qwt-qt5 application application: /usr/bin/executable qtbase: /usr/lib/libQt5Concurrent.so.5 /usr/lib/libQt5Concurrent.so.5.14 /usr/lib/libQt5Concurrent.so.5.14.2 /usr/lib/libQt5Core.so.5 /usr/lib/libQt5Core.so.5.14 /usr/lib/libQt5Core.so.5.14.2 /usr/lib/libQt5DBus.so.5 /usr/lib/libQt5DBus.so.5.14 /usr/lib/libQt5DBus.so.5.14.2 /usr/lib/libQt5Gui.so.5 /usr/lib/libQt5Gui.so.5.14 /usr/lib/libQt5Gui.so.5.14.2 /usr/lib/libQt5Network.so.5 /usr/lib/libQt5Gui.so.5.14 /usr/lib/libQt5Gui.so.5.14.2 /usr/lib/libQt5Network.so.5 /usr/lib/libQt5Network.so.5.14 /usr/lib/libQt5Network.so.5.14.2 /usr/lib/libQt5OpenGL.so.5 /usr/lib/libQt5OpenGL.so.5.14 /usr/lib/libQt5OpenGL.so.5.14.2 /usr/lib/libQt5PrintSupport.so.5 /usr/lib/libQt5PrintSupport.so.5.14 /usr/lib/libQt5PrintSupport.so.5.14.2 /usr/lib/libQt5Sql.so.5 /usr/lib/libQt5Sql.so.5.14 /usr/lib/libQt5Sql.so.5.14.2 /usr/lib/libQt5Test.so.5 /usr/lib/libQt5Test.so.5.14 /usr/lib/libQt5Test.so.5.14.2 /usr/lib/libQt5Widgets.so.5 /usr/lib/libQt5Widgets.so.5.14 /usr/lib/libQt5Widgets.so.5.14.2 /usr/lib/libQt5XcbQpa.so.5 /usr/lib/libQt5XcbQpa.so.5.14 /usr/lib/libQt5XcbQpa.so.5.14.2 /usr/lib/libQt5Xml.so.5 /usr/lib/libQt5Xml.so.5.14 /usr/lib/libQt5Xml.so.5.14.2 qwt-qt5: /usr/lib/libqwt.so.6 /usr/lib/libqwt.so.6.1 /usr/lib/libqwt.so.6.1.4 Application can't display graphics Now I login to the target and run my application which can not display the graphics: root#beaglebone-yocto:~# executable 2020/09/20 10:44:26.560: Warning: Could not connect to display 2020/09/20 10:44:26.581: Info: Could not load the Qt platform plugin "xcb" in "" even though it was found. 2020/09/20 10:44:26.581: Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix the problem. Available platform plugins are: minimal, offscreen, vnc, xcb. Aborted It looks like I have to somehow configure "Qt Platform Abstraction" (QPA) which is the platform abstraction layer for Qt5 with a lot of plugins (source) that also include a lot of platforms. My application only uses a single window so I could probably go with qeglfs or qlinuxfb. But because Beaglebone Black integrates Imagination's GPU PowerVR SGX530 which supports OpenGL|ES 2.0 (source) and this is why I want to go with qeglfs platform. Note however that currently qeglfs platform was not listed in the above error report: Available platform plugins are: minimal, offscreen, vnc, xcb. I managed to install the qeglfs platform by creating a qtbase_%.bbappend file with this content: PACKAGECONFIG:append = " eglfs gles2" Note that this activates qtbase recipe's lines: PACKAGECONFIG[eglfs] = "-eglfs,-noeglfs,drm" PACKAGECONFIG[gles2] = "-opengl es2,,virtual/libgles2 virtual/egl" These lines make sure that compilation includes eglfs as well as OpenGL|ES i.e. gles2. I chose to also include gles2 after reading / watching this (source, source): So I asumed that eglfs also needs gles2. Now eglfs is installed and is listed when I try to execute my application in the same way as before: root#beaglebone-yocto:~# executable 2020/09/20 10:44:26.560: Warning: Could not connect to display 2020/09/20 10:44:26.581: Info: Could not load the Qt platform plugin "xcb" in "" even though it was found. 2020/09/20 10:44:26.581: Fatal: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix the problem. Available platform plugins are: eglfs, minimal, offscreen, vnc, xcb. Aborted But when I try to use eglfs I get errors: root#beaglebone-yocto:~# env QT_QPA_PLATFORM=eglfs executable 2020/09/20 11:01:17.525: Warning: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' error: XDG_RUNTIME_DIR not set in the environment error: XDG_RUNTIME_DIR not set in the environment error: XDG_RUNTIME_DIR not set in the environment 2020/09/20 11:01:17.533: Fatal: Could not initialize egl display Aborted All the errors except for the last one can be fixed by adding some enviromental variables like this: root#beaglebone-yocto:~# env QT_QPA_PLATFORM=eglfs XDG_RUNTIME_DIR=/tmp/runtime-root executable 2020/09/20 11:01:17.533: Fatal: Could not initialize egl display Aborted But as you can see the last error remains and I don't know how to fix it. Debug info reveals nothing I tried exporting some enviromental variables to make debug more verbose and then I ran application again: root#beaglebone-yocto:~# export QT_LOGGING_RULES=true root#beaglebone-yocto:~# export QSG_INFO=1 root#beaglebone-yocto:~# export QT_QPA_EGLFS_DEBUG=1 root#beaglebone-yocto:~# export QT_DEBUG_PLUGINS=1 root#beaglebone-yocto:~# export QT_QPA_PLATFORM=eglfs root#beaglebone-yocto:~# export QT_QPA_EGLFS_INTEGRATION=none root#beaglebone-yocto:~# export XDG_RUNTIME_DIR=/tmp/runtime-root root#beaglebone-yocto:~# executable 2022/02/17 20:54:28.448: Debug: QFactoryLoader::QFactoryLoader() checking directory path "/usr/lib/plugins/platforms" ... 2022/02/17 20:54:28.450: Debug: QFactoryLoader::QFactoryLoader() looking at "/usr/lib/plugins/platforms/libqeglfs.so" 2022/02/17 20:54:28.451: Warning: Found metadata in lib /usr/lib/plugins/platforms/libqeglfs.so, metadata= { "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3", "MetaData": { "Keys": [ "eglfs" ] }, "archreq": 0, "className": "QEglFSIntegrationPlugin", "debug": false, "version": 331264 } 2022/02/17 20:54:28.451: Debug: Got keys from plugin meta data ("eglfs") 2022/02/17 20:54:28.451: Debug: QFactoryLoader::QFactoryLoader() looking at "/usr/lib/plugins/platforms/libqlinuxfb.so" 2022/02/17 20:54:28.452: Warning: Found metadata in lib /usr/lib/plugins/platforms/libqlinuxfb.so, metadata= { "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3", "MetaData": { "Keys": [ "linuxfb" ] }, "archreq": 0, "className": "QLinuxFbIntegrationPlugin", "debug": false, "version": 331264 } 2022/02/17 20:54:28.453: Debug: Got keys from plugin meta data ("linuxfb") 2022/02/17 20:54:28.453: Debug: QFactoryLoader::QFactoryLoader() looking at "/usr/lib/plugins/platforms/libqminimal.so" 2022/02/17 20:54:28.454: Warning: Found metadata in lib /usr/lib/plugins/platforms/libqminimal.so, metadata= { "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3", "MetaData": { "Keys": [ "minimal" ] }, "archreq": 0, "className": "QMinimalIntegrationPlugin", "debug": false, "version": 331264 } 2022/02/17 20:54:28.454: Debug: Got keys from plugin meta data ("minimal") 2022/02/17 20:54:28.454: Debug: QFactoryLoader::QFactoryLoader() looking at "/usr/lib/plugins/platforms/libqminimalegl.so" 2022/02/17 20:54:28.455: Warning: Found metadata in lib /usr/lib/plugins/platforms/libqminimalegl.so, metadata= { "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3", "MetaData": { "Keys": [ "minimalegl" ] }, "archreq": 0, "className": "QMinimalEglIntegrationPlugin", "debug": false, "version": 331264 } 2022/02/17 20:54:28.456: Debug: Got keys from plugin meta data ("minimalegl") 2022/02/17 20:54:28.456: Debug: QFactoryLoader::QFactoryLoader() looking at "/usr/lib/plugins/platforms/libqoffscreen.so" 2022/02/17 20:54:28.457: Warning: Found metadata in lib /usr/lib/plugins/platforms/libqoffscreen.so, metadata= { "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3", "MetaData": { "Keys": [ "offscreen" ] }, "archreq": 0, "className": "QOffscreenIntegrationPlugin", "debug": false, "version": 331264 } 2022/02/17 20:54:28.457: Debug: Got keys from plugin meta data ("offscreen") 2022/02/17 20:54:28.457: Debug: QFactoryLoader::QFactoryLoader() looking at "/usr/lib/plugins/platforms/libqvnc.so" 2022/02/17 20:54:28.458: Warning: Found metadata in lib /usr/lib/plugins/platforms/libqvnc.so, metadata= { "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3", "MetaData": { "Keys": [ "vnc" ] }, "archreq": 0, "className": "QVncIntegrationPlugin", "debug": false, "version": 331264 } 2022/02/17 20:54:28.458: Debug: Got keys from plugin meta data ("vnc") 2022/02/17 20:54:28.459: Debug: QFactoryLoader::QFactoryLoader() looking at "/usr/lib/plugins/platforms/libqxcb.so" 2022/02/17 20:54:28.459: Warning: Found metadata in lib /usr/lib/plugins/platforms/libqxcb.so, metadata= { "IID": "org.qt-project.Qt.QPA.QPlatformIntegrationFactoryInterface.5.3", "MetaData": { "Keys": [ "xcb" ] }, "archreq": 0, "className": "QXcbIntegrationPlugin", "debug": false, "version": 331264 } 2022/02/17 20:54:28.460: Debug: Got keys from plugin meta data ("xcb") 2022/02/17 20:54:28.460: Debug: QFactoryLoader::QFactoryLoader() checking directory path "/usr/bin/platforms" ... 2022/02/17 20:54:28.512: Debug: loaded library "/usr/lib/plugins/platforms/libqeglfs.so" 2022/02/17 20:54:28.513: Debug: QFactoryLoader::QFactoryLoader() checking directory path "/usr/lib/plugins/egldeviceintegrations" ... 2022/02/17 20:54:28.514: Debug: QFactoryLoader::QFactoryLoader() looking at "/usr/lib/plugins/egldeviceintegrations/libqeglfs-emu-integration.so" 2022/02/17 20:54:28.515: Warning: Found metadata in lib /usr/lib/plugins/egldeviceintegrations/libqeglfs-emu-integration.so, metadata= { "IID": "org.qt-project.qt.qpa.egl.QEglFSDeviceIntegrationFactoryInterface.5.5", "MetaData": { "Keys": [ "eglfs_emu" ] }, "archreq": 0, "className": "QEglFSEmulatorIntegrationPlugin", "debug": false, "version": 331264 } 2022/02/17 20:54:28.516: Debug: Got keys from plugin meta data ("eglfs_emu") 2022/02/17 20:54:28.516: Debug: QFactoryLoader::QFactoryLoader() looking at "/usr/lib/plugins/egldeviceintegrations/libqeglfs-x11-integration.so" 2022/02/17 20:54:28.517: Warning: Found metadata in lib /usr/lib/plugins/egldeviceintegrations/libqeglfs-x11-integration.so, metadata= { "IID": "org.qt-project.qt.qpa.egl.QEglFSDeviceIntegrationFactoryInterface.5.5", "MetaData": { "Keys": [ "eglfs_x11" ] }, "archreq": 0, "className": "QEglFSX11IntegrationPlugin", "debug": false, "version": 331264 } 2022/02/17 20:54:28.517: Debug: Got keys from plugin meta data ("eglfs_x11") 2022/02/17 20:54:28.517: Debug: QFactoryLoader::QFactoryLoader() checking directory path "/usr/bin/egldeviceintegrations" ... 2022/02/17 20:54:28.543: Fatal: Could not initialize egl display Now I get much more data, but not regarding the last error! That one remains unverbose as before. Really useless actually! GPU is discovered by kernel - but not used I also made sure that I added status = "okay" inside the devicetree's GPU device node. This enabled the GPU probing. So now I can see it in dmesg: [ 0.000000] AM335X ES2.1 (sgx neon) I also installed executable kmscube which I could sucessfully execute and it rendered a cube with shaders. But it was slow and top revealed that it used 100% of my CPU! So probably GPU wasn't used in this case! My display controllers & panels I have two connectors on my device - first is HDMI and the second is my embedded panel. I installed modetest DRM & KVM utility which shows, how display controllers and panels are set up: trying to open device 'i915'...failed trying to open device 'amdgpu'...failed trying to open device 'radeon'...failed trying to open device 'nouveau'...failed trying to open device 'vmwgfx'...failed trying to open device 'omapdrm'...failed trying to open device 'exynos'...failed trying to open device 'tilcdc'...done Encoders: id crtc type possible crtcs possible clones 33 32 LVDS 0x00000001 0x00000001 35 0 TMDS 0x00000001 0x00000002 Connectors: id encoder status name size (mm) modes encoders 34 33 connected LVDS-1 0x0 1 33 modes: index name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot) #0 800x480 34.89 800 840 888 928 480 493 496 525 17000 flags: nhsync, nvsync; type: preferred, driver props: 1 EDID: flags: immutable blob blobs: value: 2 DPMS: flags: enum enums: On=0 Standby=1 Suspend=2 Off=3 value: 0 5 link-status: flags: enum enums: Good=0 Bad=1 value: 0 6 non-desktop: flags: immutable range values: 0 1 value: 0 4 TILE: flags: immutable blob blobs: value: 20 CRTC_ID: flags: object value: 32 36 0 disconnected HDMI-A-1 0x0 0 35 props: 1 EDID: flags: immutable blob blobs: value: 2 DPMS: flags: enum enums: On=0 Standby=1 Suspend=2 Off=3 value: 0 5 link-status: flags: enum enums: Good=0 Bad=1 value: 0 6 non-desktop: flags: immutable range values: 0 1 value: 0 4 TILE: flags: immutable blob blobs: value: 20 CRTC_ID: flags: object value: 0 CRTCs: id fb pos size 32 37 (0,0) (800x480) #0 800x480 34.89 800 840 888 928 480 493 496 525 17000 flags: nhsync, nvsync; type: preferred, driver props: 22 ACTIVE: flags: range values: 0 1 value: 1 23 MODE_ID: flags: blob blobs: value: 68420000200348037803a0030000e001 ed01f0010d020000230000000a000000 48000000383030783438300000000000 00000000000000000000000000000000 00000000 19 OUT_FENCE_PTR: flags: range values: 0 18446744073709551615 value: 0 24 VRR_ENABLED: flags: range values: 0 1 value: 0 Planes: id crtc fb CRTC x,y x,y gamma size possible crtcs 31 32 37 0,0 0,0 0 0x00000001 formats: BG16 RG24 XR24 props: 8 type: flags: immutable enum enums: Overlay=0 Primary=1 Cursor=2 value: 1 17 FB_ID: flags: object value: 37 18 IN_FENCE_FD: flags: signed range values: -1 2147483647 value: -1 20 CRTC_ID: flags: object value: 32 13 CRTC_X: flags: signed range values: -2147483648 2147483647 value: 0 14 CRTC_Y: flags: signed range values: -2147483648 2147483647 value: 0 15 CRTC_W: flags: range values: 0 2147483647 value: 800 16 CRTC_H: flags: range values: 0 2147483647 value: 480 9 SRC_X: flags: range values: 0 4294967295 value: 0 10 SRC_Y: flags: range values: 0 4294967295 value: 0 11 SRC_W: flags: range values: 0 4294967295 value: 52428800 12 SRC_H: flags: range values: 0 4294967295 value: 31457280 Frame buffers: id size pitch Here everything looks correct and in general my displays are working fine. So this probably isn't root of my problem.
This looks like a similar issue on the Beagleboard forum. The dev was able to fix it doing this: "I updated the kernel using these options: ./update_kernel.sh --ti-channel --lts-4_14 --sgx I had to install an additional package: apt install libdrm-dev I had to do a custom GBM library install, outlined here 9. Seems not everything was set up correctly as part of the image." Source
PCIe Problem -- Why pciehp gives contradictory log info
I am running fio jobs on my NVMe SSD and hotplug it then. The platform is hot-pluggable and the system is Centos 7.0.Several seconds after my plug-out, the system encounters a crash and gives these print info: ================ [ 1026.468414] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [ 1026.468422] pciehp 0000:5d:02.0:pcie04: Card present on Slot(6-1) [ 1026.468432] pciehp 0000:5d:02.0:pcie04: slot(6-1): Link Down event [ 1026.468451] pciehp 0000:5d:02.0:pcie04: Link Down event queued on slot(6-1): currently getting powered on [ 1026.468457] pciehp 0000:5d:02.0:pcie04: Already enabled on slot(7-1) [ 1026.468705] {1}[Hardware Error]: event severity: fatal [ 1026.468744] {1}[Hardware Error]: Error 0, type: fatal [ 1026.468782] {1}[Hardware Error]: section_type: PCIe error [ 1026.468825] {1}[Hardware Error]: port_type: 0, PCIe end point [ 1026.468867] {1}[Hardware Error]: version: 3.0 [ 1026.468915] {1}[Hardware Error]: command: 0x0102, status: 0x4010 [ 1026.468961] {1}[Hardware Error]: device_id: 0000:00:00.0 [ 1026.469901] {1}[Hardware Error]: slot: 0 [ 1026.469032] {1}[Hardware Error]: secondary_bus: 0x00 [ 1026.469070] {1}[Hardware Error]: vendor_id: 0x1ded, device_id: 0x3010 [ 1026.469117] {1}[Hardware Error]: class_code: 008001 [ 1026.469155] Kernel panic - not syncing: Fatal hardware error! ================ The possible root cause for system crash is that the contradictory event pair that "card present" and "link down" have messed up the system logic. So what confuses me is that pciehp reports both "card present" and "link down" at the same time. As my experience, "card present" often comes with "link up" and "link down" normally goes by "card not present". Could anybody give me some clues about how this strange situation happens? Or which bit in PCIe register trigger "card present" event and "link down" event?
Rabbitmqctl command throws error
I am trying to create a 3 node cluster on RabbitMQ. I have the first node up and running. When I issue join cluster command from node 2, it is throwing an error that node is down. rabbitmqctl join_cluster rabbit#hostname02 I am getting the following error: Status of node rabbit#hostname02 ... Error: unable to connect to node rabbit#hostname02: nodedown DIAGNOSTICS =========== attempted to contact: [rabbit#hostname02] rabbit#hostname02: * connected to epmd (port 4369) on hostname02 * epmd reports: node 'rabbit' not running at all no other nodes on hostname02 * suggestion: start the node current node details: - node name: 'rabbitmq-cli-30#hostname02' - home dir: /var/lib/rabbitmq - cookie hash: bygafwoj/ISgb3yKej1pEg== This is my config file. [ {rabbit, [ {cluster_nodes, {[rabbit#hostname01, rabbitmq#hostname02, rabbit#hostname03], disc}}, {cluster_partition_handling, ignore}, {tcp_listen_options, [binary, {packet, raw}, {reuseaddr, true}, {backlog, 128}, {nodelay, true}, {exit_on_close, false}] }, {default_user, <<"guest">>}, {default_pass, <<"guest">>}, {log_levels, [{autocluster, debug}, {connection, info}]} ]}, {kernel, [ ]}, {rabbitmq_management, [ {listener, [ {port, 15672} ]} ]} ]. % EOF I have updated the /etc/hosts file with the details of all 3 nodes on all the 3 servers. I am not sure where I am getting this wrong.
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.