On Sun, Nov 04, 2018 at 08:10:57PM +0300, Sergey Suloev wrote:
> To be exact, the issue does not happen in case I use default kernel config
> but only with the custom one.
Can you pls grab a new backtrace on latest kernels?
Thanks, Daniel
>
>
> On 10/2/18 2:14 PM, Noralf Trønnes wrote:
> >
>
To be exact, the issue does not happen in case I use default kernel
config but only with the custom one.
On 10/2/18 2:14 PM, Noralf Trønnes wrote:
Den 01.10.2018 21.45, skrev Noralf Trønnes:
Sergey Suloev reported a crash happening in drm_client_dev_hotplug()
when fbdev had failed to registe
This doesn't seem to fix the initially reported issue. The problem still
exists with 4.19.
On 10/2/18 2:14 PM, Noralf Trønnes wrote:
Den 01.10.2018 21.45, skrev Noralf Trønnes:
Sergey Suloev reported a crash happening in drm_client_dev_hotplug()
when fbdev had failed to register.
[ 9.1245
Den 01.10.2018 21.45, skrev Noralf Trønnes:
Sergey Suloev reported a crash happening in drm_client_dev_hotplug()
when fbdev had failed to register.
[9.124598] vc4_hdmi 3f902000.hdmi: ASoC: Failed to create component debugfs
directory
[9.147667] vc4_hdmi 3f902000.hdmi: vc4-hdmi-hifi <->
Sergey Suloev reported a crash happening in drm_client_dev_hotplug()
when fbdev had failed to register.
[9.124598] vc4_hdmi 3f902000.hdmi: ASoC: Failed to create component debugfs
directory
[9.147667] vc4_hdmi 3f902000.hdmi: vc4-hdmi-hifi <-> 3f902000.hdmi mapping
ok
[9.155184] vc4_h
