On Sat, Sep 29, 2012 at 06:49:51PM +0200, Sasha Levin wrote:
> On 09/29/2012 03:37 PM, Paul E. McKenney wrote:
> > Sasha, is the easily reproducible? If so, could you please try the
> > previous patch? It will likely give us more information on where
> > this bug really lives. (Yes, it might tot
On 09/29/2012 03:37 PM, Paul E. McKenney wrote:
> Sasha, is the easily reproducible? If so, could you please try the
> previous patch? It will likely give us more information on where
> this bug really lives. (Yes, it might totally obscure the bug, but
> in that case we will just need to try som
On Sat, Sep 29, 2012 at 03:50:07PM +0200, Frederic Weisbecker wrote:
> On Sat, Sep 29, 2012 at 06:37:37AM -0700, Paul E. McKenney wrote:
> > On Sat, Sep 29, 2012 at 02:25:04PM +0200, Frederic Weisbecker wrote:
> > > 2012/9/29 Sasha Levin :
> > > > Maybe I could help here a bit.
> > > >
> > > > lapp
On Sat, Sep 29, 2012 at 06:37:37AM -0700, Paul E. McKenney wrote:
> On Sat, Sep 29, 2012 at 02:25:04PM +0200, Frederic Weisbecker wrote:
> > 2012/9/29 Sasha Levin :
> > > Maybe I could help here a bit.
> > >
> > > lappy linux # addr2line -i -e vmlinux 8111d45f
> > > /usr/src/linux/kernel/ti
On Sat, Sep 29, 2012 at 02:25:04PM +0200, Frederic Weisbecker wrote:
> 2012/9/29 Sasha Levin :
> > Maybe I could help here a bit.
> >
> > lappy linux # addr2line -i -e vmlinux 8111d45f
> > /usr/src/linux/kernel/timer.c:549
> > /usr/src/linux/include/linux/jump_label.h:101
> > /usr/src/linux
2012/9/29 Sasha Levin :
> Maybe I could help here a bit.
>
> lappy linux # addr2line -i -e vmlinux 8111d45f
> /usr/src/linux/kernel/timer.c:549
> /usr/src/linux/include/linux/jump_label.h:101
> /usr/src/linux/include/trace/events/timer.h:44
> /usr/src/linux/kernel/timer.c:601
> /usr/src/lin
On 09/28/2012 07:31 PM, Paul E. McKenney wrote:
> On Fri, Sep 28, 2012 at 03:36:43PM +0200, Frederic Weisbecker wrote:
>> > On Fri, Sep 28, 2012 at 02:51:03PM +0200, Sasha Levin wrote:
>>> > > Hi all,
>>> > >
>>> > > While fuzzing with trinity inside a KVM tools guest with the latest
>>> > > linu
On Fri, Sep 28, 2012 at 03:36:43PM +0200, Frederic Weisbecker wrote:
> On Fri, Sep 28, 2012 at 02:51:03PM +0200, Sasha Levin wrote:
> > Hi all,
> >
> > While fuzzing with trinity inside a KVM tools guest with the latest
> > linux-next kernel, I've stumbled on the following during boot:
> >
> > [
On Fri, Sep 28, 2012 at 02:51:03PM +0200, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest with the latest
> linux-next kernel, I've stumbled on the following during boot:
>
> [ 199.224369] WARNING: at kernel/rcutree.c:513
> rcu_eqs_exit_common+0x4a/0x3a0()
On Fri, Sep 28, 2012 at 02:51:03PM +0200, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest with the latest
> linux-next kernel, I've stumbled on the following during boot:
>
> [ 199.224369] WARNING: at kernel/rcutree.c:513
> rcu_eqs_exit_common+0x4a/0x3a0()
Hi all,
While fuzzing with trinity inside a KVM tools guest with the latest linux-next
kernel, I've stumbled on the following during boot:
[ 199.224369] WARNING: at kernel/rcutree.c:513 rcu_eqs_exit_common+0x4a/0x3a0()
[ 199.225307] Pid: 1, comm: init Tainted: GW
3.6.0-rc7-next-201
11 matches
Mail list logo
