On Mon, 1 May 2017, Bart Van Assche wrote:
> On Mon, 2017-05-01 at 13:39 -0400, Alan Stern wrote:
> > On Fri, 28 Apr 2017, Alan Stern wrote:
> > > On Fri, 28 Apr 2017, Bart Van Assche wrote:
> > He wrote:
> >
> > > There, that's where we hold the lock with interrupts enabled.
> > >
> > > So some
On Mon, 2017-05-01 at 13:39 -0400, Alan Stern wrote:
> On Fri, 28 Apr 2017, Alan Stern wrote:
> > On Fri, 28 Apr 2017, Bart Van Assche wrote:
> He wrote:
>
> > There, that's where we hold the lock with interrupts enabled.
> >
> > So someone forced interrupt threading and the code assumes the inte
On Fri, 28 Apr 2017, Alan Stern wrote:
> On Fri, 28 Apr 2017, Bart Van Assche wrote:
>
> > Hello,
> >
> > Every time I boot a particular development server the complaint shown
> > below appears in the system log. I don't know when this behavior has
> > been introduced. But I noticed that I can r
On Fri, 28 Apr 2017, Bart Van Assche wrote:
> Hello,
>
> Every time I boot a particular development server the complaint shown
> below appears in the system log. I don't know when this behavior has
> been introduced. But I noticed that I can reproduce this with older
> kernel versions, e.g. 4.4.6
Hello,
Every time I boot a particular development server the complaint shown
below appears in the system log. I don't know when this behavior has
been introduced. But I noticed that I can reproduce this with older
kernel versions, e.g. 4.4.63. Does anyone know what is going on or how
to fix this?