On 06/05/2013 11:48 AM, Tejun Heo wrote:
Hello, Ben.
On Wed, Jun 05, 2013 at 09:59:00AM -0700, Ben Greear wrote:
One pattern I notice repeating for at least most of the hangs is that all but
one
CPU thread has irqs disabled and is in state 2. But, there will be one thread
in state 1 that stil
Hello, Ben.
On Wed, Jun 05, 2013 at 09:59:00AM -0700, Ben Greear wrote:
> One pattern I notice repeating for at least most of the hangs is that all but
> one
> CPU thread has irqs disabled and is in state 2. But, there will be one thread
> in state 1 that still has IRQs enabled and it is reporte
Greg KH writes:
> On Mon, Jun 03, 2013 at 10:17:17AM -0400, Joe Lawrence wrote:
>> [Cc: stable@vger.kernel.org]
>>
>> Third time is a charm? The stable address was incorrect from the first
>> msg in this thread, but the relevant bits remain quoted below...
>
> Really? I'm totally confused...
>
Hello,
On Wed, Jun 05, 2013 at 01:47:43PM +0930, Rusty Russell wrote:
> > I have some printk debugging in (see bottom of email) and was using a
> > serial console, so things
> > were probably running a bit slower than on most systems. Here is trace
> > from my kernel with local patches and not s
On Mon, Jun 03, 2013 at 10:17:17AM -0400, Joe Lawrence wrote:
> [Cc: stable@vger.kernel.org]
>
> Third time is a charm? The stable address was incorrect from the first
> msg in this thread, but the relevant bits remain quoted below...
Really? I'm totally confused...
> On Mon, 3 Jun 2013, Joe
Ben Greear writes:
> On 06/04/2013 09:53 AM, Ben Greear wrote:
>> On 06/04/2013 07:07 AM, Joe Lawrence wrote:
>>> On Tue, 04 Jun 2013 15:26:28 +0930
>>> Rusty Russell wrote:
>>>
Do you have a backtrace of the 3.9.4 crash? You can add "CFLAGS_module.o
= -O0" to get a clearer backtrace i
Joe Lawrence writes:
> On Tue, 04 Jun 2013 15:26:28 +0930
> Rusty Russell wrote:
>
>> Do you have a backtrace of the 3.9.4 crash? You can add "CFLAGS_module.o
>> = -O0" to get a clearer backtrace if you want...
>
> Hi Rusty,
>
> See my 3.9 stack traces below, which may or may not be what Ben had
On 06/04/2013 09:53 AM, Ben Greear wrote:
On 06/04/2013 07:07 AM, Joe Lawrence wrote:
On Tue, 04 Jun 2013 15:26:28 +0930
Rusty Russell wrote:
Do you have a backtrace of the 3.9.4 crash? You can add "CFLAGS_module.o
= -O0" to get a clearer backtrace if you want...
Hi Rusty,
See my 3.9 stac
On Tue, 4 Jun 2013, Joe Lawrence wrote:
> Hi Rusty,
>
> See my 3.9 stack traces below, which may or may not be what Ben had
> been seeing. If you like, I can try a similar loop as the one you were
> testing in the other email.
With a modified version of your module load/unload loop (only need
On 06/04/2013 07:07 AM, Joe Lawrence wrote:
On Tue, 04 Jun 2013 15:26:28 +0930
Rusty Russell wrote:
Do you have a backtrace of the 3.9.4 crash? You can add "CFLAGS_module.o
= -O0" to get a clearer backtrace if you want...
Hi Rusty,
See my 3.9 stack traces below, which may or may not be wha
On Tue, 04 Jun 2013 15:26:28 +0930
Rusty Russell wrote:
> Do you have a backtrace of the 3.9.4 crash? You can add "CFLAGS_module.o
> = -O0" to get a clearer backtrace if you want...
Hi Rusty,
See my 3.9 stack traces below, which may or may not be what Ben had
been seeing. If you like, I can t
Ben Greear writes:
> On 06/03/2013 08:59 AM, Ben Greear wrote:
>> On 06/03/2013 07:17 AM, Joe Lawrence wrote:
>>
> Hi Rusty,
>
> I had pointed Ben (offlist) to that bugzilla entry without realizing
> there were other earlier related fixes in this space. Re-viewing bz-
> 58011,
Ben Greear writes:
>> It at least works around the problem for me as well. But, a more rare
>> migration/[0-3] (I think) related lockup still exists in 3.9.4 for me,
>> so I will also try applying that other kobject patch and continue testing
>> today...
>
> Well, that other kobject patch is alre
On 06/03/2013 08:59 AM, Ben Greear wrote:
On 06/03/2013 07:17 AM, Joe Lawrence wrote:
Hi Rusty,
I had pointed Ben (offlist) to that bugzilla entry without realizing
there were other earlier related fixes in this space. Re-viewing bz-
58011, it looks like it was opened against 3.8.12, while Be
On 06/03/2013 07:17 AM, Joe Lawrence wrote:
Hi Rusty,
I had pointed Ben (offlist) to that bugzilla entry without realizing
there were other earlier related fixes in this space. Re-viewing bz-
58011, it looks like it was opened against 3.8.12, while Ben and myself
had encountered module loading
[Cc: stable@vger.kernel.org]
Third time is a charm? The stable address was incorrect from the first
msg in this thread, but the relevant bits remain quoted below...
On Mon, 3 Jun 2013, Joe Lawrence wrote:
> [fixing Cc: sta...@kernel.org address]
>
> On Sun, 2 Jun 2013, Joe Lawrence wrote:
>
iginal Message ----
> >>Subject: Please add to stable: module: don't unlink the module until we've
> >>removed all exposure.
> >>Date: Fri, 31 May 2013 11:14:28 -0700
> >>From: Ben Greear
> >>Organization: Candela Technologies
> >>To:
On 05/31/2013 03:48 PM, Greg KH wrote:
On Fri, May 31, 2013 at 11:18:29AM -0700, Ben Greear wrote:
Typo'd the stable email the first time around...
Original Message
Subject: Please add to stable: module: don't unlink the module until we've
removed all expo
On Fri, May 31, 2013 at 11:18:29AM -0700, Ben Greear wrote:
> Typo'd the stable email the first time around...
>
>
> Original Message ----
> Subject: Please add to stable: module: don't unlink the module until we've
> removed all exposure.
> D
Typo'd the stable email the first time around...
Original Message
Subject: Please add to stable: module: don't unlink the module until we've
removed all exposure.
Date: Fri, 31 May 2013 11:14:28 -0700
From: Ben Greear
Organization: Candela Technologies
T
20 matches
Mail list logo
