On Wed, Nov 27, 2019 at 2:48 PM Valdis Klētnieks
wrote:
>
> On Tue, 26 Nov 2019 22:31:08 +, Lucas Tanure said:
> > Hi,
> >
> > What about ftrace ? Documentation/trace/ftrace.txt
>
> That won't help - his ^@^@^@ is a result of the system stopping and no longer
> writing to disk, so his logfile
On Tue, 26 Nov 2019 22:31:08 +, Lucas Tanure said:
> Hi,
>
> What about ftrace ? Documentation/trace/ftrace.txt
That won't help - his ^@^@^@ is a result of the system stopping and no longer
writing to disk, so his logfile has blocks allocated to it but not yet written
to.
Using ftrace will
Hi,
What about ftrace ? Documentation/trace/ftrace.txt
Thanks
Lucas
On Tue, Nov 26, 2019 at 8:08 PM aleave wrote:
>
> Hi everyone,
>
> I'm modifying kernel code and running into system dead-lock issues. I have
> printk statements to try to retrieve info about the freeze after I do a hard
>
Hi everyone,
I'm modifying kernel code and running into system dead-lock issues. I have
printk statements to try to retrieve info about the freeze after I do a hard
shutdown, but printk is asynchronous so /var/log/kern.log only shows NULL
character gibberish instead (^@^@^@^@). Is there a way
