On 11/16/2018 9:09 AM, Viresh Kumar wrote:
On Thu, Nov 15, 2018 at 4:23 PM Srinivas Kandagatla
wrote:
Yes, this is not the solution, but it proves that the hand-off between
booloaders and kernel is the issue.
In general there is wider issue with resources hand-off between
bootloader and kerne
On Thu, Nov 15, 2018 at 4:23 PM Srinivas Kandagatla
wrote:
> Yes, this is not the solution, but it proves that the hand-off between
> booloaders and kernel is the issue.
>
> In general there is wider issue with resources hand-off between
> bootloader and kernel.
>
> There has been some proposal i
On 15/11/18 10:33, Sai Prakash Ranjan wrote:
On 11/13/2018 3:14 PM, Srinivas Kandagatla wrote:
Hi Sai,
On 25/10/18 15:36, saiprakash.ran...@codeaurora.org wrote:
"If I disable dma node and LS-UART0, then I don't see any crash and
ftrace also works fine"
And one more observation is that e
On 11/13/2018 3:14 PM, Srinivas Kandagatla wrote:
Hi Sai,
On 25/10/18 15:36, saiprakash.ran...@codeaurora.org wrote:
"If I disable dma node and LS-UART0, then I don't see any crash and
ftrace also works fine"
And one more observation is that even without ftrace cmdline, if I use
earlycon and
Hi Sai,
On 25/10/18 15:36, saiprakash.ran...@codeaurora.org wrote:
"If I disable dma node and LS-UART0, then I don't see any crash and
ftrace also works fine"
And one more observation is that even without ftrace cmdline, if I use
earlycon and disable dma, I face the same crash.
So basically
On 10/19/2018 8:42 PM, Steven Rostedt wrote:
On Fri, 19 Oct 2018 20:18:19 +0530
Sai Prakash Ranjan wrote:
You said that if you add 'ftrace_filter=msm_read' to the command
line,
it still crashes?
So only tracing that function we have an issue, right?
Tracing msm_read does cause the crash,
On Fri, 19 Oct 2018 20:18:19 +0530
Sai Prakash Ranjan wrote:
> > You said that if you add 'ftrace_filter=msm_read' to the command line,
> > it still crashes?
> >
> > So only tracing that function we have an issue, right?
> >
>
> Tracing msm_read does cause the crash, but that is not the onl
On 10/19/2018 7:21 PM, Steven Rostedt wrote:
On Fri, 19 Oct 2018 12:24:05 +0530
Sai Prakash Ranjan wrote:
Anyone see any problems here?
This seems sane to me, he says in the other thread that he put 'notrace' to
the msm serial functions (which AIUI should prevent ftrace instrumentation)
and
On Fri, 19 Oct 2018 12:24:05 +0530
Sai Prakash Ranjan wrote:
> >> Anyone see any problems here?
> >
> > This seems sane to me, he says in the other thread that he put 'notrace' to
> > the msm serial functions (which AIUI should prevent ftrace instrumentation)
> > and he still sees the issue.
>
On 10/19/2018 9:47 AM, Joel Fernandes wrote:
On Thu, Oct 18, 2018 at 09:17:06AM -0400, Steven Rostedt wrote:
On Thu, 18 Oct 2018 10:51:18 +0530
Sai Prakash Ranjan wrote:
So something else is causing an issue besides just msm_read.
Can you do an objdump -dr of the entire vmlinux binary and gz
On Thu, Oct 18, 2018 at 09:17:06AM -0400, Steven Rostedt wrote:
> On Thu, 18 Oct 2018 10:51:18 +0530
> Sai Prakash Ranjan wrote:
>
> > > So something else is causing an issue besides just msm_read.
> > >
> > > Can you do an objdump -dr of the entire vmlinux binary and gzip it and
> > > post it s
On Thu, 18 Oct 2018 10:51:18 +0530
Sai Prakash Ranjan wrote:
> > So something else is causing an issue besides just msm_read.
> >
> > Can you do an objdump -dr of the entire vmlinux binary and gzip it and
> > post it somewhere. Not sure if it would be too big to email. You could
> > try sending
On 10/18/2018 8:03 AM, Steven Rostedt wrote:
On Wed, 17 Oct 2018 00:36:05 +0530
Sai Prakash Ranjan wrote:
On 10/17/2018 12:33 AM, Steven Rostedt wrote:
On Wed, 17 Oct 2018 00:31:03 +0530
Sai Prakash Ranjan wrote:
Haa seems like you are right! With "ftrace=function
ftrace_filter=msm_read
On Wed, 17 Oct 2018 00:36:05 +0530
Sai Prakash Ranjan wrote:
> On 10/17/2018 12:33 AM, Steven Rostedt wrote:
> > On Wed, 17 Oct 2018 00:31:03 +0530
> > Sai Prakash Ranjan wrote:
> >
> >> Haa seems like you are right! With "ftrace=function
> >> ftrace_filter=msm_read" , I can trigger the crash
On Wed, Oct 17, 2018 at 10:56 AM, Joel Fernandes wrote:
> On Wed, Oct 17, 2018 at 08:19:41PM +0530, Sai Prakash Ranjan wrote:
>> On 10/17/2018 5:08 PM, Sai Prakash Ranjan wrote:
>> > >
>> > > What do you think about the (untested) patch below? It seems to me
>> > > that it
>> > > should solve the
On Wed, Oct 17, 2018 at 08:19:41PM +0530, Sai Prakash Ranjan wrote:
> On 10/17/2018 5:08 PM, Sai Prakash Ranjan wrote:
> > >
> > > What do you think about the (untested) patch below? It seems to me
> > > that it
> > > should solve the issue of missing early crash dumps, but I have not
> > > tested
On 10/17/2018 5:08 PM, Sai Prakash Ranjan wrote:
What do you think about the (untested) patch below? It seems to me
that it
should solve the issue of missing early crash dumps, but I have not
tested it
yet. Sai, would you mind trying it out and let me know if you can see the
early crash dumps
On 10/17/2018 4:39 AM, Joel Fernandes wrote:
On Tue, Oct 16, 2018 at 05:08:25PM +0530, Sai Prakash Ranjan wrote:
Hi,
On dragonboard 410c, with "ftrace=function" boot args, the console output
slows down and board resets without any backtrace as below. This is tested
on latest kernel and seems to
On 10/17/2018 3:43 PM, Joel Fernandes wrote:
Hi Kees,
On Tue, Oct 16, 2018 at 10:02:53AM -0700, Kees Cook wrote:
On Tue, Oct 16, 2018 at 8:29 AM, Steven Rostedt wrote:
On Tue, 16 Oct 2018 17:08:25 +0530
Sai Prakash Ranjan wrote:
One more thing is for pstore dmesg-ramoops, I had to change
la
On 10/17/2018 2:21 AM, Stephen Boyd wrote:
Quoting Sai Prakash Ranjan (2018-10-16 12:35:57)
On 10/17/2018 12:45 AM, Steven Rostedt wrote:
On Wed, 17 Oct 2018 00:36:05 +0530
Sai Prakash Ranjan wrote:
On 10/17/2018 12:33 AM, Steven Rostedt wrote:
On Wed, 17 Oct 2018 00:31:03 +0530
Sai Prakash
Hi Kees,
On Tue, Oct 16, 2018 at 10:02:53AM -0700, Kees Cook wrote:
> On Tue, Oct 16, 2018 at 8:29 AM, Steven Rostedt wrote:
> > On Tue, 16 Oct 2018 17:08:25 +0530
> > Sai Prakash Ranjan wrote:
> >> One more thing is for pstore dmesg-ramoops, I had to change
> >> late_initcall to postcore_initca
On Tue, Oct 16, 2018 at 05:08:25PM +0530, Sai Prakash Ranjan wrote:
> Hi,
>
> On dragonboard 410c, with "ftrace=function" boot args, the console output
> slows down and board resets without any backtrace as below. This is tested
> on latest kernel and seems to exist even in older kernels as well.
Quoting Sai Prakash Ranjan (2018-10-16 12:35:57)
> On 10/17/2018 12:45 AM, Steven Rostedt wrote:
> > On Wed, 17 Oct 2018 00:36:05 +0530
> > Sai Prakash Ranjan wrote:
> >
> >> On 10/17/2018 12:33 AM, Steven Rostedt wrote:
> >>> On Wed, 17 Oct 2018 00:31:03 +0530
> >>> Sai Prakash Ranjan wrote:
>
On 10/17/2018 12:46 AM, Steven Rostedt wrote:
On Tue, 16 Oct 2018 15:15:16 -0400
Steven Rostedt wrote:
I'd like to see the full command line as well. I bet if you remove the
qcom,msm-uartdm from the command line, and had just ftrace=function, it
may also boot fine too. Can you try that?
Note
On Tue, 16 Oct 2018 15:15:16 -0400
Steven Rostedt wrote:
> I'd like to see the full command line as well. I bet if you remove the
> qcom,msm-uartdm from the command line, and had just ftrace=function, it
> may also boot fine too. Can you try that?
Note, I probably wont respond for the rest of th
On Wed, 17 Oct 2018 00:36:05 +0530
Sai Prakash Ranjan wrote:
> On 10/17/2018 12:33 AM, Steven Rostedt wrote:
> > On Wed, 17 Oct 2018 00:31:03 +0530
> > Sai Prakash Ranjan wrote:
> >
> >> Haa seems like you are right! With "ftrace=function
> >> ftrace_filter=msm_read" , I can trigger the crash
On 10/17/2018 12:33 AM, Steven Rostedt wrote:
On Wed, 17 Oct 2018 00:31:03 +0530
Sai Prakash Ranjan wrote:
Haa seems like you are right! With "ftrace=function
ftrace_filter=msm_read" , I can trigger the crash, but
sadly "ftrace_notrace=msm_read" also crashes.
So there's more than one problem
On Wed, 17 Oct 2018 00:31:03 +0530
Sai Prakash Ranjan wrote:
> Haa seems like you are right! With "ftrace=function
> ftrace_filter=msm_read" , I can trigger the crash, but
> sadly "ftrace_notrace=msm_read" also crashes.
So there's more than one problem area.
What about ftrace_notrace=m*
?
--
On 10/17/2018 12:11 AM, Steven Rostedt wrote:
On Tue, 16 Oct 2018 23:55:14 +0530
Sai Prakash Ranjan wrote:
On 10/16/2018 11:46 PM, Steven Rostedt wrote:
[ Removed ivan.iva...@linaro.org due to getting mail delivery errors ]
On Tue, 16 Oct 2018 23:35:00 +0530
Sai Prakash Ranjan wrote:
On Tue, 16 Oct 2018 23:55:14 +0530
Sai Prakash Ranjan wrote:
> On 10/16/2018 11:46 PM, Steven Rostedt wrote:
> >
> > [ Removed ivan.iva...@linaro.org due to getting mail delivery errors ]
> >
> > On Tue, 16 Oct 2018 23:35:00 +0530
> > Sai Prakash Ranjan wrote:
> >
> >> Ok got it, this sound
On 10/16/2018 11:46 PM, Steven Rostedt wrote:
[ Removed ivan.iva...@linaro.org due to getting mail delivery errors ]
On Tue, 16 Oct 2018 23:35:00 +0530
Sai Prakash Ranjan wrote:
Ok got it, this sounds fun. I'll give it a try.
Awesome, I'm looking forward to seeing what you come up with.
[ Removed ivan.iva...@linaro.org due to getting mail delivery errors ]
On Tue, 16 Oct 2018 23:35:00 +0530
Sai Prakash Ranjan wrote:
> Ok got it, this sounds fun. I'll give it a try.
Awesome, I'm looking forward to seeing what you come up with.
-- Steve
On 10/16/2018 11:18 PM, Steven Rostedt wrote:
On Tue, 16 Oct 2018 23:06:24 +0530
Sai Prakash Ranjan wrote:
On 10/16/2018 10:27 PM, Steven Rostedt wrote:
OK, can you add to the command line:
ftrace=function ftrace_filter=*schedule*
to see if it's a specific function that may be causing t
On Tue, 16 Oct 2018 23:06:24 +0530
Sai Prakash Ranjan wrote:
> On 10/16/2018 10:27 PM, Steven Rostedt wrote:
> >
> > OK, can you add to the command line:
> >
> > ftrace=function ftrace_filter=*schedule*
> >
> > to see if it's a specific function that may be causing the issue (but
> > hopeful
On 10/16/2018 10:27 PM, Steven Rostedt wrote:
OK, can you add to the command line:
ftrace=function ftrace_filter=*schedule*
to see if it's a specific function that may be causing the issue (but
hopefully it's not one of the scheduling functions that caused it).
Target boots fine with this
On Tue, Oct 16, 2018 at 8:29 AM, Steven Rostedt wrote:
> On Tue, 16 Oct 2018 17:08:25 +0530
> Sai Prakash Ranjan wrote:
>> One more thing is for pstore dmesg-ramoops, I had to change
>> late_initcall to postcore_initcall which brings the question as to why
>> we changed to late_initcall?
>> Simpl
On Tue, 16 Oct 2018 22:05:23 +0530
Sai Prakash Ranjan wrote:
> On 10/16/2018 8:59 PM, Steven Rostedt wrote:
> > On Tue, 16 Oct 2018 17:08:25 +0530
> > Sai Prakash Ranjan wrote:
> >
> >> Hi,
> >>
> >> On dragonboard 410c, with "ftrace=function" boot args, the console
> >> output slows down and
On 10/16/2018 8:59 PM, Steven Rostedt wrote:
On Tue, 16 Oct 2018 17:08:25 +0530
Sai Prakash Ranjan wrote:
Hi,
On dragonboard 410c, with "ftrace=function" boot args, the console
output slows down and board resets without any backtrace as below. This
is tested on latest kernel and seems to exis
On Tue, 16 Oct 2018 17:08:25 +0530
Sai Prakash Ranjan wrote:
> Hi,
>
> On dragonboard 410c, with "ftrace=function" boot args, the console
> output slows down and board resets without any backtrace as below. This
> is tested on latest kernel and seems to exist even in older kernels as well.
So
On 10/16/2018 5:14 PM, Greg Kroah-Hartman wrote:
On Tue, Oct 16, 2018 at 05:08:25PM +0530, Sai Prakash Ranjan wrote:
Hi,
On dragonboard 410c, with "ftrace=function" boot args, the console output
slows down and board resets without any backtrace as below. This is tested
on latest kernel and seem
On Tue, Oct 16, 2018 at 05:08:25PM +0530, Sai Prakash Ranjan wrote:
> Hi,
>
> On dragonboard 410c, with "ftrace=function" boot args, the console output
> slows down and board resets without any backtrace as below. This is tested
> on latest kernel and seems to exist even in older kernels as well.
Hi,
On dragonboard 410c, with "ftrace=function" boot args, the console
output slows down and board resets without any backtrace as below. This
is tested on latest kernel and seems to exist even in older kernels as well.
[2.949164] EINJ: ACPI disabled.
[3.133001] Serial: 8250/16550 dri
42 matches
Mail list logo
