[Libwebsockets] 100% CPU and lws_adopt_socket: fail. Possible LWS issue?

Andy Green andy at warmcat.com
Wed Jul 6 16:28:49 CEST 2016



On July 6, 2016 9:31:37 PM GMT+08:00, Thomas Spitz <thomas.spitz at hestia-france.com> wrote:
>Hello Andy,
>
>I was quite busy on other issues and haven't taken time to answer,
>sorry
>for that.
>
>In the meanwhile, I have had this problem a fifth time in production, I
>am
>now on it again ;-) Here is my first "poor" answers
>
>This means spinning in a tight loop and the app is dead?  Or just never
>> idle and the app continues to work?  I assume the latter.
>
>
>It is indeed "just never idle and the app continues to work". I have no
>gdb
>in production (as it is an embedded device) but using strace I haven't

Plenty of embedded devices have gdb, it's not that big.

>find
>anything particular in my main program (just my standard program log).
>Libwebsocket is launched as a thread child of my main program.
>
>Contrary to https://github.com/warmcat/libwebsockets/issues/475 I have
>no
>
>> recv(27, "", 1, 0) = 0
>
>in loop (at least after the problem occured) but still many active

Ok that's good to know.  Because I think that problem should always have been handled by poll() noticing it.

>network
>connections listed by netstat -tn when the problem occured (this list
>never
>get empty anymore after the problem):
>
>> Active Internet connections (w/o servers)
>> Proto Recv-Q Send-Q Local Address           Foreign Address        
>State
>>
>> tcp        0      0 192.168.1.4:122         192.168.1.65:33920
>>  ESTABLISHED
>> tcp      187      0 ::ffff:192.168.1.4:443  ::ffff:80.12.58.33:58407
>> CLOSE_WAIT
>> tcp      187      0 ::ffff:192.168.1.4:443 
>::ffff:109.109.109.109:49570
>> CLOSE_WAIT
>> tcp      132      0 ::ffff:192.168.1.4:443 
>::ffff:67.159.157.150:34743
>> ESTABLISHED
>> tcp      132      0 ::ffff:192.168.1.4:443 
>::ffff:67.159.157.150:34896
>> ESTABLISHED
>> tcp      187      0 ::ffff:192.168.1.4:443  ::ffff:78.253.8.33:52419
>> CLOSE_WAIT
>> tcp       51      0 ::ffff:192.168.1.4:443 
>::ffff:123.192.26.167:1134
>> CLOSE_WAIT
>> tcp      208      0 ::ffff:192.168.1.4:443 
>::ffff:109.109.109.109:49541
>> CLOSE_WAIT
>> tcp      132      0 ::ffff:192.168.1.4:443 
>::ffff:67.159.157.150:34597
>> ESTABLISHED
>> tcp      187      0 ::ffff:192.168.1.4:443  ::ffff:80.12.58.33:58414
>> CLOSE_WAIT
>> tcp      208      0 ::ffff:192.168.1.4:443 
>::ffff:109.109.109.109:61639
>> CLOSE_WAIT
>> tcp      187      0 ::ffff:192.168.1.4:443 
>::ffff:109.7.119.229:52183
>> CLOSE_WAIT
>> tcp      140      0 ::ffff:192.168.1.4:443 
>::ffff:141.212.122.161:47311
>> CLOSE_WAIT
>> tcp      200      0 ::ffff:192.168.1.4:443  ::ffff:192.168.1.70:53571
>> ESTABLISHED
>> tcp      165      0 ::ffff:192.168.1.4:443 
>::ffff:169.54.244.93:43572
>> CLOSE_WAIT
>> tcp      187      0 ::ffff:192.168.1.4:443 
>::ffff:78.244.122.170:55908
>> CLOSE_WAIT
>> tcp      186      0 ::ffff:192.168.1.4:443 
>::ffff:78.219.127.56:58399
>> ESTABLISHED
>> tcp       32      0 ::ffff:192.168.1.4:443 
>::ffff:67.159.157.150:60634
>> CLOSE_WAIT
>> tcp       49      0 ::ffff:192.168.1.4:443 
>::ffff:91.17.136.170:63813
>> CLOSE_WAIT
>> tcp      163      0 ::ffff:192.168.1.4:443 
>::ffff:169.54.244.89:50184
>> CLOSE_WAIT
>> tcp      187      0 ::ffff:192.168.1.4:443  ::ffff:80.12.58.33:58409
>> CLOSE_WAIT
>> tcp      195      0 ::ffff:192.168.1.4:443 
>::ffff:109.109.109.109:55753
>> CLOSE_WAIT
>> tcp      187      0 ::ffff:192.168.1.4:443 
>::ffff:109.109.109.109:55489
>> CLOSE_WAIT
>> tcp      208      0 ::ffff:192.168.1.4:443 
>::ffff:109.109.109.109:57424
>> CLOSE_WAIT
>> tcp      195      0 ::ffff:192.168.1.4:443 
>::ffff:109.109.109.109:63967
>> CLOSE_WAIT
>> tcp      123      0 ::ffff:192.168.1.4:443 
>::ffff:184.105.139.70:38942
>> CLOSE_WAIT
>> tcp      132      0 ::ffff:192.168.1.4:443 
>::ffff:67.159.157.150:50328
>> ESTABLISHED
>> tcp      123      0 ::ffff:192.168.1.4:443  ::ffff:74.82.47.4:41196
>> CLOSE_WAIT
>
>I also made a test program that progressively increase the number of
>simultenous client connections and all connections are stopped (after 1
>minute of TIME_WAIT in some case)

TIME_WAIT is okay.

CLOSE_WAIT isn't okay.  I'll check this out tomorrow.

>At this point I still don't see why connections are "dead locked" in
>CLOSE_WAIT OR ESTABLISHED after hours of disconnection ... I thought
>there
>would be timeout for that
>
>I understand the need of
>
>> To discover that a peer has passively died you must write on the
>> connection periodically.  Because otherwise there is no way of
>learning
>> the connection is silently no longer complete.  ws itself provide
>PING
>> and PONG control packets for that purpose.
>
>to discover quicker that a link is over (I am going to do it under my
>protocol) but I thought that TCP layers would discover that the link is
>over after a timeout in order not to keep dead sockets?

No, by default tcp doesn't randomly send things.  You can use "tcp keepalives" to make it randomly send things at specified intervals as probes for a dead link.  Otherwise if you're not sending anything either at application layer it can go on forever believing it's just idle.  (In ssl case that might do its own housekeeping on the link, I'm not sure of the conditions.)

This is talking about situations where the physical link disappears without notification, eg phone runs out of battery.  Just closing the connection with the link still valid should be nice and clean.

>Just for info
>
>> > I also tried cat /proc/my_devicePID/fd:
>> > > 0   10  12  14  16  18  2   21  23  25  27  29  30  32  34  36 
>38
>> > >  4   41  43  45  47  49  50  52  54  56  58  6   61  63  65  67 
>69
>> > >  70  72  74  76  78  8   81  83  85  87  89  90  92  94
>> > > 1   11  13  15  17  19  20  22  24  26  28  3   31  33  35  37 
>39
>> > >  40  42  44  46  48  5   51  53  55  57  59  60  62  64  66  68 
>7
>> > >   71  73  75  77  79  80  82  84  86  88  9   91  93
>> Hm do you mean ls that dir?  If you look with ls -l, at least on
>modern
>> Linux, you will get a lot more info, such as whether it's a socket or
>> if a file, which file it's open on.
>
>ls -l helped me a lot, I had a problem in my code not closing fd (as
>suggested it has no link with lws)

Great.

-Andy

>Best regards,
>Thomas
>
>2016-06-29 0:46 GMT+02:00 Andy Green <andy at warmcat.com>:
>
>> On Tue, 2016-06-28 at 16:42 +0200, Thomas Spitz wrote:
>> > Hi everyone,
>> >
>> > Since may 4, I have experienced 100% CPU blocage of my app 4 times
>on
>>
>> This means spinning in a tight loop and the app is dead?  Or just
>never
>> idle and the app continues to work?  I assume the latter.
>>
>> If it's the former, attach gdb to the process using gdb -p <pid> to
>get
>> a backtrace of where it is stuck.
>>
>> > different devices. I still think it comes from my code but I don't
>> > know yet exactly why. Thanks to netstat:
>> > > netstat -tnn
>> > > Active Internet connections (w/o servers)
>> > > Proto Recv-Q Send-Q Local Address           Foreign Address
>> > > State
>> > > tcp        0    268 192.168.0.22:122        109.109.109.109:50263
>> > > ESTABLISHED
>> > > tcp      123      0 ::ffff:192.168.0.22:443
>> > > ::ffff:184.105.139.68:39232 CLOSE_WAIT
>> > > tcp      518      0 ::ffff:192.168.0.22:443
>> > > ::ffff:198.20.70.114:59438 CLOSE_WAIT
>> > > tcp      123      0 ::ffff:192.168.0.22:443
>> > > ::ffff:184.105.139.67:47286 CLOSE_WAIT
>> > > tcp      123      0 ::ffff:192.168.0.22:443
>> > > ::ffff:184.105.247.195:47204 CLOSE_WAIT
>> > > tcp      200      0 ::ffff:192.168.0.22:443
>> > > ::ffff:88.162.134.175:51556 ESTABLISHED
>> > > tcp       65      0 ::ffff:192.168.0.22:443
>> > > ::ffff:169.229.3.91:35702 CLOSE_WAIT
>> > > tcp      200      0 ::ffff:192.168.0.22:443
>> > > ::ffff:109.109.109.109:53087 ESTABLISHED
>> > > tcp      144      0 ::ffff:192.168.0.22:443
>> > > ::ffff:141.212.122.161:2274 CLOSE_WAIT
>> > > tcp      194      0 ::ffff:192.168.0.22:443
>> > > ::ffff:88.162.134.175:40025 ESTABLISHED
>> > > tcp       65      0 ::ffff:192.168.0.22:443
>> > > ::ffff:169.229.3.91:49901 CLOSE_WAIT
>> > > tcp      200      0 ::ffff:192.168.0.22:443
>> > > ::ffff:88.162.134.175:51303 ESTABLISHED
>> > > tcp       39      0 ::ffff:192.168.0.22:443
>> > > ::ffff:198.20.70.114:60007 CLOSE_WAIT
>> > > tcp      100      0 ::ffff:192.168.0.22:443
>> > > ::ffff:180.97.106.162:39822 CLOSE_WAIT
>> > > tcp      194      0 ::ffff:192.168.0.22:443
>> > > ::ffff:88.162.134.175:52305 ESTABLISHED
>> > > tcp       65      0 ::ffff:192.168.0.22:443
>> > > ::ffff:169.229.3.91:33149 CLOSE_WAIT
>> > > tcp      130      0 ::ffff:192.168.0.22:443
>> > > ::ffff:141.212.122.193:21996 CLOSE_WAIT
>> > > tcp      110      0 ::ffff:192.168.0.22:443
>> > > ::ffff:141.212.122.145:41883 CLOSE_WAIT
>> > > tcp       69      0 ::ffff:192.168.0.22:443
>> > > ::ffff:190.103.31.165:40933 CLOSE_WAIT
>> > > tcp      144      0 ::ffff:192.168.0.22:443
>> > > ::ffff:141.212.122.209:59510 CLOSE_WAIT
>> > > tcp      106      0 ::ffff:192.168.0.22:443
>> > > ::ffff:185.17.104.10:59301 CLOSE_WAIT
>> > > tcp        1      0 ::ffff:192.168.0.22:443
>> > > ::ffff:193.9.245.64:37363 CLOSE_WAIT
>> > > tcp      194      0 ::ffff:192.168.0.22:443
>> > > ::ffff:80.215.1.151:4863 ESTABLISHED
>> > > tcp      194      0 ::ffff:192.168.0.22:443
>> > > ::ffff:88.162.134.175:41115 ESTABLISHED
>> > > tcp        1      0 ::ffff:192.168.0.22:443
>> > > ::ffff:104.155.220.255:63620 CLOSE_WAIT
>> > > tcp      133      0 ::ffff:192.168.0.22:443
>> > > ::ffff:193.9.245.64:37717 CLOSE_WAIT
>> > > tcp       49      0 ::ffff:192.168.0.22:443
>> > > ::ffff:141.212.122.145:25648 CLOSE_WAIT
>> > > tcp      227      0 ::ffff:192.168.0.22:443
>> > > ::ffff:54.229.157.36:46001 CLOSE_WAIT
>> > > tcp      123      0 ::ffff:192.168.0.22:443
>> > > ::ffff:184.105.247.195:35930 CLOSE_WAIT
>> > > tcp      195      0 ::ffff:192.168.0.22:443
>> > > ::ffff:80.215.1.151:4836 CLOSE_WAIT
>> > > tcp      195      0 ::ffff:192.168.0.22:443
>> > > ::ffff:88.162.134.175:60411 CLOSE_WAIT
>> > > tcp      144      0 ::ffff:192.168.0.22:443
>> > > ::ffff:141.212.122.209:56647 CLOSE_WAIT
>> > > tcp       65      0 ::ffff:192.168.0.22:443
>> > > ::ffff:169.229.3.91:39488 CLOSE_WAIT
>> > > tcp      106      0 ::ffff:192.168.0.22:443
>> > > ::ffff:190.7.136.147:51907 CLOSE_WAIT
>> > > tcp      169      0 ::ffff:192.168.0.22:443
>> > > ::ffff:209.88.157.240:43318 CLOSE_WAIT
>> > > tcp      123      0 ::ffff:192.168.0.22:443
>::ffff:74.82.47.2:38505
>> > > CLOSE_WAIT
>> > > tcp      144      0 ::ffff:192.168.0.22:443
>> > > ::ffff:141.212.122.161:27146 CLOSE_WAIT
>> > > tcp      140      0 ::ffff:192.168.0.22:443
>> > > ::ffff:141.212.122.209:15757 CLOSE_WAIT
>> > > tcp       65      0 ::ffff:192.168.0.22:443
>> > > ::ffff:169.229.3.91:39669 CLOSE_WAIT
>> > > tcp      106      0 ::ffff:192.168.0.22:443
>> > > ::ffff:177.84.43.252:42691 CLOSE_WAIT
>> > I am now wondering whether it could come from "not well closed
>> > connection" (due certainly to mobile phone apps that stop suddently
>> > due to lack of network)?
>> >
>> > I also tried cat /proc/my_devicePID/fd:
>> > > 0   10  12  14  16  18  2   21  23  25  27  29  30  32  34  36 
>38
>> > >  4   41  43  45  47  49  50  52  54  56  58  6   61  63  65  67 
>69
>> > >  70  72  74  76  78  8   81  83  85  87  89  90  92  94
>> > > 1   11  13  15  17  19  20  22  24  26  28  3   31  33  35  37 
>39
>> > >  40  42  44  46  48  5   51  53  55  57  59  60  62  64  66  68 
>7
>> > >   71  73  75  77  79  80  82  84  86  88  9   91  93
>>
>> Hm do you mean ls that dir?  If you look with ls -l, at least on
>modern
>> Linux, you will get a lot more info, such as whether it's a socket or
>> if a file, which file it's open on.
>>
>> > There seem to be too many fds : each time I close the connection
>> > improperly, I get one fd left (egg: switching off the client
>ethernet
>> > card). I will have to have a closer look to this problem but I
>don't
>> > think this is the source of my problem
>>
>> To discover that a peer has passively died you must write on the
>> connection periodically.  Because otherwise there is no way of
>learning
>> the connection is silently no longer complete.  ws itself provide
>PING
>> and PONG control packets for that purpose.
>>
>> > At the beginning of my app, I have the following opended fd:
>> > > 0   1   10  11  12  13  14  15  16  17  18  19  2   20  21  22 
>23
>> > >  24  25  3   4   5   6   7   8   9
>> > I tried simulating several improper disconnections, I get more fds
>> > left used but no CLOSE_WAIT:
>> > > Proto Recv-Q Send-Q Local Address           Foreign Address
>> > > State
>> > > tcp        0      0 192.168.1.66:122        109.109.109.109:55833
>> > > ESTABLISHED
>> > > tcp        0    310 192.168.1.66:443        192.168.1.65:18434
>> > >  ESTABLISHED
>> > Have you got an idea where "pending" CLOSE_WAIT in netstat could
>come
>> > from? Can it help locate an infinite loop somewhere in my code (or
>> > lws even I don't think so)?
>>
>> This is sounding a lot like this
>>
>> https://github.com/warmcat/libwebsockets/issues/475
>>
>> However I reverted it since it made other problems, and I never had
>his
>> problem.
>>
>>
>https://github.com/warmcat/libwebsockets/commit/d2feeee1d6badd4f2da90d8
>> bea29f58e77e0d68b
>>
><https://github.com/warmcat/libwebsockets/commit/d2feeee1d6badd4f2da90d8bea29f58e77e0d68b>
>>
>> You might try his one-line change, but the problems it caused were
>> real, and as explained in the patch reverting it, the meaning of 0
>from
>> recv is extremely ambiguous.
>>
>> -Andy
>>
>> > Best regards,
>> > Thomas
>> >
>> >
>> > 2016-05-04 22:14 GMT+02:00 Andy Green <andy at warmcat.com>:
>> > >
>> > > On May 4, 2016 11:43:04 PM GMT+08:00, "José Luis Millán"
><jmillan at a
>> > > liax.net> wrote:
>> > > >Hi,
>> > > >
>> > > >Probably the issues are totally different. I'm just replying in
>> > > case
>> > > >it's
>> > > >helpful for anyone.
>> > > >
>> > > >I've been using libwebsockets for a long time, with external
>poll
>> > > >(externally handled libevent), and I'm experiencing issues after
>> > > >upgrade.
>> > >
>> > > From the logs this guy's box and lws app (using lws 1.7.3) has
>been
>> > > running since at least Apr 19, I assume it was working when he
>> > > started it and stopped working at some point.  So it seems
>> > > unrelated.
>> > >
>> > > >Concretely establishing new connections. You can see the
>issue[*]
>> > > I
>> > > >opened
>> > > >and the workaround that works for me. I'm willing to understand
>> > > the
>> > > >root
>> > > >issue though.
>> > >
>> > > It's 4am here... I'll look at your results later.
>> > >
>> > > -Andy
>> > >
>> > > >[*]: https://github.com/warmcat/libwebsockets/issues/510
>> > > >
>> > > >Kind regards,
>> > > >
>> > > >2016-05-04 14:59 GMT+02:00 Thomas Spitz
>> > > ><thomas.spitz at hestia-france.com>:
>> > > >
>> > > >> Hello everyone,
>> > > >>
>> > > >> Just in case of obvious bug case. I have been running LWS on a
>> > > device
>> > > >for
>> > > >> 4 months in my program and now, I am not able to connect
>anymore
>> > > with
>> > > >LWS
>> > > >> (OK in ssh) and CPU usage for my program is 100% every 1
>second
>> > > >according
>> > > >> to top utility (I suppose Linux preempt my program because it
>> > > uses
>> > > >all the
>> > > >> CPU).
>> > > >>
>> > > >> I don't know yet where it could come from and for the moment I
>> > > only
>> > > >have
>> > > >> syslog log file where I can found error with LWS... LWS is
>> > > probably
>> > > >not the
>> > > >> cause of CPU 100% usage but I all the same copied and pasted
>the
>> > > >syslog
>> > > >> file in case of obvious bug (version 1.7.3):
>> > > >>
>> > > >> By the way, I already saw this post that looks a bit similar
>but
>> > > it
>> > > >is not
>> > > >> answered yet :
>> > > >>
>> > >
>>https://libwebsockets.org/pipermail/libwebsockets/2016-March/00224
>> > > 9.html
>> > > >>
>> > > >> Jan 15 16:55:00 MY_DEVICE syslog.info syslogd started: BusyBox
>> > > >v1.23.1
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: klogd started:
>> > > BusyBox
>> > > >>>> v1.23.1 (2015-09-01 10:22:29 CEST)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Booting Linux on
>> > > >physical
>> > > >>>> CPU 0x0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: Linux version
>> > > 3.19.8
>> > > >>>> (thomas at thomas-laptop) (gcc version 4.8.4 (Buildroot
>2015.02)
>> > > ) #3
>> > > >>>> PREEMPT Thu Mar 10 10:45:58 CET 2016
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: CPU: ARM926EJ-S
>> > > >[41069265]
>> > > >>>> revision 5 (ARMv5TEJ), cr=0005317f
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: CPU: VIVT data
>> > > cache,
>> > > >VIVT
>> > > >>>> instruction cache
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Machine model:
>> > > Armadeus
>> > > >>>> Systems APF28Dev docking/development board
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Memory policy:
>Data
>> > > >cache
>> > > >>>> writeback
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.debug kernel: On node 0
>> > > totalpages:
>> > > >32768
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.debug kernel:
>> > > free_area_init_node:
>> > > >node 0,
>> > > >>>> pgdat c065f0f8, node_mem_map c7efb000
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.debug kernel:   Normal zone:
>256
>> > > >pages
>> > > >>>> used for memmap
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.debug kernel:   Normal zone: 0
>> > > pages
>> > > >>>> reserved
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.debug kernel: pcpu-alloc: s0
>r0
>> > > >d32768
>> > > >>>> u32768 alloc=1*32768
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.debug kernel: pcpu-alloc: [0]
>0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Built 1 zonelists
>> > > in
>> > > >Zone
>> > > >>>> order, mobility grouping on.  Total pages: 32512
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: Kernel command
>> > > line:
>> > > >>>> console=ttyAMA0,115200
>> > > >>>>
>> > > >mtdparts=gpmi-nand:3M(u-
>> > >
>boot)ro,512K(env),512K(env2),512K(dtb),512K(splash),8M(kernel),100M
>> > > (rootfs),8M(kernel2),100M(rootfs2),128K(ubootscript),-(param)
>> > > >>>> ubi.mtd=rootfs2 ubi.mtd=param r
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: PID hash table
>> > > entries:
>> > > >512
>> > > >>>> (order: -1, 2048 bytes)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Dentry cache hash
>> > > table
>> > > >>>> entries: 16384 (order: 4, 65536 bytes)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Inode-cache hash
>> > > table
>> > > >>>> entries: 8192 (order: 3, 32768 bytes)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Memory:
>> > > 123188K/131072K
>> > > >>>> available (4885K kernel code, 182K rwdata, 1256K rodata,
>168K
>> > > init,
>> > > >108K
>> > > >>>> bss, 7884K reserved, 0K cma-reserved)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: Virtual kernel
>> > > memory
>> > > >>>> layout:
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:     vector  :
>> > > >0xffff0000 -
>> > > >>>> 0xffff1000   (   4 kB)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:     fixmap  :
>> > > >0xffc00000 -
>> > > >>>> 0xfff00000   (3072 kB)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: NR_IRQS:16
>> > > nr_irqs:16 16
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: sched_clock: 32
>> > > bits at
>> > > >>>> 24MHz, resolution 41ns, wraps every 178956969942ns
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Console: colour
>> > > dummy
>> > > >device
>> > > >>>> 80x30
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Calibrating delay
>> > > >loop...
>> > > >>>> 226.09 BogoMIPS (lpj=1130496)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: pid_max: default:
>> > > 32768
>> > > >>>> minimum: 301
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Mount-cache hash
>> > > table
>> > > >>>> entries: 1024 (order: 0, 4096 bytes)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Mountpoint-cache
>> > > hash
>> > > >table
>> > > >>>> entries: 1024 (order: 0, 4096 bytes)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: CPU: Testing
>write
>> > > >buffer
>> > > >>>> coherency: ok
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Setting up static
>> > > >identity
>> > > >>>> map for 0x404a7490 - 0x404a74e8
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: devtmpfs:
>> > > initialized
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: pinctrl core:
>> > > >initialized
>> > > >>>> pinctrl subsystem
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: NET: Registered
>> > > protocol
>> > > >>>> family 16
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: DMA: preallocated
>> > > 256
>> > > >KiB
>> > > >>>> pool for atomic coherent allocations
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: cpuidle: using
>> > > governor
>> > > >>>> ladder
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: cpuidle: using
>> > > governor
>> > > >menu
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Serial: AMBA
>PL011
>> > > UART
>> > > >>>> driver
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: 80074000.serial:
>> > > ttyAMA0
>> > > >at
>> > > >>>> MMIO 0x80074000 (irq = 218, base_baud = 0) is a PL011 rev2
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: console [ttyAMA0]
>> > > >enabled
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: mxs-dma
>> > > >80004000.dma-apbh:
>> > > >>>> initialized
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: mxs-dma
>> > > >80024000.dma-apbx:
>> > > >>>> initialized
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: SCSI subsystem
>> > > >initialized
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usbcore:
>registered
>> > > new
>> > > >>>> interface driver usbfs
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usbcore:
>registered
>> > > new
>> > > >>>> interface driver hub
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usbcore:
>registered
>> > > new
>> > > >>>> device driver usb
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: pps_core:
>LinuxPPS
>> > > API
>> > > >ver.
>> > > >>>> 1 registered
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: pps_core:
>Software
>> > > ver.
>> > > >>>> 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
><giometti at linux.i
>> > > t>
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: PTP clock support
>> > > >registered
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Switched to
>> > > clocksource
>> > > >>>> mxs_timer
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: NET: Registered
>> > > protocol
>> > > >>>> family 2
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: TCP established
>> > > hash
>> > > >table
>> > > >>>> entries: 1024 (order: 0, 4096 bytes)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: TCP bind hash
>table
>> > > >entries:
>> > > >>>> 1024 (order: 0, 4096 bytes)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: TCP: Hash tables
>> > > >configured
>> > > >>>> (established 1024 bind 1024)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: TCP: reno
>> > > registered
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: UDP hash table
>> > > entries:
>> > > >256
>> > > >>>> (order: 0, 4096 bytes)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: UDP-Lite hash
>table
>> > > >entries:
>> > > >>>> 256 (order: 0, 4096 bytes)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: NET: Registered
>> > > protocol
>> > > >>>> family 1
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: RPC: Registered
>> > > named
>> > > >UNIX
>> > > >>>> socket transport module.
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: RPC: Registered
>udp
>> > > >>>> transport module.
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: RPC: Registered
>tcp
>> > > >>>> transport module.
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: RPC: Registered
>tcp
>> > > >NFSv4.1
>> > > >>>> backchannel transport module.
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: futex hash table
>> > > >entries:
>> > > >>>> 256 (order: -1, 3072 bytes)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: NFS:
>Registering
>> > > the
>> > > >>>> id_resolver key type
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: Key type
>> > > id_resolver
>> > > >>>> registered
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: Key type
>> > > id_legacy
>> > > >>>> registered
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: io scheduler noop
>> > > >registered
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: io scheduler
>> > > deadline
>> > > >>>> registered (default)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.err kernel:
>> > > >of_dma_request_slave_channel:
>> > > >>>> dma-names property of node
>> > > >'/apb at 80000000/apbx at 80040000/serial at 80074000'
>> > > >>>> missing or empty
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: uart-pl011
>> > > >80074000.serial:
>> > > >>>> no DMA platform data
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: 8006a000.serial:
>> > > ttyAPP0
>> > > >at
>> > > >>>> MMIO 0x8006a000 (irq = 214, base_baud = 1500000) is a
>> > > >8006a000.serial
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: mxs-auart
>> > > >8006a000.serial:
>> > > >>>> Found APPUART 3.1.0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: 8006c000.serial:
>> > > ttyAPP1
>> > > >at
>> > > >>>> MMIO 0x8006c000 (irq = 215, base_baud = 1500000) is a
>> > > >8006c000.serial
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: mxs-auart
>> > > >8006c000.serial:
>> > > >>>> Found APPUART 3.1.0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: 8006e000.serial:
>> > > ttyAPP2
>> > > >at
>> > > >>>> MMIO 0x8006e000 (irq = 216, base_baud = 1500000) is a
>> > > >8006e000.serial
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: mxs-auart
>> > > >8006e000.serial:
>> > > >>>> Found APPUART 3.1.0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: 80070000.serial:
>> > > ttyAPP3
>> > > >at
>> > > >>>> MMIO 0x80070000 (irq = 217, base_baud = 1500000) is a
>> > > >80070000.serial
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: mxs-auart
>> > > >80070000.serial:
>> > > >>>> Found APPUART 3.1.0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: st: Version
>> > > 20101219,
>> > > >fixed
>> > > >>>> bufsize 32768, s/g segs 256
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: SCSI Media
>Changer
>> > > >driver
>> > > >>>> v0.25
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: nand: device
>found,
>> > > >>>> Manufacturer ID: 0x2c, Chip ID: 0xda
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: nand: Micron
>> > > >MT29F2G08ABAEAWP
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: nand: 256 MiB,
>SLC,
>> > > >erase
>> > > >>>> size: 128 KiB, page size: 2048, OOB size: 64
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Scanning device
>for
>> > > bad
>> > > >>>> blocks
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: Bad eraseblock 0
>at
>> > > >>>> 0x000000000000
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: Bad eraseblock 1
>at
>> > > >>>> 0x000000020000
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: Bad eraseblock 2
>at
>> > > >>>> 0x000000040000
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: Bad eraseblock 3
>at
>> > > >>>> 0x000000060000
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: Bad eraseblock 4
>at
>> > > >>>> 0x000000080000
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: Bad eraseblock 5
>at
>> > > >>>> 0x0000000a0000
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: Bad eraseblock 6
>at
>> > > >>>> 0x0000000c0000
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: Bad eraseblock 7
>at
>> > > >>>> 0x0000000e0000
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: 11 cmdlinepart
>> > > >partitions
>> > > >>>> found on MTD device gpmi-nand
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: Creating 11 MTD
>> > > >partitions
>> > > >>>> on "gpmi-nand":
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:
>> > > >>>> 0x000000000000-0x000000300000 : "u-boot"
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:
>> > > >>>> 0x000000300000-0x000000380000 : "env"
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:
>> > > >>>> 0x000000380000-0x000000400000 : "env2"
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:
>> > > >>>> 0x000000400000-0x000000480000 : "dtb"
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:
>> > > >>>> 0x000000480000-0x000000500000 : "splash"
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:
>> > > >>>> 0x000000500000-0x000000d00000 : "kernel"
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:
>> > > >>>> 0x000000d00000-0x000007100000 : "rootfs"
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:
>> > > >>>> 0x000007100000-0x000007900000 : "kernel2"
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:
>> > > >>>> 0x000007900000-0x00000dd00000 : "rootfs2"
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:
>> > > >>>> 0x00000dd00000-0x00000dd20000 : "ubootscript"
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel:
>> > > >>>> 0x00000dd20000-0x000010000000 : "param"
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: gpmi-nand
>> > > >>>> 8000c000.gpmi-nand: driver registered.
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: 800f0000.ethernet
>> > > supply
>> > > >phy
>> > > >>>> not found, using dummy regulator
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: libphy:
>> > > >fec_enet_mii_bus:
>> > > >>>> probed
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: ehci_hcd: USB 2.0
>> > > >'Enhanced'
>> > > >>>> Host Controller (EHCI) Driver
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usbcore:
>registered
>> > > new
>> > > >>>> interface driver cdc_acm
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: cdc_acm: USB
>> > > Abstract
>> > > >>>> Control Model driver for USB modems and ISDN adapters
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usbcore:
>registered
>> > > new
>> > > >>>> interface driver usblp
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usbcore:
>registered
>> > > new
>> > > >>>> interface driver cdc_wdm
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usbcore:
>registered
>> > > new
>> > > >>>> interface driver usb-storage
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: 80090000.usb
>supply
>> > > vbus
>> > > >not
>> > > >>>> found, using dummy regulator
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: ci_hdrc
>ci_hdrc.0:
>> > > EHCI
>> > > >Host
>> > > >>>> Controller
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: ci_hdrc
>ci_hdrc.0:
>> > > new
>> > > >USB
>> > > >>>> bus registered, assigned bus number 1
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: ci_hdrc
>ci_hdrc.0:
>> > > USB
>> > > >2.0
>> > > >>>> started, EHCI 1.00
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usb usb1: New USB
>> > > device
>> > > >>>> found, idVendor=1d6b, idProduct=0002
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usb usb1: New USB
>> > > device
>> > > >>>> strings: Mfr=3, Product=2, SerialNumber=1
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usb usb1:
>Product:
>> > > EHCI
>> > > >Host
>> > > >>>> Controller
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usb usb1:
>> > > Manufacturer:
>> > > >>>> Linux 3.19.8 ehci_hcd
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usb usb1:
>> > > SerialNumber:
>> > > >>>> ci_hdrc.0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: hub 1-0:1.0: USB
>> > > hub
>> > > >found
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: hub 1-0:1.0: 1
>port
>> > > >detected
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: mousedev: PS/2
>> > > mouse
>> > > >device
>> > > >>>> common for all mice
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: stmp3xxx-rtc
>> > > >80056000.rtc:
>> > > >>>> rtc core: registered 80056000.rtc as rtc0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: i2c /dev entries
>> > > driver
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: stmp3xxx_rtc_wdt
>> > > >>>> stmp3xxx_rtc_wdt: initialized watchdog with heartbeat 19s
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: Driver 'mmcblk'
>> > > needs
>> > > >>>> updating - please use bus_type methods
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: 80010000.ssp
>supply
>> > > vmmc
>> > > >not
>> > > >>>> found, using dummy regulator
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: mxs-mmc
>> > > 80010000.ssp:
>> > > >>>> initialized
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usbcore:
>registered
>> > > new
>> > > >>>> interface driver usbhid
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: usbhid: USB HID
>> > > core
>> > > >driver
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: oprofile: no
>> > > performance
>> > > >>>> counters
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: oprofile: using
>> > > timer
>> > > >>>> interrupt.
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: TCP: cubic
>> > > registered
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: NET: Registered
>> > > protocol
>> > > >>>> family 10
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: sit: IPv6 over
>IPv4
>> > > >>>> tunneling driver
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: NET: Registered
>> > > protocol
>> > > >>>> family 17
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: Key type
>> > > dns_resolver
>> > > >>>> registered
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-0:
>> > > >>>> ubi_attach_mtd_dev:attaching mtd8 to ubi0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.warn kernel: mmc0: host does
>not
>> > > >support
>> > > >>>> reading read-only switch, assuming write-enable
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: mmc0: new high
>> > > speed
>> > > >SDHC
>> > > >>>> card at address aaaa
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: mmcblk0:
>mmc0:aaaa
>> > > SS08G
>> > > >>>> 7.40 GiB
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel:  mmcblk0: p1
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: random:
>> > > nonblocking
>> > > >pool is
>> > > >>>> initialized
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-0:
>> > > >scan_all:scanning is
>> > > >>>> finished
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-0:
>> > > >>>> ubi_attach_mtd_dev:attached mtd8 (name "rootfs2", size 100
>> > > MiB)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-0:
>> > > >>>> ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB
>size:
>> > > >126976 bytes
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-0:
>> > > >>>> ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-
>> > > page
>> > > >size 2048
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-0:
>> > > >>>> ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048),
>> > > data
>> > > >offset: 4096
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-0:
>> > > >>>> ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted
>> > > PEBs: 0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-0:
>> > > >>>> ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max.
>> > > >volumes count:
>> > > >>>> 128
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-0:
>> > > >>>> ubi_attach_mtd_dev:max/mean erase counter: 9/4, WL
>threshold:
>> > > 4096,
>> > > >image
>> > > >>>> sequence number: 535698515
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-0:
>> > > >>>> ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs:
>> > > 800,
>> > > >PEBs
>> > > >>>> reserved for bad PEB handling: 40
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-0:
>> > > >>>> ubi_thread:background thread "ubi_bgt0d" started, PID 523
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-1:
>> > > >>>> ubi_attach_mtd_dev:attaching mtd10 to ubi1
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-1:
>> > > >scan_all:scanning is
>> > > >>>> finished
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-1:
>> > > >>>> ubi_attach_mtd_dev:attached mtd10 (name "param", size 34
>MiB)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-1:
>> > > >>>> ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB
>size:
>> > > >126976 bytes
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-1:
>> > > >>>> ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-
>> > > page
>> > > >size 2048
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-1:
>> > > >>>> ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048),
>> > > data
>> > > >offset: 4096
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-1:
>> > > >>>> ubi_attach_mtd_dev:good PEBs: 279, bad PEBs: 0, corrupted
>> > > PEBs: 0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-1:
>> > > >>>> ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max.
>> > > >volumes count:
>> > > >>>> 128
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-1:
>> > > >>>> ubi_attach_mtd_dev:max/mean erase counter: 6/3, WL
>threshold:
>> > > 4096,
>> > > >image
>> > > >>>> sequence number: 3580535270
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-1:
>> > > >>>> ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs:
>> > > 279,
>> > > >PEBs
>> > > >>>> reserved for bad PEB handling: 40
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBI-1:
>> > > >>>> ubi_thread:background thread "ubi_bgt1d" started, PID 526
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: input: gpio-keys
>as
>> > > >>>> /devices/soc0/gpio-keys/input/input0
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: stmp3xxx-rtc
>> > > >80056000.rtc:
>> > > >>>> setting system clock to 1970-01-15 16:54:58 UTC (1270498)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS: recovery
>> > > needed
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS: recovery
>> > > >deferred
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS: mounted
>> > > UBI
>> > > >device
>> > > >>>> 0, volume 0, name "rootfs", R/O mode
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS: LEB
>size:
>> > > >126976
>> > > >>>> bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048
>> > > bytes
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS: FS size:
>> > > >94597120
>> > > >>>> bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB,
>> > > 72
>> > > >LEBs)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS: reserved
>> > > for
>> > > >root: 0
>> > > >>>> bytes (0 KiB)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS: media
>> > > format:
>> > > >w4/r0
>> > > >>>> (latest is w4/r0), UUID
>38081A8B-2F96-4AFD-83EA-7B2C2D553250,
>> > > small
>> > > >LPT
>> > > >>>> model
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: VFS: Mounted root
>> > > (ubifs
>> > > >>>> filesystem) readonly on device 0:14.
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: devtmpfs: mounted
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.info kernel: Freeing unused
>> > > kernel
>> > > >>>> memory: 168K (c0608000 - c0632000)
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS:
>completing
>> > > >deferred
>> > > >>>> recovery
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS:
>background
>> > > >thread
>> > > >>>> "ubifs_bgt0_0" started, PID 540
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS: deferred
>> > > >recovery
>> > > >>>> completed
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS:
>background
>> > > >thread
>> > > >>>> "ubifs_bgt1_0" started, PID 581
>> > > >>>
>> > > >>> Jan 15 16:55:00 MY_DEVICE kern.notice kernel: UBIFS: recovery
>> > > needed
>> > > >>>
>> > > >>> Jan 15 16:55:01 MY_DEVICE kern.notice kernel: UBIFS: recovery
>> > > >completed
>> > > >>>
>> > > >>> Jan 15 16:55:01 MY_DEVICE kern.notice kernel: UBIFS: mounted
>> > > UBI
>> > > >device
>> > > >>>> 1, volume 0, name "param"
>> > > >>>
>> > > >>> Jan 15 16:55:01 MY_DEVICE kern.notice kernel: UBIFS: LEB
>size:
>> > > >126976
>> > > >>>> bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048
>> > > bytes
>> > > >>>
>> > > >>> Jan 15 16:55:01 MY_DEVICE kern.notice kernel: UBIFS: FS size:
>> > > >28569600
>> > > >>>> bytes (27 MiB, 225 LEBs), journal size 1396736 bytes (1 MiB,
>> > > 11
>> > > >LEBs)
>> > > >>>
>> > > >>> Jan 15 16:55:01 MY_DEVICE kern.notice kernel: UBIFS: reserved
>> > > for
>> > > >root:
>> > > >>>> 1349412 bytes (1317 KiB)
>> > > >>>
>> > > >>> Jan 15 16:55:01 MY_DEVICE kern.notice kernel: UBIFS: media
>> > > format:
>> > > >w4/r0
>> > > >>>> (latest is w4/r0), UUID
>EC44CF88-3EA1-4997-88CF-DE5E18EF502A,
>> > > small
>> > > >LPT
>> > > >>>> model
>> > > >>>
>> > > >>> Jan 15 16:55:02 MY_DEVICE auth.info sshd[585]: Server
>listening
>> > > on
>> > > >::
>> > > >>>> port 122.
>> > > >>>
>> > > >>> Jan 15 16:55:02 MY_DEVICE auth.info sshd[585]: Server
>listening
>> > > on
>> > > >>>> 0.0.0.0 port 122.
>> > > >>>
>> > > >>> Jan 15 16:55:02 MY_DEVICE auth.info sshd[585]: Received
>signal
>> > > 15;
>> > > >>>> terminating.
>> > > >>>
>> > > >>> Jan 15 16:55:02 MY_DEVICE daemon.info init: starting pid 593,
>> > > tty
>> > > >>>> '/dev/ttyAMA0': '/sbin/getty -L  ttyAMA0 0 vt100 '
>> > > >>>
>> > > >>> Jan 15 16:55:02 MY_DEVICE uucp.debug V4[592]: V4 version
>> > > applicatif
>> > > >0.1.1
>> > > >>>
>> > > >>> Jan 15 16:55:02 MY_DEVICE kern.info kernel: kjournald
>starting.
>> > > >Commit
>> > > >>>> interval 5 seconds
>> > > >>>
>> > > >>> Jan 15 16:55:02 MY_DEVICE kern.info kernel: EXT3-fs
>> > > (mmcblk0p1):
>> > > >using
>> > > >>>> internal journal
>> > > >>>
>> > > >>> Jan 15 16:55:02 MY_DEVICE kern.info kernel: EXT3-fs
>> > > (mmcblk0p1):
>> > > >>>> recovery complete
>> > > >>>
>> > > >>> Jan 15 16:55:02 MY_DEVICE kern.info kernel: EXT3-fs
>> > > (mmcblk0p1):
>> > > >mounted
>> > > >>>> filesystem with ordered data mode
>> > > >>>
>> > > >>> Jan 15 16:55:27 MY_DEVICE daemon.info ifplugd(eth0)[624]:
>> > > ifplugd
>> > > >0.28
>> > > >>>> initializing.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info ifplugd(eth0)[624]:
>Using
>> > > >>>> interface eth0/00:1E:AC:00:96:4E with driver <fec> (version:
>> > > >Revision: 1.0)
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE kern.info kernel: fec
>> > > 800f0000.ethernet
>> > > >eth0:
>> > > >>>> Freescale FEC PHY driver [Generic PHY]
>> > > >>>> (mii_bus:phy_addr=800f0000.etherne:00, irq=-1)
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE kern.info kernel: IPv6:
>> > > >ADDRCONF(NETDEV_UP):
>> > > >>>> eth0: link is not ready
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info ifplugd(eth0)[624]:
>Using
>> > > >>>> detection mode: SIOCETHTOOL
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info ifplugd(eth0)[624]:
>> > > >Initialization
>> > > >>>> complete, link beat not detected.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>Found
>> > > user
>> > > >>>> 'avahi' (UID 1001) and group 'avahi' (GID 1001).
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > >Successfully
>> > > >>>> dropped root privileges.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > >avahi-daemon
>> > > >>>> 0.6.31 starting up.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > WARNING: No
>> > > >NSS
>> > > >>>> support for mDNS detected, consider installing nss-mdns!
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.warn avahi-daemon[634]:
>Failed
>> > > to
>> > > >open
>> > > >>>> /etc/resolv.conf: No such file or directory
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Loading
>> > > >service
>> > > >>>> file /etc/avahi/services/hestia-v4.service.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Loading
>> > > >service
>> > > >>>> file /etc/avahi/services/sftp-ssh.service.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Loading
>> > > >service
>> > > >>>> file /etc/avahi/services/ssh.service.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Network
>> > > >>>> interface enumeration completed.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Registering
>> > > >>>> HINFO record with values 'ARMV5TEJL'/'LINUX'.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>Server
>> > > >startup
>> > > >>>> complete. Host name is MY_DEVICE.local. Local service cookie
>> > > is
>> > > >2838373760.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Service
>> > > >>>> "MY_DEVICE" (/etc/avahi/services/ssh.service) successfully
>> > > >established.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Service
>> > > >>>> "MY_DEVICE" (/etc/avahi/services/sftp-ssh.service)
>> > > successfully
>> > > >established.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Service
>> > > >>>> "MY_DEVICE" (/etc/avahi/services/hestia-v4.service)
>> > > successfully
>> > > >>>> established.
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]:
>> > > libwebsockets
>> > > >test
>> > > >>>> server - license LGPL2.1+SLE
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]: (C)
>> > > Copyright
>> > > >>>> 2010-2016 Andy Green <andy at warmcat.com>
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]: Initial
>> > > logging
>> > > >level
>> > > >>>> 7
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]:
>> > > Libwebsockets
>> > > >>>> version: 1.7.3 thomas at thomas-laptop-
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]: IPV6
>> > > compiled in
>> > > >and
>> > > >>>> enabled
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]: libev
>> > > support
>> > > >not
>> > > >>>> compiled in
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]:  Threads:
>1
>> > > each
>> > > >1024
>> > > >>>> fds
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]:  mem:
>> > > platform
>> > > >fd
>> > > >>>> map:  4096 bytes
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]:  mem:
>per-
>> > > conn:
>> > > >>>>    308 bytes + protocol rx buf
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]:
>> > > >canonical_hostname =
>> > > >>>> MY_DEVICE
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]:  Compiled
>> > > with
>> > > >>>> OpenSSL support
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]:  Using
>SSL
>> > > mode
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]:  SSL ECDH
>> > > curve
>> > > >>>> 'prime256v1'
>> > > >>>
>> > > >>> Jan 15 16:55:28 MY_DEVICE daemon.notice lwsts[592]: 
>Listening
>> > > on
>> > > >port 443
>> > > >>>
>> > > >>> Jan 15 16:55:30 MY_DEVICE kern.info kernel: fec
>> > > 800f0000.ethernet
>> > > >eth0:
>> > > >>>> Link is Up - 100Mbps/Full - flow control rx/tx
>> > > >>>
>> > > >>> Jan 15 16:55:30 MY_DEVICE kern.info kernel: IPv6:
>> > > >>>> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>> > > >>>
>> > > >>> Jan 15 16:55:30 MY_DEVICE daemon.info ifplugd(eth0)[624]:
>Link
>> > > beat
>> > > >>>> detected.
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.info ifplugd(eth0)[624]:
>> > > Executing
>> > > >>>> '/etc/ifplugd/ifplugd.action eth0 up'.
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.warn ifplugd(eth0)[624]:
>> > > client:
>> > > >udhcpc
>> > > >>>> (v1.23.1) started
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Registering
>> > > >new
>> > > >>>> address record for fe80::21e:acff:fe00:964e on eth0.*.
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.warn ifplugd(eth0)[624]:
>> > > client:
>> > > >Failed
>> > > >>>> to kill daemon: No such file or directory
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.warn ifplugd(eth0)[624]:
>> > > client:
>> > > >Sending
>> > > >>>> discover...
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.warn ifplugd(eth0)[624]:
>> > > client:
>> > > >Sending
>> > > >>>> select for 192.168.1.125...
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.warn ifplugd(eth0)[624]:
>> > > client:
>> > > >Lease
>> > > >>>> of 192.168.1.125 obtained, lease time 43200
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.warn ifplugd(eth0)[624]:
>> > > client:
>> > > >Failed
>> > > >>>> to kill daemon: No such file or directory
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Joining
>> > > >mDNS
>> > > >>>> multicast group on interface eth0.IPv4 with address
>> > > 192.168.1.125.
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.info avahi-daemon[634]: New
>> > > >relevant
>> > > >>>> interface eth0.IPv4 for mDNS.
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.warn ifplugd(eth0)[624]:
>> > > client:
>> > > >>>> deleting routers
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Registering
>> > > >new
>> > > >>>> address record for 192.168.1.125 on eth0.IPv4.
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.warn ifplugd(eth0)[624]:
>> > > client:
>> > > >adding
>> > > >>>> dns 192.168.1.254
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE daemon.info ifplugd(eth0)[624]:
>> > > Program
>> > > >>>> executed successfully.
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE auth.info sshd[661]: Server
>listening
>> > > on
>> > > >::
>> > > >>>> port 122.
>> > > >>>
>> > > >>> Jan 15 16:55:31 MY_DEVICE auth.info sshd[661]: Server
>listening
>> > > on
>> > > >>>> 0.0.0.0 port 122.
>> > > >>>
>> > > >>> Jan 15 16:55:32 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Registering
>> > > >new
>> > > >>>> address record for 2a01:e34:efd0:8210:21e:acff:fe00:964e on
>> > > eth0.*.
>> > > >>>
>> > > >>> Jan 15 16:55:32 MY_DEVICE daemon.info avahi-daemon[634]:
>> > > Withdrawing
>> > > >>>> address record for fe80::21e:acff:fe00:964e on eth0.
>> > > >>>
>> > > >>> Apr 19 19:11:40 MY_DEVICE daemon.notice lwsts[592]:
>> > > >>>> lws_header_table_detach: wsi 0x10e8500: ah held 4s, ah.rxpos
>> > > -1,
>> > > >ah.rxlen
>> > > >>>> -1, mode/state 0 4,wsi->more_rx_waiting 0
>> > > >>>
>> > > >>> Apr 19 23:46:12 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 20 08:53:36 MY_DEVICE daemon.err lwsts[592]: Unknown
>> > > mimetype
>> > > >for
>> > > >>>> /root/serveurweb/robots.txt
>> > > >>>
>> > > >>> Apr 20 13:19:57 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 20 22:07:58 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 21 01:58:55 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 21 13:20:28 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 21 15:03:31 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 21 16:46:32 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 21 19:39:01 MY_DEVICE daemon.notice lwsts[592]: wsi
>> > > 0x10e8500:
>> > > >>>> TIMEDOUT WAITING on 9 (did hdr 0, ah (nil), wl 0, pfd events
>> > > 0)
>> > > >>>
>> > > >>> Apr 21 23:52:36 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 22 15:51:20 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.80.
>> > > >>>
>> > > >>> Apr 22 15:51:20 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.90.
>> > > >>>
>> > > >>> Apr 22 15:51:20 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.49.
>> > > >>>
>> > > >>> Apr 22 15:51:21 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.90.
>> > > >>>
>> > > >>> Apr 22 15:51:21 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.80.
>> > > >>>
>> > > >>> Apr 22 15:51:21 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.49.
>> > > >>>
>> > > >>> Apr 22 15:51:23 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.90.
>> > > >>>
>> > > >>> Apr 22 15:51:23 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.80.
>> > > >>>
>> > > >>> Apr 22 15:51:23 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.49.
>> > > >>>
>> > > >>> Apr 22 15:51:27 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.80.
>> > > >>>
>> > > >>> Apr 22 15:51:27 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.90.
>> > > >>>
>> > > >>> Apr 22 15:51:27 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.49.
>> > > >>>
>> > > >>> Apr 22 15:51:35 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.80.
>> > > >>>
>> > > >>> Apr 22 15:51:35 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.90.
>> > > >>>
>> > > >>> Apr 22 15:51:35 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.49.
>> > > >>>
>> > > >>> Apr 22 15:51:51 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.80.
>> > > >>>
>> > > >>> Apr 22 15:51:51 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.90.
>> > > >>>
>> > > >>> Apr 22 15:51:51 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.49.
>> > > >>>
>> > > >>> Apr 22 15:55:35 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.90.
>> > > >>>
>> > > >>> Apr 22 15:55:35 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.80.
>> > > >>>
>> > > >>> Apr 22 15:55:35 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.49.
>> > > >>>
>> > > >>> Apr 23 01:22:43 MY_DEVICE daemon.notice lwsts[592]: wsi
>> > > 0x10e8500:
>> > > >>>> TIMEDOUT WAITING on 9 (did hdr 0, ah (nil), wl 0, pfd events
>> > > 0)
>> > > >>>
>> > > >>> Apr 23 01:25:50 MY_DEVICE daemon.notice lwsts[592]: wsi
>> > > 0x10e8500:
>> > > >>>> TIMEDOUT WAITING on 9 (did hdr 0, ah (nil), wl 0, pfd events
>> > > 0)
>> > > >>>
>> > > >>> Apr 23 01:25:52 MY_DEVICE daemon.notice lwsts[592]: wsi
>> > > 0x10d6db0:
>> > > >>>> TIMEDOUT WAITING on 9 (did hdr 0, ah (nil), wl 0, pfd events
>> > > 0)
>> > > >>>
>> > > >>> Apr 23 03:13:45 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 23 03:51:58 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 23 03:52:03 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 23 11:58:20 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 23 22:47:30 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 25 01:07:39 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 25 21:23:27 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 26 02:43:06 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 26 13:13:47 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 26 14:18:37 MY_DEVICE daemon.notice lwsts[592]:
>> > > >>>> lws_header_table_detach: wsi 0x10e8500: ah held 5s, ah.rxpos
>> > > -1,
>> > > >ah.rxlen
>> > > >>>> -1, mode/state 0 4,wsi->more_rx_waiting 0
>> > > >>>
>> > > >>> Apr 26 19:08:35 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 26 22:30:02 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 27 09:11:26 MY_DEVICE daemon.err lwsts[592]: Unknown
>> > > mimetype
>> > > >for
>> > > >>>> /root/serveurweb/robots.txt
>> > > >>>
>> > > >>> Apr 27 09:52:29 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 27 11:58:40 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 27 21:05:32 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 28 16:23:17 MY_DEVICE auth.info sshd[2406]: Did not
>receive
>> > > >>>> identification string from 185.7.100.97
>> > > >>>
>> > > >>> Apr 28 16:23:30 MY_DEVICE daemon.warn lwsts[592]: Missing URI
>> > > in
>> > > >HTTP
>> > > >>>> request
>> > > >>>
>> > > >>> Apr 28 16:23:33 MY_DEVICE daemon.err lwsts[592]: Unknown
>> > > mimetype
>> > > >for
>> > > >>>> /root/serveurweb/sip:nm
>> > > >>>
>> > > >>> Apr 28 16:24:03 MY_DEVICE daemon.err lwsts[592]: Unable to
>open
>> > > >>>> '/root/serveurweb/favicon.ico'
>> > > >>>
>> > > >>> Apr 28 16:24:03 MY_DEVICE auth.info sshd[2407]: Protocol
>major
>> > > >versions
>> > > >>>> differ for 185.7.100.97: SSH-2.0-OpenSSH_6.7 vs.
>> > > >>>> SSH-1.5-Nmap-SSH1-Hostkey
>> > > >>>
>> > > >>> Apr 28 16:24:04 MY_DEVICE auth.info sshd[2408]: Connection
>> > > closed by
>> > > >>>> 185.7.100.97 [preauth]
>> > > >>>
>> > > >>> Apr 28 16:24:05 MY_DEVICE auth.info sshd[2410]: Connection
>> > > closed by
>> > > >>>> 185.7.100.97 [preauth]
>> > > >>>
>> > > >>> Apr 28 16:24:05 MY_DEVICE auth.info sshd[2412]: Protocol
>major
>> > > >versions
>> > > >>>> differ for 185.7.100.97: SSH-2.0-OpenSSH_6.7 vs.
>> > > >SSH-1.5-NmapNSE_1.0
>> > > >>>
>> > > >>> Apr 28 16:24:05 MY_DEVICE daemon.err lwsts[592]: Unknown
>> > > mimetype
>> > > >for
>> > > >>>> /root/serveurweb/robots.txt
>> > > >>>
>> > > >>> Apr 28 16:24:05 MY_DEVICE daemon.err lwsts[592]: Unknown
>> > > mimetype
>> > > >for
>> > > >>>> /root/serveurweb/nmaplowercheck1461849551
>> > > >>>
>> > > >>> Apr 28 16:24:06 MY_DEVICE daemon.err lwsts[592]: Unknown
>> > > mimetype
>> > > >for
>> > > >>>> /root/serveurweb/HNAP1
>> > > >>>
>> > > >>> Apr 28 16:24:06 MY_DEVICE auth.info sshd[2413]: Connection
>> > > closed by
>> > > >>>> 185.7.100.97 [preauth]
>> > > >>>
>> > > >>> Apr 28 16:24:06 MY_DEVICE auth.crit sshd[2415]: fatal: no
>> > > hostkey
>> > > >alg
>> > > >>>> [preauth]
>> > > >>>
>> > > >>> Apr 28 16:24:07 MY_DEVICE daemon.notice lwsts[592]:
>> > > >>>> LWS_CALLBACK_HTTP_BODY: <methodCall> <method... len 88
>> > > >>>
>> > > >>> Apr 28 16:24:07 MY_DEVICE daemon.notice lwsts[592]:
>> > > >>>> LWS_CALLBACK_HTTP_BODY_COMPLETION
>> > > >>>
>> > > >>> Apr 28 16:24:07 MY_DEVICE auth.crit sshd[2417]: fatal: no
>> > > hostkey
>> > > >alg
>> > > >>>> [preauth]
>> > > >>>
>> > > >>> Apr 28 16:24:09 MY_DEVICE daemon.notice lwsts[592]:
>> > > >>>> LWS_CALLBACK_HTTP_BODY: <?xml version="1.0" ... len 555
>> > > >>>
>> > > >>> Apr 28 16:24:09 MY_DEVICE daemon.notice lwsts[592]:
>> > > >>>> LWS_CALLBACK_HTTP_BODY_COMPLETION
>> > > >>>
>> > > >>> Apr 28 21:49:58 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 28 23:38:11 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 29 03:12:30 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 29 08:26:14 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 29 15:15:57 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:15:57 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:15:58 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:15:58 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:16:03 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:16:03 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:16:08 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:16:08 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:16:16 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:16:16 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:16:50 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:16:50 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >legacy
>> > > >>>> unicast query packet.
>> > > >>>
>> > > >>> Apr 29 15:19:49 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 29 23:35:43 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 30 16:41:09 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 30 22:29:23 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> Apr 30 23:08:15 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> May  1 11:42:28 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> May  1 12:19:06 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> May  1 21:35:06 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> May  1 23:00:14 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> May  2 12:47:39 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> May  2 23:24:09 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> May  3 05:33:26 MY_DEVICE daemon.err lwsts[592]:
>> > > lws_adopt_socket:
>> > > >fail
>> > > >>>
>> > > >>> May  3 13:31:14 MY_DEVICE daemon.warn avahi-daemon[634]:
>> > > Invalid
>> > > >response
>> > > >>>> packet from host 192.168.1.49.
>> > > >>>
>> > > >>> May  3 16:30:31 MY_DEVICE daemon.notice lwsts[592]:
>> > > >>>> lws_header_table_detach: wsi 0x10e8500: ah held 4s, ah.rxpos
>> > > -1,
>> > > >ah.rxlen
>> > > >>>> -1, mode/state 0 4,wsi->more_rx_waiting 0
>> > > >>>
>> > > >>> May  4 15:25:06 MY_DEVICE auth.info sshd[3539]: Accepted
>> > > password
>> > > >for
>> > > >>>> root from 109.190.164.198 port 49998 ssh2
>> > > >>>
>> > > >>> May  4 15:25:07 MY_DEVICE auth.err sshd[3544]: error: open
>> > > /dev/tty
>> > > >>>> failed - could not set controlling tty: Permission denied
>> > > >>>
>> > > >>>
>> > > >> Thanks in advance,
>> > > >> Best regards,
>> > > >> Thomas
>> > > >>
>> > > >>
>> > > >> _______________________________________________
>> > > >> Libwebsockets mailing list
>> > > >> Libwebsockets at ml.libwebsockets.org
>> > > >> http://libwebsockets.org/mailman/listinfo/libwebsockets
>> > > >>
>> > > >>
>> > >
>> > >
>> >
>>




More information about the Libwebsockets mailing list