On Thu, 2014-06-19 at 20:20 +0900, Masami Hiramatsu wrote:
> (2014/06/19 20:01), Masami Hiramatsu wrote:
>
> > Ah, those messages should be shown in dmesg when booting if it doesn't
> > work,
> > because the messages are printed by initialization process of kprobe
> > blacklist.
(2014/06/19 20:01), Masami Hiramatsu wrote:
> Ah, those messages should be shown in dmesg when booting if it doesn't
> work,
> because the messages are printed by initialization process of kprobe
> blacklist.
> So, reproducing it is just enabling CONFIG_KPROBES and boot it.
(2014/06/19 18:45), Suzuki K. Poulose wrote:
> On 06/19/2014 12:56 PM, Masami Hiramatsu wrote:
>> (2014/06/19 15:40), Suzuki K. Poulose wrote:
>>> On 06/19/2014 10:22 AM, Masami Hiramatsu wrote:
(2014/06/19 10:30), Michael Ellerman wrote:
> On Wed, 2014-06-18 at 17:46 +0900, Masami
(2014/06/19 15:40), Suzuki K. Poulose wrote:
> On 06/19/2014 10:22 AM, Masami Hiramatsu wrote:
>> (2014/06/19 10:30), Michael Ellerman wrote:
>>> On Wed, 2014-06-18 at 17:46 +0900, Masami Hiramatsu wrote:
(2014/06/18 16:56), Michael Ellerman wrote:
> On Fri, 2014-06-06 at 15:38 +0900,
(2014/06/19 15:40), Suzuki K. Poulose wrote:
On 06/19/2014 10:22 AM, Masami Hiramatsu wrote:
(2014/06/19 10:30), Michael Ellerman wrote:
On Wed, 2014-06-18 at 17:46 +0900, Masami Hiramatsu wrote:
(2014/06/18 16:56), Michael Ellerman wrote:
On Fri, 2014-06-06 at 15:38 +0900, Masami Hiramatsu
(2014/06/19 18:45), Suzuki K. Poulose wrote:
On 06/19/2014 12:56 PM, Masami Hiramatsu wrote:
(2014/06/19 15:40), Suzuki K. Poulose wrote:
On 06/19/2014 10:22 AM, Masami Hiramatsu wrote:
(2014/06/19 10:30), Michael Ellerman wrote:
On Wed, 2014-06-18 at 17:46 +0900, Masami Hiramatsu wrote:
(2014/06/19 20:01), Masami Hiramatsu wrote:
Ah, those messages should be shown in dmesg when booting if it doesn't
work,
because the messages are printed by initialization process of kprobe
blacklist.
So, reproducing it is just enabling CONFIG_KPROBES and boot it.
Well, we don't get
On Thu, 2014-06-19 at 20:20 +0900, Masami Hiramatsu wrote:
(2014/06/19 20:01), Masami Hiramatsu wrote:
Ah, those messages should be shown in dmesg when booting if it doesn't
work,
because the messages are printed by initialization process of kprobe
blacklist.
So, reproducing it is
On Wed, 2014-06-18 at 17:46 +0900, Masami Hiramatsu wrote:
> (2014/06/18 16:56), Michael Ellerman wrote:
> > On Fri, 2014-06-06 at 15:38 +0900, Masami Hiramatsu wrote:
> >> Ping?
> >>
> >> I guess this should go to 3.16 branch, shouldn't it?
> >
> >>> diff --git a/arch/powerpc/include/asm/types.h
(2014/06/18 16:56), Michael Ellerman wrote:
> On Fri, 2014-06-06 at 15:38 +0900, Masami Hiramatsu wrote:
>> Ping?
>>
>> I guess this should go to 3.16 branch, shouldn't it?
>
>>> diff --git a/arch/powerpc/include/asm/types.h
>>> b/arch/powerpc/include/asm/types.h
>>> index bfb6ded..8b89d65
(2014/06/18 16:56), Michael Ellerman wrote:
On Fri, 2014-06-06 at 15:38 +0900, Masami Hiramatsu wrote:
Ping?
I guess this should go to 3.16 branch, shouldn't it?
diff --git a/arch/powerpc/include/asm/types.h
b/arch/powerpc/include/asm/types.h
index bfb6ded..8b89d65 100644
---
On Wed, 2014-06-18 at 17:46 +0900, Masami Hiramatsu wrote:
(2014/06/18 16:56), Michael Ellerman wrote:
On Fri, 2014-06-06 at 15:38 +0900, Masami Hiramatsu wrote:
Ping?
I guess this should go to 3.16 branch, shouldn't it?
diff --git a/arch/powerpc/include/asm/types.h
12 matches
Mail list logo