On Monday, March 27, 2017 09:08:43 AM Josh Poimboeuf wrote:
> On Sat, Mar 25, 2017 at 02:20:11PM +0100, Rafael J. Wysocki wrote:
> > On Friday, March 24, 2017 02:41:14 PM Steven Rostedt wrote:
> > > On Fri, 24 Mar 2017 13:12:54 -0500
> > > Josh Poimboeuf wrote:
> > >
> > >
On Monday, March 27, 2017 09:08:43 AM Josh Poimboeuf wrote:
> On Sat, Mar 25, 2017 at 02:20:11PM +0100, Rafael J. Wysocki wrote:
> > On Friday, March 24, 2017 02:41:14 PM Steven Rostedt wrote:
> > > On Fri, 24 Mar 2017 13:12:54 -0500
> > > Josh Poimboeuf wrote:
> > >
> > >
> > > > Instead I was
On Sat, Mar 25, 2017 at 02:20:11PM +0100, Rafael J. Wysocki wrote:
> On Friday, March 24, 2017 02:41:14 PM Steven Rostedt wrote:
> > On Fri, 24 Mar 2017 13:12:54 -0500
> > Josh Poimboeuf wrote:
> >
> >
> > > Instead I was able to "fix" it by ignoring ftrace calls in real
On Sat, Mar 25, 2017 at 02:20:11PM +0100, Rafael J. Wysocki wrote:
> On Friday, March 24, 2017 02:41:14 PM Steven Rostedt wrote:
> > On Fri, 24 Mar 2017 13:12:54 -0500
> > Josh Poimboeuf wrote:
> >
> >
> > > Instead I was able to "fix" it by ignoring ftrace calls in real mode:
> > >
> > >
On Friday, March 24, 2017 02:41:14 PM Steven Rostedt wrote:
> On Fri, 24 Mar 2017 13:12:54 -0500
> Josh Poimboeuf wrote:
>
>
> > Instead I was able to "fix" it by ignoring ftrace calls in real mode:
> >
> > -
> > index 8f3d9cf..5c0d0c6 100644
> > ---
On Friday, March 24, 2017 02:41:14 PM Steven Rostedt wrote:
> On Fri, 24 Mar 2017 13:12:54 -0500
> Josh Poimboeuf wrote:
>
>
> > Instead I was able to "fix" it by ignoring ftrace calls in real mode:
> >
> > -
> > index 8f3d9cf..5c0d0c6 100644
> > --- a/arch/x86/kernel/ftrace.c
> > +++
On Fri, 24 Mar 2017 13:12:54 -0500
Josh Poimboeuf wrote:
> Instead I was able to "fix" it by ignoring ftrace calls in real mode:
>
> -
> index 8f3d9cf..5c0d0c6 100644
> --- a/arch/x86/kernel/ftrace.c
> +++ b/arch/x86/kernel/ftrace.c
> @@ -983,6 +983,9 @@ void
On Fri, 24 Mar 2017 13:12:54 -0500
Josh Poimboeuf wrote:
> Instead I was able to "fix" it by ignoring ftrace calls in real mode:
>
> -
> index 8f3d9cf..5c0d0c6 100644
> --- a/arch/x86/kernel/ftrace.c
> +++ b/arch/x86/kernel/ftrace.c
> @@ -983,6 +983,9 @@ void prepare_ftrace_return(unsigned
On Tue, Mar 21, 2017 at 09:44:03PM +0100, Paul Menzel wrote:
> I checked out Linux 4.9.16, applied your patch on top, and copied the Debian
> 4.9 Linux kernel configuration, did `make menuconfig`, disabled building
> debugging symbols, and executed `ARCH=i386 make -j40 deb-pkg`.
>
> I installed
On Tue, Mar 21, 2017 at 09:44:03PM +0100, Paul Menzel wrote:
> I checked out Linux 4.9.16, applied your patch on top, and copied the Debian
> 4.9 Linux kernel configuration, did `make menuconfig`, disabled building
> debugging symbols, and executed `ARCH=i386 make -j40 deb-pkg`.
>
> I installed
Dear Josh,
On 2017-03-21 21:44, Paul Menzel wrote:
On 2017-03-16 14:56, Josh Poimboeuf wrote:
Paul Menzel reported a warning:
WARNING: CPU: 0 PID: 774 at
/build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functions_graph.c:233
ftrace_return_to_handler+0x1aa/0x1e0
Bad frame pointer:
Dear Josh,
On 2017-03-21 21:44, Paul Menzel wrote:
On 2017-03-16 14:56, Josh Poimboeuf wrote:
Paul Menzel reported a warning:
WARNING: CPU: 0 PID: 774 at
/build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functions_graph.c:233
ftrace_return_to_handler+0x1aa/0x1e0
Bad frame pointer:
Dear Josh,
On 2017-03-16 14:56, Josh Poimboeuf wrote:
Paul Menzel reported a warning:
WARNING: CPU: 0 PID: 774 at
/build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functions_graph.c:233
ftrace_return_to_handler+0x1aa/0x1e0
Bad frame pointer: expected f6919d98, received f6919db0
from
Dear Josh,
On 2017-03-16 14:56, Josh Poimboeuf wrote:
Paul Menzel reported a warning:
WARNING: CPU: 0 PID: 774 at
/build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functions_graph.c:233
ftrace_return_to_handler+0x1aa/0x1e0
Bad frame pointer: expected f6919d98, received f6919db0
from
On Thu, 16 Mar 2017 08:56:28 -0500
Josh Poimboeuf wrote:
> Paul Menzel reported a warning:
>
> WARNING: CPU: 0 PID: 774 at
> /build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functions_graph.c:233
> ftrace_return_to_handler+0x1aa/0x1e0
> Bad frame pointer: expected
On Thu, 16 Mar 2017 08:56:28 -0500
Josh Poimboeuf wrote:
> Paul Menzel reported a warning:
>
> WARNING: CPU: 0 PID: 774 at
> /build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functions_graph.c:233
> ftrace_return_to_handler+0x1aa/0x1e0
> Bad frame pointer: expected f6919d98, received
Paul Menzel reported a warning:
WARNING: CPU: 0 PID: 774 at
/build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functions_graph.c:233
ftrace_return_to_handler+0x1aa/0x1e0
Bad frame pointer: expected f6919d98, received f6919db0
from func acpi_pm_device_sleep_wake return to c43b6f9d
The
Paul Menzel reported a warning:
WARNING: CPU: 0 PID: 774 at
/build/linux-ROBWaj/linux-4.9.13/kernel/trace/trace_functions_graph.c:233
ftrace_return_to_handler+0x1aa/0x1e0
Bad frame pointer: expected f6919d98, received f6919db0
from func acpi_pm_device_sleep_wake return to c43b6f9d
The
18 matches
Mail list logo