On Wed, Jul 31, 2013 at 03:13:23PM +0200, Hannes Frederic Sowa wrote:
> On Wed, Jul 31, 2013 at 05:55:13AM -0700, Paul E. McKenney wrote:
> > On Wed, Jul 31, 2013 at 04:40:47PM +0530, vinayak menon wrote:
> > > Hi,
> > >
> > > A crash was seen on 3.4.5 kernel during some random wlan operations.
>
On Wed, Jul 31, 2013 at 6:43 PM, Hannes Frederic Sowa
wrote:
> On Wed, Jul 31, 2013 at 05:55:13AM -0700, Paul E. McKenney wrote:
>> On Wed, Jul 31, 2013 at 04:40:47PM +0530, vinayak menon wrote:
>> > Hi,
>> >
>> > A crash was seen on 3.4.5 kernel during some random wlan operations.
>> >
>> > CPU:
On Wed, Jul 31, 2013 at 05:55:13AM -0700, Paul E. McKenney wrote:
> On Wed, Jul 31, 2013 at 04:40:47PM +0530, vinayak menon wrote:
> > Hi,
> >
> > A crash was seen on 3.4.5 kernel during some random wlan operations.
> >
> > CPU: Single core ARM Cortex A9.
> >
> > fib_route_seq_next was called wi
On Wed, Jul 31, 2013 at 04:40:47PM +0530, vinayak menon wrote:
> Hi,
>
> A crash was seen on 3.4.5 kernel during some random wlan operations.
>
> CPU: Single core ARM Cortex A9.
>
> fib_route_seq_next was called with second argument (void *v) as 0xd6e3e360
> which is a "freed" object of the "ip_
Hi,
A crash was seen on 3.4.5 kernel during some random wlan operations.
CPU: Single core ARM Cortex A9.
fib_route_seq_next was called with second argument (void *v) as
0xd6e3e360 which is a "freed" object of the "ip_fib_trie" cache. I
confirmed that the object was freed with crash utility.
Seq
5 matches
Mail list logo