On Sun, May 8, 2016 at 1:25 AM, Paul E. McKenney
wrote:
> On Fri, May 06, 2016 at 04:25:16PM +1000, Ross Green wrote:
>> On Sun, Apr 3, 2016 at 6:18 PM, Paul E. McKenney
>> wrote:
>> > On Thu, Mar 31, 2016 at 08:42:55AM -0700, Paul E. McKenney wrote:
>> >>
Feb 25, 2016 at 04:13:11PM +1100, Ross Green wrote:
>> > On Wed, Feb 24, 2016 at 8:28 AM, Ross Green wrote:
>> > > On Wed, Feb 24, 2016 at 7:55 AM, Paul E. McKenney
>> > > wrote:
>>
>> [ . . . ]
>>
>> > &g
On Wed, Feb 24, 2016 at 8:28 AM, Ross Green wrote:
> On Wed, Feb 24, 2016 at 7:55 AM, Paul E. McKenney
> wrote:
>> On Tue, Feb 23, 2016 at 08:34:11PM +, Mathieu Desnoyers wrote:
>>> - On Feb 21, 2016, at 1:15 PM, Ross Green rgker...@gmail.com wrote:
>>>
>
On Thu, Feb 25, 2016 at 1:13 PM, Ross Green wrote:
> On Thu, Feb 25, 2016 at 11:11 AM, Emil Goode wrote:
>> Hello Ross
>>
>> On Wed, Feb 24, 2016 at 04:40:50PM +1100, Ross Green wrote:
>>> On Wed, Feb 17, 2016 at 4:34 PM, Ross Green wrote:
>>> > Apprec
On Thu, Feb 25, 2016 at 11:11 AM, Emil Goode wrote:
> Hello Ross
>
> On Wed, Feb 24, 2016 at 04:40:50PM +1100, Ross Green wrote:
>> On Wed, Feb 17, 2016 at 4:34 PM, Ross Green wrote:
>> > Appreciate your efforts!
>> >
>> > Just trying to make sure it
On Wed, Feb 17, 2016 at 4:34 PM, Ross Green wrote:
> Appreciate your efforts!
>
> Just trying to make sure it does not get lost.
> Introduced in rc1, not fixed by ... rc4.
>
> Anyway, I will continue to test, lots of other things still to chase
> even in rc4!
>
> Reg
On Wed, Feb 24, 2016 at 7:55 AM, Paul E. McKenney
wrote:
> On Tue, Feb 23, 2016 at 08:34:11PM +, Mathieu Desnoyers wrote:
>> - On Feb 21, 2016, at 1:15 PM, Ross Green rgker...@gmail.com wrote:
>>
>> > On Sun, Feb 21, 2016 at 4:04 PM, Ross Green wrote:
>> &
On Sat, Feb 20, 2016 at 5:32 PM, Paul E. McKenney
wrote:
> On Sat, Feb 20, 2016 at 03:34:30PM +1100, Ross Green wrote:
>> On Sat, Feb 20, 2016 at 4:33 AM, Paul E. McKenney
>> wrote:
>> > On Thu, Feb 18, 2016 at 08:13:18PM -0800, John Stultz wrote:
>> >> O
On Sun, Feb 21, 2016 at 4:04 PM, Ross Green wrote:
> On Sat, Feb 20, 2016 at 5:32 PM, Paul E. McKenney
> wrote:
>> On Sat, Feb 20, 2016 at 03:34:30PM +1100, Ross Green wrote:
>>> On Sat, Feb 20, 2016 at 4:33 AM, Paul E. McKenney
>>> wrote:
>>> > On T
On Sat, Feb 20, 2016 at 4:33 AM, Paul E. McKenney
wrote:
> On Thu, Feb 18, 2016 at 08:13:18PM -0800, John Stultz wrote:
>> On Thu, Feb 18, 2016 at 7:56 PM, Ross Green wrote:
>> > Well a bonus extra!
>> > Kept everything running and there was another stall.
>&g
On Fri, Feb 19, 2016 at 3:22 PM, Paul E. McKenney
wrote:
> On Thu, Feb 18, 2016 at 11:14:21PM +, Mathieu Desnoyers wrote:
>> - On Feb 18, 2016, at 6:51 AM, Ross Green rgker...@gmail.com wrote:
>>
>> > On Thu, Feb 18, 2016 at 10:19 AM, Paul E. McKenney
>>
On Fri, Feb 19, 2016 at 10:14 AM, Mathieu Desnoyers
wrote:
> - On Feb 18, 2016, at 6:51 AM, Ross Green rgker...@gmail.com wrote:
>
>> On Thu, Feb 18, 2016 at 10:19 AM, Paul E. McKenney
>> wrote:
>>> On Wed, Feb 17, 2016 at 12:28:29PM -0800, Paul E. McKenney wrote
gt; On Tue, Feb 16, 2016 at 09:45:49PM -0800, Paul E. McKenney wrote:
>> > > > On Tue, Feb 09, 2016 at 09:11:55PM +1100, Ross Green wrote:
>> > > > > Continued testing with the latest linux-4.5-rc3 release.
>> > > > >
>> > > > > Pl
Appreciate your efforts!
Just trying to make sure it does not get lost.
Introduced in rc1, not fixed by ... rc4.
Anyway, I will continue to test, lots of other things still to chase
even in rc4!
Regards,
Ross Green
On Wed, Feb 17, 2016 at 2:24 AM, Kalle Valo wrote:
> Ross Green wri
size brings the module back to
>> it's functional state.
>>
>> Fixes: 3719c17e1816 ("wlcore/wl18xx: fw logger over sdio")
>> Reported-by: Ross Green
>> Signed-off-by: Emil Goode
>> [kv...@codeaurora.org: improved commit log]
>
> Thanks, app
completion and then leave the system idle away with just a few daemons
running.
the self detected stalls in this instance turned up after a days run time.
There were NO heavy artificial computational loads on the machine.
Regards,
Ross Green
dmesg-4.5-rc3
Description: Binary data
On Mon, Feb 8, 2016 at 9:05 AM, Emil Goode wrote:
> Hello,
>
> On Tue, Feb 02, 2016 at 05:05:38PM +0100, Sebastian Reichel wrote:
>> On Tue, Feb 02, 2016 at 04:41:13PM +1100, Ross Green wrote:
>> > On Tue, Feb 2, 2016 at 3:34 PM, Sebastian Reichel wrote:
>> > >
On Wed, Feb 3, 2016 at 3:05 AM, Sebastian Reichel wrote:
> Hi Ross,
>
> Please don't top-post on kernel mailinglists. Use either inline
> style or bottom posting.
>
> On Tue, Feb 02, 2016 at 04:41:13PM +1100, Ross Green wrote:
>> On Tue, Feb 2, 2016 at 3:34 PM, Seba
rds,
Ross Green
On Tue, Feb 2, 2016 at 3:34 PM, Sebastian Reichel wrote:
> Hi,
>
> On Mon, Feb 01, 2016 at 11:38:38PM +1100, Ross Green wrote:
>> On Mon, Jan 25, 2016 at 11:47 PM, Ross Green wrote:
>> > Just tried the new kernel release on faithful pandaboard es
with linux-4.5-rc2?
Just for completeness also tested the latest linux-4.4.1 kernel and
found no problems with the wireless modules.
Regards,
Ross Green
On Mon, Jan 25, 2016 at 11:47 PM, Ross Green wrote:
> Just tried the new kernel release on faithful pandaboard es with the
> new 4
this board.
Here is a dmesg dump in the attachment.
Anyone have any ideas here?
Regards,
Ross Green
dmesg-panda-4.5-rc1
Description: Binary data
cords of these stall warnings before these kernels. I guess someone
must have suspected there was a potential for these stalls and hence
the detection facility.
Regards,
Ross
On Tue, Jan 5, 2016 at 1:21 AM, Ross Green wrote:
> Well with the release of 4.4-rc8 I have built and
> started
induce these stalls
with heavy loading of the system. The only method I can be sure of is
to leave the system quiet and let time go by till a stall occurs.
Regards,
Ross
On Mon, Jan 4, 2016 at 9:00 AM, Ross Green wrote:
> Thanks Paul for your analysis and investigation,
>
> I unders
!
Please see the attachments.
Regards,
Ross
On Sun, Jan 3, 2016 at 5:17 PM, Paul E. McKenney
wrote:
> On Sun, Jan 03, 2016 at 04:29:11PM +1100, Ross Green wrote:
>> Still seeing these rcu_preempt stalls on kernels through to 4.4-rc7
>>
>> Still have not found a sure fire
way back to 3.17.
Most recent kernels have included 4.4-rc5 4.4-rc6 and 4.4-rc7
Regards,
Ross
On Fri, Dec 11, 2015 at 10:17 PM, Ross Green wrote:
> I have been getting these stalls in kernels going back to 3.17.
>
> This stall occurs usually under light load but often requires several
I have been getting these stalls in kernels going back to 3.17.
This stall occurs usually under light load but often requires several
days to show itself. I have not found any simple way to trigger the
stall. Indeed heavy workloads seems not to show the fault.
Anyone have any thoughts here?
The
I too have traced a similar RCU stall all the way back to 3.17.
Seems to affect RCU preempt code as well.
I had not been able to find a sure fail way to trigger this and it
could take several days running before problem arises.
Ross
--
To unsubscribe from this list: send the line "unsubscribe li
27 matches
Mail list logo
