On 02/27/2014 09:25 PM, Boaz Harrosh wrote:
> On 02/27/2014 09:16 PM, Richard Weinberger wrote:
>> Hi!
>>
>> Am 27.02.2014 20:05, schrieb Boaz Harrosh:
>>> Hi Richard, uml hackers
>>>
>>> Since some time my "echo t > /proc/sysrq-trigger" stopped producing the
>>> proper global back-traces for all
On 02/27/2014 09:22 PM, Richard Weinberger wrote:
>
>
> Am 27.02.2014 20:05, schrieb Boaz Harrosh:
>> Hi Richard, uml hackers
>>
>> Since some time my "echo t > /proc/sysrq-trigger" stopped producing the
>> proper global back-traces for all Kernel threads.
>> All I get is:
>
> I have an idea, d
On 02/27/2014 09:16 PM, Richard Weinberger wrote:
> Hi!
>
> Am 27.02.2014 20:05, schrieb Boaz Harrosh:
>> Hi Richard, uml hackers
>>
>> Since some time my "echo t > /proc/sysrq-trigger" stopped producing the
>> proper global back-traces for all Kernel threads.
>> All I get is:
>
> "some time" is
Am 27.02.2014 20:05, schrieb Boaz Harrosh:
> Hi Richard, uml hackers
>
> Since some time my "echo t > /proc/sysrq-trigger" stopped producing the
> proper global back-traces for all Kernel threads.
> All I get is:
I have an idea, do you see this regression starting with v3.12?
Thanks,
//richar
Hi!
Am 27.02.2014 20:05, schrieb Boaz Harrosh:
> Hi Richard, uml hackers
>
> Since some time my "echo t > /proc/sysrq-trigger" stopped producing the
> proper global back-traces for all Kernel threads.
> All I get is:
"some time" is a bit vague. Do you have more details?
Thanks,
//richard
Hi Richard, uml hackers
Since some time my "echo t > /proc/sysrq-trigger" stopped producing the proper
global back-traces for all Kernel threads.
All I get is:
Feb 27 12:47:32 fc18-buml18 kernel: [189390.94] ksoftirqd/0 3
58344.325336124146 120 0
