linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: linux-usb@vger.kernel.org, open list <linux-kernel@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Peter.Chen@nxp.com, lkft-triage@lists.linaro.org,
	Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: msm_hsusb 78d9000.usb: failed to create device link to ci_hdrc.0.ulpi
Date: Mon, 17 Feb 2020 14:02:57 +0530	[thread overview]
Message-ID: <CA+G9fYtnwFVPQxgHOU2Bi9y5+q4sSsww47yxK+_3ZAQ9=kyhUg@mail.gmail.com> (raw)

arm64 APQ 8016 SBC ( Dragonboard 410c)  device running Linux next boot
failed due to below error.

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd030]
[    0.000000] Linux version 5.6.0-rc2-next-20200217 (oe-user@oe-host)
(gcc version 7.3.0 (GCC)) #1 SMP PREEMPT Mon Feb 17 04:27:31 UTC 2020
[    0.000000] Machine model: Qualcomm Technologies, Inc. APQ 8016 SBC
<>
[    4.439291] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.448891] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.457879] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.467331] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.475636] mmc0: new HS200 MMC card at address 0001
[    4.478895] mmcblk0: mmc0:0001 DS2008 7.28 GiB
[    4.480629] mmcblk0boot0: mmc0:0001 DS2008 partition 1 4.00 MiB
[    4.484719] mmcblk0boot1: mmc0:0001 DS2008 partition 2 4.00 MiB
[    4.492247] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.502611] mmcblk0rpmb: mmc0:0001 DS2008 partition 3 4.00 MiB,
chardev (234:0)
[    4.506949] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.517901] random: fast init done
[    4.521420] mmc1: new ultra high speed SDR104 SDHC card at address aaaa
[    4.523400] mmcblk1: mmc1:aaaa SL16G 14.8 GiB
[    4.532843] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.539131]  mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14
[    4.542309]  mmcblk1: p1
[    4.561843] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.573481] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.585283] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.592622] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.600074] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.607204] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi
[    4.614679] msm_hsusb 78d9000.usb: failed to create device link to
ci_hdrc.0.ulpi

metadata:
  git branch: master
  git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
  git commit: c25a951c50dca1da4a449a985a9debd82dc18573
  git describe: next-20200217
  make_kernelversion: 5.6.0-rc2
  kernel-config:
http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/dragonboard-410c/lkft/linux-next/705/config
  build-location:
http://snapshots.linaro.org/openembedded/lkft/lkft/sumo/dragonboard-410c/lkft/linux-next/705

ref:
https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20200217/testrun/1223296/log
https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20200217/testrun/1223301/log
https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20200217/testrun/1223310/log
https://qa-reports.linaro.org/lkft/linux-next-oe/build/next-20200217/testrun/1223308/log

             reply	other threads:[~2020-02-17  8:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17  8:32 Naresh Kamboju [this message]
2020-02-19  1:38 ` msm_hsusb 78d9000.usb: failed to create device link to ci_hdrc.0.ulpi Peter Chen
2020-02-19  2:45   ` Jack Pham
2020-02-19  9:23     ` Andy Shevchenko
2020-02-19 10:00       ` Alexandre Torgue
2020-02-19 11:28         ` Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+G9fYtnwFVPQxgHOU2Bi9y5+q4sSsww47yxK+_3ZAQ9=kyhUg@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=Peter.Chen@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).