On 10/20/2014 06:20 PM, Stephen Boyd wrote:
> On 10/20, Stephen Boyd wrote:
>> On 10/20, Peter Hurley wrote:
>>>
>>> FWIW, __msm_console_write() is a deadlock-waiting-to_happen since it does
>>> not disable interrupts with spin_lock_irqsave().
>>>
>>
>> Yeah we should fix that. As far as I can
On 10/20/2014 06:20 PM, Stephen Boyd wrote:
On 10/20, Stephen Boyd wrote:
On 10/20, Peter Hurley wrote:
FWIW, __msm_console_write() is a deadlock-waiting-to_happen since it does
not disable interrupts with spin_lock_irqsave().
Yeah we should fix that. As far as I can tell we've never used
On 10/20, Stephen Boyd wrote:
> On 10/20, Peter Hurley wrote:
> >
> > FWIW, __msm_console_write() is a deadlock-waiting-to_happen since it does
> > not disable interrupts with spin_lock_irqsave().
> >
>
> Yeah we should fix that. As far as I can tell we've never used
> the irqsave variant of
On 10/20, Peter Hurley wrote:
> On 10/20/2014 02:27 PM, Stephen Boyd wrote:
> > On 10/17/2014 06:13 AM, Kumar Gala wrote:
> >> With CONFIG_DEBUG_SPINLOCK enabled we see:
> >>
> >> BUG: spinlock bad magic on CPU#0, swapper/0
> >> lock: early_console_dev+0x8/0x160, .magic: , .owner: /-1,
On 10/20/2014 02:27 PM, Stephen Boyd wrote:
> On 10/17/2014 06:13 AM, Kumar Gala wrote:
>> With CONFIG_DEBUG_SPINLOCK enabled we see:
>>
>> BUG: spinlock bad magic on CPU#0, swapper/0
>> lock: early_console_dev+0x8/0x160, .magic: , .owner: /-1,
>> .owner_cpu: 0
>> CPU: 0 PID: 0 Comm:
On 10/17/2014 06:13 AM, Kumar Gala wrote:
With CONFIG_DEBUG_SPINLOCK enabled we see:
BUG: spinlock bad magic on CPU#0, swapper/0
lock: early_console_dev+0x8/0x160, .magic: , .owner: /-1,
.owner_cpu: 0
CPU: 0 PID: 0 Comm: swapper Not tainted 3.17.0-09733-gb446b33-dirty #18
[...]
On 10/17/2014 06:13 AM, Kumar Gala wrote:
With CONFIG_DEBUG_SPINLOCK enabled we see:
BUG: spinlock bad magic on CPU#0, swapper/0
lock: early_console_dev+0x8/0x160, .magic: , .owner: none/-1,
.owner_cpu: 0
CPU: 0 PID: 0 Comm: swapper Not tainted 3.17.0-09733-gb446b33-dirty #18
[...]
On 10/20/2014 02:27 PM, Stephen Boyd wrote:
On 10/17/2014 06:13 AM, Kumar Gala wrote:
With CONFIG_DEBUG_SPINLOCK enabled we see:
BUG: spinlock bad magic on CPU#0, swapper/0
lock: early_console_dev+0x8/0x160, .magic: , .owner: none/-1,
.owner_cpu: 0
CPU: 0 PID: 0 Comm: swapper Not
On 10/20, Peter Hurley wrote:
On 10/20/2014 02:27 PM, Stephen Boyd wrote:
On 10/17/2014 06:13 AM, Kumar Gala wrote:
With CONFIG_DEBUG_SPINLOCK enabled we see:
BUG: spinlock bad magic on CPU#0, swapper/0
lock: early_console_dev+0x8/0x160, .magic: , .owner: none/-1,
On 10/20, Stephen Boyd wrote:
On 10/20, Peter Hurley wrote:
FWIW, __msm_console_write() is a deadlock-waiting-to_happen since it does
not disable interrupts with spin_lock_irqsave().
Yeah we should fix that. As far as I can tell we've never used
the irqsave variant of the lock in
With CONFIG_DEBUG_SPINLOCK enabled we see:
BUG: spinlock bad magic on CPU#0, swapper/0
lock: early_console_dev+0x8/0x160, .magic: , .owner: /-1,
.owner_cpu: 0
CPU: 0 PID: 0 Comm: swapper Not tainted 3.17.0-09733-gb446b33-dirty #18
Call trace:
[] dump_backtrace+0x0/0x140
[]
With CONFIG_DEBUG_SPINLOCK enabled we see:
BUG: spinlock bad magic on CPU#0, swapper/0
lock: early_console_dev+0x8/0x160, .magic: , .owner: none/-1,
.owner_cpu: 0
CPU: 0 PID: 0 Comm: swapper Not tainted 3.17.0-09733-gb446b33-dirty #18
Call trace:
[c0087ba0] dump_backtrace+0x0/0x140
12 matches
Mail list logo