This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Yocto, meta-ti 4.1 kernel fetcher failure



Hello,

Trying to fetch the source code for the 4.1 kernel fails. This is the only recipe during a clean (no downloads or sstate-cache) build that fails the fetch task. We are using socat on the git protocol to get around the local firewall. I don't believe there is a problem with our proxy settings since we are able to download source for all other packages that are part of the build.

WARNING: Failed to fetch URL git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git;protocol=git;branch=ti-lsk-linux-4.1.y, attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 128, output:
Cloning into bare repository '/home/devbuild/yocto-fido/build/downloads/git2/git.ti.com.ti-linux-kernel.ti-linux-kernel.git'...
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
ERROR: Function failed: Fetcher failure for URL: 'git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git;protocol=git;branch=ti-lsk-linux-4.1.y'. Unable to fetch URL from any source.
NOTE: recipe linux-ti-staging-4.1.18+gitAUTOINC+6b41ca0b94-r22l.18: task do_fetch: Failed
ERROR: Task 73 (/home/devbuild/yocto-fido/poky/../sources/meta-ti/recipes-kernel/linux/linux-ti-staging_4.1.bb, do_fetch) failed with exit code '1'

Regards,

Tim Entinger

  • Hello,

    Did you follow this guide:
    processors.wiki.ti.com/.../Processor_SDK_Building_The_SDK
    What is the device that you are using here?

    BR
    Margarita
  • That does not help, because as I mentioned in my post, I am able to fetch other sources from git.ti.com using bitbake. From a terminal prompt on the same machine I can do

    git clone --branch=ti-lsk-linux-4.1.y git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git

    and I am able to checkout the ti-lsk-linux-4.1.y branch, but it's at the HEAD revision. From there I can checkout the proper commit id specified by SRCREV in the recipe. A acceptable workaround could be to provide an alternative mirror in the recipe to download a tar file of the source if the git protocol fails. The SRCREV isn't being updated in the recipe to follow new work done on the branch so I wouldn't expect a lot of churn.