On 07/08/2013 06:05 AM, Rafael J. Wysocki wrote:
>
> That's because no one knows how to fix it. Actually, we don't even know
> what the root cause of it is. Sorry about that.
>
> Are you still able to make things work again by reverting the commit you
> bisected to?
>
Well, we know now. Hop
On 07/12/2013 04:36 PM, Christian Sünkenberg wrote:
>
> Jonas tried your patch and it fixes suspend/resume on his T43, although
> IMHO the safest approach would be to just add an exception for
> Vendor==Intel && Family==6 && Model==13, or more generally Vendor==Intel
> && !supports_long_mode, as t
Hello,
On 07/11/2013 01:57 AM, H. Peter Anvin wrote:
> On 07/10/2013 01:52 PM, Christian Sünkenberg wrote:
>> Hello,
>>
>> On 05/01/2013 07:33 PM, H. Peter Anvin wrote:
>>> On 05/01/2013 10:01 AM, Jonas Heinrich wrote:
Hello, I tried the newest kernel, 3.9 today but the bug is still
pres
On 07/10/2013 01:52 PM, Christian Sünkenberg wrote:
> Hello,
>
> On 05/01/2013 07:33 PM, H. Peter Anvin wrote:
>> On 05/01/2013 10:01 AM, Jonas Heinrich wrote:
>>> Hello, I tried the newest kernel, 3.9 today but the bug is still
>>> present. Applying the attached patch solves the bug for me.
>>>
>
Hello,
On 05/01/2013 07:33 PM, H. Peter Anvin wrote:
> On 05/01/2013 10:01 AM, Jonas Heinrich wrote:
>> Hello, I tried the newest kernel, 3.9 today but the bug is still
>> present. Applying the attached patch solves the bug for me.
>>
>> Best regards, Jonas Heinrich
>
> Okay... WTF is going on he
On Monday, July 08, 2013 09:50:43 AM Jonas Heinrich wrote:
> On 05-03 15:15, Jarkko Sakkinen wrote:
> > Hi
> >
> > On Friday, May 03, 2013 02:07:05 PM Jonas Heinrich wrote:
> > > On 05-03 01:29, Rafael J. Wysocki wrote:
> > > > On Thursday, May 02, 2013 08:32:30 PM Jonas Heinrich wrote:
> > > > >
On 05-03 15:15, Jarkko Sakkinen wrote:
> Hi
>
> On Friday, May 03, 2013 02:07:05 PM Jonas Heinrich wrote:
> > On 05-03 01:29, Rafael J. Wysocki wrote:
> > > On Thursday, May 02, 2013 08:32:30 PM Jonas Heinrich wrote:
> > > > On 05-02 02:45, Rafael J. Wysocki wrote:
> > > > > On Wednesday, May 01,
On Friday, May 03, 2013 01:37:45 PM Rafael J. Wysocki wrote:
> On Friday, May 03, 2013 11:07:05 AM Jonas Heinrich wrote:
> > On 05-03 01:29, Rafael J. Wysocki wrote:
> > > On Thursday, May 02, 2013 08:32:30 PM Jonas Heinrich wrote:
> > > > On 05-02 02:45, Rafael J. Wysocki wrote:
> > > > > On Wedne
Hi
On Friday, May 03, 2013 02:07:05 PM Jonas Heinrich wrote:
> On 05-03 01:29, Rafael J. Wysocki wrote:
> > On Thursday, May 02, 2013 08:32:30 PM Jonas Heinrich wrote:
> > > On 05-02 02:45, Rafael J. Wysocki wrote:
> > > > On Wednesday, May 01, 2013 11:55:10 AM H. Peter Anvin wrote:
> > > > > On 0
On Friday, May 03, 2013 11:07:05 AM Jonas Heinrich wrote:
> On 05-03 01:29, Rafael J. Wysocki wrote:
> > On Thursday, May 02, 2013 08:32:30 PM Jonas Heinrich wrote:
> > > On 05-02 02:45, Rafael J. Wysocki wrote:
> > > > On Wednesday, May 01, 2013 11:55:10 AM H. Peter Anvin wrote:
> > > > > On 05/01
On 05-03 01:29, Rafael J. Wysocki wrote:
> On Thursday, May 02, 2013 08:32:30 PM Jonas Heinrich wrote:
> > On 05-02 02:45, Rafael J. Wysocki wrote:
> > > On Wednesday, May 01, 2013 11:55:10 AM H. Peter Anvin wrote:
> > > > On 05/01/2013 11:51 AM, Jonas Heinrich wrote:
> > > > > Well, you could give
On Thursday, May 02, 2013 08:32:30 PM Jonas Heinrich wrote:
> On 05-02 02:45, Rafael J. Wysocki wrote:
> > On Wednesday, May 01, 2013 11:55:10 AM H. Peter Anvin wrote:
> > > On 05/01/2013 11:51 AM, Jonas Heinrich wrote:
> > > > Well, you could give me instructions on how to debug this (I'll do
> >
On 05-02 02:45, Rafael J. Wysocki wrote:
> On Wednesday, May 01, 2013 11:55:10 AM H. Peter Anvin wrote:
> > On 05/01/2013 11:51 AM, Jonas Heinrich wrote:
> > > Well, you could give me instructions on how to debug this (I'll do
> > > everything ;)) or I could ship you the Thinkpad T43. I guess this
On Wednesday, May 01, 2013 11:55:10 AM H. Peter Anvin wrote:
> On 05/01/2013 11:51 AM, Jonas Heinrich wrote:
> > Well, you could give me instructions on how to debug this (I'll do
> > everything ;)) or I could ship you the Thinkpad T43. I guess this
> > would worth the effort since this bug is som
On 05/01/2013 11:51 AM, Jonas Heinrich wrote:
> Well, you could give me instructions on how to debug this (I'll do
> everything ;)) or I could ship you the Thinkpad T43. I guess this
> would worth the effort since this bug is somehow critical.
>
> Best regards, Jonas
I'll put together a debug pa
Well, you could give me instructions on how to debug this (I'll do
everything ;)) or I could ship you the Thinkpad T43. I guess this would
worth the effort since this bug is somehow critical.
Best regards,
Jonas
On 05-01 10:33, H. Peter Anvin wrote:
> On 05/01/2013 10:01 AM, Jonas Heinrich wrote:
On 05/01/2013 10:01 AM, Jonas Heinrich wrote:
> Hello, I tried the newest kernel, 3.9 today but the bug is still
> present. Applying the attached patch solves the bug for me.
>
> Best regards, Jonas Heinrich
Okay... WTF is going on here? Does pmode_behavior just not get set up
correctly? Since
Hello,
I tried the newest kernel, 3.9 today but the bug is still present.
Applying the attached patch solves the bug for me.
Best regards,
Jonas Heinrich
On 03-20 14:32, Jonas Heinrich wrote:
> Hello Peter,
> sorry for responding that late to your advice ...
>
> On 02-23 13:54, H. Peter Anvin wr
On 02/23/2013 05:18 AM, Jonas Heinrich wrote:
Hi,
thank you for your replay and the effort you invest in helping me out
with this problem.
Today, I further debuged the problem and reverted this part of your commit
(without understanding the actual code):
Hi, that commit is indeed buggy, but it
Hi,
thank you for your replay and the effort you invest in helping me out
with this problem.
Today, I further debuged the problem and reverted this part of your commit
(without understanding the actual code):
diff --git a/arch/x86/realmode/rm/wakeup_asm.S
b/arch/x86/realmode/rm/wakeup_asm.S
index
I might be able to get my hands on a T43 later this week and see if I can
reproduce this. This patch seems more plausible, at least... but still
puzzling.
Jonas Heinrich wrote:
>On 02-17 21:40, Rafael J. Wysocki wrote:
>> Does the commit immediately preceding this one behave correctly?
>Stran
T43 is quite old... which might have exposed unique bugs. How reliable is the
failure? Even one misidentified commit results in git bisect giving garbage.
Jonas Heinrich wrote:
>Hello,
>since kernel version 3.7-rc1 I can't resume my notebook (Thinkpad T43)
>from suspend2ram anymore.
>
>I star
On Sunday, February 17, 2013 05:48:25 PM Jonas Heinrich wrote:
> Hello,
> since kernel version 3.7-rc1 I can't resume my notebook (Thinkpad T43)
> from suspend2ram anymore.
>
> I started a kernel bisection (see bisection_log in attachement). Also
> see kernel conifg @ attachement.
>
> The culprit
On 10/18/2012 04:17 PM, H. Peter Anvin wrote:
> On 10/18/2012 05:26 AM, Cédric Godin wrote:
>> Hello,
>>
>> After upgrading my kernel from 3.6 to 3.7-rc1 on my laptop, I can't resume
>> anymore.
>> I bisected the problem to
>>
>
> There is a fix for this already queued up. Please try the attached
On 10/18/2012 05:26 AM, Cédric Godin wrote:
Hello,
After upgrading my kernel from 3.6 to 3.7-rc1 on my laptop, I can't resume
anymore.
I bisected the problem to
There is a fix for this already queued up. Please try the attached
patch to verify that it fixes your problem.
-hpa
--
25 matches
Mail list logo