On Tue, Oct 28, 2014 at 10:47:42AM +, Mark Brown wrote:
> On Mon, Oct 27, 2014 at 09:26:26PM -0700, Nicolin Chen wrote:
> > On Tue, Oct 28, 2014 at 12:19:04AM +, Mark Brown wrote:
>
> > > It's not a bug, it's not reasonable to default allocations to atomic and
> > > we can't really tell wh
On Mon, Oct 27, 2014 at 09:26:26PM -0700, Nicolin Chen wrote:
> On Tue, Oct 28, 2014 at 12:19:04AM +, Mark Brown wrote:
> > It's not a bug, it's not reasonable to default allocations to atomic and
> > we can't really tell what context we're in. Anything used inside a
> > heavily locked path s
On Tue, Oct 28, 2014 at 12:19:04AM +, Mark Brown wrote:
> On Fri, Oct 24, 2014 at 07:03:57PM -0700, Nicolin Chen wrote:
> > Kernel dump (WARN_ON) ocurred during system boot-up inside regmap_write():
> >
> > [ cut here ]
> > WARNING: CPU: 0 PID: 47 at kernel/locking/lock
On Fri, Oct 24, 2014 at 07:03:57PM -0700, Nicolin Chen wrote:
> Kernel dump (WARN_ON) ocurred during system boot-up inside regmap_write():
>
> [ cut here ]
> WARNING: CPU: 0 PID: 47 at kernel/locking/lockdep.c:2744
> lockdep_trace_alloc+0xe8/0x108()
Applied, thanks. Plea
Kernel dump (WARN_ON) ocurred during system boot-up inside regmap_write():
[ cut here ]
WARNING: CPU: 0 PID: 47 at kernel/locking/lockdep.c:2744
lockdep_trace_alloc+0xe8/0x108()
DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))
Modules linked in:
CPU: 0 PID: 47 Comm: kworker