Hello Steve,
On 02.02.24 02:46, Steven Rostedt wrote:
> On Thu, 1 Feb 2024 13:21:37 +0100
> Ahmad Fatoum wrote:
>> For this to be maximally useful, I need to configure this not only at
>> boot-time,
>> but also dump the ftrace buffer at boot time. Probe deferral can hinder the
>> kernel from
>>
Hello Masami-san,
On 02.02.24 07:04, Masami Hiramatsu (Google) wrote:
> On Thu, 1 Feb 2024 13:21:37 +0100
> Ahmad Fatoum wrote:
>> For drivers that don't call dev_err_probe, I find myself sometimes doing
>> printf
>> debugging inside the probe function.
[snip]
>> I would like to replace this w
Hi Ahmad,
On Thu, 1 Feb 2024 13:21:37 +0100
Ahmad Fatoum wrote:
> Hello,
>
> I semi-regularly debug probe failures. For drivers that use dev_err_probe
> rigorously, this is a quick matter: The probe function records a deferral
> reason
> and if the deferral persists, deferred_probe_timeout_wor
On Thu, 1 Feb 2024 13:21:37 +0100
Ahmad Fatoum wrote:
> Hello,
>
> I semi-regularly debug probe failures. For drivers that use dev_err_probe
> rigorously, this is a quick matter: The probe function records a deferral
> reason
> and if the deferral persists, deferred_probe_timeout_work_func() wi
Hello,
I semi-regularly debug probe failures. For drivers that use dev_err_probe
rigorously, this is a quick matter: The probe function records a deferral reason
and if the deferral persists, deferred_probe_timeout_work_func() will print
the collected reasons, even if PID 1 is never started.
For
5 matches
Mail list logo