On Thu, Jun 12, 2014 at 10:54:22AM +0200, Mike Galbraith wrote:
> On Thu, 2014-06-12 at 10:26 +0200, Jan Kara wrote:
> > On Wed 11-06-14 23:07:04, Sasha Levin wrote:
>
> > > The first patch fixed it (I assumed that there's no need to try the
> > > second).
> > Good. So that shows that it is th
On Wed 11-06-14 23:07:04, Sasha Levin wrote:
> On 06/11/2014 05:31 PM, Jan Kara wrote:
> > On Wed 11-06-14 22:34:36, Jan Kara wrote:
> >> > On Wed 11-06-14 10:55:55, Sasha Levin wrote:
> >>> > > On 06/10/2014 11:59 AM, Peter Hurley wrote:
> > > > On 06/06/2014 03:05 PM, Sasha Levin wrote:
> >>
On Thu, 2014-06-12 at 10:26 +0200, Jan Kara wrote:
> On Wed 11-06-14 23:07:04, Sasha Levin wrote:
> > The first patch fixed it (I assumed that there's no need to try the second).
> Good. So that shows that it is the increased lockdep coverage which is
> causing problems - with my patch, lockdep
On Wed 11-06-14 23:07:04, Sasha Levin wrote:
> On 06/11/2014 05:31 PM, Jan Kara wrote:
> > On Wed 11-06-14 22:34:36, Jan Kara wrote:
> >> > On Wed 11-06-14 10:55:55, Sasha Levin wrote:
> >>> > > On 06/10/2014 11:59 AM, Peter Hurley wrote:
> > > > On 06/06/2014 03:05 PM, Sasha Levin wrote:
> >>
On 06/11/2014 05:31 PM, Jan Kara wrote:
> On Wed 11-06-14 22:34:36, Jan Kara wrote:
>> > On Wed 11-06-14 10:55:55, Sasha Levin wrote:
>>> > > On 06/10/2014 11:59 AM, Peter Hurley wrote:
> > > On 06/06/2014 03:05 PM, Sasha Levin wrote:
> > > >> On 05/30/2014 10:07 AM, Jan Kara wrote:
>>
On Wed 11-06-14 22:34:36, Jan Kara wrote:
> On Wed 11-06-14 10:55:55, Sasha Levin wrote:
> > On 06/10/2014 11:59 AM, Peter Hurley wrote:
> > > On 06/06/2014 03:05 PM, Sasha Levin wrote:
> > >> On 05/30/2014 10:07 AM, Jan Kara wrote:
> > >>> On Fri 30-05-14 09:58:14, Peter Hurley wrote:
> > > On
On Wed 11-06-14 10:55:55, Sasha Levin wrote:
> On 06/10/2014 11:59 AM, Peter Hurley wrote:
> > On 06/06/2014 03:05 PM, Sasha Levin wrote:
> >> On 05/30/2014 10:07 AM, Jan Kara wrote:
> >>> On Fri 30-05-14 09:58:14, Peter Hurley wrote:
> > On 05/30/2014 09:11 AM, Sasha Levin wrote:
> >>> Hi
On Wed 11-06-14 11:34:28, Peter Hurley wrote:
> On 06/11/2014 10:55 AM, Sasha Levin wrote:
> >On 06/10/2014 11:59 AM, Peter Hurley wrote:
> >>On 06/06/2014 03:05 PM, Sasha Levin wrote:
> >>>On 05/30/2014 10:07 AM, Jan Kara wrote:
> On Fri 30-05-14 09:58:14, Peter Hurley wrote:
> >>On 05/30/
On Wed, Jun 11, 2014 at 10:38 AM, Linus Torvalds
wrote:
>
> Ok, I'm going to revert that commit. The games it plays with cpu
> numbers and preemption make me worried, and it looks silly.
>
> If the only reason for that patch is interrupt latency, then if the
> "preempt_disable()" had been done *b
On Wed, Jun 11, 2014 at 7:55 AM, Sasha Levin wrote:
>
> I've ran a bisection again and ended up at the same commit as Jet Chen (the
> commit
> unfortunately already made it to Linus's tree).
Ok, I'm going to revert that commit. The games it plays with cpu
numbers and preemption make me worried,
On 06/11/2014 10:55 AM, Sasha Levin wrote:
On 06/10/2014 11:59 AM, Peter Hurley wrote:
On 06/06/2014 03:05 PM, Sasha Levin wrote:
On 05/30/2014 10:07 AM, Jan Kara wrote:
On Fri 30-05-14 09:58:14, Peter Hurley wrote:
On 05/30/2014 09:11 AM, Sasha Levin wrote:
Hi all,
I sometime see lockups w
On 06/10/2014 11:59 AM, Peter Hurley wrote:
> On 06/06/2014 03:05 PM, Sasha Levin wrote:
>> On 05/30/2014 10:07 AM, Jan Kara wrote:
>>> On Fri 30-05-14 09:58:14, Peter Hurley wrote:
> On 05/30/2014 09:11 AM, Sasha Levin wrote:
>>> Hi all,
>>>
>>> I sometime see lockups when booting
On 06/06/2014 03:05 PM, Sasha Levin wrote:
On 05/30/2014 10:07 AM, Jan Kara wrote:
On Fri 30-05-14 09:58:14, Peter Hurley wrote:
On 05/30/2014 09:11 AM, Sasha Levin wrote:
Hi all,
I sometime see lockups when booting my KVM guest with the latest -next kernel,
it basically hangs right when it s
On 05/30/2014 10:07 AM, Jan Kara wrote:
> On Fri 30-05-14 09:58:14, Peter Hurley wrote:
>> > On 05/30/2014 09:11 AM, Sasha Levin wrote:
>>> > >Hi all,
>>> > >
>>> > >I sometime see lockups when booting my KVM guest with the latest -next
>>> > >kernel,
>>> > >it basically hangs right when it should
On Fri 30-05-14 09:58:14, Peter Hurley wrote:
> On 05/30/2014 09:11 AM, Sasha Levin wrote:
> >Hi all,
> >
> >I sometime see lockups when booting my KVM guest with the latest -next
> >kernel,
> >it basically hangs right when it should start 'init', and after a while I get
> >the following spew:
> >
On 05/30/2014 09:11 AM, Sasha Levin wrote:
Hi all,
I sometime see lockups when booting my KVM guest with the latest -next kernel,
it basically hangs right when it should start 'init', and after a while I get
the following spew:
[ 30.790833] BUG: spinlock lockup suspected on CPU#1, swapper/1/0
Hi all,
I sometime see lockups when booting my KVM guest with the latest -next kernel,
it basically hangs right when it should start 'init', and after a while I get
the following spew:
[ 30.790833] BUG: spinlock lockup suspected on CPU#1, swapper/1/0
[ 30.770667] BUG: spinlock lockup suspecte
17 matches
Mail list logo