On 11-05-19 03:01 PM, Maciej Rutecki wrote:
> On czwartek, 21 kwietnia 2011 o 19:22:05 Maciej Rutecki wrote:
>> (add LKML)
>>
>> On niedziela, 17 kwietnia 2011 o 18:04:04 Maciej Rutecki wrote:
>>> Hi
>>>
>>> Last known good: 2.6.38
>>> Failing kernel: 2.6.39-rc3
>>> Subsystem: Intel graphics driver
On 11-05-19 03:01 PM, Maciej Rutecki wrote:
> On czwartek, 21 kwietnia 2011 o 19:22:05 Maciej Rutecki wrote:
>> (add LKML)
>>
>> On niedziela, 17 kwietnia 2011 o 18:04:04 Maciej Rutecki wrote:
>>> Hi
>>>
>>> Last known good: 2.6.38
>>> Failing kernel: 2.6.39-rc3
>>> Subsystem: Intel graphics driver
On 10-11-19 05:58 PM, Alex Deucher wrote:
On Fri, Nov 19, 2010 at 5:55 PM, Mark Lord wrote:
It now comes back at resume time.
So that patch helped?
I think so. It didn't used to resume from suspend with 2.6.36, and now it does.
But suffers long delays (also sometimes with 2.6.35)
On 10-11-19 11:39 AM, Alex Deucher wrote:
On Thu, Nov 18, 2010 at 7:47 PM, Mark Lord wrote:
My non-Intel graphics notebook (has ATI X1400 graphics) also has a resume
regression with 2.6.36. But it does work fine with 2.6.35 (and earlier,
back many years). As a result, I'm stuck with 2
On 10-11-19 05:58 PM, Alex Deucher wrote:
> On Fri, Nov 19, 2010 at 5:55 PM, Mark Lord wrote:
>
>> It now comes back at resume time.
>
> So that patch helped?
I think so. It didn't used to resume from suspend with 2.6.36, and now it does.
>> But suffers long delay
On 10-11-19 11:39 AM, Alex Deucher wrote:
> On Thu, Nov 18, 2010 at 7:47 PM, Mark Lord wrote:
>
>> My non-Intel graphics notebook (has ATI X1400 graphics) also has a resume
>> regression with 2.6.36. But it does work fine with 2.6.35 (and earlier,
>> back many years).
On 10-11-18 06:50 PM, Rafael J. Wysocki wrote:
This message contains a list of some post-2.6.35 regressions introduced before
2.6.36, for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.
If you know of any other unre
On 10-11-18 06:50 PM, Rafael J. Wysocki wrote:
> This message contains a list of some post-2.6.35 regressions introduced before
> 2.6.36, for which there are no fixes in the mainline known to the tracking
> team.
> If any of them have been fixed already, please let us know.
>
> If you know of any
