[Gelöst] hm-rpc disconnected wieder, legt sogar CCU2 lahm
-
Die Konfiguraionen sehen ok aus.
Das log zeigt nur dass bei jedem Neustart die Datenpunkte wieder neu eingelesen und auch über rega die Klarnamen von der CCU geholt werden.
Letzteres belastet natürlich die ReGa auf der CCU wenn es häufig und lange passiert und kann zum Absturz der CCU führen.
Soll es aber nicht!
Also sollte ggf. Auf der CCU noch etwas im Systemlog zu finden sein.
Meiner Meinung nach liegt dort das Problem.
Gruß
Rainer
-
Guten Tag Rainer,
komme endlich dazu einen Test zu fahren.
Als Vorabinformation, ich habe die XML-API deinstalliert. Zudem habe ich IPV6 bei meinem Windows 10 deaktiviert. Leider hat es nichts gebracht.
Im Spoiler findest du den CCU-Log
CCU frisch gestartet, ioBroker aus.
Weiter unten siehst du, wann ich ioBroker REGA + RPC.1 (Wired per XML-RPC PROTOKOLL) gestartet habe.
Die Zentrale ist direkt knapp 10 minuten schwer beschäftigt und nicht ansprechbar. Erst wenn ich die Instanzen stoppe, dauert es 2-3min, dann erst kann ich drauf zugreifen und die Log Datei downloaden.
! Feb 26 14:45:52 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2016-11-22 12:43:12 CET)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] Booting Linux on physical CPU 0
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] Initializing cgroup subsys cpu
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] Linux version 3.4.11.ccu2 (hudson@entw-build-10) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70) ) #1 PREEMPT Tue Nov 22 13:09:59 CET 2016
! Feb 26 14:45:53 homematic-ccu2 user.warn kernel: [ 0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
! Feb 26 14:45:53 homematic-ccu2 user.warn kernel: [ 0.000000] CPU: VIVT data cache, VIVT instruction cache
! Feb 26 14:45:53 homematic-ccu2 user.warn kernel: [ 0.000000] Machine: eQ-3 HomeMatic CCU2
! Feb 26 14:45:53 homematic-ccu2 user.warn kernel: [ 0.000000] Memory policy: ECC disabled, Data cache writeback
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 0.000000] On node 0 totalpages: 65536
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 0.000000] free_area_init_node: node 0, pgdat c03c42ec, node_mem_map c03f8000
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 0.000000] Normal zone: 512 pages used for memmap
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 0.000000] Normal zone: 0 pages reserved
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 0.000000] Normal zone: 65024 pages, LIFO batch:15
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 0.000000] pcpu-alloc: [0] 0
! Feb 26 14:45:53 homematic-ccu2 user.warn kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] Kernel command line: eQ3Mode=production console=ttyAMA0,115200 ubi.mtd=7 ubi.mtd=6 ro ip=none root=ubi0:root ubi.mtd=7 rootfstype=ubifs noinitrd mtdparts=gpmi-nand:1024k(fcb)ro,1024k(bbt),1024k(bootenv),1536k(boo
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] allocated 524288 bytes of page_cgroup
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] Memory: 256MB = 256MB total
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] Memory: 255276k/255276k available, 6868k reserved, 0K highmem
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] Virtual kernel memory layout:
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] vmalloc : 0xd0800000 - 0xff000000 ( 744 MB)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] .text : 0xc0008000 - 0xc037d000 (3540 kB)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] .init : 0xc037d000 - 0xc039a000 ( 116 kB)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] .data : 0xc039a000 - 0xc03c4a20 ( 171 kB)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.000000] .bss : 0xc03c4a44 - 0xc03f77dc ( 204 kB)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] NR_IRQS:304
! Feb 26 14:45:53 homematic-ccu2 user.err kernel: [ 0.000000] saif0_clk_set_rate: clock is gated
! Feb 26 14:45:53 homematic-ccu2 user.err kernel: [ 0.000000] saif1_clk_set_rate: clock is gated
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] Console: colour dummy device 80x30
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.000000] Calibrating delay loop… 226.09 BogoMIPS (lpj=1130496)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.070000] pid_max: default: 32768 minimum: 301
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.070000] Mount-cache hash table entries: 512
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.070000] Initializing cgroup subsys cpuacct
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.070000] Initializing cgroup subsys memory
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.070000] Initializing cgroup subsys devices
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.070000] Initializing cgroup subsys freezer
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.070000] CPU: Testing write buffer coherency: ok
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.070000] Setting up static identity map for 0x402b1198 - 0x402b11f0
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.070000] devtmpfs: initialized
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.080000] dummy:
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.080000] NET: Registered protocol family 16
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.080000] gpiochip_add: registered GPIOs 0 to 31 on device: gpio-mxs.0
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.080000] gpiochip_add: registered GPIOs 32 to 63 on device: gpio-mxs.1
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.080000] gpiochip_add: registered GPIOs 64 to 95 on device: gpio-mxs.2
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.080000] gpiochip_add: registered GPIOs 96 to 127 on device: gpio-mxs.3
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.080000] gpiochip_add: registered GPIOs 128 to 159 on device: gpio-mxs.4
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.090000] Serial: AMBA PL011 UART driver
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.090000] duart: ttyAMA0 at MMIO 0x80074000 (irq = 47) is a PL011 rev2
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.100000] console [ttyAMA0] enabled
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.100000] mxs-usbphy mxs-usbphy.0: initialized usb phy
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.110000] mxs-usbphy mxs-usbphy.1: initialized usb phy
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.120000] bio: create slab <bio-0>at 0
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.130000] mxs-dma mxs-dma-apbh: initialized
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.140000] mxs-dma mxs-dma-apbx: initialized
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.140000] REG-3V3: 3300 mV normal
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.150000] REG-1V8: 1800 mV normal
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.150000] USB 5V: 5000 mV normal
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.150000] VDDIO-SD: 3300 mV normal
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.160000] Switching to clocksource mxs_timer
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.200000] NET: Registered protocol family 2
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.200000] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.210000] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.220000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.220000] TCP: Hash tables configured (established 8192 bind 8192)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.230000] TCP: reno registered
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.230000] UDP hash table entries: 256 (order: 0, 4096 bytes)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.240000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.250000] NET: Registered protocol family 1
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.250000] RPC: Registered named UNIX socket transport module.
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.260000] RPC: Registered udp transport module.
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.260000] RPC: Registered tcp transport module.
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.270000] RPC: Registered tcp NFSv4.1 backchannel transport module.
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.280000] audit: initializing netlink socket (disabled)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.280000] type=2000 audit(0.280:1): initialized
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.490000] fuse init (API version 7.18)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.500000] msgmni has been set to 498
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.500000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.510000] io scheduler noop registered (default)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.520000] uart-pl011 duart: no DMA platform data
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.520000] mxs-auart.1: ttyAPP1 at MMIO 0x8006c000 (irq = 113) is a mxs-auart.1
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.530000] mxs-auart mxs-auart.1: Found APPUART 3.1.0
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.540000] NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 0.550000] Scanning device for bad blocks
! Feb 26 14:45:53 homematic-ccu2 user.warn kernel: [ 0.580000] Bad eraseblock 167 at 0x0000014e0000
! Feb 26 14:45:53 homematic-ccu2 user.warn kernel: [ 0.690000] Bad eraseblock 667 at 0x000005360000
! Feb 26 14:45:53 homematic-ccu2 user.warn kernel: [ 0.720000] Bad eraseblock 797 at 0x0000063a0000
! Feb 26 14:45:53 homematic-ccu2 user.warn kernel: [ 0.920000] Bad eraseblock 1764 at 0x00000dc80000
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.980000] 8 cmdlinepart partitions found on MTD device gpmi-nand
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.980000] Creating 8 MTD partitions on "gpmi-nand":
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 0.990000] 0x000000000000-0x000000100000 : "fcb"
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.000000] 0x000000100000-0x000000200000 : "bbt"
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.000000] 0x000000200000-0x000000300000 : "bootenv"
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.010000] 0x000000300000-0x000000480000 : "bootstream0"
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.020000] 0x000000480000-0x000000a80000 : "bootstream1"
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.030000] 0x000000a80000-0x000000e80000 : "kernel"
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.040000] 0x000000e80000-0x000003e80000 : "user"
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.050000] 0x000003e80000-0x000010000000 : "root"
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 1.050000] GPMI NAND driver registered. (IMX)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.060000] UBI: attaching mtd7 to ubi0
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.060000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.070000] UBI: logical eraseblock size: 126976 bytes
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.080000] UBI: smallest flash I/O unit: 2048
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.080000] UBI: VID header offset: 2048 (aligned 2048)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 1.090000] UBI: data offset: 4096
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.790000] UBI: max. sequence number: 7
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.810000] UBI: attached mtd7 to ubi0
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.820000] UBI: MTD device name: "root"
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.820000] UBI: MTD device size: 193 MiB
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.830000] UBI: number of good PEBs: 1545
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.830000] UBI: number of bad PEBs: 3
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.840000] UBI: number of corrupted PEBs: 0
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.840000] UBI: max. allowed volumes: 128
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.850000] UBI: wear-leveling threshold: 4096
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.850000] UBI: number of internal volumes: 1
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.860000] UBI: number of user volumes: 1
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.860000] UBI: available PEBs: 0
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.860000] UBI: total number of reserved PEBs: 1545
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.870000] UBI: number of PEBs reserved for bad PEB handling: 15
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.880000] UBI: max/mean erase counter: 6/2
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.880000] UBI: image sequence number: 215908552
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.880000] UBI: background thread "ubi_bgt0d" started, PID 32
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.890000] UBI: attaching mtd6 to ubi1
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.890000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.900000] UBI: logical eraseblock size: 126976 bytes
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.910000] UBI: smallest flash I/O unit: 2048
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.910000] UBI: VID header offset: 2048 (aligned 2048)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 2.920000] UBI: data offset: 4096
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.340000] UBI: max. sequence number: 732
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.360000] UBI: attached mtd6 to ubi1
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.370000] UBI: MTD device name: "user"
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.370000] UBI: MTD device size: 48 MiB
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.380000] UBI: number of good PEBs: 383
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.380000] UBI: number of bad PEBs: 1
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.390000] UBI: number of corrupted PEBs: 0
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.390000] UBI: max. allowed volumes: 128
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.400000] UBI: wear-leveling threshold: 4096
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.400000] UBI: number of internal volumes: 1
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.410000] UBI: number of user volumes: 1
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.410000] UBI: available PEBs: 0
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.410000] UBI: total number of reserved PEBs: 383
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.420000] UBI: number of PEBs reserved for bad PEB handling: 3
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.430000] UBI: max/mean erase counter: 4/2
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.430000] UBI: image sequence number: 2047575981
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.430000] UBI: background thread "ubi_bgt1d" started, PID 33
! Feb 26 14:45:53 homematic-ccu2 user.err kernel: [ 3.440000] UBI error: ubi_init: cannot attach mtd7
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.470000] fec_enet_mii_bus: probed
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.480000] rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.500000] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.510000] stmp3xxx-rtc stmp3xxx-rtc: rtc core: registered stmp3xxx-rtc as rtc1
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.520000] watchdog watchdog0: watchdog initialized, 115 seconds remaining
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.520000] cpuidle: using governor ladder
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.530000] cpuidle: using governor menu
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 3.530000] Registered led device: power
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 3.530000] Registered led device: internet
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 3.530000] Registered led device: info
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.530000] NET: Registered protocol family 17
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.540000] registered taskstats version 1
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.550000] rtc-rs5c372 0-0032: setting system clock to 2017-02-26 13:45:50 UTC (1488116750)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.710000] UBIFS: mounted UBI device 0, volume 0, name "root"
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.720000] UBIFS: mounted read-only
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.720000] UBIFS: file system size: 192368640 bytes (187860 KiB, 183 MiB, 1515 LEBs)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.730000] UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.730000] UBIFS: media format: w4/r0 (latest is w4/r0)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.740000] UBIFS: default compressor: lzo
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 3.740000] UBIFS: reserved for root: 0 bytes (0 KiB)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.750000] VFS: Mounted root (ubifs filesystem) readonly on device 0:12.
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.760000] devtmpfs: mounted
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 3.770000] Freeing init memory: 116K
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 4.270000] UBIFS: recovery needed
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 4.560000] UBIFS: recovery completed
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 4.570000] UBIFS: mounted UBI device 1, volume 0, name "user"
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 4.570000] UBIFS: file system size: 46346240 bytes (45260 KiB, 44 MiB, 365 LEBs)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 4.580000] UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 4.590000] UBIFS: media format: w4/r0 (latest is w4/r0)
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 4.600000] UBIFS: default compressor: lzo
! Feb 26 14:45:53 homematic-ccu2 user.notice kernel: [ 4.600000] UBIFS: reserved for root: 0 bytes (0 KiB)
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.250000] eq3spi eq3spi.0: master is unqueued, this is deprecated
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.320000] input: gpio-keys as /devices/platform/gpio-keys/input/input0
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.370000] Freescale High-Speed USB SOC Device Controller driver (Apr 20, 2007)
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 5.380000] mxs-usbphy mxs-usbphy.0: enabling gadget mode
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.460000] usb0: MAC 00:1a:22:00:05:87
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.460000] usb0: HOST MAC 00:1a:22:00:05:86
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.470000] g_multi gadget: Mass Storage Function, version: 2009/09/11
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.480000] g_multi gadget: Number of LUNs=1
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.480000] lun0: LUN: read only CD-ROM file: /usr/share/eq3/install.iso
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.490000] g_multi gadget: Multifunction Composite Gadget
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.490000] g_multi gadget: g_multi ready
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.500000] fsl-usb2-udc: bind to driver g_multi
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.530000] tun: Universal TUN/TAP device driver, 1.6
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.530000] tun: (C) 1999-2004 Max Krasnyansky maxk@qualcomm.com
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.610000] usbcore: registered new interface driver usbfs
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.620000] usbcore: registered new interface driver hub
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.630000] usbcore: registered new device driver usb
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.650000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.660000] mxs-ehci mxs-ehci.1: initializing i.MX USB Controller
! Feb 26 14:45:53 homematic-ccu2 user.debug kernel: [ 5.680000] mxs-usbphy mxs-usbphy.1: enabling host mode
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.700000] mxs-ehci mxs-ehci.1: using regulator to control VBUS
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.700000] mxs-ehci mxs-ehci.1: Freescale On-Chip EHCI Host Controller
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.710000] mxs-ehci mxs-ehci.1: new USB bus registered, assigned bus number 1
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.750000] mxs-ehci mxs-ehci.1: irq 92, io mem 0x80090000
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.770000] mxs-ehci mxs-ehci.1: USB 2.0 started, EHCI 1.00
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.770000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.780000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.790000] usb usb1: Product: Freescale On-Chip EHCI Host Controller
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.790000] usb usb1: Manufacturer: Linux 3.4.11.ccu2 ehci_hcd
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.800000] usb usb1: SerialNumber: mxs-ehci.1
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.800000] hub 1-0:1.0: USB hub found
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.810000] hub 1-0:1.0: 1 port detected
! Feb 26 14:45:53 homematic-ccu2 user.info kernel: [ 5.840000] mxs-raw-auart mxs-raw-auart.0: Found raw APPUART 3.1.0
! Feb 26 14:45:53 homematic-ccu2 user.err kernel: 0>[ 6.400000] udevd[103]: starting version 182
! Feb 26 13:45:53 homematic-ccu2 daemon.err udevd[103]: specified group 'dialout' unknown
! Feb 26 13:45:53 homematic-ccu2 daemon.err udevd[103]: specified group 'kmem' unknown
! Feb 26 13:45:53 homematic-ccu2 daemon.err udevd[103]: specified group 'video' unknown
! Feb 26 13:45:53 homematic-ccu2 daemon.err udevd[103]: specified group 'lp' unknown
! Feb 26 13:45:53 homematic-ccu2 daemon.err udevd[103]: specified group 'floppy' unknown
! Feb 26 13:45:53 homematic-ccu2 daemon.err udevd[103]: specified group 'cdrom' unknown
! Feb 26 13:45:53 homematic-ccu2 daemon.err udevd[103]: specified group 'tape' unknown
! Feb 26 14:45:54 homematic-ccu2 user.info kernel: [ 7.450000] mxs-mmc mxs-mmc.0: using regulator to control VDDIO-SD
! Feb 26 14:45:54 homematic-ccu2 user.info kernel: [ 7.500000] mxs-mmc mxs-mmc.0: initialized
! Feb 26 14:45:54 homematic-ccu2 daemon.info udhcpd[133]: udhcpd (v1.20.2) started
! Feb 26 14:45:54 homematic-ccu2 daemon.err udhcpd[133]: can't open '/var/lib/misc/udhcpd.leases': No such file or directory
! Feb 26 14:45:55 homematic-ccu2 user.info kernel: [ 8.860000] eth0: Freescale FEC PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=imx28-fec-1:00, irq=185)
! Feb 26 14:45:57 homematic-ccu2 user.info kernel: [ 10.860000] PHY: imx28-fec-1:00 - Link is Up - 100/Full
! Feb 26 13:46:02 homematic-ccu2 daemon.info ifplugd(eth0)[260]: ifplugd 0.28 initializing.
! Feb 26 13:46:02 homematic-ccu2 daemon.info ifplugd(eth0)[260]: Using interface eth0/00:1A:22:08:43:FA with driver <fec>(version: Revision: 1.0)
! Feb 26 13:46:02 homematic-ccu2 daemon.info ifplugd(eth0)[260]: Using detection mode: SIOCETHTOOL
! Feb 26 13:46:02 homematic-ccu2 daemon.info ifplugd(eth0)[260]: Initialization complete, link beat detected.
! Feb 26 13:46:02 homematic-ccu2 daemon.info ifplugd(eth0)[260]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
! Feb 26 13:46:02 homematic-ccu2 daemon.warn ifplugd(eth0)[260]: client: ifup: interface eth0 already configured
! Feb 26 13:46:02 homematic-ccu2 daemon.info ifplugd(eth0)[260]: Program executed successfully.
! Feb 26 14:46:04 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
! Feb 26 14:46:05 homematic-ccu2 user.debug setclock: Sun Feb 26 14:46:05 CET 2017
! Feb 26 14:46:05 homematic-ccu2 daemon.info cuxd[318]: write_pid /var/run/cuxd.pid [318]
! Feb 26 14:46:05 homematic-ccu2 user.info homematic: started cux-daemon
! Feb 26 14:46:05 homematic-ccu2 daemon.info cuxd[318]: CUx-Daemon(1.8a) on CCU(2.25.15) start PID:318
! Feb 26 13:46:05 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
! Feb 26 14:46:05 homematic-ccu2 daemon.info cuxd[318]: write_proxy /var/cache/cuxd_proxy.ini (127.0.0.1 8700 318 /usr/local/addons/cuxd/ 1.8a)
! Feb 26 14:46:05 homematic-ccu2 daemon.info cuxd[318]: add interface 'CUxD'
! Feb 26 14:46:06 homematic-ccu2 daemon.info cuxd[318]: write 5 interfaces to /usr/local/etc/config/InterfacesList.xml
! Feb 26 14:46:06 homematic-ccu2 daemon.info cuxd[318]: TTY(/ttyAPP1) connect(57600:8N1)
! Feb 26 13:46:06 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
! Feb 26 13:46:06 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
! Feb 26 14:46:06 homematic-ccu2 daemon.info cuxd[318]: TTY(/ttyAPP1) use KEY1(EO:VB5Lfy+KMQ1AGmSq)
! Feb 26 13:46:06 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
! Feb 26 13:46:06 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware
! Feb 26 13:46:06 homematic-ccu2 user.info update-lgw-firmware: LAN Gateway Firmware Update…
! Feb 26 13:46:06 homematic-ccu2 user.info update-lgw-firmware: Gateway MEQ0673328
! Feb 26 13:46:08 homematic-ccu2 user.info update-lgw-firmware: Gateway type is eQ3-HMW-LGW-App
! Feb 26 13:46:08 homematic-ccu2 user.info update-lgw-firmware: Available Firmware Version: 1.0.5
! Feb 26 13:46:08 homematic-ccu2 user.info update-lgw-firmware: Lan Gateway Firmware Version: 1.0.5
! Feb 26 13:46:08 homematic-ccu2 user.info update-lgw-firmware: Firmware is up to date
! Feb 26 14:46:14 homematic-ccu2 user.info update-coprocessor: Version: 2.4.3
! Feb 26 14:46:14 homematic-ccu2 user.info update-coprocessor: No update necessary
! Feb 26 14:46:15 homematic-ccu2 user.info kernel: [ 27.870000] eq3loop: created slave ttyS0
! Feb 26 14:46:15 homematic-ccu2 user.info kernel: [ 27.880000] eq3loop: created slave mmd_bidcos
! Feb 26 14:46:17 homematic-ccu2 user.info kernel: [ 30.220000] eq3loop: eq3loop_open_slave() mmd_bidcos
! Feb 26 14:47:39 homematic-ccu2 daemon.warn cuxd[318]: process_rpc_request(127.0.0.1) - illegal XMLRPC(listDevices) request
! Feb 26 14:47:55 homematic-ccu2 user.info kernel: [ 127.480000] eq3loop: eq3loop_open_slave() ttyS0
! Feb 26 14:47:55 homematic-ccu2 user.info kernel: [ 127.480000] eq3loop: eq3loop_close_slave() ttyS0
! Feb 26 14:47:55 homematic-ccu2 user.info kernel: [ 127.700000] eq3loop: eq3loop_open_slave() ttyS0
! Feb 26 14:47:55 homematic-ccu2 user.info kernel: [ 127.730000] eq3loop: eq3loop_close_slave() ttyS0
! Feb 26 14:47:56 homematic-ccu2 user.info kernel: [ 129.390000] eq3loop: eq3loop_open_slave() ttyS0
! Feb 26 14:47:57 homematic-ccu2 user.notice kernel: [ 129.460000] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x5459
! Feb 26 14:47:57 homematic-ccu2 user.notice kernel: [ 129.460000] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D
! Feb 26 14:48:22 homematic-ccu2 daemon.warn cuxd[318]: process_rpc_request(127.0.0.1) - illegal XMLRPC(init) request
! Feb 26 14:48:25 homematic-ccu2 user.warn kernel: [ 158.340000] tun: module has no symbols (stripped?)
! Feb 26 14:48:26 homematic-ccu2 user.info : hss_lcd: Programm initialisiert.
! Feb 26 13:48:26 homematic-ccu2 daemon.info init: starting pid 530, tty '/dev/ttyAMA0': '/sbin/getty -L ttyAMA0 115200 vt100 '
! Feb 26 13:48:27 homematic-ccu2 daemon.info init: starting pid 531, tty '/dev/ttyGS0': '/sbin/getty -L ttyGS0 115200 vt100 '
! Feb 26 14:48:48 homematic-ccu2 daemon.info cuxd[318]: INIT 'xmlrpc_bin://127.0.0.1:1999' '1238'
! HIER STARTE ICH IOBROKER mit dem RPC.1 (Wired) per XML-RPC PROTOKOLL
! Feb 26 14:51:41 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: XmlrpcTypeToIseVal failed [../Platform/DOM/iseXmlRpc.cpp (1455)]
! Feb 26 14:51:41 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [../Platform/DOM/iseDOMdpHSS.cpp (130)]
! Feb 26 14:51:41 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: XmlrpcTypeToIseVal failed [../Platform/DOM/iseXmlRpc.cpp (1455)]
! Feb 26 14:51:41 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [../Platform/DOM/iseDOMdpHSS.cpp (130)]
! Feb 26 14:52:56 homematic-ccu2 user.err hs485d: XmlRpc transport error calling system.listMethods({"hm-rpc.1"}) on http://192.168.88.92:2000/RPC2:
! Feb 26 14:53:59 homematic-ccu2 user.err hs485d: XmlRpc transport error calling listDevices({"hm-rpc.1"}) on http://192.168.88.92:2000/RPC2:
! Feb 26 14:55:02 homematic-ccu2 user.err hs485d: XmlRpc transport error calling system.listMethods({"hm-rpc.1"}) on http://192.168.88.92:2000/RPC2:
! Feb 26 14:56:06 homematic-ccu2 user.err hs485d: XmlRpc transport error calling listDevices({"hm-rpc.1"}) on http://192.168.88.92:2000/RPC2:
! Feb 26 14:57:09 homematic-ccu2 user.err hs485d: XmlRpc transport error calling system.listMethods({"hm-rpc.1"}) on http://192.168.88.92:2000/RPC2:
! Feb 26 14:58:12 homematic-ccu2 user.err hs485d: XmlRpc transport error calling listDevices({"hm-rpc.1"}) on http://192.168.88.92:2000/RPC2:
! Feb 26 14:59:15 homematic-ccu2 user.err hs485d: XmlRpc transport error calling system.listMethods({"hm-rpc.1"}) on http://192.168.88.92:2000/RPC2:
! Feb 26 15:00:18 homematic-ccu2 user.err hs485d: XmlRpc transport error calling listDevices({"hm-rpc.1"}) on http://192.168.88.92:2000/RPC2:
! Feb 26 15:00:39 homematic-ccu2 user.err hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"hm-rpc.1","MEQ1770181:13","STATE",true}]}) on http://192.168.88.92:2000/RPC2:
! Feb 26 15:00:39 homematic-ccu2 user.err hs485d: XmlRpc transport error</fec></bio-0>Versuche es gleich nochmal mit dem BIN Protokoll und reiche den Log nach.
Viele Grüße Tom
-
Hallo Tom,
ich bin nicht brauchbar bei CCU Logs
aber wenn ich das richtig sehe hat die ReGa schon eine Minute vor der Anfrage von hm-rpc.1 Probleme.
Gruß
Rainer
-
Hallo Rainer,
das ist Schade. Vielleicht schaut noch jemand mal drüber. ich bin wirklich ratlos. Es kann ja nicht sein, dass ich der einzige bin, der mit dem Problem kämpft.
hier nochmal das gleiche per BIN Protokoll.
hm-rpc.1 verbindet sich, nach den eingestellten 60 Sekunden Verbindungscheck wieder ein Disconnect und die CCU zeigt mir Ihre Eieruhr…Feierabend. Diesmal erholt sie sich anscheinend gar nicht mehr, auch wenn beide Instanzen von mir gestoppt werden.
Viele Grüße
Tom
! Feb 26 15:35:55 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2016-11-22 12:43:12 CET)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] Booting Linux on physical CPU 0
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] Initializing cgroup subsys cpu
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] Linux version 3.4.11.ccu2 (hudson@entw-build-10) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70) ) #1 PREEMPT Tue Nov 22 13:09:59 CET 2016
! Feb 26 15:35:55 homematic-ccu2 user.warn kernel: [ 0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
! Feb 26 15:35:55 homematic-ccu2 user.warn kernel: [ 0.000000] CPU: VIVT data cache, VIVT instruction cache
! Feb 26 15:35:55 homematic-ccu2 user.warn kernel: [ 0.000000] Machine: eQ-3 HomeMatic CCU2
! Feb 26 15:35:55 homematic-ccu2 user.warn kernel: [ 0.000000] Memory policy: ECC disabled, Data cache writeback
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 0.000000] On node 0 totalpages: 65536
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 0.000000] free_area_init_node: node 0, pgdat c03c42ec, node_mem_map c03f8000
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 0.000000] Normal zone: 512 pages used for memmap
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 0.000000] Normal zone: 0 pages reserved
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 0.000000] Normal zone: 65024 pages, LIFO batch:15
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 0.000000] pcpu-alloc: [0] 0
! Feb 26 15:35:55 homematic-ccu2 user.warn kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] Kernel command line: eQ3Mode=production console=ttyAMA0,115200 ubi.mtd=7 ubi.mtd=6 ro ip=none root=ubi0:root ubi.mtd=7 rootfstype=ubifs noinitrd mtdparts=gpmi-nand:1024k(fcb)ro,1024k(bbt),1024k(bootenv),1536k(boo
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] allocated 524288 bytes of page_cgroup
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] Memory: 256MB = 256MB total
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] Memory: 255276k/255276k available, 6868k reserved, 0K highmem
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] Virtual kernel memory layout:
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] vmalloc : 0xd0800000 - 0xff000000 ( 744 MB)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] .text : 0xc0008000 - 0xc037d000 (3540 kB)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] .init : 0xc037d000 - 0xc039a000 ( 116 kB)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] .data : 0xc039a000 - 0xc03c4a20 ( 171 kB)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.000000] .bss : 0xc03c4a44 - 0xc03f77dc ( 204 kB)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] NR_IRQS:304
! Feb 26 15:35:55 homematic-ccu2 user.err kernel: [ 0.000000] saif0_clk_set_rate: clock is gated
! Feb 26 15:35:55 homematic-ccu2 user.err kernel: [ 0.000000] saif1_clk_set_rate: clock is gated
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] Console: colour dummy device 80x30
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.000000] Calibrating delay loop… 226.09 BogoMIPS (lpj=1130496)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.070000] pid_max: default: 32768 minimum: 301
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.070000] Mount-cache hash table entries: 512
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.070000] Initializing cgroup subsys cpuacct
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.070000] Initializing cgroup subsys memory
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.070000] Initializing cgroup subsys devices
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.070000] Initializing cgroup subsys freezer
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.070000] CPU: Testing write buffer coherency: ok
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.070000] Setting up static identity map for 0x402b1198 - 0x402b11f0
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.070000] devtmpfs: initialized
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.080000] dummy:
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.080000] NET: Registered protocol family 16
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.080000] gpiochip_add: registered GPIOs 0 to 31 on device: gpio-mxs.0
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.080000] gpiochip_add: registered GPIOs 32 to 63 on device: gpio-mxs.1
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.080000] gpiochip_add: registered GPIOs 64 to 95 on device: gpio-mxs.2
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.080000] gpiochip_add: registered GPIOs 96 to 127 on device: gpio-mxs.3
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.080000] gpiochip_add: registered GPIOs 128 to 159 on device: gpio-mxs.4
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.090000] Serial: AMBA PL011 UART driver
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.090000] duart: ttyAMA0 at MMIO 0x80074000 (irq = 47) is a PL011 rev2
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.100000] console [ttyAMA0] enabled
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.100000] mxs-usbphy mxs-usbphy.0: initialized usb phy
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.110000] mxs-usbphy mxs-usbphy.1: initialized usb phy
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.120000] bio: create slab <bio-0>at 0
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.130000] mxs-dma mxs-dma-apbh: initialized
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.140000] mxs-dma mxs-dma-apbx: initialized
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.140000] REG-3V3: 3300 mV normal
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.150000] REG-1V8: 1800 mV normal
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.150000] USB 5V: 5000 mV normal
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.150000] VDDIO-SD: 3300 mV normal
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.160000] Switching to clocksource mxs_timer
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.200000] NET: Registered protocol family 2
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.200000] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.210000] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.220000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.220000] TCP: Hash tables configured (established 8192 bind 8192)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.230000] TCP: reno registered
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.230000] UDP hash table entries: 256 (order: 0, 4096 bytes)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.240000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.250000] NET: Registered protocol family 1
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.250000] RPC: Registered named UNIX socket transport module.
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.260000] RPC: Registered udp transport module.
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.260000] RPC: Registered tcp transport module.
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.270000] RPC: Registered tcp NFSv4.1 backchannel transport module.
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.280000] audit: initializing netlink socket (disabled)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.280000] type=2000 audit(0.280:1): initialized
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.490000] fuse init (API version 7.18)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.500000] msgmni has been set to 498
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.500000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.510000] io scheduler noop registered (default)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.520000] uart-pl011 duart: no DMA platform data
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.520000] mxs-auart.1: ttyAPP1 at MMIO 0x8006c000 (irq = 113) is a mxs-auart.1
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.530000] mxs-auart mxs-auart.1: Found APPUART 3.1.0
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.540000] NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 0.550000] Scanning device for bad blocks
! Feb 26 15:35:55 homematic-ccu2 user.warn kernel: [ 0.580000] Bad eraseblock 167 at 0x0000014e0000
! Feb 26 15:35:55 homematic-ccu2 user.warn kernel: [ 0.690000] Bad eraseblock 667 at 0x000005360000
! Feb 26 15:35:55 homematic-ccu2 user.warn kernel: [ 0.720000] Bad eraseblock 797 at 0x0000063a0000
! Feb 26 15:35:55 homematic-ccu2 user.warn kernel: [ 0.920000] Bad eraseblock 1764 at 0x00000dc80000
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.980000] 8 cmdlinepart partitions found on MTD device gpmi-nand
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.980000] Creating 8 MTD partitions on "gpmi-nand":
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 0.990000] 0x000000000000-0x000000100000 : "fcb"
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.000000] 0x000000100000-0x000000200000 : "bbt"
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.000000] 0x000000200000-0x000000300000 : "bootenv"
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.010000] 0x000000300000-0x000000480000 : "bootstream0"
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.020000] 0x000000480000-0x000000a80000 : "bootstream1"
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.030000] 0x000000a80000-0x000000e80000 : "kernel"
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.040000] 0x000000e80000-0x000003e80000 : "user"
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.050000] 0x000003e80000-0x000010000000 : "root"
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 1.050000] GPMI NAND driver registered. (IMX)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.060000] UBI: attaching mtd7 to ubi0
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.060000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.070000] UBI: logical eraseblock size: 126976 bytes
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.080000] UBI: smallest flash I/O unit: 2048
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.080000] UBI: VID header offset: 2048 (aligned 2048)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 1.090000] UBI: data offset: 4096
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.790000] UBI: max. sequence number: 7
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.820000] UBI: attached mtd7 to ubi0
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.820000] UBI: MTD device name: "root"
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.820000] UBI: MTD device size: 193 MiB
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.830000] UBI: number of good PEBs: 1545
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.830000] UBI: number of bad PEBs: 3
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.840000] UBI: number of corrupted PEBs: 0
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.840000] UBI: max. allowed volumes: 128
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.850000] UBI: wear-leveling threshold: 4096
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.850000] UBI: number of internal volumes: 1
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.860000] UBI: number of user volumes: 1
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.860000] UBI: available PEBs: 0
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.870000] UBI: total number of reserved PEBs: 1545
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.870000] UBI: number of PEBs reserved for bad PEB handling: 15
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.880000] UBI: max/mean erase counter: 6/2
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.880000] UBI: image sequence number: 215908552
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.890000] UBI: background thread "ubi_bgt0d" started, PID 32
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.890000] UBI: attaching mtd6 to ubi1
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.900000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.900000] UBI: logical eraseblock size: 126976 bytes
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.910000] UBI: smallest flash I/O unit: 2048
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.910000] UBI: VID header offset: 2048 (aligned 2048)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 2.920000] UBI: data offset: 4096
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.340000] UBI: max. sequence number: 741
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.370000] UBI: attached mtd6 to ubi1
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.370000] UBI: MTD device name: "user"
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.370000] UBI: MTD device size: 48 MiB
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.380000] UBI: number of good PEBs: 383
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.380000] UBI: number of bad PEBs: 1
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.390000] UBI: number of corrupted PEBs: 0
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.390000] UBI: max. allowed volumes: 128
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.400000] UBI: wear-leveling threshold: 4096
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.400000] UBI: number of internal volumes: 1
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.410000] UBI: number of user volumes: 1
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.410000] UBI: available PEBs: 0
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.420000] UBI: total number of reserved PEBs: 383
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.420000] UBI: number of PEBs reserved for bad PEB handling: 3
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.430000] UBI: max/mean erase counter: 4/2
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.430000] UBI: image sequence number: 2047575981
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.440000] UBI: background thread "ubi_bgt1d" started, PID 33
! Feb 26 15:35:55 homematic-ccu2 user.err kernel: [ 3.440000] UBI error: ubi_init: cannot attach mtd7
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.480000] fec_enet_mii_bus: probed
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.480000] rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.500000] rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.510000] stmp3xxx-rtc stmp3xxx-rtc: rtc core: registered stmp3xxx-rtc as rtc1
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.520000] watchdog watchdog0: watchdog initialized, 115 seconds remaining
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.520000] cpuidle: using governor ladder
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.530000] cpuidle: using governor menu
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 3.530000] Registered led device: power
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 3.530000] Registered led device: internet
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 3.530000] Registered led device: info
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.530000] NET: Registered protocol family 17
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.540000] registered taskstats version 1
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.550000] rtc-rs5c372 0-0032: setting system clock to 2017-02-26 14:35:52 UTC (1488119752)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.710000] UBIFS: mounted UBI device 0, volume 0, name "root"
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.720000] UBIFS: mounted read-only
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.720000] UBIFS: file system size: 192368640 bytes (187860 KiB, 183 MiB, 1515 LEBs)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.730000] UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.740000] UBIFS: media format: w4/r0 (latest is w4/r0)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.740000] UBIFS: default compressor: lzo
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 3.750000] UBIFS: reserved for root: 0 bytes (0 KiB)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.760000] VFS: Mounted root (ubifs filesystem) readonly on device 0:12.
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.770000] devtmpfs: mounted
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 3.770000] Freeing init memory: 116K
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 4.270000] UBIFS: recovery needed
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 4.640000] UBIFS: recovery completed
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 4.650000] UBIFS: mounted UBI device 1, volume 0, name "user"
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 4.660000] UBIFS: file system size: 46346240 bytes (45260 KiB, 44 MiB, 365 LEBs)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 4.660000] UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 4.670000] UBIFS: media format: w4/r0 (latest is w4/r0)
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 4.680000] UBIFS: default compressor: lzo
! Feb 26 15:35:55 homematic-ccu2 user.notice kernel: [ 4.680000] UBIFS: reserved for root: 0 bytes (0 KiB)
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.330000] eq3spi eq3spi.0: master is unqueued, this is deprecated
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.400000] input: gpio-keys as /devices/platform/gpio-keys/input/input0
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.460000] Freescale High-Speed USB SOC Device Controller driver (Apr 20, 2007)
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 5.460000] mxs-usbphy mxs-usbphy.0: enabling gadget mode
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.540000] usb0: MAC 00:1a:22:00:05:87
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.540000] usb0: HOST MAC 00:1a:22:00:05:86
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.550000] g_multi gadget: Mass Storage Function, version: 2009/09/11
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.560000] g_multi gadget: Number of LUNs=1
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.560000] lun0: LUN: read only CD-ROM file: /usr/share/eq3/install.iso
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.570000] g_multi gadget: Multifunction Composite Gadget
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.580000] g_multi gadget: g_multi ready
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.580000] fsl-usb2-udc: bind to driver g_multi
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.610000] tun: Universal TUN/TAP device driver, 1.6
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.620000] tun: (C) 1999-2004 Max Krasnyansky maxk@qualcomm.com
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.700000] usbcore: registered new interface driver usbfs
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.700000] usbcore: registered new interface driver hub
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.710000] usbcore: registered new device driver usb
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.730000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.740000] mxs-ehci mxs-ehci.1: initializing i.MX USB Controller
! Feb 26 15:35:55 homematic-ccu2 user.debug kernel: [ 5.760000] mxs-usbphy mxs-usbphy.1: enabling host mode
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.780000] mxs-ehci mxs-ehci.1: using regulator to control VBUS
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.780000] mxs-ehci mxs-ehci.1: Freescale On-Chip EHCI Host Controller
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.790000] mxs-ehci mxs-ehci.1: new USB bus registered, assigned bus number 1
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.830000] mxs-ehci mxs-ehci.1: irq 92, io mem 0x80090000
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.850000] mxs-ehci mxs-ehci.1: USB 2.0 started, EHCI 1.00
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.850000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.860000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.870000] usb usb1: Product: Freescale On-Chip EHCI Host Controller
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.870000] usb usb1: Manufacturer: Linux 3.4.11.ccu2 ehci_hcd
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.880000] usb usb1: SerialNumber: mxs-ehci.1
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.880000] hub 1-0:1.0: USB hub found
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.890000] hub 1-0:1.0: 1 port detected
! Feb 26 15:35:55 homematic-ccu2 user.info kernel: [ 5.920000] mxs-raw-auart mxs-raw-auart.0: Found raw APPUART 3.1.0
! Feb 26 15:35:55 homematic-ccu2 user.err kernel: 0>[ 6.470000] udevd[103]: starting version 182
! Feb 26 14:35:55 homematic-ccu2 daemon.err udevd[103]: specified group 'dialout' unknown
! Feb 26 14:35:55 homematic-ccu2 daemon.err udevd[103]: specified group 'kmem' unknown
! Feb 26 14:35:55 homematic-ccu2 daemon.err udevd[103]: specified group 'video' unknown
! Feb 26 14:35:55 homematic-ccu2 daemon.err udevd[103]: specified group 'lp' unknown
! Feb 26 14:35:55 homematic-ccu2 daemon.err udevd[103]: specified group 'floppy' unknown
! Feb 26 14:35:55 homematic-ccu2 daemon.err udevd[103]: specified group 'cdrom' unknown
! Feb 26 14:35:55 homematic-ccu2 daemon.err udevd[103]: specified group 'tape' unknown
! Feb 26 15:35:56 homematic-ccu2 user.info kernel: [ 7.570000] mxs-mmc mxs-mmc.0: using regulator to control VDDIO-SD
! Feb 26 15:35:56 homematic-ccu2 user.info kernel: [ 7.590000] mxs-mmc mxs-mmc.0: initialized
! Feb 26 15:35:56 homematic-ccu2 daemon.info udhcpd[129]: udhcpd (v1.20.2) started
! Feb 26 15:35:56 homematic-ccu2 daemon.err udhcpd[129]: can't open '/var/lib/misc/udhcpd.leases': No such file or directory
! Feb 26 15:35:57 homematic-ccu2 user.info kernel: [ 8.980000] eth0: Freescale FEC PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=imx28-fec-1:00, irq=185)
! Feb 26 15:35:59 homematic-ccu2 user.info kernel: [ 10.990000] PHY: imx28-fec-1:00 - Link is Up - 100/Full
! Feb 26 14:36:04 homematic-ccu2 daemon.info ifplugd(eth0)[259]: ifplugd 0.28 initializing.
! Feb 26 14:36:04 homematic-ccu2 daemon.info ifplugd(eth0)[259]: Using interface eth0/00:1A:22:08:43:FA with driver <fec>(version: Revision: 1.0)
! Feb 26 14:36:04 homematic-ccu2 daemon.info ifplugd(eth0)[259]: Using detection mode: SIOCETHTOOL
! Feb 26 14:36:04 homematic-ccu2 daemon.info ifplugd(eth0)[259]: Initialization complete, link beat detected.
! Feb 26 14:36:04 homematic-ccu2 daemon.info ifplugd(eth0)[259]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
! Feb 26 14:36:04 homematic-ccu2 daemon.warn ifplugd(eth0)[259]: client: ifup: interface eth0 already configured
! Feb 26 14:36:04 homematic-ccu2 daemon.info ifplugd(eth0)[259]: Program executed successfully.
! Feb 26 15:36:05 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
! Feb 26 15:36:06 homematic-ccu2 user.debug setclock: Sun Feb 26 15:36:06 CET 2017
! Feb 26 15:36:07 homematic-ccu2 user.info homematic: started cux-daemon
! Feb 26 15:36:07 homematic-ccu2 daemon.info cuxd[319]: write_pid /var/run/cuxd.pid [319]
! Feb 26 15:36:07 homematic-ccu2 daemon.info cuxd[319]: CUx-Daemon(1.8a) on CCU(2.25.15) start PID:319
! Feb 26 14:36:07 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
! Feb 26 15:36:07 homematic-ccu2 daemon.info cuxd[319]: write_proxy /var/cache/cuxd_proxy.ini (127.0.0.1 8700 319 /usr/local/addons/cuxd/ 1.8a)
! Feb 26 15:36:07 homematic-ccu2 daemon.info cuxd[319]: add interface 'CUxD'
! Feb 26 15:36:07 homematic-ccu2 daemon.info cuxd[319]: write 5 interfaces to /usr/local/etc/config/InterfacesList.xml
! Feb 26 14:36:07 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
! Feb 26 15:36:07 homematic-ccu2 daemon.info cuxd[319]: TTY(/ttyAPP1) connect(57600:8N1)
! Feb 26 14:36:07 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
! Feb 26 14:36:08 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
! Feb 26 15:36:08 homematic-ccu2 daemon.info cuxd[319]: TTY(/ttyAPP1) use KEY1(EO:VB5Lfy+KMQ1AGmSq)
! Feb 26 14:36:08 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware
! Feb 26 14:36:08 homematic-ccu2 user.info update-lgw-firmware: LAN Gateway Firmware Update…
! Feb 26 14:36:08 homematic-ccu2 user.info update-lgw-firmware: Gateway MEQ0673328
! Feb 26 14:36:10 homematic-ccu2 user.info update-lgw-firmware: Gateway type is eQ3-HMW-LGW-App
! Feb 26 14:36:10 homematic-ccu2 user.info update-lgw-firmware: Available Firmware Version: 1.0.5
! Feb 26 14:36:10 homematic-ccu2 user.info update-lgw-firmware: Lan Gateway Firmware Version: 1.0.5
! Feb 26 14:36:10 homematic-ccu2 user.info update-lgw-firmware: Firmware is up to date
! Feb 26 15:36:16 homematic-ccu2 user.info update-coprocessor: Version: 2.4.3
! Feb 26 15:36:16 homematic-ccu2 user.info update-coprocessor: No update necessary
! Feb 26 15:36:17 homematic-ccu2 user.info kernel: [ 29.040000] eq3loop: created slave ttyS0
! Feb 26 15:36:17 homematic-ccu2 user.info kernel: [ 29.050000] eq3loop: created slave mmd_bidcos
! Feb 26 15:36:20 homematic-ccu2 user.info kernel: [ 31.410000] eq3loop: eq3loop_open_slave() mmd_bidcos
! Feb 26 15:37:52 homematic-ccu2 daemon.warn cuxd[319]: process_rpc_request(127.0.0.1) - illegal XMLRPC(listDevices) request
! Feb 26 15:38:06 homematic-ccu2 user.info kernel: [ 138.040000] eq3loop: eq3loop_open_slave() ttyS0
! Feb 26 15:38:06 homematic-ccu2 user.info kernel: [ 138.050000] eq3loop: eq3loop_close_slave() ttyS0
! Feb 26 15:38:06 homematic-ccu2 user.info kernel: [ 138.210000] eq3loop: eq3loop_open_slave() ttyS0
! Feb 26 15:38:06 homematic-ccu2 user.info kernel: [ 138.210000] eq3loop: eq3loop_close_slave() ttyS0
! Feb 26 15:38:07 homematic-ccu2 user.info kernel: [ 138.580000] eq3loop: eq3loop_open_slave() ttyS0
! Feb 26 15:38:07 homematic-ccu2 user.notice kernel: [ 138.630000] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x5459
! Feb 26 15:38:07 homematic-ccu2 user.notice kernel: [ 138.630000] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D
! Feb 26 15:38:38 homematic-ccu2 daemon.warn cuxd[319]: process_rpc_request(127.0.0.1) - illegal XMLRPC(init) request
! Feb 26 15:38:40 homematic-ccu2 user.warn kernel: [ 172.190000] tun: module has no symbols (stripped?)
! Feb 26 15:38:41 homematic-ccu2 user.info : hss_lcd: Programm initialisiert.
! Feb 26 14:38:42 homematic-ccu2 daemon.info init: starting pid 588, tty '/dev/ttyAMA0': '/sbin/getty -L ttyAMA0 115200 vt100 '
! Feb 26 14:38:42 homematic-ccu2 daemon.info init: starting pid 589, tty '/dev/ttyGS0': '/sbin/getty -L ttyGS0 115200 vt100 '
! Feb 26 15:39:04 homematic-ccu2 daemon.info cuxd[319]: INIT 'xmlrpc_bin://127.0.0.1:1999' '1238'
! HIER STARTE ICH IOBROKER mit dem RPC.1 (Wired) per BIN-RPC PROTOKOLL
! Feb 26 15:40:05 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: XmlrpcTypeToIseVal failed [../Platform/DOM/iseXmlRpc.cpp (1455)]
! Feb 26 15:40:05 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [../Platform/DOM/iseDOMdpHSS.cpp (130)]
! Feb 26 15:40:05 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: XmlrpcTypeToIseVal failed [../Platform/DOM/iseXmlRpc.cpp (1455)]
! Feb 26 15:40:05 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [../Platform/DOM/iseDOMdpHSS.cpp (130)]
! Feb 26 15:41:03 homematic-ccu2 user.err hs485d: XmlRpc transport error calling system.listMethods({"hm-rpc.1"}) on binary://192.168.88.92:2000/RPC2:
! Feb 26 15:42:07 homematic-ccu2 user.err hs485d: XmlRpc transport error calling listDevices({"hm-rpc.1"}) on binary://192.168.88.92:2000/RPC2:
! Feb 26 15:42:27 homematic-ccu2 user.err hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"hm-rpc.1","MEQ1770181:15","STATE",false}],[methodName:"event",params:{"hm-rpc.1","MEQ1770181:15","WORKING",false}]}) on binary://192.168.88.92:2000/RPC2:
! Feb 26 15:42:27 homematic-ccu2 user.err hs485d: XmlRpc transport error
! Feb 26 15:42:37 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::GetObjectByHSSAddress: no exists device object with address= CENTRAL [../Platform/DOM/iseXmlRpc.cpp (2166)]
! Feb 26 15:42:47 homematic-ccu2 user.err hs485d: XmlRpcClient error calling event({[methodName:"event",params:{"hm-rpc.1","LEQ0868904:1","SENSOR",true}],[methodName:"event",params:{"hm-rpc.1","LEQ0868904:2","SENSOR",true}],[methodName:"event",params:{"hm-rpc.1","LEQ0868904:3"
! Feb 26 15:42:47 homematic-ccu2 user.err hs485d: XmlRpc transport error</fec></bio-0> -
Da waren früher mal schon so ähnliche Probleme, wenn die IP in der Instanz nicht eindeutig und erreichbar war.
Sieht zwar im Screenshot so aus, aber ist die IP für den ioBroker richtig eingestellt. Ist kein /Router/Firewall/Dienst dazwischen, welcher die Kommunikation beeinflussen (blockieren) könnte?
-
Hallo Yves,
was meinst du mit IP für ioBroker richtig eingestellt?
Die IP 192.168.88.92 ist der PC auf dem ioBroker aktuell läuft.
Die 192.168.88.147 ist die CCU2.
Ich würde ja auch sagen, dass es vielleicht an einer Firewall oder ähnlichen liegt, aber bei den beiden anderen Instanzen scheint es ja zu laufen.
Problemkind ist wirklich das Wired RPC. Da zerlegt sich die CCU2. Selbst CUxD läuft, zwar nicht schnell, aber es läuft.
Danke und viele Grüße
Tom
-
Ich fische da auch im Trüben.
Früher war das so, dass man im Konfig-Dialog auch 0.0.0.0 oder andere installierte Interface auswählen konnte. Wenn einer dann die 0.0.0.0 erwischte, ist die CCU ins Leere gelaufen und ist zerschellt. Wie gesagt, sieht bei Dir gut aus (ausser Du hättest mehere NICs drin
)Die CCU muss jedenfalls die eingestellten IP (inkl. Port) erreichen können!
-
Ich fische da auch im Trüben.
Früher war das so, dass man im Konfig-Dialog auch 0.0.0.0 oder andere installierte Interface auswählen konnte. Wenn einer dann die 0.0.0.0 erwischte, ist die CCU ins Leere gelaufen und ist zerschellt. Wie gesagt, sieht bei Dir gut aus (ausser Du hättest mehere NICs drin
)Die CCU muss jedenfalls die eingestellten IP (inkl. Port) erreichen können! `
Da geht's mir wie dir.
Ich halte nur den Teil mit den Einstellungen für "nicht schuldig"
Firewall o.ä schon eher, erst recht wenn ich höre:
@dil3ttant:Die IP 192.168.88.92 ist der PC auf dem ioBroker aktuell läuft. `
Aber mein erster Augenmerk ist nach wie vor die CCU.
Ich weiss nicht wo sich dieses EnOcean-modul einklinkt.
Fehler wie:
@dil3ttant:XmlRpc transport error calling system `
könnten schon auf Probleme mit der Erreichbarkeit von ioBroker von der CCU aus hindeuten.Aber wie schon gesagt beginnt es bereits eine Minute vorher:
@Homoran:Feb 26 14:51:41 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: XmlrpcTypeToIseVal failed [../Platform/DOM/iseXmlRpc.cpp (1455)]
Feb 26 14:51:41 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [../Platform/DOM/iseDOMdpHSS.cpp (130)]
Feb 26 14:51:41 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: XmlrpcTypeToIseVal failed [../Platform/DOM/iseXmlRpc.cpp (1455)]
Feb 26 14:51:41 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [../Platform/DOM/iseDOMdpHSS.cpp (130)]
Feb 26 14:52:56 homematic-ccu2 user.err hs485d: XmlRpc transport error calling system.listMethods({"hm-rpc.1"}) on http://192.168.88.92:2000/RPC2: `
und laut Tom geht nach einer Minute der Reload los. Da ist hm-rpc schon tot.
Gruß
Rainer
-
Ich brech ins Essen :oops: :lol: :lol: :lol:
Sorry für den Ausdruck, aber das hat mich jetzt mehrere Abende und unzählige Stunden gekostet, ölfzig mal de und wieder installiert, drölfzig mal Adapter an und aus gestellt und ich weiß nicht mehr wie oft die CCU resetet. :? :? :?
Es war die Firewall. :shock: :shock: :shock:
Das hatte ich gar nicht auf dem Schirm. Dachte immer, wenn was geblockt wird, meldet die sich mit einem Popup Fenster, so ist sie nämlich eingestellt.
Hab sie grad mal zum testen komplett deaktiviert und siehe da, alle Adapter und Instanzen haben sich sofort verbunden und die CCU2 ist flott und sauber ansprechbar.
Und die "Synchronisiere Geräte neu (einmalig)" Haken verschwinden nun auch so wie sie sollen
Jetzt muss ich mal schauen, welche Einträge da geblockt werden, schätze aber dass es die Node.js Server-side JavaScript ist.
Ich danke euch beiden vielmals, dass ihr mich wachgerüttelt habt.
Aber eine Frage habe ich noch.
Ist es normal, dass sich der "CUxD rpc" weiterhin alle "Verbindungs-Check Interval(sekunden)", bei mir nun wieder 180, vorher zum testen 60 Sekunden, disconnected und sofort wieder connected ?
Das machen die beiden anderen (rfd und wired) nicht.
Wie hoch sollte man den Verbindungs-Check Interval einstellen? Bei 180 belassen oder ruhig höher stellen?
So, nochmal DANKE, DANKE, DANKE!!!!
Beste Grüße
Tom
-
Ich brech ins Essen :oops: :lol: :lol: :lol:
Sorry für den Ausdruck, aber das hat mich jetzt mehrere Abende und unzählige Stunden gekostet, ölfzig mal de und wieder installiert, drölfzig mal Adapter an und aus gestellt und ich weiß nicht mehr wie oft die CCU resetet. :? :? :?
Es war die Firewall. :shock: :shock: :shock:
Das hatte ich gar nicht auf dem Schirm. Dachte immer, wenn was geblockt wird, meldet die sich mit einem Popup Fenster, so ist sie nämlich eingestellt.
Hab sie grad mal zum testen komplett deaktiviert und siehe da, alle Adapter und Instanzen haben sich sofort verbunden und die CCU2 ist flott und sauber ansprechbar.
Und die "Synchronisiere Geräte neu (einmalig)" Haken verschwinden nun auch so wie sie sollen
Jetzt muss ich mal schauen, welche Einträge da geblockt werden, schätze aber dass es die Node.js Server-side JavaScript ist.
Ich danke euch beiden vielmals, dass ihr mich wachgerüttelt habt.
Aber eine Frage habe ich noch.
Ist es normal, dass sich der "CUxD rpc" weiterhin alle "Verbindungs-Check Interval(sekunden)", bei mir nun wieder 180, vorher zum testen 60 Sekunden, disconnected und sofort wieder connected ?
Das machen die beiden anderen (rfd und wired) nicht.
Wie hoch sollte man den Verbindungs-Check Interval einstellen? Bei 180 belassen oder ruhig höher stellen?
So, nochmal DANKE, DANKE, DANKE!!!!
Beste Grüße
Tom `
Hey Tom,
habe das gleiche Problem !!! wo hast du die Einstellungen vorgenommen???
grüße
Svemo
-
Hallo,
sorry erstmal fürs späte melden. Bin z.Z. total im Stress. Der Bau ging los und ich hab aus zeitgründen hier nicht rein schauen können.
Bei mir hat sich eigentlich ein anderer "dummer" Fehler eingeschlichen. Denn anscheinend hat mich Windows gefragt, ob ich es in der Firewall blocken oder freigeben möchte. Da war alles in Ordnung und da muss mal eigentlich keine Einstellungen mehr vornehmen.
Ich muss aber irgendwann mal in der Systemsteuerung " Diesen Computer im Netzwerk sichtbar machen auf Nein gestellt haben. Das hat aber zur Folge, dass die Firewall nicht auf Privat, sondern auf Öffentlich gestellt wird. Und unter öffentlich ist Node.js nämlich "richtigerweise" geblockt.
Viele Grüße
Tom
-
Hallo,
hatte die letzten zwei Tage das selbe Problem.
IObroker konnte sich nicht mehr mit der CCU2 verbinden.
Web Oberfläche der CCU selbst war instabil.
Durch den Thread hier bin ich dann auch auf die Windows FW gestoßen.
Das "große Creator Update" hatte die FW einfach wieder eingeschaltet, ohne Bescheid zu sagen.
TIP: nach dem ausschalten der FW CCU und IOBroker einmal durchstarten.
