On Sun, Mar 30, 2014 at 08:41:18PM +0800, Fengguang Wu wrote:
> This fix is not yet in linux-next, can anyone help merge it? Thanks!
sorry for late reply, I was out last week,
I'll resend this with proper changelog
jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Sun, Mar 30, 2014 at 08:41:18PM +0800, Fengguang Wu wrote:
This fix is not yet in linux-next, can anyone help merge it? Thanks!
sorry for late reply, I was out last week,
I'll resend this with proper changelog
jirka
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
This fix is not yet in linux-next, can anyone help merge it? Thanks!
On Tue, Mar 11, 2014 at 08:14:56PM +0800, Fengguang Wu wrote:
> Jiri,
>
> It works, thank you!
>
> Tested-by: Fengguang Wu
>
> > ---
> > diff --git a/kernel/events/core.c b/kernel/events/core.c
> > index 661951a..a53857e
This fix is not yet in linux-next, can anyone help merge it? Thanks!
On Tue, Mar 11, 2014 at 08:14:56PM +0800, Fengguang Wu wrote:
Jiri,
It works, thank you!
Tested-by: Fengguang Wu fengguang...@intel.com
---
diff --git a/kernel/events/core.c b/kernel/events/core.c
index
Jiri,
It works, thank you!
Tested-by: Fengguang Wu
> ---
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 661951a..a53857e 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -5423,6 +5423,8 @@ struct swevent_htable {
>
> /* Recursion avoidance in
Jiri,
It works, thank you!
Tested-by: Fengguang Wu fengguang...@intel.com
---
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 661951a..a53857e 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -5423,6 +5423,8 @@ struct swevent_htable {
/* Recursion
Hi Jiri,
On Mon, Mar 10, 2014 at 01:53:19PM +0100, Jiri Olsa wrote:
> On Sat, Mar 08, 2014 at 02:51:53PM +0800, Fengguang Wu wrote:
> >
> > Hi all,
> >
> > This is a very old WARNING, too old to be bisectable. The below 3 different
> > back traces show that it's always triggered by trinity at
On Mon, Mar 10, 2014 at 11:40:23PM +0100, Jiri Olsa wrote:
> On Mon, Mar 10, 2014 at 01:53:19PM +0100, Jiri Olsa wrote:
> > On Sat, Mar 08, 2014 at 02:51:53PM +0800, Fengguang Wu wrote:
> > >
> > > Hi all,
> > >
> > > This is a very old WARNING, too old to be bisectable. The below 3
> > >
On Mon, Mar 10, 2014 at 01:53:19PM +0100, Jiri Olsa wrote:
> On Sat, Mar 08, 2014 at 02:51:53PM +0800, Fengguang Wu wrote:
> >
> > Hi all,
> >
> > This is a very old WARNING, too old to be bisectable. The below 3 different
> > back traces show that it's always triggered by trinity at system
On Sat, Mar 08, 2014 at 02:51:53PM +0800, Fengguang Wu wrote:
>
> Hi all,
>
> This is a very old WARNING, too old to be bisectable. The below 3 different
> back traces show that it's always triggered by trinity at system reboot time.
> Any ideas to quiet it? Thank you!
hi,
is there cpu hotplug
On Sat, Mar 08, 2014 at 02:51:53PM +0800, Fengguang Wu wrote:
Hi all,
This is a very old WARNING, too old to be bisectable. The below 3 different
back traces show that it's always triggered by trinity at system reboot time.
Any ideas to quiet it? Thank you!
hi,
is there cpu hotplug
On Mon, Mar 10, 2014 at 01:53:19PM +0100, Jiri Olsa wrote:
On Sat, Mar 08, 2014 at 02:51:53PM +0800, Fengguang Wu wrote:
Hi all,
This is a very old WARNING, too old to be bisectable. The below 3 different
back traces show that it's always triggered by trinity at system reboot
time.
On Mon, Mar 10, 2014 at 11:40:23PM +0100, Jiri Olsa wrote:
On Mon, Mar 10, 2014 at 01:53:19PM +0100, Jiri Olsa wrote:
On Sat, Mar 08, 2014 at 02:51:53PM +0800, Fengguang Wu wrote:
Hi all,
This is a very old WARNING, too old to be bisectable. The below 3
different
back
Hi Jiri,
On Mon, Mar 10, 2014 at 01:53:19PM +0100, Jiri Olsa wrote:
On Sat, Mar 08, 2014 at 02:51:53PM +0800, Fengguang Wu wrote:
Hi all,
This is a very old WARNING, too old to be bisectable. The below 3 different
back traces show that it's always triggered by trinity at system
14 matches
Mail list logo
