On 01/10/2014 10:52 AM, Samuel Ortiz wrote:
> Hi Francis,
>
> On Fri, Jan 10, 2014 at 08:26:13AM +0100, Francis Moreau wrote:
>> Hi.
>>
>> On 12/10/2013 09:29 AM, Samuel Ortiz wrote:
>>> Hi Micky,
>>>
>>> On Tue, Dec 10, 2013 at 09:56:48AM +0800, micky wrote:
Hi Francis:
On 12/10/2013
Hi Francis,
On Fri, Jan 10, 2014 at 08:26:13AM +0100, Francis Moreau wrote:
> Hi.
>
> On 12/10/2013 09:29 AM, Samuel Ortiz wrote:
> > Hi Micky,
> >
> > On Tue, Dec 10, 2013 at 09:56:48AM +0800, micky wrote:
> >> Hi Francis:
> >> On 12/10/2013 09:39 AM, wwang wrote:
> >>> which is based on
Hi,
On 01/10/2014 03:26 PM, Francis Moreau wrote:
I still can see any traces of this fix in Linus' tree.
Shouldn't this get merged before 3.13 is out ?
Thanks
Good, I think it is good to merge. Thanks.
Best Regards.
micky.
--
To unsubscribe from this list: send the line "unsubscribe
Hi,
On 01/10/2014 03:26 PM, Francis Moreau wrote:
I still can see any traces of this fix in Linus' tree.
Shouldn't this get merged before 3.13 is out ?
Thanks
Good, I think it is good to merge. Thanks.
Best Regards.
micky.
--
To unsubscribe from this list: send the line unsubscribe
Hi Francis,
On Fri, Jan 10, 2014 at 08:26:13AM +0100, Francis Moreau wrote:
Hi.
On 12/10/2013 09:29 AM, Samuel Ortiz wrote:
Hi Micky,
On Tue, Dec 10, 2013 at 09:56:48AM +0800, micky wrote:
Hi Francis:
On 12/10/2013 09:39 AM, wwang wrote:
which is based on Thomas' patch.
Can
On 01/10/2014 10:52 AM, Samuel Ortiz wrote:
Hi Francis,
On Fri, Jan 10, 2014 at 08:26:13AM +0100, Francis Moreau wrote:
Hi.
On 12/10/2013 09:29 AM, Samuel Ortiz wrote:
Hi Micky,
On Tue, Dec 10, 2013 at 09:56:48AM +0800, micky wrote:
Hi Francis:
On 12/10/2013 09:39 AM, wwang wrote:
Hi.
On 12/10/2013 09:29 AM, Samuel Ortiz wrote:
> Hi Micky,
>
> On Tue, Dec 10, 2013 at 09:56:48AM +0800, micky wrote:
>> Hi Francis:
>> On 12/10/2013 09:39 AM, wwang wrote:
>>> which is based on Thomas' patch.
>>
>> Can you help us test this patch, we disable irq while suspend here.
> I already
Hi.
On 12/10/2013 09:29 AM, Samuel Ortiz wrote:
Hi Micky,
On Tue, Dec 10, 2013 at 09:56:48AM +0800, micky wrote:
Hi Francis:
On 12/10/2013 09:39 AM, wwang wrote:
which is based on Thomas' patch.
Can you help us test this patch, we disable irq while suspend here.
I already pushed a patch
On Friday, December 20, 2013 10:31 AM, micky wrote:
>
> Hi Francis,
>
> We are trying to get the environment same with yours, so it may take
> some to solve this problem.
> maybe next month.
Yes, in this case, the problem should be reproduced.
And then, try debugging repeatedly.
Best regards,
Hi Francis,
We are trying to get the environment same with yours, so it may take
some to solve this problem.
maybe next month.
Best Regards.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Hi Francis,
We are trying to get the environment same with yours, so it may take
some to solve this problem.
maybe next month.
Best Regards.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Friday, December 20, 2013 10:31 AM, micky wrote:
Hi Francis,
We are trying to get the environment same with yours, so it may take
some to solve this problem.
maybe next month.
Yes, in this case, the problem should be reproduced.
And then, try debugging repeatedly.
Best regards,
On 12/18/2013 05:05 AM, micky wrote:
> Hi:
>
> It seems that the card-reader was removed during suspend or resume, is
> that right? or did you removed by hand?
yes during a suspend/resume cycle.
> I want to know with Thomas' patch, after resume, is the card-reader and
> card-reader driver
On 12/18/2013 05:05 AM, micky wrote:
Hi:
It seems that the card-reader was removed during suspend or resume, is
that right? or did you removed by hand?
yes during a suspend/resume cycle.
I want to know with Thomas' patch, after resume, is the card-reader and
card-reader driver still
Hi:
It seems that the card-reader was removed during suspend or resume, is
that right? or did you removed by hand?
I want to know with Thomas' patch, after resume, is the card-reader and
card-reader driver still exist?
if not exist, I also want to know which function called first,
Hi,
On 12/10/2013 02:56 AM, micky wrote:
> Hi Francis:
> On 12/10/2013 09:39 AM, wwang wrote:
>> which is based on Thomas' patch.
>
> Can you help us test this patch, we disable irq while suspend here.
This patch doesn't seem to help, it still oops:
[ 29.843910] [ cut here
Hi,
On 12/10/2013 02:56 AM, micky wrote:
Hi Francis:
On 12/10/2013 09:39 AM, wwang wrote:
which is based on Thomas' patch.
Can you help us test this patch, we disable irq while suspend here.
This patch doesn't seem to help, it still oops:
[ 29.843910] [ cut here
Hi:
It seems that the card-reader was removed during suspend or resume, is
that right? or did you removed by hand?
I want to know with Thomas' patch, after resume, is the card-reader and
card-reader driver still exist?
if not exist, I also want to know which function called first,
Hi,
On 12/10/2013 02:56 AM, micky wrote:
> Hi Francis:
> On 12/10/2013 09:39 AM, wwang wrote:
>> which is based on Thomas' patch.
>
> Can you help us test this patch, we disable irq while suspend here.
I'll give it a try tonight.
Thanks.
--
To unsubscribe from this list: send the line
Hi,
On 12/09/2013 11:17 PM, Samuel Ortiz wrote:
> Hi Francis,
>
> Adding Lee to the Cc list.
>
> On Tue, Dec 03, 2013 at 09:14:14AM +0100, Francis Moreau wrote:
>> Now that you did the hard work, I hope driver's maintainer/developper
>> will care about this issue.
> I applied Thomas' patch to
Hi Micky,
On Tue, Dec 10, 2013 at 09:56:48AM +0800, micky wrote:
> Hi Francis:
> On 12/10/2013 09:39 AM, wwang wrote:
> >which is based on Thomas' patch.
>
> Can you help us test this patch, we disable irq while suspend here.
I already pushed a patch from Thomas to mfd-fixes that seems to fix
Hi Micky,
On Tue, Dec 10, 2013 at 09:56:48AM +0800, micky wrote:
Hi Francis:
On 12/10/2013 09:39 AM, wwang wrote:
which is based on Thomas' patch.
Can you help us test this patch, we disable irq while suspend here.
I already pushed a patch from Thomas to mfd-fixes that seems to fix the
Hi,
On 12/09/2013 11:17 PM, Samuel Ortiz wrote:
Hi Francis,
Adding Lee to the Cc list.
On Tue, Dec 03, 2013 at 09:14:14AM +0100, Francis Moreau wrote:
Now that you did the hard work, I hope driver's maintainer/developper
will care about this issue.
I applied Thomas' patch to mfd-fixes.
Hi,
On 12/10/2013 02:56 AM, micky wrote:
Hi Francis:
On 12/10/2013 09:39 AM, wwang wrote:
which is based on Thomas' patch.
Can you help us test this patch, we disable irq while suspend here.
I'll give it a try tonight.
Thanks.
--
To unsubscribe from this list: send the line unsubscribe
Hi Francis:
On 12/10/2013 09:39 AM, wwang wrote:
which is based on Thomas' patch.
Can you help us test this patch, we disable irq while suspend here.
From 6b2bd6d85780bfd8d4fe5289aee1b09dd655d2d4 Mon Sep 17 00:00:00 2001
From: Micky Ching
Date: Thu, 5 Dec 2013 16:44:19 +0800
Subject: [PATCH]
On 12/10/2013 06:17 AM, Samuel Ortiz wrote:
Hi Francis,
Adding Lee to the Cc list.
On Tue, Dec 03, 2013 at 09:14:14AM +0100, Francis Moreau wrote:
Now that you did the hard work, I hope driver's maintainer/developper
will care about this issue.
I applied Thomas' patch to mfd-fixes.
Thanks a
Hi Francis,
On Mon, Dec 09, 2013 at 08:33:32PM +0100, Francis Moreau wrote:
> On 12/03/2013 09:14 AM, Francis Moreau wrote:
> > Hello Thomas,
> >
> > On 12/02/2013 12:20 PM, Thomas Gleixner wrote:
> >> On Mon, 2 Dec 2013, Thomas Gleixner wrote:
> >>> On Sat, 30 Nov 2013, Francis Moreau wrote:
>
Hi Francis,
Adding Lee to the Cc list.
On Tue, Dec 03, 2013 at 09:14:14AM +0100, Francis Moreau wrote:
> Now that you did the hard work, I hope driver's maintainer/developper
> will care about this issue.
I applied Thomas' patch to mfd-fixes.
Thanks a lot to you and Thomas for that.
Cheers,
On 12/03/2013 09:14 AM, Francis Moreau wrote:
> Hello Thomas,
>
> On 12/02/2013 12:20 PM, Thomas Gleixner wrote:
>> On Mon, 2 Dec 2013, Thomas Gleixner wrote:
>>> On Sat, 30 Nov 2013, Francis Moreau wrote:
Hello Thomas,
Sorry for the delay.
On 11/29/2013 10:02 AM, Thomas
On 12/03/2013 09:14 AM, Francis Moreau wrote:
Hello Thomas,
On 12/02/2013 12:20 PM, Thomas Gleixner wrote:
On Mon, 2 Dec 2013, Thomas Gleixner wrote:
On Sat, 30 Nov 2013, Francis Moreau wrote:
Hello Thomas,
Sorry for the delay.
On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
On Fri, 29
Hi Francis,
Adding Lee to the Cc list.
On Tue, Dec 03, 2013 at 09:14:14AM +0100, Francis Moreau wrote:
Now that you did the hard work, I hope driver's maintainer/developper
will care about this issue.
I applied Thomas' patch to mfd-fixes.
Thanks a lot to you and Thomas for that.
Cheers,
Hi Francis,
On Mon, Dec 09, 2013 at 08:33:32PM +0100, Francis Moreau wrote:
On 12/03/2013 09:14 AM, Francis Moreau wrote:
Hello Thomas,
On 12/02/2013 12:20 PM, Thomas Gleixner wrote:
On Mon, 2 Dec 2013, Thomas Gleixner wrote:
On Sat, 30 Nov 2013, Francis Moreau wrote:
Hello Thomas,
On 12/10/2013 06:17 AM, Samuel Ortiz wrote:
Hi Francis,
Adding Lee to the Cc list.
On Tue, Dec 03, 2013 at 09:14:14AM +0100, Francis Moreau wrote:
Now that you did the hard work, I hope driver's maintainer/developper
will care about this issue.
I applied Thomas' patch to mfd-fixes.
Thanks a
Hi Francis:
On 12/10/2013 09:39 AM, wwang wrote:
which is based on Thomas' patch.
Can you help us test this patch, we disable irq while suspend here.
From 6b2bd6d85780bfd8d4fe5289aee1b09dd655d2d4 Mon Sep 17 00:00:00 2001
From: Micky Ching micky_ch...@realsil.com.cn
Date: Thu, 5 Dec 2013
Hello Thomas,
On 12/02/2013 12:20 PM, Thomas Gleixner wrote:
> On Mon, 2 Dec 2013, Thomas Gleixner wrote:
>> On Sat, 30 Nov 2013, Francis Moreau wrote:
>>> Hello Thomas,
>>>
>>> Sorry for the delay.
>>>
>>> On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
On Fri, 29 Nov 2013, Francis Moreau
Hello Thomas,
On 12/02/2013 12:20 PM, Thomas Gleixner wrote:
On Mon, 2 Dec 2013, Thomas Gleixner wrote:
On Sat, 30 Nov 2013, Francis Moreau wrote:
Hello Thomas,
Sorry for the delay.
On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
On Fri, 29 Nov 2013, Francis Moreau wrote:
Since it seems
On Mon, 2 Dec 2013, Thomas Gleixner wrote:
> On Sat, 30 Nov 2013, Francis Moreau wrote:
> > Hello Thomas,
> >
> > Sorry for the delay.
> >
> > On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
> > > On Fri, 29 Nov 2013, Francis Moreau wrote:
> > >> Since it seems to be related to rtsx driver or its
On Sat, 30 Nov 2013, Francis Moreau wrote:
> Hello Thomas,
>
> Sorry for the delay.
>
> On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
> > On Fri, 29 Nov 2013, Francis Moreau wrote:
> >> Since it seems to be related to rtsx driver or its upper layer, could
> >> the folks involved in this area
On Sat, 30 Nov 2013, Francis Moreau wrote:
Hello Thomas,
Sorry for the delay.
On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
On Fri, 29 Nov 2013, Francis Moreau wrote:
Since it seems to be related to rtsx driver or its upper layer, could
the folks involved in this area have a look to
On Mon, 2 Dec 2013, Thomas Gleixner wrote:
On Sat, 30 Nov 2013, Francis Moreau wrote:
Hello Thomas,
Sorry for the delay.
On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
On Fri, 29 Nov 2013, Francis Moreau wrote:
Since it seems to be related to rtsx driver or its upper layer,
On 11/30/2013 09:17 PM, Rafael J. Wysocki wrote:
[...]
> If your system survives resume (I guess it does?), can you please send
> /proc/interrupts before and after the first suspend/resume cycle?
>
Please find both dumps attached.
Thanks
CPU0 CPU1 CPU2 CPU3
On 11/30/2013 09:17 PM, Rafael J. Wysocki wrote:
> On Saturday, November 30, 2013 04:07:36 PM Francis Moreau wrote:
>> Hello Thomas,
>>
>> Sorry for the delay.
>>
>> On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
>>> On Fri, 29 Nov 2013, Francis Moreau wrote:
Since it seems to be related to
On 11/30/2013 09:17 PM, Rafael J. Wysocki wrote:
On Saturday, November 30, 2013 04:07:36 PM Francis Moreau wrote:
Hello Thomas,
Sorry for the delay.
On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
On Fri, 29 Nov 2013, Francis Moreau wrote:
Since it seems to be related to rtsx driver or its
On 11/30/2013 09:17 PM, Rafael J. Wysocki wrote:
[...]
If your system survives resume (I guess it does?), can you please send
/proc/interrupts before and after the first suspend/resume cycle?
Please find both dumps attached.
Thanks
CPU0 CPU1 CPU2 CPU3
On Saturday, November 30, 2013 04:07:36 PM Francis Moreau wrote:
> Hello Thomas,
>
> Sorry for the delay.
>
> On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
> > On Fri, 29 Nov 2013, Francis Moreau wrote:
> >> Since it seems to be related to rtsx driver or its upper layer, could
> >> the folks
Hello Thomas,
Sorry for the delay.
On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
> On Fri, 29 Nov 2013, Francis Moreau wrote:
>> Since it seems to be related to rtsx driver or its upper layer, could
>> the folks involved in this area have a look to this issue please ?
>
> I'm not involved, but
Hello Thomas,
Sorry for the delay.
On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
On Fri, 29 Nov 2013, Francis Moreau wrote:
Since it seems to be related to rtsx driver or its upper layer, could
the folks involved in this area have a look to this issue please ?
I'm not involved, but
On Saturday, November 30, 2013 04:07:36 PM Francis Moreau wrote:
Hello Thomas,
Sorry for the delay.
On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
On Fri, 29 Nov 2013, Francis Moreau wrote:
Since it seems to be related to rtsx driver or its upper layer, could
the folks involved in
On Fri, 29 Nov 2013, Francis Moreau wrote:
> Since it seems to be related to rtsx driver or its upper layer, could
> the folks involved in this area have a look to this issue please ?
I'm not involved, but looking at the debug objects backtrace it's
related to the delayed work in rtsx.
Does the
Hello,
On 11/25/2013 11:47 AM, Rafael J. Wysocki wrote:
> On Monday, November 25, 2013 08:42:21 AM Francis Moreau wrote:
>> On 11/24/2013 10:06 PM, Rafael J. Wysocki wrote:
>>> On Sunday, November 24, 2013 10:39:20 AM Francis Moreau wrote:
Hello Thomas
On 11/22/2013 11:27 PM,
Hello,
On 11/25/2013 11:47 AM, Rafael J. Wysocki wrote:
On Monday, November 25, 2013 08:42:21 AM Francis Moreau wrote:
On 11/24/2013 10:06 PM, Rafael J. Wysocki wrote:
On Sunday, November 24, 2013 10:39:20 AM Francis Moreau wrote:
Hello Thomas
On 11/22/2013 11:27 PM, Thomas Gleixner wrote:
On Fri, 29 Nov 2013, Francis Moreau wrote:
Since it seems to be related to rtsx driver or its upper layer, could
the folks involved in this area have a look to this issue please ?
I'm not involved, but looking at the debug objects backtrace it's
related to the delayed work in rtsx.
Does the
On Monday, November 25, 2013 08:42:21 AM Francis Moreau wrote:
> On 11/24/2013 10:06 PM, Rafael J. Wysocki wrote:
> > On Sunday, November 24, 2013 10:39:20 AM Francis Moreau wrote:
> >> Hello Thomas
> >>
> >> On 11/22/2013 11:27 PM, Thomas Gleixner wrote:
> >>> On Fri, 22 Nov 2013, Rafael J.
On Monday, November 25, 2013 08:42:21 AM Francis Moreau wrote:
On 11/24/2013 10:06 PM, Rafael J. Wysocki wrote:
On Sunday, November 24, 2013 10:39:20 AM Francis Moreau wrote:
Hello Thomas
On 11/22/2013 11:27 PM, Thomas Gleixner wrote:
On Fri, 22 Nov 2013, Rafael J. Wysocki wrote:
On
On 11/24/2013 10:06 PM, Rafael J. Wysocki wrote:
> On Sunday, November 24, 2013 10:39:20 AM Francis Moreau wrote:
>> Hello Thomas
>>
>> On 11/22/2013 11:27 PM, Thomas Gleixner wrote:
>>> On Fri, 22 Nov 2013, Rafael J. Wysocki wrote:
On Friday, November 22, 2013 10:36:23 PM Francis Moreau
On Sunday, November 24, 2013 10:39:20 AM Francis Moreau wrote:
> Hello Thomas
>
> On 11/22/2013 11:27 PM, Thomas Gleixner wrote:
> > On Fri, 22 Nov 2013, Rafael J. Wysocki wrote:
> >> On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
> >>> Ok, I've finally managed to find out the bad
On Sun, Nov 24, 2013 at 10:39:20AM +0100, Francis Moreau wrote:
> This looks like it was a good idea.
>
> The kernel now outputs the following traces after resuming.
>
> [ 26.973928] WARNING: CPU: 0 PID: 4 at lib/debugobjects.c:260
> debug_print_object+0x83/0xa0()
> [ 26.973932] ODEBUG: free
Hello Rafael,
On 11/22/2013 11:08 PM, Rafael J. Wysocki wrote:
> On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
>> On 11/22/2013 01:54 PM, Rafael J. Wysocki wrote:
>>> On Friday, November 22, 2013 10:57:25 AM Francis Moreau wrote:
Le 22/11/2013 08:43, Francis Moreau a écrit :
Hello Rafael,
On 11/22/2013 11:08 PM, Rafael J. Wysocki wrote:
On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
On 11/22/2013 01:54 PM, Rafael J. Wysocki wrote:
On Friday, November 22, 2013 10:57:25 AM Francis Moreau wrote:
Le 22/11/2013 08:43, Francis Moreau a écrit :
Le
On Sun, Nov 24, 2013 at 10:39:20AM +0100, Francis Moreau wrote:
This looks like it was a good idea.
The kernel now outputs the following traces after resuming.
[ 26.973928] WARNING: CPU: 0 PID: 4 at lib/debugobjects.c:260
debug_print_object+0x83/0xa0()
[ 26.973932] ODEBUG: free active
On Sunday, November 24, 2013 10:39:20 AM Francis Moreau wrote:
Hello Thomas
On 11/22/2013 11:27 PM, Thomas Gleixner wrote:
On Fri, 22 Nov 2013, Rafael J. Wysocki wrote:
On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
Ok, I've finally managed to find out the bad commit:
On 11/24/2013 10:06 PM, Rafael J. Wysocki wrote:
On Sunday, November 24, 2013 10:39:20 AM Francis Moreau wrote:
Hello Thomas
On 11/22/2013 11:27 PM, Thomas Gleixner wrote:
On Fri, 22 Nov 2013, Rafael J. Wysocki wrote:
On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
Ok, I've
On Fri, 22 Nov 2013, Rafael J. Wysocki wrote:
> On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
> > Ok, I've finally managed to find out the bad commit:
> > ad07277e82dedabacc52c82746633680a3187d25: ACPI / PM: Hold acpi_scan_lock
> > over system PM transitions
> >
> > I verified
On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
> On 11/22/2013 01:54 PM, Rafael J. Wysocki wrote:
> > On Friday, November 22, 2013 10:57:25 AM Francis Moreau wrote:
> >> Le 22/11/2013 08:43, Francis Moreau a écrit :
> >>> Le 21/11/2013 12:17, Jingoo Han a écrit :
> >>> [...]
>
On 11/22/2013 01:54 PM, Rafael J. Wysocki wrote:
> On Friday, November 22, 2013 10:57:25 AM Francis Moreau wrote:
>> Le 22/11/2013 08:43, Francis Moreau a écrit :
>>> Le 21/11/2013 12:17, Jingoo Han a écrit :
>>> [...]
>
>> Also I took a look at the changes between v3.11 and v3.12 in this
On Friday, November 22, 2013 10:57:25 AM Francis Moreau wrote:
> Le 22/11/2013 08:43, Francis Moreau a écrit :
> > Le 21/11/2013 12:17, Jingoo Han a écrit :
> > [...]
> >>>
> Also I took a look at the changes between v3.11 and v3.12 in this area
> and those changes match the issue I'm
Le 22/11/2013 08:43, Francis Moreau a écrit :
> Le 21/11/2013 12:17, Jingoo Han a écrit :
> [...]
>>>
Also I took a look at the changes between v3.11 and v3.12 in this area
and those changes match the issue I'm facing:
$ git log --oneline v3.11..v3.12 -- drivers/mfd/rtsx_pcr.c
Le 22/11/2013 08:43, Francis Moreau a écrit :
Le 21/11/2013 12:17, Jingoo Han a écrit :
[...]
Also I took a look at the changes between v3.11 and v3.12 in this area
and those changes match the issue I'm facing:
$ git log --oneline v3.11..v3.12 -- drivers/mfd/rtsx_pcr.c
09fd867 mfd: rtsx:
On Friday, November 22, 2013 10:57:25 AM Francis Moreau wrote:
Le 22/11/2013 08:43, Francis Moreau a écrit :
Le 21/11/2013 12:17, Jingoo Han a écrit :
[...]
Also I took a look at the changes between v3.11 and v3.12 in this area
and those changes match the issue I'm facing:
$ git log
On 11/22/2013 01:54 PM, Rafael J. Wysocki wrote:
On Friday, November 22, 2013 10:57:25 AM Francis Moreau wrote:
Le 22/11/2013 08:43, Francis Moreau a écrit :
Le 21/11/2013 12:17, Jingoo Han a écrit :
[...]
Also I took a look at the changes between v3.11 and v3.12 in this area
and those
On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
On 11/22/2013 01:54 PM, Rafael J. Wysocki wrote:
On Friday, November 22, 2013 10:57:25 AM Francis Moreau wrote:
Le 22/11/2013 08:43, Francis Moreau a écrit :
Le 21/11/2013 12:17, Jingoo Han a écrit :
[...]
Also I took a
On Fri, 22 Nov 2013, Rafael J. Wysocki wrote:
On Friday, November 22, 2013 10:36:23 PM Francis Moreau wrote:
Ok, I've finally managed to find out the bad commit:
ad07277e82dedabacc52c82746633680a3187d25: ACPI / PM: Hold acpi_scan_lock
over system PM transitions
I verified that the
Le 21/11/2013 12:17, Jingoo Han a écrit :
[...]
>>
>>> Also I took a look at the changes between v3.11 and v3.12 in this area
>>> and those changes match the issue I'm facing:
>>>
>>> $ git log --oneline v3.11..v3.12 -- drivers/mfd/rtsx_pcr.c
>>> 09fd867 mfd: rtsx: Copyright modifications
>>>
On Thursday, November 21, 2013 7:13 PM, Borislav Petkov wrote:
> On Thu, Nov 21, 2013 at 09:22:02AM +0100, Francis Moreau wrote:
> > Hmm, I think it's more than that because if I'm removing both
> > rtsx_pci_ms and memstick modules, then suspending and resuming doesn't
> > oops anymore.
>
>
Le 21/11/2013 12:17, Jingoo Han a écrit :
[...]
Also I took a look at the changes between v3.11 and v3.12 in this area
and those changes match the issue I'm facing:
$ git log --oneline v3.11..v3.12 -- drivers/mfd/rtsx_pcr.c
09fd867 mfd: rtsx: Copyright modifications
eb891c6 mfd: rtsx:
On Thursday, November 21, 2013 7:13 PM, Borislav Petkov wrote:
On Thu, Nov 21, 2013 at 09:22:02AM +0100, Francis Moreau wrote:
Hmm, I think it's more than that because if I'm removing both
rtsx_pci_ms and memstick modules, then suspending and resuming doesn't
oops anymore.
Interesting -
On Wed, Nov 20, 2013 at 10:45:05AM +0100, Francis Moreau wrote:
> Unfortunately the bisect session didn't give any positive results: I
> couldn't be sure if a specific revision was good or bad because the
> bug wasn't reproductible every time.
>
> But I got a different kernel oops on my stripped
Hello Borislav,
On 11/19/2013 11:15 AM, Borislav Petkov wrote:
> On Tue, Nov 19, 2013 at 11:01:14AM +0100, Francis Moreau wrote:
>> I think the easiest way to do it is to install a minimal system on a
>> USB stick and try to reproduce first in order to preserve my system.
>
> Yep, sounds simple
Hello Borislav,
On 11/19/2013 11:15 AM, Borislav Petkov wrote:
On Tue, Nov 19, 2013 at 11:01:14AM +0100, Francis Moreau wrote:
I think the easiest way to do it is to install a minimal system on a
USB stick and try to reproduce first in order to preserve my system.
Yep, sounds simple enough.
On Wed, Nov 20, 2013 at 10:45:05AM +0100, Francis Moreau wrote:
Unfortunately the bisect session didn't give any positive results: I
couldn't be sure if a specific revision was good or bad because the
bug wasn't reproductible every time.
But I got a different kernel oops on my stripped system
On Tue, Nov 19, 2013 at 11:01:14AM +0100, Francis Moreau wrote:
> I think the easiest way to do it is to install a minimal system on a
> USB stick and try to reproduce first in order to preserve my system.
Yep, sounds simple enough.
> Then I'll try to see if this issue exists in a previous
On Tue, Nov 19, 2013 at 11:01:14AM +0100, Francis Moreau wrote:
I think the easiest way to do it is to install a minimal system on a
USB stick and try to reproduce first in order to preserve my system.
Yep, sounds simple enough.
Then I'll try to see if this issue exists in a previous kernel
Le 17/11/2013 23:46, Borislav Petkov a écrit :
> On Sun, Nov 17, 2013 at 11:34:20PM +0100, Rafael J. Wysocki wrote:
>> This looks like a softirq bug to me (and related to cpuidle).
>
> Reportedly, it happens right after resume from RAM. Francis, is that
> correct?
yes that's correct. I haven't
Le 17/11/2013 23:34, Rafael J. Wysocki a écrit :
> On Sunday, November 17, 2013 11:06:12 PM Borislav Petkov wrote:
>> On Sun, Nov 17, 2013 at 09:49:40PM +0100, Francis Moreau wrote:
>>> On Sun, Nov 17, 2013 at 8:53 PM, Borislav Petkov wrote:
On Sun, Nov 17, 2013 at 07:02:21PM +0100, Francis
Hello Borislav,
Le 17/11/2013 23:06, Borislav Petkov a écrit :
> On Sun, Nov 17, 2013 at 09:49:40PM +0100, Francis Moreau wrote:
>> On Sun, Nov 17, 2013 at 8:53 PM, Borislav Petkov wrote:
>>> On Sun, Nov 17, 2013 at 07:02:21PM +0100, Francis Moreau wrote:
Sorry I haven't taken the original
Hello Borislav,
Le 17/11/2013 23:06, Borislav Petkov a écrit :
On Sun, Nov 17, 2013 at 09:49:40PM +0100, Francis Moreau wrote:
On Sun, Nov 17, 2013 at 8:53 PM, Borislav Petkov b...@alien8.de wrote:
On Sun, Nov 17, 2013 at 07:02:21PM +0100, Francis Moreau wrote:
Sorry I haven't taken the
Le 17/11/2013 23:34, Rafael J. Wysocki a écrit :
On Sunday, November 17, 2013 11:06:12 PM Borislav Petkov wrote:
On Sun, Nov 17, 2013 at 09:49:40PM +0100, Francis Moreau wrote:
On Sun, Nov 17, 2013 at 8:53 PM, Borislav Petkov b...@alien8.de wrote:
On Sun, Nov 17, 2013 at 07:02:21PM +0100,
Le 17/11/2013 23:46, Borislav Petkov a écrit :
On Sun, Nov 17, 2013 at 11:34:20PM +0100, Rafael J. Wysocki wrote:
This looks like a softirq bug to me (and related to cpuidle).
Reportedly, it happens right after resume from RAM. Francis, is that
correct?
yes that's correct. I haven't been
On Mon, Nov 18, 2013 at 11:33:25AM +1100, Kevin Easton wrote:
> That's part of an ASCII string, "DEP=2\0SE", so if that looks familiar
> to anyone (part of a kernel command line?) it might give a clue to
> where the timer callback pointer is being overwritten.
Yeah, it could be anything, maybe
On Sun, Nov 17, 2013 at 11:06:12PM +0100, Borislav Petkov wrote:
> and the virtual address in rIP is 8106f5c3, i.e. the same one
> as in the photo. Thus, the CALL instruction tries to call the timer
> function 'fn' which we pass as an argument to call_timer_fn.
>
> However, the address
On Sun, Nov 17, 2013 at 11:34:20PM +0100, Rafael J. Wysocki wrote:
> This looks like a softirq bug to me (and related to cpuidle).
Reportedly, it happens right after resume from RAM. Francis, is that
correct?
> I'm wondering if that happens with any of the older kernels or just
> 3.12?
That
On Sunday, November 17, 2013 11:06:12 PM Borislav Petkov wrote:
> On Sun, Nov 17, 2013 at 09:49:40PM +0100, Francis Moreau wrote:
> > On Sun, Nov 17, 2013 at 8:53 PM, Borislav Petkov wrote:
> > > On Sun, Nov 17, 2013 at 07:02:21PM +0100, Francis Moreau wrote:
> > >> Sorry I haven't taken the
On Sun, Nov 17, 2013 at 09:49:40PM +0100, Francis Moreau wrote:
> On Sun, Nov 17, 2013 at 8:53 PM, Borislav Petkov wrote:
> > On Sun, Nov 17, 2013 at 07:02:21PM +0100, Francis Moreau wrote:
> >> Sorry I haven't taken the original picture large enough, and getting
> >> this kernel panic is pretty
On Sun, Nov 17, 2013 at 8:53 PM, Borislav Petkov wrote:
> On Sun, Nov 17, 2013 at 07:02:21PM +0100, Francis Moreau wrote:
>> Sorry I haven't taken the original picture large enough, and getting
>> this kernel panic is pretty hard since the kernel usually displays the
>> black screen.
>
> Ok, just
On Sun, Nov 17, 2013 at 07:02:21PM +0100, Francis Moreau wrote:
> Sorry I haven't taken the original picture large enough, and getting
> this kernel panic is pretty hard since the kernel usually displays the
> black screen.
Ok, just try to make a readable picture of the whole line, next time you
On Sun, Nov 17, 2013 at 5:01 PM, Borislav Petkov wrote:
> On Sun, Nov 17, 2013 at 04:50:23PM +0100, Francis Moreau wrote:
>> AFAIK, the kernel has 2 simple patches on top of the vanilla one.
>> They're both are trivial and can't be related to this issue.
>>
>> You can have look to them here:
>>
On Sun, Nov 17, 2013 at 04:50:23PM +0100, Francis Moreau wrote:
> AFAIK, the kernel has 2 simple patches on top of the vanilla one.
> They're both are trivial and can't be related to this issue.
>
> You can have look to them here:
> https://wiki.archlinux.org/index.php/Kernels#Official_packages
Le 17/11/2013 14:25, Borislav Petkov a écrit :
> On Sun, Nov 17, 2013 at 10:42:05AM +0100, Francis Moreau wrote:
>> Today I got a different behaviour, after resuming I got a
>> kernel panic. I could take a picture of the laptop screen:
>> http://imgur.com/f5uWFTY
>
> Does archlinux ship the
On Sun, Nov 17, 2013 at 10:42:05AM +0100, Francis Moreau wrote:
> Today I got a different behaviour, after resuming I got a
> kernel panic. I could take a picture of the laptop screen:
> http://imgur.com/f5uWFTY
Does archlinux ship the upstream kernel or do they have patches ontop?
If "yes" to
Hello,
I recently acquiered a new laptop. After installing archlinux which is
shipping a kernel 3.12, I've got some troubles after resuming from each
suspend to RAM.
The behaviour is as following: each resumes correctly and my session
seems to be restored but after typing a command on the term,
1 - 100 of 112 matches
Mail list logo
