Ble.0 Adapter bremst ganzen IObroker in 2 Min.
-
@arnold Keine Screenshots!
-
pi@raspberrypi4-iob:~ $ dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.4.51-v7l+ (dom@buildbot) (gcc version 4.9.3 (cros stool-NG crosstool-ng-1.22.0-88-g8460611)) #1327 SMP Thu Jul 23 11:04:39 BST 202 0 [ 0.000000] CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.1 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] Reserved memory: created CMA memory pool at 0x000000001ec00000, s ize 256 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id share d-dma-pool [ 0.000000] On node 0 totalpages: 1012736 [ 0.000000] DMA zone: 2304 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 196608 pages, LIFO batch:63 [ 0.000000] HighMem zone: 816128 pages, LIFO batch:63 [ 0.000000] percpu: Embedded 20 pages/cpu s49856 r8192 d23872 u81920 [ 0.000000] pcpu-alloc: s49856 r8192 d23872 u81920 alloc=20*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1010432 [ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835 .enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 smsc95xx.macaddr=DC:A6:32:40:6D:89 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0 x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=ea7d04d6-02 rootfstyp e=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-s erial-consoles [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, li near) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] software IO TLB: mapped [mem 0x17cc0000-0x1bcc0000] (64MB) [ 0.000000] Memory: 3655620K/4050944K available (10240K kernel code, 725K rwd ata, 2740K rodata, 2048K init, 853K bss, 133180K reserved, 262144K cma-reserved, 3264512K highmem) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] ftrace: allocating 30051 entries in 59 pages [ 0.000000] rcu: Hierarchical RCU implementation. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jif fies. [ 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+0x340/0x518 wit h crng_init=0 [ 0.000008] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2 147483647500ns [ 0.000024] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_ idle_ns: 1911260446275 ns [ 0.000099] bcm2835: system timer (irq = 17) [ 0.000762] arch_timer: cp15 timer(s) running at 54.00MHz (phys). [ 0.000778] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns [ 0.000795] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 43980 46511102ns [ 0.000807] Switching to timer-based delay loop, resolution 18ns [ 0.001044] Console: colour dummy device 80x30 [ 0.001076] printk: console [tty1] enabled [ 0.001124] Calibrating delay loop (skipped), value calculated using timer fr equency.. 108.00 BogoMIPS (lpj=540000) [ 0.001145] pid_max: default: 32768 minimum: 301 [ 0.001455] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linea r) [ 0.001477] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.002640] Disabling memory control group subsystem [ 0.002738] CPU: Testing write buffer coherency: ok [ 0.003209] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.004031] Setting up static identity map for 0x200000 - 0x20003c [ 0.004218] rcu: Hierarchical SRCU implementation. [ 0.004835] smp: Bringing up secondary CPUs ... [ 0.005967] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.007221] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.008428] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.008574] smp: Brought up 1 node, 4 CPUs [ 0.008590] SMP: Total of 4 processors activated (432.00 BogoMIPS). [ 0.008602] CPU: All CPU(s) started in HYP mode. [ 0.008612] CPU: Virtualization extensions available. [ 0.009368] devtmpfs: initialized [ 0.022441] VFP support v0.3: implementor 41 architecture 3 part 40 variant 8 rev 0 [ 0.022682] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, ma x_idle_ns: 19112604462750000 ns [ 0.022708] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.030379] pinctrl core: initialized pinctrl subsystem [ 0.031451] NET: Registered protocol family 16 [ 0.035139] DMA: preallocated 1024 KiB pool for atomic coherent allocations [ 0.036877] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. [ 0.036890] hw-breakpoint: maximum watchpoint size is 8 bytes. [ 0.037209] Serial: AMBA PL011 UART driver [ 0.040601] bcm2835-mbox fe00b880.mailbox: mailbox enabled [ 0.060836] raspberrypi-firmware soc:firmware: Attached to firmware from 2020 -07-17 10:59, variant start [ 0.070851] raspberrypi-firmware soc:firmware: Firmware hash is 21a15cb094f41 c7506ad65d2cb9b29c550693057 [ 0.124588] bcm2835-dma fe007000.dma: DMA legacy API manager, dmachans=0x1 [ 0.129013] vgaarb: loaded [ 0.129461] SCSI subsystem initialized [ 0.129683] usbcore: registered new interface driver usbfs [ 0.129750] usbcore: registered new interface driver hub [ 0.129863] usbcore: registered new device driver usb [ 0.131496] clocksource: Switched to clocksource arch_sys_counter [ 0.881318] VFS: Disk quotas dquot_6.6.0 [ 0.881415] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 0.881612] FS-Cache: Loaded [ 0.881793] CacheFiles: Loaded [ 0.882584] simple-framebuffer: probe of 0.framebuffer failed with error -12 [ 0.892187] thermal_sys: Registered thermal governor 'step_wise' [ 0.892530] NET: Registered protocol family 2 [ 0.893252] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear) [ 0.893282] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 0.893357] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.893430] TCP: Hash tables configured (established 8192 bind 8192) [ 0.893570] UDP hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.893600] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) [ 0.893840] NET: Registered protocol family 1 [ 0.894519] RPC: Registered named UNIX socket transport module. [ 0.894532] RPC: Registered udp transport module. [ 0.894543] RPC: Registered tcp transport module. [ 0.894555] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.894575] PCI: CLS 0 bytes, default 64 [ 0.896448] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counte rs available [ 0.898544] Initialise system trusted keyrings [ 0.898767] workingset: timestamp_bits=14 max_order=20 bucket_order=6 [ 0.909413] FS-Cache: Netfs 'nfs' registered for caching [ 0.910091] NFS: Registering the id_resolver key type [ 0.910128] Key type id_resolver registered [ 0.910140] Key type id_legacy registered [ 0.910162] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 0.911201] Key type asymmetric registered [ 0.911215] Asymmetric key parser 'x509' registered [ 0.911383] bounce: pool size: 64 pages [ 0.911424] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 2 49) [ 0.911667] io scheduler mq-deadline registered [ 0.911680] io scheduler kyber registered [ 0.915398] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges: [ 0.915421] brcm-pcie fd500000.pcie: No bus range found for /scb/pcie@7d500 000, using [bus 00-ff] [ 0.915485] brcm-pcie fd500000.pcie: MEM 0x0600000000..0x0603ffffff -> 0 x00f8000000 [ 0.915549] brcm-pcie fd500000.pcie: IB MEM 0x0000000000..0x00bfffffff -> 0 x0000000000 [ 0.973615] brcm-pcie fd500000.pcie: link up, 5 GT/s x1 (SSC) [ 0.973917] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00 [ 0.973935] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.973955] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address [0xf8000000-0xfbffffff]) [ 0.974010] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400 [ 0.974247] pci 0000:00:00.0: PME# supported from D0 D3hot [ 0.977572] PCI: bus0: Fast back to back transfers disabled [ 0.977594] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), rec onfiguring [ 0.977856] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330 [ 0.977999] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit] [ 0.978383] pci 0000:01:00.0: PME# supported from D0 D3cold [ 0.981755] PCI: bus1: Fast back to back transfers disabled [ 0.981774] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 0.981811] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff] [ 0.981833] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64 bit] [ 0.981913] pci 0000:00:00.0: PCI bridge to [bus 01] [ 0.981936] pci 0000:00:00.0: bridge window [mem 0x600000000-0x6000fffff] [ 0.982238] pcieport 0000:00:00.0: enabling device (0140 -> 0142) [ 0.982452] pcieport 0000:00:00.0: PME: Signaling with IRQ 55 [ 0.982818] pcieport 0000:00:00.0: AER: enabled with IRQ 55 [ 0.983136] pci 0000:01:00.0: enabling device (0140 -> 0142) [ 0.989946] iproc-rng200 fe104000.rng: hwrng registered [ 0.990261] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000 000(1024 MiB) [ 0.990903] vc-sm: Videocore shared memory driver [ 0.991425] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe2 00000 [ 1.003061] brd: module loaded [ 1.014901] loop: module loaded [ 1.016229] Loading iSCSI transport class v2.0-870. [ 1.018160] libphy: Fixed MDIO Bus: probed [ 1.018725] bcmgenet fd580000.ethernet: failed to get enet clock [ 1.018743] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000 [ 1.018764] bcmgenet fd580000.ethernet: failed to get enet-wol clock [ 1.018784] bcmgenet fd580000.ethernet: failed to get enet-eee clock [ 1.018810] bcmgenet: Skipping UMAC reset [ 1.031535] libphy: bcmgenet MII bus: probed [ 1.121597] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus [ 1.122602] usbcore: registered new interface driver r8152 [ 1.122667] usbcore: registered new interface driver lan78xx [ 1.122725] usbcore: registered new interface driver smsc95xx [ 1.123126] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 1.123158] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus numbe r 1 [ 1.125418] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 qu irks 0x0000001000000890 [ 1.126628] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bc dDevice= 5.04 [ 1.126644] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber= 1 [ 1.126659] usb usb1: Product: xHCI Host Controller [ 1.126673] usb usb1: Manufacturer: Linux 5.4.51-v7l+ xhci-hcd [ 1.126686] usb usb1: SerialNumber: 0000:01:00.0 [ 1.127265] hub 1-0:1.0: USB hub found [ 1.127358] hub 1-0:1.0: 1 port detected [ 1.127899] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 1.127922] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus numbe r 2 [ 1.127945] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed [ 1.128427] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bc dDevice= 5.04 [ 1.128443] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber= 1 [ 1.128458] usb usb2: Product: xHCI Host Controller [ 1.128471] usb usb2: Manufacturer: Linux 5.4.51-v7l+ xhci-hcd [ 1.128485] usb usb2: SerialNumber: 0000:01:00.0 [ 1.129070] hub 2-0:1.0: USB hub found [ 1.129155] hub 2-0:1.0: 4 ports detected [ 1.130559] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [ 1.130828] dwc_otg: FIQ enabled [ 1.130840] dwc_otg: NAK holdoff enabled [ 1.130851] dwc_otg: FIQ split-transaction FSM enabled [ 1.130865] Module dwc_common_port init [ 1.131270] usbcore: registered new interface driver uas [ 1.131382] usbcore: registered new interface driver usb-storage [ 1.131618] mousedev: PS/2 mouse device common for all mice [ 1.133659] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer [ 1.136109] sdhci: Secure Digital Host Controller Interface driver [ 1.136121] sdhci: Copyright(c) Pierre Ossman [ 1.136678] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe [ 1.137195] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.140845] ledtrig-cpu: registered to indicate activity on CPUs [ 1.141147] hidraw: raw HID events driver (C) Jiri Kosina [ 1.141319] usbcore: registered new interface driver usbhid [ 1.141330] usbhid: USB HID core driver [ 1.142375] vchiq: vchiq_init_state: slot_zero = (ptrval) [ 1.144260] [vc_sm_connected_init]: start [ 1.153164] [vc_sm_connected_init]: end - returning 0 [ 1.155164] Initializing XFRM netlink socket [ 1.155200] NET: Registered protocol family 17 [ 1.155308] Key type dns_resolver registered [ 1.155795] Registering SWP/SWPB emulation handler [ 1.156112] registered taskstats version 1 [ 1.156131] Loading compiled-in X.509 certificates [ 1.156615] Key type ._fscrypt registered [ 1.156627] Key type .fscrypt registered [ 1.166818] uart-pl011 fe201000.serial: cts_event_workaround enabled [ 1.166883] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 29, base_baud = 0) is a PL011 rev2 [ 1.172785] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains drive r [ 1.173686] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0 [ 1.173700] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated [ 1.223941] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 1.225582] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.227313] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.230239] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 1.231901] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.239505] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using A DMA [ 1.242497] of_cfs_init [ 1.242621] of_cfs_init: OK [ 1.243792] Waiting for root device PARTUUID=ea7d04d6-02... [ 1.280931] random: fast init done [ 1.302206] mmc1: new high speed SDIO card at address 0001 [ 1.349788] mmc0: new ultra high speed DDR50 SDHC card at address aaaa [ 1.350672] mmcblk0: mmc0:aaaa SB16G 14.8 GiB [ 1.353744] mmcblk0: p1 p2 [ 1.365103] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesyst em [ 1.365117] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [ 1.491572] usb 1-1: new high-speed USB device number 2 using xhci_hcd [ 1.597549] EXT4-fs (mmcblk0p2): recovery complete [ 1.599541] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. O pts: (null) [ 1.599610] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [ 1.600332] devtmpfs: mounted [ 1.608246] Freeing unused kernel memory: 2048K [ 1.608534] Run /sbin/init as init process [ 1.674259] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcd Device= 4.21 [ 1.674277] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 1.674292] usb 1-1: Product: USB2.0 Hub [ 1.676191] hub 1-1:1.0: USB hub found [ 1.676427] hub 1-1:1.0: 4 ports detected [ 2.001578] usb 1-1.3: new full-speed USB device number 3 using xhci_hcd [ 2.033908] systemd[1]: System time before build time, advancing clock. [ 2.145693] NET: Registered protocol family 10 [ 2.146984] Segment Routing with IPv6 [ 2.150395] usb 1-1.3: New USB device found, idVendor=0451, idProduct=16a8, b cdDevice= 0.09 [ 2.150413] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber =3 [ 2.150429] usb 1-1.3: Product: TI CC2531 USB CDC [ 2.150444] usb 1-1.3: Manufacturer: Texas Instruments [ 2.150459] usb 1-1.3: SerialNumber: __0X00124B001936DCEE [ 2.177207] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SEL INUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL + XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybr id) [ 2.177963] systemd[1]: Detected architecture arm. [ 2.237002] systemd[1]: Set hostname to <raspberrypi4-iob>. [ 3.002096] random: systemd: uninitialized urandom read (16 bytes read) [ 3.040022] systemd[1]: Condition check resulted in Journal Audit Socket bein g skipped. [ 3.040182] random: systemd: uninitialized urandom read (16 bytes read) [ 3.040550] systemd[1]: Listening on initctl Compatibility Named Pipe. [ 3.040815] random: systemd: uninitialized urandom read (16 bytes read) [ 3.041342] systemd[1]: Listening on fsck to fsckd communication Socket. [ 3.042062] systemd[1]: Listening on Journal Socket (/dev/log). [ 3.042642] systemd[1]: Listening on Syslog Socket. [ 3.044721] systemd[1]: Created slice User and Session Slice. [ 3.045275] systemd[1]: Listening on udev Kernel Socket. [ 3.197324] i2c /dev entries driver [ 3.649584] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) [ 3.749859] systemd-journald[105]: Received request to flush runtime journal from PID 1 [ 4.324434] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Reg isters at 0xfeb00000 length 0x00010000 [ 4.325292] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised : Registers at 0xfeb10000 length 0x00001000 [ 4.325908] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Reg isters at 0xfeb20000 length 0x00010000 [ 4.326417] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Regis ters at 0xfeb30000 length 0x00010000 [ 4.360601] vc_sm_cma: module is from the staging directory, the quality is u nknown, you have been warned. [ 4.367209] bcm2835_vc_sm_cma_probe: Videocore shared memory driver [ 4.367233] [vc_sm_connected_init]: start [ 4.370193] mc: Linux media interface: v0.10 [ 4.378269] [vc_sm_connected_init]: installed successfully [ 4.406302] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. [ 4.425787] videodev: Linux video capture interface: v2.00 [ 4.430575] bcm2835_audio bcm2835_audio: card created with 8 channels [ 4.475458] bcm2835_mmal_vchiq: module is from the staging directory, the qua lity is unknown, you have been warned. [ 4.486376] bcm2835_v4l2: module is from the staging directory, the quality i s unknown, you have been warned. [ 4.511755] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned. [ 4.526417] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev /video13 [ 4.526935] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /de v/video14 [ 4.527377] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /de v/video15 [ 4.527713] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/ video16 [ 4.527736] bcm2835-isp bcm2835-isp: Register output node 0 with media contro ller [ 4.527757] bcm2835-isp bcm2835-isp: Register capture node 1 with media contr oller [ 4.527776] bcm2835-isp bcm2835-isp: Register capture node 2 with media contr oller [ 4.527795] bcm2835-isp bcm2835-isp: Register capture node 3 with media contr oller [ 4.528002] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp [ 4.535700] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned. [ 4.548353] bcm2835-codec bcm2835-codec: Device registered as /dev/video10 [ 4.548397] bcm2835-codec bcm2835-codec: Loaded V4L2 decode [ 4.557223] bcm2835-codec bcm2835-codec: Device registered as /dev/video11 [ 4.557264] bcm2835-codec bcm2835-codec: Loaded V4L2 encode [ 4.567722] bcm2835-codec bcm2835-codec: Device registered as /dev/video12 [ 4.567766] bcm2835-codec bcm2835-codec: Loaded V4L2 isp [ 4.844037] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0 [ 4.854734] cfg80211: Loading compiled-in X.509 certificates for regulatory d atabase [ 4.921374] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device [ 4.924794] usbcore: registered new interface driver cdc_acm [ 4.924810] cdc_acm: USB Abstract Control Model driver for USB modems and ISD N adapters [ 4.984539] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 4.985104] [drm] No displays found. Consider forcing hotplug if HDMI is atta ched [ 4.985244] vc4-drm gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4]) [ 4.985268] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 4.985280] [drm] No driver support for vblank timestamp query. [ 4.985291] [drm] Setting vblank_disable_immediate to false because get_vblan k_timestamp == NULL [ 4.991103] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 [ 5.059231] brcmfmac: F1 signature read @0x18000000=0x15264345 [ 5.075548] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio f or chip BCM4345/6 [ 5.076334] usbcore: registered new interface driver brcmfmac [ 5.102585] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455 -sdio.raspberrypi,4-model-b.txt failed with error -2 [ 5.340985] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio f or chip BCM4345/6 [ 5.357233] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 2 2020 23:30:41 version 7.45.202 (r724630 CY) FWID 01-72f6ece2 [ 6.965476] uart-pl011 fe201000.serial: no DMA platform data [ 6.983222] random: crng init done [ 6.983239] random: 7 urandom warning(s) missed due to ratelimiting [ 7.193648] 8021q: 802.1Q VLAN Support v1.8 [ 7.451720] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:1 02396k SSFS [ 7.595612] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled [ 7.842770] bcmgenet: Skipping UMAC reset [ 7.844496] bcmgenet fd580000.ethernet: configuring instance for external RGM II [ 7.844688] bcmgenet fd580000.ethernet eth0: Link is Down [ 13.005231] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 13.583627] Bluetooth: Core ver 2.22 [ 13.583671] NET: Registered protocol family 31 [ 13.583676] Bluetooth: HCI device and connection manager initialized [ 13.583690] Bluetooth: HCI socket layer initialized [ 13.583698] Bluetooth: L2CAP socket layer initialized [ 13.583711] Bluetooth: SCO socket layer initialized [ 13.591298] Bluetooth: HCI UART driver ver 2.3 [ 13.591306] Bluetooth: HCI UART protocol H4 registered [ 13.591360] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 13.592605] Bluetooth: HCI UART protocol Broadcom registered [ 13.809347] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 13.809354] Bluetooth: BNEP filters: protocol multicast [ 13.809372] Bluetooth: BNEP socket layer initialized [ 13.898461] Bluetooth: RFCOMM TTY layer initialized [ 13.898481] Bluetooth: RFCOMM socket layer initialized [ 13.898505] Bluetooth: RFCOMM ver 1.11 [ 14.644373] ICMPv6: process `dhcpcd' is using deprecated sysctl (syscall) net .ipv6.neigh.wlan0.retrans_time - use net.ipv6.neigh.wlan0.retrans_time_ms instea d pi@raspberrypi4-iob:~ $ -
[ 1.350672] mmcblk0: mmc0:aaaa SB16G 14.8 GiB [ 1.353744] mmcblk0: p1 p2 [ 1.365103] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesyst em [ 1.365117] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [ 1.491572] usb 1-1: new high-speed USB device number 2 using xhci_hcd [ 1.597549] EXT4-fs (mmcblk0p2): recovery complete [ 1.599541] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. O pts: (null) [ 1.599610] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.Könnte auf eine beschädigte SD-Karte hindeuten. Recovery macht das System eigentlich nur, wenn es zuvor irgendwo klemmt.
Auf meinem System sieht die Passage so aus:
[ 1.307921] mmc1: new high speed SDIO card at address 0001 [ 1.343328] mmc0: new ultra high speed DDR50 SDHC card at address 0001 [ 1.344616] mmcblk0: mmc0:0001 EB1QT 29.8 GiB [ 1.347586] mmcblk0: p1 p2 < p5 p6 p7 > [ 1.371115] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null) [ 1.371200] VFS: Mounted root (ext4 filesystem) readonly on device 179:7. -
kann ich mir Image von der karte machen und auf neu karte daraufspielen .
oder ich übertrage den Fehler ?
das ganze dürfte doch nicht mit dem ble Adapter zu tun haben oder ?
ein gesicherten Image spiele ich gerade auf NEUE Sd . dann dürfte mit neue karte doch anders aussehen -
@arnold Ein Image kopiert auch zerbröselte Dinge auf das Backup.
Ich würde auf der NEUEN Karte auch das System NEU aufsetzen. Und zwar 'zu Fuß', ohne da wieder ein Image draufzubügeln, von dem du nicht weißt ob das i. O. ist. -
@arnold Auf welchem Wert steht eigentlich in der ble-Adapter-Konfig der
RSSI Update-Intervall [ms]:Ich habe da 30000 drin.
-
@arnold Also mit sowas komme ich immer mehr auf "Hardware bzw OS/Treiber Themen"
-
Werde ausprobieren einen fast gleichen image von bekanten auf meinem RPI4 ausprobieren,um Hartware Fehler auszuschließen .
aber wollte noch vorher Meinen Ble.0 Adapter löschen ,mit ganzem Müll /Resten.
- Adapter löschen
- Ordner Löschen /opt/iobroker/node_modules/iobroker .Ble
- Ordner Löschen /opt/iobroker/iobroker-data/ble.admin
und noch was zum löschen ????
-
@arnold
Woher kommt eigentlich diese Obsession mit den Images unbekannter Herkunft? Installier das flugs zu Fuß auf der neuen Karte. Da wieder mit einem Image zu arbeiten ist doch Quark.
Wenn der Adapter deinstalliert wird, dann werden auch die Objekte aus den Instanzen gelöscht. -
@Thomas-Braun ich habe iobroker Komplet neu installiert zu Fuß, und auf den noch "nackten" Iobroker Ble. adapter installiert,( ist sofort auf grün geschaltet und bekommt Daten von xiaomi -Temperatur ) ABER dann bricht das System zusamen so nach ca 1-2 min .
Ble Adapter ausschalten und System läuft stabil.
deswegen oder ich mache was falsch oder Hartware Fehler . Deswegen versuche ich mit einen image oder meine Sd in anderen Rpi 4.wenn ich Adapter lösche dann sind auch Objekte gelöscht aber ich habe noch Leichen Reste in meinem System gefunden
/opt/iobroker/node_modules/iobroker .Ble
/opt/iobroker/iobroker-data/ble.admingibst noch was per Hand zu löschen ???
-
@arnold
Dann hat deine Hardware einen Schuß.
Was steht denn intail -f /var/log/messageswenn das System hustet?
-
@Thomas-Braun said in Ble.0 Adapter bremst ganzen IObroker in 2 Min.:
tail -f /var/log/messages
Habe gerade adapter Ble.0 gelöscht
ohne adapter
tail -f /var/log/messagespi@raspberrypi4-iob:~ $ tail -f /var/log/messages Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.583016] Bluetooth: HCI UART prot ocol H4 registered Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.583052] Bluetooth: HCI UART prot ocol Three-wire (H5) registered Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.583197] Bluetooth: HCI UART prot ocol Broadcom registered Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.863211] Bluetooth: BNEP (Etherne t Emulation) ver 1.3 Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.863218] Bluetooth: BNEP filters: protocol multicast Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.863232] Bluetooth: BNEP socket l ayer initialized Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.992222] Bluetooth: RFCOMM TTY la yer initialized Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.992238] Bluetooth: RFCOMM socket layer initialized Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.992258] Bluetooth: RFCOMM ver 1. 11 Jul 26 16:22:05 raspberrypi4-iob kernel: [ 14.949461] ICMPv6: process `dhcpcd' is using deprecated sysctl (syscall) net.ipv6.neigh.wlan0.retrans_time - use ne t.ipv6.neigh.wlan0.retrans_time_ms instead pi@raspberrypi4-iob:~ $ tail -f /var/log/messages Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.583016] Bluetooth: HCI UART prot ocol H4 registered Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.583052] Bluetooth: HCI UART prot ocol Three-wire (H5) registered Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.583197] Bluetooth: HCI UART prot ocol Broadcom registered Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.863211] Bluetooth: BNEP (Etherne t Emulation) ver 1.3 Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.863218] Bluetooth: BNEP filters: protocol multicast Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.863232] Bluetooth: BNEP socket l ayer initialized Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.992222] Bluetooth: RFCOMM TTY la yer initialized Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.992238] Bluetooth: RFCOMM socket layer initialized Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.992258] Bluetooth: RFCOMM ver 1. 11 Jul 26 16:22:05 raspberrypi4-iob kernel: [ 14.949461] ICMPv6: process `dhcpcd' is using deprecated sysctl (syscall) net.ipv6.neigh.wlan0.retrans_time - use ne t.ipv6.neigh.wlan0.retrans_time_ms instead pi@raspberrypi4-iob:~ $ tail -f /var/log/messages Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.583016] Bluetooth: HCI UART prot ocol H4 registered Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.583052] Bluetooth: HCI UART prot ocol Three-wire (H5) registered Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.583197] Bluetooth: HCI UART prot ocol Broadcom registered Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.863211] Bluetooth: BNEP (Etherne t Emulation) ver 1.3 Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.863218] Bluetooth: BNEP filters: protocol multicast Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.863232] Bluetooth: BNEP socket l ayer initialized Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.992222] Bluetooth: RFCOMM TTY la yer initialized Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.992238] Bluetooth: RFCOMM socket layer initialized Jul 26 16:22:04 raspberrypi4-iob kernel: [ 13.992258] Bluetooth: RFCOMM ver 1. 11 Jul 26 16:22:05 raspberrypi4-iob kernel: [ 14.949461] ICMPv6: proc -
@arnold Interessant ist die Ausgabe wenn das Ding abschmiert.
Und du kannst das durchlaufen lassen. tail schaut kontinuierlich auf neue Einträge in der Datei. -
Moin Zusammen,
ich habe seit 2 Tage genau das gleiche Problem, sobald der ble adapter startet, ist mein System nicht mehr erreichbar.
Bin ich nicht eingeloggt über SSH so komme ich auch nicht mehr zur Passworteingabe mit "ssh pi@..."
Bin ich eingeloggt über SSH so wird es extrem langsam.Die Adminoberfläche lädt sich nen Wolf bzw. zeigt nur die Infos vor dem Start des ble Adapters an (Info Tab und nicht vorher geladene Seiten der Admin Oberfläche bleiben leer). Ein erneutes Laden der Website führt zum endlosen Ladebalken in der Adresszeile.
Ich hatte dieses Problem schonmal vor einem halben Jahr:
Brandneue Installation Iobroker, Entfernung von Objects.json, löschen zigmaliges Neuinstallieren verschiedener Versionen von BLE, hatte nichts gebracht.
Nach verschiedenen Lösungsversuchen hatte damals irgendetwas funktioniert nur weiß ich nicht mehr was..Bis zum sudo apt update und anschließenden upgrade (und anschließenden "iobroker fix") lief alles einwandfrei.
Ich war vorher etwas rückständig was js-controller anging und es war auch nicht die aktuellste node.js drauf. Jetzt ist alles aktuell, aber dafür bin ich wieder bei dem gleichen Punkt:
ble an - dann geht nix mehr.
ble aus - alles läuft toll.RadarAdapter habe ich nicht installiert.
Ich nutze parallel Zigbee (was auch wundbar funktioniert).
Ich benutze das interne Bluetooth.Ich habe bisher versucht:
- (diverse Male) ble deinstallieren, neuinstallieren
- iobroker rebuild ble
- direkt über GitHub installieren
- fixer laufen lassen
- die Tips hier in diesem Beitrag
Was ich im Adapter noch ausprobiert habe:
- die Abfrage habe ich auf 0, 6000, 30000, 60000 ms getestet. - keine Wirkung
- neue Geräte hinzufügen auf false/true. - keine Wirkung
- BT scan auf false/true. - keine Wirkung
Welche Optionen mir noch einfallen:
-
Ich habe mir jetzt einen BT USB Stick bestellt und vielleicht wird das Abhilfe bringen.
-
Als alternative (weil ich es nur für meine Mi-Flora benutze) die Geräte über einen externen ESP32 per MQTT einzubinden. (würde ich gerne vermeiden, da es ja mit den Bordmitteln bisher gut geklappt hat)
Eine (erneute) Neuinstallation sehe ich nicht als sinnvoll - das hatte damals auch keine Abhilfe gebracht und ich bezweifle dass es ein Hardwareproblem ist - es war ja vor einem halben Jahr exact die gleiche Symptomatik.
Vielleicht hat ja der ursprüngliche Ersteller bereits eine Lösung gefunden für das Problem? Oder jemand noch eine Idee das Problem anzugehen?
Zu meinem System:
Raspberry Pi 4 - 4GB
Node.js - 12.20.0
NPM - 6.14.8
JS-Controller - Installiert: 3.1.6Vielen Dank für eure Hilfe.
Grüße! -
AllowNewDevices auch auf false gesetzt?
Wie viele Objekte hast du in der Instanz mittlerweile angesammelt? -
@Thomas-Braun
AllowNewDevices auch auf false gesetzt?Ja (das meinte ich eigentlich mit "neue Geräte false") das hatte leider auch keinen Unterschied gemacht, auch kein reboot danach, leider.
Es waren insgesamt 10 Devices wovon 4 unbekannt waren.
Als es noch lief waren es deutlich mehr, vor allem viel mehr unbekannte/unerkannte. -
@DominikW Falsch eingestellt sind das leicht Zehntausende. Führt dann zum beobachteten Verhalten des Systems.
Die Objekte müssen dann von Hand gelöscht werden. -
@Thomas-Braun wie lösche ich die denn von Hand?
Ich habe wenn ich den Adapter neu installiere 10 Geräte unter Objekte stehen, die er findet.Den Adapter im "node-modules" Ordner hatte ich auch von hand gelöscht gehabt.
Anschließend nochmal neu installiert.Zudem lief es vorher reibungslos mit den weit mehr gefundenen Devices.
-
@DominikW
In den Objekten stehen die drin, wenn die auflaufen. -
@Thomas-Braun du meinst unter ble.0 richtig?
Da stehen wie gesagt nur 10 Stück - 5 miFlora, 1 Fernseher & 4 Unbekannte.Wenn ich dich richtig verstehe sind die Geräte dann auch gelöscht, wenn ich den Adapter vollständig lösche (also die Instanz "ble.0" im iobroker entferne und den Ordner aus dem Modulordner lösche)?
Dann dürfte dies denke ich auch nicht das Problem sein oder sehe ich das falsch.
Ich kann es gerne nochmal installieren und einen Screenshot anfügen wenn dir das weiterhilft.
