• Kunden aus Hessen und Nordrhein-Westfalen können über die Rufnummer 0221 / 466 191 00 Hilfe bei allen Problemen in Anspruch nehmen.
    Kunden aus Baden-Württemberg können über die Rufnummer 0711 / 54 888 150 Hilfe bei allen Problemen in Anspruch nehmen.

Unitymedia Technicolor TC4400 Docsis 3.1 Modem Info Thread

Diskutiere Technicolor TC4400 Docsis 3.1 Modem Info Thread im Internet und Telefon über das TV-Kabelnetz Forum im Bereich Internet und Telefon; Ist doch durchaus nicht ungewöhnlich, dass während der Umkonfigurierung des CMTS dieser nicht aktiv ist... von da her ist das "abgesoffene"...
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.526
why_ schrieb:
Interessant sieht das aus.
Zum Vergrößern anklicken....

Ist doch durchaus nicht ungewöhnlich, dass während der Umkonfigurierung des CMTS dieser nicht aktiv ist... von da her ist das "abgesoffene" Spektrum ab 477 MHz aufwärts nicht überraschend ...
Irritierend ist die "Zacke" bei 620 MHz ... Ingress?
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.527
Leider hat auch der neue OFDMA Kanal scheinbar nicht viel gebracht. Aktuell wieder 10-15 Mbit Upload von 50.
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.528
Ich habe den Verdacht, dass im Upload einige wenige Power-Uploader im Segment reichen, um es zuzustopfen ...
Filesharing, Server betreiben o. Ä. könnte das Problem sein ...

Eine Möglichkeit, mehr Informationen, als das auf der Webseite zu sehende (z. B. über SNMP?) zu bekommen, wäre intereressant - da ist ja nicht einmal die Modulationsart der Up-Kanäle zu sehen ...
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.529
Ich bleibe der Ansicht dass man durch den OFDMA nichts gewonnen hat, sofern im Segment noch viele D3.0 Geräte aktiv sind und der OFDMA gleichzeitig nicht mit höchst möglicher Modulation arbeiten kann um die erhöhte Auslastung der verbleibenden sc-qam kanäle auszugleichen. Und dadurch oftmals einige keinerlei verbesserung spüren was den upload angeht.
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.530
Selbst, wenn die Modulation nur gleichwertig von der Packungsdichte mit den vier verbleibenden DOCSIS 3.0 Up-Kanälen ist, gewinnt man eine Winzigkeit Kapazität: Statt 6,3 MHz beim weggefallenen DOCSIS 3.0 Kanal hat man nun 10,4 MHz Spektrum beim hinzugekommenen OFDMA Kanal zu Verfügung ....

Wenn die Lastverteilung "intelligent" wäre, könnten die "Early Birds" mit ihren DOCSIS 3.1 Modem profitieren ...
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.531
MartinP_Do schrieb:
Ich habe den Verdacht, dass im Upload einige wenige Power-Uploader im Segment reichen, um es zuzustopfen ...
Filesharing, Server betreiben o. Ä. könnte das Problem sein ...

Eine Möglichkeit, mehr Informationen, als das auf der Webseite zu sehende (z. B. über SNMP?) zu bekommen, wäre intereressant - da ist ja nicht einmal die Modulationsart der Up-Kanäle zu sehen ...
Zum Vergrößern anklicken....
Also die Vodafone Station (Arris TG3442de) müsste sich über SNMP auslesen lassen.
Zumindest gibt es die entsprechende MIB dazu:


Folgende Ports sind innerhalb des Heimnetzes auf der VF Station erreichbar:

Code: 
PORT STATE SERVICE
22/tcp filtered ssh
23/tcp filtered telnet
53/tcp filtered domain
80/tcp open http
111/tcp filtered rpcbind
443/tcp open https
 
Zuletzt bearbeitet:
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.532
Der OFDMA liefert max. 40 MBit/s und ist bei mir Abends schon am Limit. Es funken also doch einige der 950 Modem hier im Segment darauf. Ich konnte auch eine Verbesserung feststellen, habe aber aktuell noch ein anderes Problem welches ich am erforschen bin. Daher nochmal die Bitte: wer Probleme mit der Leitung hat, seitdem der OFDMA aufgeschaltet ist, bitte hier melden samt Firmwareversion und Modemlog.
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.533
nur 40? das sind ja grad mal 10mbit mehr als mit dem sc-qam. War da nedmal die rede davon, dass er 40mbit mehr liefert und somit die gesamtbandbreite auf 190mbit oder so erweitert? wegen 10mbit mehr betreibt man doch nicht so einen aufwand, der sogar nach hinten losgehen kann wenn der ofdma schlecht läuft
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.534
Bei mir hat er auch kaum was gebracht. Der Upload ist nur leicht gestiegen.
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.535
Bei mir ist der Anschluss seit OFDMA Aufschaltung kaputt, Upload ist voll da, Download liegt bei 2kbyte/s.
mWSB3eY.png


Firmware ist SR70.12.20. Hat sonst noch wer das Problem mit der Firmware?
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.536
modem reset mal gemacht? was sagt das log?
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.537
ja schon mehrfach
Log
Code: 
Date/Time Facility Severity Message
Jan 1 00:00:02 daemon info MA [1436]: [udsProcess:378] Listening
Jan 1 00:00:02 user debug bootassist: [readCfgFile:1007] -> readCfgFile
Jan 1 00:00:02 user info bootassist: [readCfgFile:1012] Failed to open config file bootassist.cfg
Jan 1 00:00:02 user debug bootassist: [readCfgFile:1031] <- readCfgFile
Jan 1 00:00:02 daemon info BA [1442]: [prep:1313] Requesting DTB from kernel
Jan 1 00:00:02 daemon info BA [1442]: [main:1730] Boot Assist daemon running
Jan 1 00:00:02 daemon info BA [1442]: [main:1731] Board: 3390B0 - BCM93390DCM
Jan 1 00:00:02 daemon info BA [1442]: [main:1732] BA dev file: /dev/ba
Jan 1 00:00:02 daemon info BA [1442]: [main:1733] MBOX dev file: /dev/mbox
Jan 1 00:00:02 daemon info BA [1442]: [cmShow:980] CM Boot Image: cmboot.bin
Jan 1 00:00:02 daemon info BA [1442]: [cmShow:981] CM Run Image 0: cmrun0.bin
Jan 1 00:00:02 daemon info BA [1442]: [cmShow:982] CM Run Image 1: cmrun1.bin
Jan 1 00:00:02 daemon info BA [1442]: [cmShow:983] CM Permanent non-vol: /mnt/cmnonvol/cm_perm.bin
Jan 1 00:00:02 daemon info BA [1442]: [cmShow:984] CM Dynamic non-vol: /mnt/cmnonvol/cm_dyn.bin
Jan 1 00:00:02 daemon info BA [1442]: [cmShow:985] CM Data: /tmp/cm_data.bin
Jan 1 00:00:02 daemon info BA [1442]: [main:1739] RG: auto
Jan 1 00:00:02 daemon info BA [1442]: [main:1740] STB: auto
Jan 1 00:00:02 daemon info BA [1442]: [main:1741] CM: auto
Jan 1 00:00:02 daemon info BA [1442]: [main:1742] Boot: parallel
Jan 1 00:00:02 daemon err BA [1442]: [cntrlProcess:693] On battery, parallel boot mode is not available! Forced to "normal".
Jan 1 00:00:02 daemon info BA [1442]: [cntrlProcess:697] BMU Power state: Battery
Jan 1 00:00:02 daemon info BA [1442]: [cntrlProcess:698] OTP: 0x18000003 0x00000000
Jan 1 00:00:02 daemon info BA [1442]: [cntrlProcess:699] CM Power: Unknown
Jan 1 00:00:02 daemon info BA [1442]: [cntrlProcess:700] CM state: Unknown
Jan 1 00:00:02 daemon info BA [1442]: [cntrlProcess:701] RG Power: High Power
Jan 1 00:00:02 daemon info BA [1442]: [cntrlProcess:702] RG state: Running
Jan 1 00:00:02 daemon info BA [1442]: [cntrlProcess:703] STB Power: Unknown
Jan 1 00:00:02 daemon info BA [1442]: [cntrlProcess:704] STB state: Unknown
Jan 1 00:00:02 daemon info BA [1442]: [cntrlProcess:705] SVM Power: High Power
Jan 1 00:00:02 daemon info BA [1442]: [cntrlProcess:706] SVM state: Running
Jan 1 00:00:02 daemon info BA [1442]: [show_map:551] ARM boot ROM:
Jan 1 00:00:02 daemon info BA [1442]: [show_map:553] Memory: 0x10000@0x9430000 (64kB@148MB)
Jan 1 00:00:02 daemon info BA [1442]: [show_map:558] TP1:
Jan 1 00:00:02 daemon info BA [1442]: [show_map:560] Memory: 0x1400000@0x8000000 (20MB@128MB)
Jan 1 00:00:02 daemon info BA [1442]: [show_map:563] CM:
Jan 1 00:00:02 daemon info BA [1442]: [show_map:565] Memory: 0x3f00000@0x4000000 (63MB@64MB)
Jan 1 00:00:02 daemon info BA [1442]: [show_atw:503] ATW[0]: 0x4000000 from 0x4000000 to 0x0 (64MB from 64MB to 0MB)
Jan 1 00:00:02 daemon info BA [1442]: [show_atw:518] For clients: 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0a 0x0b 0x0c 0x0d 0x0e 0x0f 0x10 0x11 0x12 0x1b 0x1e
Jan 1 00:00:02 daemon info BA [1442]: [show_map:568] LEAP:
Jan 1 00:00:02 daemon info BA [1442]: [show_map:570] 0x100000@0x7f00000 (1MB@127MB)
Jan 1 00:00:02 daemon info BA [1442]: [show_map:572] CM DSP:
Jan 1 00:00:02 daemon info BA [1442]: [show_atw:503] ATW[1]: 0x200000 from 0x8000000 to 0x7e00000 (2MB from 128MB to 126MB)
Jan 1 00:00:02 daemon info BA [1442]: [show_atw:518] For clients: 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0a 0x0b 0x0c 0x0d 0x0e 0x0f 0x12 0x1b 0x1e
Jan 1 00:00:02 daemon info BA [1442]: [show_map:575] CM BOOT:
Jan 1 00:00:02 daemon info BA [1442]: [show_atw:503] ATW[2]: 0x10000 from 0x9400000 to 0x1fc00000 (0MB from 148MB to 508MB)
Jan 1 00:00:02 daemon info BA [1442]: [show_atw:518] For clients: 0x12
Jan 1 00:00:02 daemon info BA [1442]: [show_map:578] CM <-> Host Xfer:
Jan 1 00:00:02 daemon info BA [1442]: [show_map:580] 2 buffers - 0x20000@0x9410000 (128KB@148MB)
Jan 1 00:00:02 daemon info BA [1442]: [cmBootToMem:691] Opening cmboot.bin
Jan 1 00:00:02 daemon info BA [1442]: [cmPower:852] Powering on CM
Jan 1 00:00:04 user notice kernel: brcmklogd: Started
Jan 1 00:00:04 user info kernel: Booting Linux on physical CPU 0x0
Jan 1 00:00:04 user notice kernel: Linux version 3.14.28-rgProd_6.1.0mp1 (tc4400_ref@rennslxcomp35) (gcc version 4.8.5 (Broadcom stbgcc-4.8-1.5) ) #5 SMP Wed Oct 26 12:47:20 CEST 2016
Jan 1 00:00:04 user info kernel: CPU: ARMv7 Processor [420f00f3] revision 3 (ARMv7), cr=30c7387d
Jan 1 00:00:04 user info kernel: CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Jan 1 00:00:04 user info kernel: Machine model: BCM93390DCM
Jan 1 00:00:04 user info kernel: moving dtb from 0x0000000007636000 to 0x000000000076eb04
Jan 1 00:00:04 user info kernel: Memory policy: Data cache writealloc
Jan 1 00:00:04 user debug kernel: On node 0 totalpages: 65536
Jan 1 00:00:04 user debug kernel: Normal zone: 512 pages used for memmap
Jan 1 00:00:04 user debug kernel: Normal zone: 0 pages reserved
Jan 1 00:00:04 user debug kernel: Normal zone: 65536 pages, LIFO batch:15
Jan 1 00:00:04 user info kernel: MCP: Disabling write pairing
Jan 1 00:00:04 user info kernel: PERCPU: Embedded 8 pages/cpu @cfddd000 s8768 r8192 d15808 u32768
Jan 1 00:00:04 user debug kernel: pcpu-alloc: s8768 r8192 d15808 u32768 alloc=8*4096
Jan 1 00:00:04 user debug kernel: pcpu-alloc: [0] 0 [0] 1
Jan 1 00:00:04 user warn kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Jan 1 00:00:04 user notice kernel: Kernel command line: ubi.mtd=flash1.rg0 rootfstype=ubifs root=ubi0:rootfs platformboot ubifs_apps jffs2_data coherent_pool=1M noconsole console=null
Jan 1 00:00:04 user info kernel: PID hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 00:00:04 user info kernel: Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Jan 1 00:00:04 user info kernel: Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Jan 1 00:00:04 user warn kernel: Memory: 92396K/262144K available (5265K kernel code, 257K rwdata, 1584K rodata, 260K init, 200K bss, 169748K reserved, 0K highmem)
Jan 1 00:00:04 user notice kernel: Virtual kernel memory layout:
Jan 1 00:00:04 user notice kernel: vector : 0xffff0000 - 0xffff1000 ( 4 kB)
Jan 1 00:00:04 user notice kernel: fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
Jan 1 00:00:04 user notice kernel: vmalloc : 0xd0800000 - 0xff000000 ( 744 MB)
Jan 1 00:00:04 user notice kernel: lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
Jan 1 00:00:04 user notice kernel: pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
Jan 1 00:00:04 user notice kernel: modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
Jan 1 00:00:04 user notice kernel: .text : 0xc0008000 - 0xc06b8848 (6851 kB)
Jan 1 00:00:04 user notice kernel: .init : 0xc06b9000 - 0xc06fa240 ( 261 kB)
Jan 1 00:00:04 user notice kernel: .data : 0xc06fc000 - 0xc073c758 ( 258 kB)
Jan 1 00:00:04 user notice kernel: .bss : 0xc073c760 - 0xc076eb04 ( 201 kB)
Jan 1 00:00:04 user info kernel: Hierarchical RCU implementation.
Jan 1 00:00:04 user info kernel: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
Jan 1 00:00:04 user info kernel: RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
Jan 1 00:00:04 user info kernel: NR_IRQS:16 nr_irqs:16 16
Jan 1 00:00:04 user info kernel: irq_brcmstb_l2: registered L2 intc (mem: 0xfc403000, parent irq: 95)
Jan 1 00:00:04 user info kernel: irq_brcmstb_l2: registered L2 intc (mem: 0xfc4a1000, parent irq: 63)
Jan 1 00:00:04 user info kernel: irq_brcmstb_l2: registered L2 intc (mem: 0xfc410640, parent irq: 97)
Jan 1 00:00:04 user info kernel: irq_brcmstb_l2: registered L2 intc (mem: 0xfc431200, parent irq: 50)
Jan 1 00:00:04 user info kernel: irq_bcm7120_l2: registered BCM7120 L2 intc (mem: 0xfc40a600, parent IRQ(s): 2)
Jan 1 00:00:04 user info kernel: irq_bcm7120_l2: registered BCM7120 L2 intc (mem: 0xfc417200, parent IRQ(s): 3)
Jan 1 00:00:04 user info kernel: Architected cp15 timer(s) running at 27.00MHz (virt).
Jan 1 00:00:04 user info kernel: sched_clock: 56 bits at 27MHz, resolution 37ns, wraps every 2545165795328ns
Jan 1 00:00:04 user info kernel: Switching to timer-based delay loop
Jan 1 00:00:04 user info kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 54.00 BogoMIPS (lpj=270000)
Jan 1 00:00:04 user info kernel: pid_max: default: 32768 minimum: 301
Jan 1 00:00:04 user info kernel: Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 00:00:04 user info kernel: Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan 1 00:00:04 user info kernel: CPU: Testing write buffer coherency: ok
Jan 1 00:00:04 user info kernel: CPU0: update cpu_power 1024
Jan 1 00:00:04 user info kernel: CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Jan 1 00:00:04 user info kernel: Setting up static identity map for 0x503ee0 - 0x503f38
Jan 1 00:00:04 user warn kernel: CPU1: Booted secondary processor
Jan 1 00:00:04 user info kernel: CPU1: update cpu_power 1024
Jan 1 00:00:04 user info kernel: CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Jan 1 00:00:04 user info kernel: Brought up 2 CPUs
Jan 1 00:00:04 user info kernel: SMP: Total of 2 processors activated.
Jan 1 00:00:04 user info kernel: CPU: All CPU(s) started in SVC mode.
Jan 1 00:00:04 user info kernel: devtmpfs: initialized
Jan 1 00:00:04 user info kernel: VFP support v0.3: implementor 42 architecture 4 part 00 variant 0 rev 0
Jan 1 00:00:04 user info kernel: pinctrl core: initialized pinctrl subsystem
Jan 1 00:00:04 user info kernel: regulator-dummy: no parameters
Jan 1 00:00:04 user info kernel: NET: Registered protocol family 16
Jan 1 00:00:04 user info kernel: DMA: preallocated 1024 KiB pool for atomic coherent allocations
Jan 1 00:00:04 user info kernel: cpuidle: using governor ladder
Jan 1 00:00:04 user info kernel: cpuidle: using governor menu
Jan 1 00:00:04 user info kernel: syscon f0404000.syscon: regmap [mem 0xf0404000-0xf040452f] registered
Jan 1 00:00:04 user info kernel: syscon f04a2400.syscon: regmap [mem 0xf04a2400-0xf04a27ff] registered
Jan 1 00:00:04 user info kernel: syscon f0450000.syscon: regmap [mem 0xf0450000-0xf04500ff] registered
Jan 1 00:00:04 user info kernel: syscon f0404100.syscon: regmap [mem 0xf0404100-0xf040413f] registered
Jan 1 00:00:04 user info kernel: syscon f0404140.syscon: regmap [mem 0xf0404140-0xf0404167] registered
Jan 1 00:00:04 user info kernel: syscon f0410700.syscon: regmap [mem 0xf0410700-0xf041070b] registered
Jan 1 00:00:04 user info kernel: syscon f041070c.syscon: regmap [mem 0xf041070c-0xf0410713] registered
Jan 1 00:00:04 user info kernel: syscon f1501004.syscon: regmap [mem 0xf1501004-0xf1501403] registered
Jan 1 00:00:04 user info kernel: syscon f0404080.syscon: regmap [mem 0xf0404080-0xf0404083] registered
Jan 1 00:00:04 user info kernel: syscon f04040a4.syscon: regmap [mem 0xf04040a4-0xf04040a7] registered
Jan 1 00:00:04 user info kernel: syscon f04a0154.syscon: regmap [mem 0xf04a0154-0xf04a0157] registered
Jan 1 00:00:04 user info kernel: syscon f04a0354.syscon: regmap [mem 0xf04a0354-0xf04a0357] registered
Jan 1 00:00:04 user info kernel: syscon f04a0400.syscon: regmap [mem 0xf04a0400-0xf04a0403] registered
Jan 1 00:00:04 user info kernel: No ATAGs?
Jan 1 00:00:04 user info kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
Jan 1 00:00:04 user info kernel: hw-breakpoint: maximum watchpoint size is 8 bytes.
Jan 1 00:00:04 user info kernel: bio: create slab at 0
Jan 1 00:00:04 user info kernel: brcmstb-gpio f040a000.gpio: bank=0, base=0, ngpio=32, width=32
Jan 1 00:00:04 user info kernel: brcmstb-gpio f040a000.gpio: bank=1, base=32, ngpio=32, width=32
Jan 1 00:00:04 user info kernel: brcmstb-gpio f040a000.gpio: bank=2, base=64, ngpio=32, width=32
Jan 1 00:00:04 user info kernel: brcmstb-gpio f040a000.gpio: bank=3, base=96, ngpio=32, width=7
Jan 1 00:00:04 user info kernel: brcmstb-gpio f040a000.gpio: bank=4, base=128, ngpio=32, width=6
Jan 1 00:00:04 user info kernel: brcmstb-gpio f040a000.gpio: Registered 5 banks (GPIO(s): 0-159)
Jan 1 00:00:04 user info kernel: brcmstb-gpio f0417000.gpio: bank=0, base=160, ngpio=32, width=20
Jan 1 00:00:04 user info kernel: brcmstb-gpio f0417000.gpio: bank=1, base=192, ngpio=32, width=2
Jan 1 00:00:04 user info kernel: brcmstb-gpio f0417000.gpio: Registered 2 banks (GPIO(s): 160-223)
Jan 1 00:00:04 user notice kernel: SCSI subsystem initialized
Jan 1 00:00:04 user debug kernel: libata version 3.00 loaded.
Jan 1 00:00:04 user info kernel: usbcore: registered new interface driver usbfs
Jan 1 00:00:04 user info kernel: usbcore: registered new interface driver hub
Jan 1 00:00:04 user info kernel: usbcore: registered new device driver usb
Jan 1 00:00:04 user info kernel: Switched to clocksource arch_sys_counter
Jan 1 00:00:04 user info kernel: NET: Registered protocol family 2
Jan 1 00:00:04 user info kernel: TCP established hash table entries: 2048 (order: 1, 8192 bytes)
Jan 1 00:00:04 user info kernel: TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
Jan 1 00:00:04 user info kernel: TCP: Hash tables configured (established 2048 bind 2048)
Jan 1 00:00:04 user info kernel: TCP: reno registered
Jan 1 00:00:04 user info kernel: UDP hash table entries: 256 (order: 1, 8192 bytes)
Jan 1 00:00:04 user info kernel: UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
Jan 1 00:00:04 user info kernel: NET: Registered protocol family 1
Jan 1 00:00:04 user info kernel: RPC: Registered named UNIX socket transport module.
Jan 1 00:00:04 user info kernel: RPC: Registered udp transport module.
Jan 1 00:00:04 user info kernel: RPC: Registered tcp transport module.
Jan 1 00:00:04 user info kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 1 00:00:04 user info kernel: hw perfevents: enabled with ARMv7 Cortex-A15 PMU driver, 7 counters available
Jan 1 00:00:04 user info kernel: brcm-waketimer f0417480.waketimer: registered, with irq 261
Jan 1 00:00:04 user info kernel: brcm-gisb-arb f0400000.gisb-arb: registered mem: fc400000, irqs: 259, 260
Jan 1 00:00:04 user info kernel: futex hash table entries: 512 (order: 3, 32768 bytes)
Jan 1 00:00:04 user info kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
Jan 1 00:00:04 user notice kernel: NFS: Registering the id_resolver key type
Jan 1 00:00:04 user notice kernel: Key type id_resolver registered
Jan 1 00:00:04 user notice kernel: Key type id_legacy registered
Jan 1 00:00:04 user info kernel: nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Jan 1 00:00:04 user info kernel: jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
Jan 1 00:00:04 user info kernel: fuse init (API version 7.22)
Jan 1 00:00:04 user info kernel: msgmni has been set to 180
Jan 1 00:00:04 user info kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
Jan 1 00:00:04 user info kernel: io scheduler noop registered
Jan 1 00:00:04 user info kernel: io scheduler deadline registered
Jan 1 00:00:04 user info kernel: io scheduler cfq registered (default)
Jan 1 00:00:04 user info kernel: pinctrl-single f04040a4.pinmux: allocating 1568 pins
Jan 1 00:00:04 user info kernel: pinctrl-single f04040a4.pinmux: 1568 pins at pa fc4040a4 size 196
Jan 1 00:00:04 user info kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Jan 1 00:00:04 user info kernel: f040a900.serial: ttyS0 at MMIO 0xf040a900 (irq = 108, base_baud = 5062500) is a 16550A
Jan 1 00:00:04 user info kernel: f040a940.serial: ttyS1 at MMIO 0xf040a940 (irq = 109, base_baud = 5062500) is a 16550A
Jan 1 00:00:04 user info kernel: f040a980.serial: ttyS2 at MMIO 0xf040a980 (irq = 110, base_baud = 5062500) is a 16550A
Jan 1 00:00:04 user info kernel: d3881800.serial: ttyS3 at MMIO 0xd3881800 (irq = 111, base_baud = 5062500) is a 16550A
Jan 1 00:00:04 user info kernel: brd: module loaded
Jan 1 00:00:04 user info kernel: loop: module loaded
Jan 1 00:00:04 user info kernel: brcmnand f04a2800.nand: using HIF_INTR2 cascaded IRQ
Jan 1 00:00:04 user info kernel: brcmnand f04a2800.nand: enabling FLASH_DMA
Jan 1 00:00:04 user info kernel: nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xf1
Jan 1 00:00:04 user info kernel: nand: Macronix MX30LF1G18AC
Jan 1 00:00:04 user info kernel: nand: 128MiB, SLC, page size: 2048, OOB size: 64
Jan 1 00:00:04 user info kernel: brcmnand f04a2800.nand: 128MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, BCH-4
Jan 1 00:00:04 user info kernel: Bad block table found at page 65472, version 0x01
Jan 1 00:00:04 user info kernel: Bad block table found at page 65408, version 0x01
Jan 1 00:00:04 user notice kernel: 7 ofpart partitions found on MTD device f04a2800.nand
Jan 1 00:00:04 user notice kernel: Creating 7 MTD partitions on "f04a2800.nand":
Jan 1 00:00:04 user notice kernel: 0x000000000000-0x000000620000 : "flash1.kernel0"
Jan 1 00:00:04 user notice kernel: 0x000000620000-0x000000c40000 : "flash1.kernel1"
Jan 1 00:00:04 user notice kernel: 0x000000c40000-0x000001fa0000 : "flash1.cm0"
Jan 1 00:00:04 user notice kernel: 0x000001fa0000-0x000003300000 : "flash1.cm1"
Jan 1 00:00:04 user notice kernel: 0x000003300000-0x000005980000 : "flash1.rg0"
Jan 1 00:00:04 user notice kernel: 0x000005980000-0x000008000000 : "flash1.rg1"
Jan 1 00:00:04 user notice kernel: 0x000000000000-0x000008000000 : "flash1"
Jan 1 00:00:04 user err kernel: spi_brcmstb f04a3400.spi: unable to get clock
Jan 1 00:00:04 user info kernel: spi_brcmstb f04a3400.spi: 1-lane output, 3-byte address
Jan 1 00:00:04 user info kernel: spi_brcmstb f04a3400.spi: master is unqueued, this is deprecated
Jan 1 00:00:04 user warn kernel: m25p80 spi32766.0: found mx25l3205d, expected m25p80
Jan 1 00:00:04 user info kernel: m25p80 spi32766.0: mx25l3205d (4096 Kbytes)
Jan 1 00:00:04 user notice kernel: 11 ofpart partitions found on MTD device spi32766.0
Jan 1 00:00:04 user notice kernel: Creating 11 MTD partitions on "spi32766.0":
Jan 1 00:00:04 user notice kernel: 0x000000000000-0x000000100000 : "flash0.bolt"
Jan 1 00:00:04 user notice kernel: 0x000000100000-0x000000120000 : "flash0.macadr"
Jan 1 00:00:04 user notice kernel: 0x000000120000-0x000000140000 : "flash0.nvram"
Jan 1 00:00:04 user notice kernel: 0x000000140000-0x000000160000 : "flash0.nvram1"
Jan 1 00:00:04 user notice kernel: 0x000000160000-0x000000180000 : "flash0.devtree0"
Jan 1 00:00:04 user notice kernel: 0x000000180000-0x0000001a0000 : "flash0.devtree1"
Jan 1 00:00:04 user notice kernel: 0x0000001a0000-0x000000200000 : "flash0.cmnonvol0"
Jan 1 00:00:04 user notice kernel: 0x000000200000-0x000000260000 : "flash0.cmnonvol1"
Jan 1 00:00:04 user notice kernel: 0x000000260000-0x000000330000 : "flash0.rgnonvol0"
Jan 1 00:00:04 user notice kernel: 0x000000330000-0x000000400000 : "flash0.rgnonvol1"
Jan 1 00:00:04 user notice kernel: 0x000000000000-0x000000400000 : "flash0"
Jan 1 00:00:04 user info kernel: libphy: Fixed MDIO Bus: probed
Jan 1 00:00:04 daemon info MA [1436]: [cntrlProcess:742] CM state: Waiting For Runtime
Jan 1 00:00:04 daemon info BA [1442]: [cntrlProcess:799] CM state: Waiting For Runtime
Jan 1 00:00:04 user info kernel: libphy: UniMAC MDIO bus: probed
Jan 1 00:00:04 daemon info BA [1442]: [cmImageProcess:423] CM Request: (cmrun1.bin)(1)(0x80000001)
Jan 1 00:00:04 user info kernel: unimac-mdio d040062c.mdio: Broadcom UniMAC MDIO bus at 0xd09f662c
Jan 1 00:00:04 user info kernel: libphy: UniMAC MDIO bus: probed
Jan 1 00:00:04 user info kernel: unimac-mdio d4e403c0.mdio: Broadcom UniMAC MDIO bus at 0xd09f83c0
Jan 1 00:00:04 user info kernel: pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
Jan 1 00:00:04 user info kernel: usbcore: registered new interface driver pegasus
Jan 1 00:00:04 user info kernel: usbcore: registered new interface driver asix
Jan 1 00:00:04 user info kernel: usbcore: registered new interface driver ax88179_178a
Jan 1 00:00:04 user info kernel: usbcore: registered new interface driver cdc_ether
Jan 1 00:00:04 user info kernel: usbcore: registered new interface driver cdc_ncm
Jan 1 00:00:04 user err kernel: usb-brcm f1000200.usb: Clock not found in Device Tree
Jan 1 00:00:04 user err kernel: usb-brcm f1010200.usb: Clock not found in Device Tree
Jan 1 00:00:04 user info kernel: xhci-brcm: xHCI BRCM driver
Jan 1 00:00:04 user err kernel: xhci-brcm f1001000.xhci: Clock not found in Device Tree
Jan 1 00:00:04 user info kernel: xhci-brcm f1001000.xhci: xHCI Host Controller
Jan 1 00:00:04 user info kernel: xhci-brcm f1001000.xhci: new USB bus registered, assigned bus number 1
Jan 1 00:00:04 user info kernel: xhci-brcm f1001000.xhci: irq 117, io mem 0xf1001000
Jan 1 00:00:04 user info kernel: hub 1-0:1.0: USB hub found
Jan 1 00:00:04 user err kernel: hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
Jan 1 00:00:04 user info kernel: xhci-brcm f1001000.xhci: xHCI Host Controller
Jan 1 00:00:04 user info kernel: xhci-brcm f1001000.xhci: new USB bus registered, assigned bus number 2
Jan 1 00:00:04 daemon info BA [1442]: [cmImageProcess:423] CM Request: (cmrun1.bin)(2)(0x80000002)
Jan 1 00:00:04 user info kernel: hub 2-0:1.0: USB hub found
Jan 1 00:00:04 user info kernel: hub 2-0:1.0: 1 port detected
Jan 1 00:00:04 user err kernel: xhci-brcm f1011000.xhci: Clock not found in Device Tree
Jan 1 00:00:04 user info kernel: xhci-brcm f1011000.xhci: xHCI Host Controller
Jan 1 00:00:04 user info kernel: xhci-brcm f1011000.xhci: new USB bus registered, assigned bus number 3
Jan 1 00:00:04 user info kernel: xhci-brcm f1011000.xhci: irq 118, io mem 0xf1011000
Jan 1 00:00:04 user info kernel: hub 3-0:1.0: USB hub found
Jan 1 00:00:04 user err kernel: hub 3-0:1.0: config failed, hub doesn't have any ports! (err -19)
Jan 1 00:00:04 user info kernel: xhci-brcm f1011000.xhci: xHCI Host Controller
Jan 1 00:00:04 user info kernel: xhci-brcm f1011000.xhci: new USB bus registered, assigned bus number 4
Jan 1 00:00:04 user info kernel: hub 4-0:1.0: USB hub found
Jan 1 00:00:04 user info kernel: hub 4-0:1.0: 1 port detected
Jan 1 00:00:04 user info kernel: ehci-brcm: EHCI BRCM driver
Jan 1 00:00:04 user err kernel: ehci-brcm f1000300.ehci: Clock not found in Device Tree
Jan 1 00:00:04 user info kernel: ehci-brcm f1000300.ehci: EHCI Host Controller
Jan 1 00:00:04 user info kernel: ehci-brcm f1000300.ehci: new USB bus registered, assigned bus number 5
Jan 1 00:00:04 user info kernel: ehci-brcm f1000300.ehci: irq 113, io mem 0xf1000300
Jan 1 00:00:04 user info kernel: ehci-brcm f1000300.ehci: USB 2.0 started, EHCI 1.00
Jan 1 00:00:04 daemon info BA [1442]: [cmImageProcess:423] CM Request: (cmrun1.bin)(3)(0x80000003)
Jan 1 00:00:04 user info kernel: hub 5-0:1.0: USB hub found
Jan 1 00:00:04 user info kernel: hub 5-0:1.0: 1 port detected
Jan 1 00:00:04 user err kernel: ehci-brcm f1010300.ehci: Clock not found in Device Tree
Jan 1 00:00:04 user info kernel: ehci-brcm f1010300.ehci: EHCI Host Controller
Jan 1 00:00:04 user info kernel: ehci-brcm f1010300.ehci: new USB bus registered, assigned bus number 6
Jan 1 00:00:04 user info kernel: ehci-brcm f1010300.ehci: irq 114, io mem 0xf1010300
Jan 1 00:00:04 user info kernel: ehci-brcm f1010300.ehci: USB 2.0 started, EHCI 1.00
Jan 1 00:00:04 user info kernel: hub 6-0:1.0: USB hub found
Jan 1 00:00:04 user info kernel: hub 6-0:1.0: 1 port detected
Jan 1 00:00:04 user info kernel: ohci-brcm: OHCI BRCM driver
Jan 1 00:00:04 user err kernel: ohci-brcm f1000400.ohci: Clock not found in Device Tree
Jan 1 00:00:04 user info kernel: ohci-brcm f1000400.ohci: BRCM OHCI controller
Jan 1 00:00:04 user info kernel: ohci-brcm f1000400.ohci: new USB bus registered, assigned bus number 7
Jan 1 00:00:04 user info kernel: ohci-brcm f1000400.ohci: irq 115, io mem 0xf1000400
Jan 1 00:00:04 user info kernel: hub 7-0:1.0: USB hub found
Jan 1 00:00:04 user info kernel: hub 7-0:1.0: 1 port detected
Jan 1 00:00:04 user err kernel: ohci-brcm f1010400.ohci: Clock not found in Device Tree
Jan 1 00:00:04 user info kernel: ohci-brcm f1010400.ohci: BRCM OHCI controller
Jan 1 00:00:04 user info kernel: ohci-brcm f1010400.ohci: new USB bus registered, assigned bus number 8
Jan 1 00:00:04 user info kernel: ohci-brcm f1010400.ohci: irq 116, io mem 0xf1010400
Jan 1 00:00:04 user info kernel: hub 8-0:1.0: USB hub found
Jan 1 00:00:04 user info kernel: hub 8-0:1.0: 1 port detected
Jan 1 00:00:04 user info kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan 1 00:00:04 user info kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jan 1 00:00:04 user info kernel: usbcore: registered new interface driver usb-storage
Jan 1 00:00:04 user info kernel: bcm7038-wdt f040a128.watchdog: Registered Broadcom Watchdog
Jan 1 00:00:04 user info kernel: bcm7038-wdt f10b0928.watchdog: Registered Broadcom Watchdog
Jan 1 00:00:04 user info kernel: bcm7038-wdt f040a200.watchdog: Registered Broadcom Watchdog
Jan 1 00:00:04 user warn kernel: cpufreq_cpu0: failed to get cpu0 regulator: -19
Jan 1 00:00:04 user info kernel: sdhci: Secure Digital Host Controller Interface driver
Jan 1 00:00:04 user info kernel: sdhci: Copyright(c) Pierre Ossman
Jan 1 00:00:04 user info kernel: sdhci-pltfm: SDHCI platform and OF driver helper
Jan 1 00:00:04 user err kernel: sdhci-brcmstb f04a0000.sdhci: Clock not found in Device Tree
Jan 1 00:00:04 daemon info BA [1442]: [cmImageProcess:423] CM Request: (cmrun1.bin)(4)(0x80000004)
Jan 1 00:00:04 user info kernel: mmc0: no vqmmc regulator found
Jan 1 00:00:04 user info kernel: mmc0: no vmmc regulator found
Jan 1 00:00:04 user info kernel: mmc0: SDHCI controller on f04a0000.sdhci [f04a0000.sdhci] using ADMA
Jan 1 00:00:04 user info kernel: brcm-fpm: FPM with 1 pool(s)
Jan 1 00:00:04 user info kernel: brcm-dqm: DQM device cpucomm with 96 Q's
Jan 1 00:00:04 user info kernel: ethsw_init_plat: Device name: ethsw
Jan 1 00:00:04 user info kernel: ethsw_init_plat: MII port params: <0x4 0 0x3e8>
Jan 1 00:00:04 user info kernel: ethsw_init_plat: IMP port params: <0x5 0x7d0>
Jan 1 00:00:04 user info kernel: ethsw_init_plat: IMP port params: <0x7 0x7d0>
Jan 1 00:00:04 user info kernel: ethsw_init_plat: IMP port params: <0x8 0x7d0>
Jan 1 00:00:04 user info kernel: ethsw_init_plat: LED map: 0xf
Jan 1 00:00:04 user info kernel: ethsw_init_plat: Device mem: 0xd4e00000 - 0xd4e41fff
Jan 1 00:00:04 user info kernel: ethsw_init_plat: Device irq0: 145
Jan 1 00:00:04 user info kernel: ethsw_init_plat: Device irq1: 146
Jan 1 00:00:04 user info kernel: ethsw_phy: PHY port params for 0: <0x0 0x2>
Jan 1 00:00:04 user info kernel: ethsw_phy: PHY port params for 1: <0x1 0x3>
Jan 1 00:00:04 user info kernel: ethsw_phy: PHY port params for 2: <0x2 0x4>
Jan 1 00:00:04 user info kernel: ethsw_phy: PHY port params for 3: <0x3 0x5>
Jan 1 00:00:04 user info kernel: ethsw_flow_control: Enabling ACB
Jan 1 00:00:04 user info kernel: ethsw_3390: Device ID 3390
Jan 1 00:00:04 user info kernel: libphy: ethsw_mdio: probed
Jan 1 00:00:04 user info kernel: ethsw_phy: Ethsw PHY initialized
Jan 1 00:00:04 user info kernel: ethsw_api: Port 0 config reset
Jan 1 00:00:04 user info kernel: ethsw_api: Port 0 config set: auto_neg = 1, full_duplex = 1, speed = 2
Jan 1 00:00:04 user info kernel: ethsw_api: Port 0 disabled
Jan 1 00:00:04 user info kernel: ethsw_api: Port 1 config reset
Jan 1 00:00:04 user info kernel: ethsw_api: Port 1 config set: auto_neg = 1, full_duplex = 1, speed = 2
Jan 1 00:00:04 user info kernel: ethsw_api: Port 1 disabled
Jan 1 00:00:04 daemon info BA [1442]: [cmImageProcess:423] CM Request: (cmrun1.bin)(5)(0x80000005)
Jan 1 00:00:04 user info kernel: ethsw_api: Port 2 config reset
Jan 1 00:00:04 user info kernel: ethsw_api: Port 2 config set: auto_neg = 1, full_duplex = 1, speed = 2
Jan 1 00:00:04 user info kernel: ethsw_api: Port 2 disabled
Jan 1 00:00:04 user info kernel: ethsw_api: Port 3 config reset
Jan 1 00:00:04 user info kernel: ethsw_api: Port 3 config set: auto_neg = 1, full_duplex = 1, speed = 2
Jan 1 00:00:04 user info kernel: ethsw_api: Port 3 disabled
Jan 1 00:00:04 user info kernel: ethsw_proc: /proc/driver/ethsw dir and files created
Jan 1 00:00:04 user info kernel: ethsw_proc: Ethsw proc initialized
Jan 1 00:00:04 user info kernel: ethsw_init_plat: Ethsw driver probed
Jan 1 00:00:04 user info kernel: ethsw_init_plat: Ethsw module initialized
Jan 1 00:00:04 user info kernel: rpc_service_init: initializing rpc_init service
Jan 1 00:00:04 user info kernel: rpc_register_functions registered rpc_init service with 1 functions
Jan 1 00:00:04 user info kernel: rpc_service_init: initializing rpc_misc service
Jan 1 00:00:04 user info kernel: rpc_service_init: initializing rpc_flash service
Jan 1 00:00:04 user err kernel: rpc_service_init: skipping inactive rpc_nonvol service
Jan 1 00:00:04 user info kernel: rpc_service_init: initializing rpc_erouter service
Jan 1 00:00:04 user err kernel: rpc_service_init: skipping inactive rpc_erouter_pm service
Jan 1 00:00:04 user info kernel: rpc_service_init: initializing rpc_wpsctl service
Jan 1 00:00:04 user err kernel: rpc_service_init: skipping inactive rpc_bash service
Jan 1 00:00:04 user err kernel: rpc_service_init: skipping inactive rpc_testu service
Jan 1 00:00:04 user info kernel: dev-name = rg-cm
Jan 1 00:00:04 user info kernel: dqm = cpucomm
Jan 1 00:00:04 user info kernel: tx-q = 2h
Jan 1 00:00:04 user info kernel: rx-q = 3h
Jan 1 00:00:04 user err kernel: rpc_probe sent handshake message
Jan 1 00:00:04 user info kernel: dev-name = svm-cm
Jan 1 00:00:04 user info kernel: dqm = cpucomm
Jan 1 00:00:04 user info kernel: tx-q = 14h
Jan 1 00:00:04 user info kernel: rx-q = 15h
Jan 1 00:00:04 user err kernel: rpc_probe sent handshake message
Jan 1 00:00:04 user info kernel: rpc_register_functions registered rpc_misc service with 5 functions
Jan 1 00:00:04 user info kernel: gre: GRE over IPv4 demultiplexor driver
Jan 1 00:00:04 user info kernel: ip_gre: GRE over IPv4 tunneling driver
Jan 1 00:00:04 user info kernel: TCP: cubic registered
Jan 1 00:00:04 user info kernel: NET: Registered protocol family 10
Jan 1 00:00:04 user info kernel: ip6_gre: GRE over IPv6 tunneling driver
Jan 1 00:00:04 user info kernel: NET: Registered protocol family 17
Jan 1 00:00:04 user notice kernel: Bridge firewalling registered
Jan 1 00:00:04 user info kernel: Initializing MCPD Module
Jan 1 00:00:04 user info kernel: 8021q: 802.1Q VLAN Support v1.8
Jan 1 00:00:04 user notice kernel: Key type dns_resolver registered
Jan 1 00:00:04 user notice kernel: Registering SWP/SWPB emulation handler
Jan 1 00:00:04 user info kernel: regulator-dummy: disabling
Jan 1 00:00:04 user notice kernel: UBI: attaching mtd4 to ubi0
Jan 1 00:00:04 daemon info BA [1442]: [cmImageProcess:423] CM Request: (cmrun1.bin)(6)(0x80000006)
Jan 1 00:00:04 user notice kernel: UBI: scanning is finished
Jan 1 00:00:04 user notice kernel: UBI: attached mtd4 (name "flash1.rg0", size 38 MiB) to ubi0
Jan 1 00:00:04 user notice kernel: UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Jan 1 00:00:04 user notice kernel: UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Jan 1 00:00:04 user notice kernel: UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
Jan 1 00:00:04 user notice kernel: UBI: good PEBs: 308, bad PEBs: 0, corrupted PEBs: 0
Jan 1 00:00:04 user notice kernel: UBI: user volume: 2, internal volumes: 1, max. volumes count: 128
Jan 1 00:00:04 user notice kernel: UBI: max/mean erase counter: 14/4, WL threshold: 256, image sequence number: 671118203
Jan 1 00:00:04 user notice kernel: UBI: available PEBs: 0, total reserved PEBs: 308, PEBs reserved for bad PEB handling: 20
Jan 1 00:00:04 user notice kernel: UBI: background thread "ubi_bgt0d" started, PID 1163
Jan 1 00:00:04 user err kernel: Warning: unable to open an initial console.
Jan 1 00:00:04 user notice kernel: UBIFS: mounted UBI device 0, volume 0, name "rootfs", R/O mode
Jan 1 00:00:04 user notice kernel: UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Jan 1 00:00:04 user notice kernel: UBIFS: FS size: 9015296 bytes (8 MiB, 71 LEBs), journal size 4317184 bytes (4 MiB, 34 LEBs)
Jan 1 00:00:04 user notice kernel: UBIFS: reserved for root: 0 bytes (0 KiB)
Jan 1 00:00:04 user notice kernel: UBIFS: media format: w4/r0 (latest is w4/r0), UUID 035410A2-E666-4CBA-83A0-8AB80AB37A32, small LPT model
Jan 1 00:00:04 user info kernel: VFS: Mounted root (ubifs filesystem) readonly on device 0:13.
Jan 1 00:00:04 user info kernel: devtmpfs: mounted
Jan 1 00:00:04 user info kernel: Freeing unused kernel memory: 260K (c06b9000 - c06fa000)
Jan 1 00:00:04 user notice kernel: random: nonblocking pool is initialized
Jan 1 00:00:04 user notice kernel: UBI: attaching mtd2 to ubi1
Jan 1 00:00:04 user notice kernel: UBI: scanning is finished
Jan 1 00:00:04 user notice kernel: UBI: attached mtd2 (name "flash1.cm0", size 19 MiB) to ubi1
Jan 1 00:00:04 user notice kernel: UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Jan 1 00:00:04 user notice kernel: UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Jan 1 00:00:04 user notice kernel: UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
Jan 1 00:00:04 user notice kernel: UBI: good PEBs: 155, bad PEBs: 0, corrupted PEBs: 0
Jan 1 00:00:04 user notice kernel: UBI: user volume: 1, internal volumes: 1, max. volumes count: 128
Jan 1 00:00:04 user notice kernel: UBI: max/mean erase counter: 15/4, WL threshold: 256, image sequence number: 926171971
Jan 1 00:00:04 user notice kernel: UBI: available PEBs: 0, total reserved PEBs: 155, PEBs reserved for bad PEB handling: 20
Jan 1 00:00:04 user notice kernel: UBI: background thread "ubi_bgt1d" started, PID 1347
Jan 1 00:00:04 user notice kernel: UBIFS: background thread "ubifs_bgt1_1" started, PID 1354
Jan 1 00:00:04 user notice kernel: UBIFS: recovery needed
Jan 1 00:00:04 user notice kernel: UBIFS: recovery completed
Jan 1 00:00:04 user notice kernel: UBIFS: mounted UBI device 1, volume 1, name "images"
Jan 1 00:00:04 user notice kernel: UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Jan 1 00:00:04 user notice kernel: UBIFS: FS size: 15364096 bytes (14 MiB, 121 LEBs), journal size 4317184 bytes (4 MiB, 34 LEBs)
Jan 1 00:00:04 user notice kernel: UBIFS: reserved for root: 0 bytes (0 KiB)
Jan 1 00:00:04 user notice kernel: UBIFS: media format: w4/r0 (latest is w4/r0), UUID 6A92C135-875F-4AA0-88D0-52FCDB4E9822, small LPT model
Jan 1 00:00:04 daemon info BA [1442]: [cmImageProcess:423] CM Request: (cmrun1.bin)(7)(0x80000007)
Jan 1 00:00:04 user warn kernel: rdpa: module license 'Proprietary' taints kernel.
Jan 1 00:00:04 user warn kernel: Disabling lock debugging due to kernel taint
Jan 1 00:00:04 user warn kernel: RDP Physical address=0xd5000000 Virtual address = 0xd0e00000
Jan 1 00:00:04 user warn kernel: passing rdd_init_params.runner_iptv_tables_base_ptr=0x9b00000
Jan 1 00:00:04 user warn kernel: configure_runner: NATC keysize 0x100070 key element size 16 contextsize 0x400000 context element size 64
Jan 1 00:00:04 user warn kernel: rdd_init_params.runner_nat_cache_key_ptr=0xd3200000
Jan 1 00:00:04 user warn kernel: g_runner_ddr0_iptv_lookup_ptr=0xd3440000
Jan 1 00:00:04 user warn kernel: g_runner_ddr0_iptv_context_ptr=0xd3400000
Jan 1 00:00:04 user warn kernel: g_runner_ddr0_iptv_ssm_context_ptr=0xd3480000
Jan 1 00:00:04 user warn kernel: FPM_BPM phy_addr 0xd3a30000,virt_addr 0xd0dca000
Jan 1 00:00:04 user info kernel: brcm-dqnet: net device priv0
Jan 1 00:00:04 user info kernel: ethsw_api: Device eth0 connected to port 0
Jan 1 00:00:04 user info kernel: brcm-dqnet: net device eth0
Jan 1 00:00:04 user info kernel: ethsw_api: Device eth1 connected to port 1
Jan 1 00:00:04 user info kernel: brcm-dqnet: net device eth1
Jan 1 00:00:04 user info kernel: ethsw_api: Device eth2 connected to port 2
Jan 1 00:00:04 user info kernel: brcm-dqnet: net device eth2
Jan 1 00:00:04 user info kernel: ethsw_api: Device eth3 connected to port 3
Jan 1 00:00:04 user info kernel: brcm-dqnet: net device eth3
Jan 1 00:00:04 user info kernel: brcm-dqnet: net device cm0
Jan 1 00:00:04 user info kernel: device priv0 entered promiscuous mode
Jan 1 00:00:04 user info kernel: IPv6: ADDRCONF(NETDEV_UP): priv0: link is not ready
Jan 1 00:00:04 user info kernel: IPv6: ADDRCONF(NETDEV_UP): privbr: link is not ready
Jan 1 00:00:04 user info kernel: IPv6: ADDRCONF(NETDEV_UP): privbr: link is not ready
Jan 1 00:00:04 user notice kernel: UBIFS: background thread "ubifs_bgt0_1" started, PID 1727
Jan 1 00:00:04 user notice kernel: UBIFS: recovery needed
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.538
ich dachte eher an das snmp log xd
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.539
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.540
Hö? Das Modem hat doch ein Log. Dort wo man auch die Kanalinfos abruft
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.541
Doch, aber ich hab den Wald vor lauter Bäumen nicht gesehen 🤣. Ich dachte ich müsste das per SNMPwalk abziehen kannte aber die community nicht aber das CM Event Log ist heist auch SNMP Event Log.
Index Time Priority Description

1 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

2 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

3 Time Not Established Critical (3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MA...

4 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

5 Time Not Established Critical (3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MA...

6 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

7 Mon Jan 28 02:48:00 2021 Critical (3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=60:3d:26:15:9e...

8 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

9 Time Not Established Critical (3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MA...

10 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

11 Time Not Established Critical (3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MA...

12 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

13 Time Not Established Critical (3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MA...

14 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

15 Time Not Established Critical (3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MA...

16 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

17 Time Not Established Critical (3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MA...

18 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

19 Time Not Established Critical (3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MA...

20 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

21 Time Not Established Critical (3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MA...

22 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

23 Time Not Established Critical (3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MA...

24 Time Not Established Critical (3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=60:3d:2...

25 Time Not Established Critical (3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MA...

26 Time Not Established Notice (6) "Honoring MDD; IP provisioning mode = IPv4"

27 Time Not Established Warning (5) "DHCP WARNING - Non-critical field invalid in response ;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01...

28 Mon Jan 28 22:26:36 2021 Notice (6) "TLV-11 - unrecognized OID;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:6b:e0:6f;CM-QOS=1.1;CM-VE...
Zum Vergrößern anklicken....
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.542
Na wenn das Log Mal kein Grund ist, die Hotline anzurufen.
Massive Downstream Störung melden, mit Durchsatz im Kilobyte bereich. Das isn Fall für die Technik.
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.543
Ich glaube nicht das es daran liegt. Meine Werte passen eigentlich.
zRfevos.png
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.544
Ok Hotline anrufen hat mir soweit schonmal die Info gebracht das bei denen gerade wohl die Bude brennt und die mit Störungsmeldungen überhäuft werden. Mal gucken wie das dann morgen oder übermorgen aussieht.
Gibt es wohl Entschädigung für die Kunden wenn die ihr System kaputt updaten? Höhere gewallt ist das ja wohl nicht mehr.
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.545
generell störungsmeldungen oder haben sie gesagt aus deiner region?
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.546
Abend, ich hatte damals Feb 2018 die TC4400 in einer sammelbestellung hier mit bestellt. Softwarestand wurde seit dem nicht geändert. Alles wie es damals war. Wurde von UM provisioniert.
Jetzt gab es hier nem Kabelbruch und Wartung und seitdem versteht sich das Modem nicht mehr mit der FRITZ!Box dahinter. Ich kann mit NB über lan-Kabel direkt an Modem ins Internet. Die Fritz zeigt aber immer keine Verbindung an, das nichts durchkommt. Ebenfalls komm ich nicht über lan an Modem mit pc auf die gui, also mit den Bekannten logdaten. Weißt vielleicht jemand woran das liegen kann udn hat vielleicht einen Typ für mich wie ich das wieder hinbekomme? Hotline sagt, kommen zum Modem durch, können nicht mehr machen.

danke schon einmal und Gruß
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.547
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.548
Hi,

@Hitz Hast du schon einen Hardreset des Modems probiert? Dazu den Reset-Taster auf der Rückseite für mindestens 10 Sekunden gedrückt halten.
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.549
why_ schrieb:
Doch, aber ich hab den Wald vor lauter Bäumen nicht gesehen 🤣. Ich dachte ich müsste das per SNMPwalk abziehen kannte aber die community nicht aber das CM Event Log ist heist auch SNMP Event Log.
Zum Vergrößern anklicken....
War das direkt nach dem Neustart des Modem? Sieht für mich jetzt erst mal normal aus. Hier gibt es jemanden mit OFDMA und der .20 der keine Probleme hat. Ich würde aber immer nochmal den Idiotentest machen und das Modem mal direkt an einen Rechner hängen und testen.
 
  • Technicolor TC4400 Docsis 3.1 Modem Info Thread Beitrag #9.550
Ja war direkt nach dem Neustart des Modems. Problem ist Identisch wenn ich das Modem direkt an den PC anschließe.
root@raspberrypi4b:~# iperf3 -c speedtest.myloc.de -p 5200 -4 -R
Connecting to host speedtest.myloc.de, port 5200
Reverse mode, remote host speedtest.myloc.de is sending
[ 5] local 10.13.37.2 port 39406 connected to 37.157.253.246 port 5200
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 3.00-4.00 sec 25.5 KBytes 209 Kbits/sec
[ 5] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 5.00-6.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 6.00-7.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 8.00-9.00 sec 0.00 Bytes 0.00 bits/sec
[ 5] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.28 sec 105 KBytes 83.4 Kbits/sec 18 sender
[ 5] 0.00-10.00 sec 25.5 KBytes 20.8 Kbits/sec receiver

iperf Done.
root@raspberrypi4b:~# iperf3 -c speedtest.myloc.de -p 5200 -4
Connecting to host speedtest.myloc.de, port 5200
[ 5] local 10.13.37.2 port 39454 connected to 37.157.253.246 port 5200
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 4.94 MBytes 41.4 Mbits/sec 7 156 KBytes
[ 5] 1.00-2.00 sec 6.21 MBytes 52.1 Mbits/sec 1 130 KBytes
[ 5] 2.00-3.00 sec 4.66 MBytes 39.1 Mbits/sec 0 154 KBytes
[ 5] 3.00-4.00 sec 5.97 MBytes 50.0 Mbits/sec 3 130 KBytes
[ 5] 4.00-5.00 sec 6.21 MBytes 52.1 Mbits/sec 0 163 KBytes
[ 5] 5.00-6.00 sec 6.21 MBytes 52.1 Mbits/sec 0 189 KBytes
[ 5] 6.00-7.00 sec 6.15 MBytes 51.6 Mbits/sec 1 161 KBytes
[ 5] 7.00-8.00 sec 6.21 MBytes 52.1 Mbits/sec 1 132 KBytes
[ 5] 8.00-9.00 sec 6.21 MBytes 52.1 Mbits/sec 0 163 KBytes
[ 5] 9.00-10.00 sec 6.15 MBytes 51.6 Mbits/sec 2 136 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 58.9 MBytes 49.4 Mbits/sec 15 sender
[ 5] 0.00-10.01 sec 58.4 MBytes 48.9 Mbits/sec receiver

iperf Done.
Zum Vergrößern anklicken....
Download quasi nicht vorhanden, Upload voll da.
 
Zuletzt bearbeitet:
Thema:

Technicolor TC4400 Docsis 3.1 Modem Info Thread

Technicolor TC4400 Docsis 3.1 Modem Info Thread - Ähnliche Themen

Netgear CM2000 (US Modem)

Netgear CM2000 (US Modem): Dank DOCSIS 3.1 und dem dortigen Wegfall der Unterscheidung zwischen DOCSIS und EuroDOCSIS sind einige Modems aus den USA durchaus im Vodafone...
Unitymedia

Technicolor CGA4233 Docsis 3.1 Router Info Tread

Unitymedia Technicolor CGA4233 Docsis 3.1 Router Info Tread: Wie auch schon bei TC4400 dient dieser Thread zum Sammeln von Informationen zum Technicolor CGA4233. Default login: user / VTmgQapcEUaE Link zum...
Unitymedia

Kabelmodem Arris CM8200B

Unitymedia Kabelmodem Arris CM8200B: Moin, Das Arris CM8200B wurde hier schon gelegentlich erwähnt, aber nie vertiefend. Da bei mir seit ein paar Tagen eines herumsteht starte ich...
Unitymedia

Cisco EPC3208 verliert immer Verbindung -> Vodafone Station als Lösung? (DOCSIS 3.1 schuld?)

Unitymedia Cisco EPC3208 verliert immer Verbindung -> Vodafone Station als Lösung? (DOCSIS 3.1 schuld?): Nabend! Ich habe seit 25.11. plötzlich ein massives Problem mit meinem Anschluß, und könnte etwas Aufklärung von Insidern brauchen bevor ich zur...
Unitymedia

[Q] Probleme mit Bridge Network Model Virtualisierungsserver

Unitymedia [Q] Probleme mit Bridge Network Model Virtualisierungsserver: Hallo! Ich habe eine Virtualisierungsplattform mit Web-Oberfläche (Proxmox VE 3.3) aufgesetzt und den Server direkt mit dem Kabel-Gateway TC7200...
Registrieren

Neueste Beiträge

Oben