[U-Boot] Sandbox 'usb start' causes segment fault
Simon Glass
sjg at chromium.org
Thu Sep 21 04:58:30 UTC 2017
Hi Bin,
On 20 September 2017 at 08:06, Bin Meng <bmeng.cn at gmail.com> wrote:
> Hi Simon,
>
> On Wed, Sep 20, 2017 at 9:49 PM, Simon Glass <sjg at chromium.org> wrote:
>> Hi Bin,
>>
>> On 19 September 2017 at 21:40, Bin Meng <bmeng.cn at gmail.com> wrote:
>>> Hi,
>>>
>>> Not sure if I am running sandbox correctly with USB support, but here
>>> is the log:
>>>
>>> $ ./u-boot -D
>>>
>>>
>>> U-Boot 2017.09-00191-gc145392-dirty (Sep 17 2017 - 21:33:01 +0800)
>>>
>>> Model: sandbox
>>> DRAM: 128 MiB
>>> MMC:
>>> Using default environment
>>>
>>> In: cros-ec-keyb
>>> Out: vidconsole
>>> Err: vidconsole
>>> Model: sandbox
>>> SCSI: Net: eth0: eth at 10002000, eth1: eth at 80000000, eth5: eth at 90000000
>>> IDE: Bus 0: not available
>>> => usb start
>>> starting USB...
>>> USB0: scanning bus 0 for devices... Segmentation fault (core dumped)
>>
>> I don't seem to have that commit, but for me, it works OK.
>>
>
> Oops!
>
> commit c145392ce0926d92aad6a42b3ab694bc7e232f7f
> Author: Simon Glass <sjg at chromium.org>
> Date: Sat Sep 16 15:23:26 2017 -0600
>
> log: Add documentation
>
> Add documentation for the log system.
>
> Signed-off-by: Simon Glass <sjg at chromium.org>
>
> Guess maybe your log series causes some issues?
Yes I think so, sorry there are quite a few test failures. I'll take a
look before v2 but wanted to get the series out for comment as I have
been stewing on it for over a month.
Regards,
Simon
More information about the U-Boot
mailing list