lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 17 Jun 2022 13:50:24 +0200
From:   MR <m.reichl@...etechno.de>
To:     linux-rockchip@...ts.infradead.org,
        Corentin Labbe <clabbe.montjoie@...il.com>
CC:     Robin Murphy <robin.murphy@....com>, heiko@...ech.de,
        robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: rk3399-roc-pc does not boot



Am 17. Juni 2022 13:47:05 MESZ schrieb Corentin Labbe <clabbe.montjoie@...il.com>:
>Le Fri, Jun 17, 2022 at 01:43:05PM +0200, MR a écrit :
>> 
>> 
>> Am 17. Juni 2022 11:58:03 MESZ schrieb Robin Murphy <robin.murphy@....com>:
>> >On 2022-06-17 10:06, Corentin Labbe wrote:
>> >> Hello
>> >> 
>> >> I try to add rk3399-roc-pc to kernelCI but this board fail to ends its boot with any kernel I try.
>> >> It boot normally up to starting init but it stucks shorty after.
>> >> It fail on 5.10, 5.15, 5.17, 5.18 and linux-next.
>> >> When disabling CONFIG_USB, the board boots successfully.
>> >> 
>> >> In dmesg I see OF: graph: no port node found in /i2c@...60000/usb-typec@22
>> >> According to Documentation/devicetree/bindings/usb/fcs,fusb302.txt, the port is mandatory.
>> >> Can it be possible that the problem was that the power port being disabled ?
>> >
>> >Indeed, I believe the OF graph error is just a meaningless annoyance, but the general problem sounds like it's probably the same thing that's come up before:
>> >
>> >https://lore.kernel.org/all/0ac6bbe7-6395-526d-213c-ac58a19d8673@fivetechno.de/
>> >
>> >Disabling CONFIG_TYPEC_FUSB302 or blacklisting the fusb302 module should help confirm that. I have no idea if it's still an open problem, or if it's been fixed and you might just need to define the proper power role in the DT; this just triggered a memory of that older thread :)
>> >
>> >Robin.
>> 
>> Yes, the issue above is still there. I therefore use dumb 5 V, 4 A USB power supplies  that do not react on the USB-C communication.
>> 
>> Markus
>
>@Markus
>Could you try the diff I just send ?

Right on holiday, but will test it next week.
>
>Thanks
>
>_______________________________________________
>Linux-rockchip mailing list
>Linux-rockchip@...ts.infradead.org
>http://lists.infradead.org/mailman/listinfo/linux-rockchip
>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ