10 Replies Latest reply on Aug 2, 2017 12:38 PM by FocaaBR

    DHCP Is making my board reboot

    FocaaBR

      Hello,

      I`m using an Intel Edison board on a project. When the board does not show the battery errors it shows these following messages and is rebooting unstoppable. If anyone know how to fix it please let me know.

       

      5299520 bytes read in 132 ms (38.3 MiB/s)

      Valid Boot Flag

      Setup Size = 0x00003c00

      Magic signature found

      Using boot protocol version 2.0c

      Linux kernel version 3.10.17-yocto-standard-r2 (root@p32mac) #7 SMP PREEMPT Thu                                                                                                              Feb 26 09:57:06 UTC 2015

      Building boot_params at 0x00090000

      Loading bzImage at address 00100000 (5284160 bytes)

      Magic signature found

      Kernel command line: "root=/dev/mmcblk1p1 rootdelay=3 rootfstype=ext4 console=tt                                                                                                             yMFD2 earlyprintk=ttyMFD2,keep loglevel=4 systemd.unit=first-install.target hard                                                                                                             ware_id=00 g_multi.iSerialNumber=bb559091645a234f7cbbf68f3f652005 g_multi.dev_ad                                                                                                             dr=02:00:86:65:20:05"

       

       

      Starting kernel ...

       

       

      [    0.748118] pca953x 1-0020: failed reading register

      [    0.753278] pca953x 1-0021: failed reading register

      [    0.753681] pca953x 1-0022: failed reading register

      [    0.763207] pca953x 1-0023: failed reading register

      [    1.656935] pmic_ccsm pmic_ccsm: Error reading battery profile from battid fr                                                                                                             mwrk

      [    1.666019] pmic_ccsm pmic_ccsm: Battery0 temperature inside boundary

      [    1.734082] mmc1: error -84 whilst initialising SD card

      INIT: version 2.88 booting

      [info] Using makefile-style concurrent boot in runlevel S.

      [ ok ] Starting the hotplug events dispatcher: udevd.

      [ ok ] Synthesizing the initial hotplug events...done.

      [ ok ] Waiting for /dev to be fully populated...done.

      [ ok ] Activating swap...done.

      [ ok ] Cleaning up temporary files... /tmp.

      [info] Loading kernel module bcm_bt_lpm.

      [info] Loading kernel module bcm4334x.

      [info] Loading kernel module g_multi.

      [info] Loading kernel module uvcvideo.

      [info] Loading kernel module ftdi_sio.

      [....] Activating lvm and md swap...[   10.963250] hub 1-1:1.0: over-current condition on port 2

      done.

      [....] Checking file systems...fsck from util-linux 2.20.1

      [   11.183186] hub 1-1:1.0: over-current condition on port 3

      dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN

      /dev/mmcblk0p7: 4 files, 2676/16343 clusters

      /dev/mmcblk0p10: recovering journal

      /dev/mmcblk0p10: clean, 12/87120 files, 14182/348155 blocks

      done.

      [ ok ] Mounting local filesystems...done.

      [   11.792962] usb 1-1.6: device not accepting address 5, error -71

      [ ok ] Activating swapfile swap...done.

      [....] Cleaning up temporary files...[   12.292941] usb 1-1.6: device not accepting address 6, error -71

      . ok

      [ ok ] Setting kernel variables ...done.

      [....] Configuring network interfaces...[   12.793169] usb 1-1.6: device not accepting address 7, error -71

      [   13.293101] usb 1-1.6: device not accepting address 8, error -71

      [   13.293504] hub 1-1:1.0: unable to enumerate USB device on port 6

      [   13.522969] hub 1-1:1.0: over-current condition on port 7

      Internet Systems Consortium DHCP Client 4.2.2

      Copyright 2004-2011 Internet Systems Consortium.

      All rights reserved.

      For info, please visit https://www.isc.org/software/dhcp/

       

       

      Listening on LPF/wlan0/00:ae:fa:02:a6:c5

      Sending on   LPF/wlan0/00:ae:fa:02:a6:c5

      Sending on   Socket/fallback

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10

      DHCPREQUEST on wlan0 to 255.255.255.255 port 67

      DHCPOFFER from 192.168.25.1

      DHCPNAK from 192.168.25.1

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8

      DHCPREQUEST on wlan0 to 255.255.255.255 port 67

      DHCPOFFER from 192.168.25.1

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8

      DHCPREQUEST on wlan0 to 255.255.255.255 port 67

      DHCPOFFER from 192.168.25.1

      DHCPNAK from 192.168.25.1

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5

      DHCPREQUEST on wlan0 to 255.255.255.255 port 67

      DHCPOFFER from 192.168.25.1

      DHCPNAK from 192.168.25.1

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7

       

       

       

       

      ******************************

      PSH KERNEL VERSION: b0182929

                      WR: 20104000

      ******************************

       

       

      SCU IPC: 0x800000d0  0xfffce92c

       

       

      PSH miaHOB version: TNG.B0.VVBD.0000000c

       

       

      microkernel built 10:14:01 Jan 13 2015

       

       

      ******* PSH loader *******

      PCM page cache size = 192 KB

      Cache Constraint = 0 Pages

      Arming IPC driver ..

      Adding page store pool ..

      PagestoreAddr(IMR Start Address) = 0x04899000

      pageStoreSize(IMR Size)          = 0x00080000

       

       

      *** Ready to receive application ***

       

       

       

       

      U-Boot 2014.04 (Feb 09 2015 - 15:40:31)

       

       

             Watchdog enabled

      DRAM:  980.6 MiB

      MMC:   tangier_sdhci: 0

      In:    serial

      Out:   serial

      Err:   serial

      Hit any key to stop autoboot:  0

      Target:blank

      Partitioning already done...

      Flashing already done...

      GADGET DRIVER: usb_dnl_dfu

      reading vmlinuz

      5299520 bytes read in 131 ms (38.6 MiB/s)

      Valid Boot Flag

      Setup Size = 0x00003c00

      Magic signature found

      Using boot protocol version 2.0c

      Linux kernel version 3.10.17-yocto-standard-r2 (root@p32mac) #7 SMP PREEMPT Thu Feb 26 09:57:06 UTC 2015

      Building boot_params at 0x00090000

      Loading bzImage at address 00100000 (5284160 bytes)

      Magic signature found

      Kernel command line: "root=/dev/mmcblk1p1 rootdelay=3 rootfstype=ext4 console=ttyMFD2 earlyprintk=ttyMFD2,keep loglevel=4 systemd.unit=first-install.target hardware_id=00 g_multi.iSerialNumber=bb559091645a234f7cbbf68f3f652005 g_multi.dev_addr=02:00:86:65:20:05"

       

       

      Starting kernel ...

       

       

      [    0.748212] pca953x 1-0020: failed reading register

      [    0.753366] pca953x 1-0021: failed reading register

      [    0.753773] pca953x 1-0022: failed reading register

      [    0.763301] pca953x 1-0023: failed reading register

      [    1.659533] pmic_ccsm pmic_ccsm: Error reading battery profile from battid frmwrk

      [    1.668345] pmic_ccsm pmic_ccsm: Battery0 temperature inside boundary

      [    1.676352] pmic_ccsm pmic_ccsm: Battery0 temperature inside boundary

      INIT: version 2.88 booting

      [info] Using makefile-style concurrent boot in runlevel S.

      [ ok ] Starting the hotplug events dispatcher: udevd.

      [ ok ] Synthesizing the initial hotplug events...done.

      [ ok ] Waiting for /dev to be fully populated...done.

      [ ok ] Activating swap...done.

      [ ok ] Cleaning up temporary files... /tmp.

      [info] Loading kernel module bcm_bt_lpm.

      [info] Loading kernel module bcm4334x.

      [info] Loading kernel module g_multi.

      [info] Loading kernel module uvcvideo.

      [info] Loading kernel module ftdi_sio.

      [ ok ] Activating lvm and md swap...done.

      [....] Checking file systems...fsck from util-linux 2.20.1

      dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN

      /dev/mmcblk0p7: 4 files, 2676/16343 clusters

      /dev/mmcblk0p10: recovering journal

      /dev/mmcblk0p10: clean, 12/87120 files, 14182/348155 blocks

      done.

      [   11.275676] usb 1-1.6: device not accepting address 5, error -71

      [ ok ] Mounting local filesystems...done.

      [ ok ] Activating swapfile swap...[   11.785706] usb 1-1.6: device not accepting address 6, error -71

      done.

      [ ok ] Cleaning up temporary files....

      [....] Setting kernel variables ...[   12.285572] usb 1-1.6: device not accepting address 7, error -71

      done.

      [....] Configuring network interfaces...[   12.785452] usb 1-1.6: device not accepting address 8, error -71

      [   12.785788] hub 1-1:1.0: unable to enumerate USB device on port 6

      Internet Systems Consortium DHCP Client 4.2.2

      Copyright 2004-2011 Internet Systems Consortium.

      All rights reserved.

      For info, please visit https://www.isc.org/software/dhcp/

       

       

      Listening on LPF/wlan0/00:ae:fa:02:a6:c5

      Sending on   LPF/wlan0/00:ae:fa:02:a6:c5

      Sending on   Socket/fallback

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6

      DHCPREQUEST on wlan0 to 255.255.255.255 port 67

      DHCPOFFER from 192.168.25.1

      DHCPNAK from 192.168.25.1

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6

      DHCPREQUEST on wlan0 to 255.255.255.255 port 67

      DHCPOFFER from 192.168.25.1

      DHCPNAK from 192.168.25.1

      DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3

      DHCPREQUEST on wlan0 to 255.255.255.255 port 67

      DHCPOFFER from 192.168.25.1

      DHCPNAK from 192.168.25.1

        • 1. Re: DHCP Is making my board reboot
          Intel Corporation
          This message was posted on behalf of Intel Corporation

          Hi FocaaBR,
           
          Thanks for reaching out.
           
          I would like to know a little bit more information regarding this issue in order to further assist you. When did that behavior begin? Have you been able to use your Edison before facing this issue? How are you powering your Edison?
           
          I’ll be waiting for your response.                                              
           
          Regards,
          -Yermi A.
           

          • 2. Re: DHCP Is making my board reboot
            FocaaBR

            Hello!

             

            This behavior began out from nowhere. The day before this error began I was using the board normally. I thought that the problem was that I was not with network connection but when I restored the connection the error was still there.

            I tried to power with a phone charger and via usb. I measure the voltage level on the board and it is normal.

            • 3. Re: DHCP Is making my board reboot
              Intel Corporation
              This message was posted on behalf of Intel Corporation

              It could be a power issue, the Intel Edison board will reboot continuously or result in unpredictable behavior, especially when using Wi-Fi, if it is not receiving enough power. Could you please provide the specs of the phone charger you are using? Are you using the mini-breakout board or the Arduino expansion board?
               
              Regards,
              -Yermi A.
               

              • 4. Re: DHCP Is making my board reboot
                FocaaBR

                Hi Yermi,

                 

                I was using a Samsung Galaxy S7 charger. The USB is the left port of the Dell Gaming 15" with the cable of the charger. Regarding of the breakout/expansion, I'm using a custom board to fix the Edison with a DF40 connector because I'm using a GPRS and Zigbee module.

                 

                But what it is intriguing me is these DHCP messages. The supply interferes directly on it? Because if the supply is the problem the board should not even be "started boot", should it? It looks like it is starting to boot but when it tries to match the IP it could not connect and then restart the process.

                 

                Thank you.

                • 5. Re: DHCP Is making my board reboot
                  Intel Corporation
                  This message was posted on behalf of Intel Corporation

                  Power supply issues can cause that the board starts to boot, but suddenly it reboots and keeps in that cycle because it is not receiving enough current or power. It could be causality that it reboots when the DHCP messages appears.
                   
                  I would like to know if you have any of the official expansion boards, either the Arduino or mini-breakout board, and a power supply of 7-15V in order to test it and discard any power supply issues.
                   
                  Regards,
                  -Yermi A.
                   

                  • 6. Re: DHCP Is making my board reboot
                    FocaaBR

                    Hello,

                     

                    Yes. Actually I have an Arduino expansion for Intel Edison. I`ll try to boot from there.

                     

                    Thank you.

                    • 7. Re: DHCP Is making my board reboot
                      FocaaBR

                      Hello,

                       

                      I tried to boot with the Arduino Breakout but the problem persists. Any ideia what should I try this time?

                       

                      Thank you.

                      • 8. Re: DHCP Is making my board reboot
                        Intel Corporation
                        This message was posted on behalf of Intel Corporation

                        Hi FocaaBR,
                         
                        Have you powered (using the J1 connector) the Arduino expansion board just with the Edison module on it? I mean without using the GPRS and Zigbee modules.
                         
                        Another thing we can try is re-flashing the Edison, here you can find the instruction to do that: Flashing your Board.
                         
                        Regards,
                        -Yermi A.
                         

                        • 9. Re: DHCP Is making my board reboot
                          Intel Corporation
                          This message was posted on behalf of Intel Corporation

                          Hi FocaaBR,
                           
                          Do you have any updates?
                           
                          Regards,
                          -Yermi A.
                           

                          • 10. Re: DHCP Is making my board reboot
                            FocaaBR

                            Hi, Yermi!

                             

                            Sorry for the delay! Actually I tried to burn the .iso of my sdcard and the problem is gone.  What I think that was happening is that my application was saving the data inside the sdcard when I was without network and at some point the "database" was full and crash the sdcard image. Luckily I had a backup imagem so I formatted the sd then burn it again and everything is working!

                             

                            Thank you =D