* Thomas Gleixner | 2014-02-19 10:50:29 [+0100]:
>On Fri, 14 Feb 2014, Fernando Lopez-Lezcano wrote:
>> I could try to boot one of the machines into 3.12.xrtyy, replicate the
>> conditions and wait. What should I look for if I can catch this in the act?
>
>dmesg and sysrq-t output would be a good
* Fernando Lopez-Lezcano | 2014-02-13 14:56:09 [-0800]:
>On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
>>On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
>>>[771508.546449] RIP: 0010:[] []
>>>smp_call_function_many+0x2ca/0x330
>>
>>Can you decode the exact location inside of
* Fernando Lopez-Lezcano | 2014-02-13 14:56:09 [-0800]:
On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
[771508.546449] RIP: 0010:[810dc60a] [810dc60a]
smp_call_function_many+0x2ca/0x330
Can you decode the exact location inside
* Thomas Gleixner | 2014-02-19 10:50:29 [+0100]:
On Fri, 14 Feb 2014, Fernando Lopez-Lezcano wrote:
I could try to boot one of the machines into 3.12.xrtyy, replicate the
conditions and wait. What should I look for if I can catch this in the act?
dmesg and sysrq-t output would be a good start
On Fri, 14 Feb 2014, Fernando Lopez-Lezcano wrote:
> I could try to boot one of the machines into 3.12.xrtyy, replicate the
> conditions and wait. What should I look for if I can catch this in the act?
dmesg and sysrq-t output would be a good start I guess.
Thanks,
tglx
--
To
On Fri, 14 Feb 2014, Fernando Lopez-Lezcano wrote:
I could try to boot one of the machines into 3.12.xrtyy, replicate the
conditions and wait. What should I look for if I can catch this in the act?
dmesg and sysrq-t output would be a good start I guess.
Thanks,
tglx
--
To unsubscribe
On 02/14/2014 02:43 AM, Thomas Gleixner wrote:
On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
On 02/13/2014 03:55 PM, Thomas Gleixner wrote:
On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
On Wed, 12 Feb 2014, Fernando Lopez-Lezcano
On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
> On 02/13/2014 03:55 PM, Thomas Gleixner wrote:
> > On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
> >
> > > On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
> > > > On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
> > > > > [771508.546449]
On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
On 02/13/2014 03:55 PM, Thomas Gleixner wrote:
On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
[771508.546449] RIP:
On 02/14/2014 02:43 AM, Thomas Gleixner wrote:
On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
On 02/13/2014 03:55 PM, Thomas Gleixner wrote:
On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
On Wed, 12 Feb 2014, Fernando Lopez-Lezcano
On 02/13/2014 03:55 PM, Thomas Gleixner wrote:
On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
[771508.546449] RIP: 0010:[] []
smp_call_function_many+0x2ca/0x330
Can you decode the exact
On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
> On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
> > On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
> > > [771508.546449] RIP: 0010:[] []
> > > smp_call_function_many+0x2ca/0x330
> >
> > Can you decode the exact location inside of
On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
[771508.546449] RIP: 0010:[] []
smp_call_function_many+0x2ca/0x330
Can you decode the exact location inside of smp_call_function_many via
addr2line please ?
Hope this is useful (adding
On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
> [771508.546449] RIP: 0010:[] []
> smp_call_function_many+0x2ca/0x330
Can you decode the exact location inside of smp_call_function_many via
addr2line please ?
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe
On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
[771508.546449] RIP: 0010:[810dc60a] [810dc60a]
smp_call_function_many+0x2ca/0x330
Can you decode the exact location inside of smp_call_function_many via
addr2line please ?
Thanks,
tglx
--
To unsubscribe from this
On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
[771508.546449] RIP: 0010:[810dc60a] [810dc60a]
smp_call_function_many+0x2ca/0x330
Can you decode the exact location inside of smp_call_function_many via
addr2line please ?
On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
[771508.546449] RIP: 0010:[810dc60a] [810dc60a]
smp_call_function_many+0x2ca/0x330
Can you decode the exact location
On 02/13/2014 03:55 PM, Thomas Gleixner wrote:
On Thu, 13 Feb 2014, Fernando Lopez-Lezcano wrote:
On 02/13/2014 02:25 PM, Thomas Gleixner wrote:
On Wed, 12 Feb 2014, Fernando Lopez-Lezcano wrote:
[771508.546449] RIP: 0010:[810dc60a] [810dc60a]
Hi all,
I'm seeing these BUGs with 3.12.9-rt13 finally caught the messages.
I was getting frozen machines with no traces left behind, this could
possibly be it (see below - I have to retest with rt15)
-- Fernando
[771508.546420] BUG: soft lockup - CPU#5 stuck for 23s!
Hi all,
I'm seeing these BUGs with 3.12.9-rt13 finally caught the messages.
I was getting frozen machines with no traces left behind, this could
possibly be it (see below - I have to retest with rt15)
-- Fernando
[771508.546420] BUG: soft lockup - CPU#5 stuck for 23s!
20 matches
Mail list logo