On Friday 03 of April 2009, Chris Wright wrote:
> * Ingo Molnar (mi...@elte.hu) wrote:
> > * Chris Wright wrote:
> > > * Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> > > > On Friday 03 of April 2009, Chris Wright wrote:
> > > > > * Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> >
* Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> On Friday 03 of April 2009, Chris Wright wrote:
> > * Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> > > What about 9ea09af3bd3090e8349ca2899ca2011bd94cda85 ?
> > >
> > > stop_machine: introduce stop_machine_create/destroy.
> >
> > Th
* Ingo Molnar (mi...@elte.hu) wrote:
>
> * Chris Wright wrote:
>
> > * Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> > > On Friday 03 of April 2009, Chris Wright wrote:
> > > > * Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> > > > > What about 9ea09af3bd3090e8349ca2899ca2011bd9
* Chris Wright wrote:
> * Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> > On Friday 03 of April 2009, Chris Wright wrote:
> > > * Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> > > > What about 9ea09af3bd3090e8349ca2899ca2011bd94cda85 ?
> > > >
> > > > stop_machine: introduce st
* Arkadiusz Miskiewicz wrote:
> On Friday 03 of April 2009, Chris Wright wrote:
> > * Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> > > What about 9ea09af3bd3090e8349ca2899ca2011bd94cda85 ?
> > >
> > > stop_machine: introduce stop_machine_create/destroy.
> >
> > That is later fixed in a
On Friday 03 of April 2009, Chris Wright wrote:
> * Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> > What about 9ea09af3bd3090e8349ca2899ca2011bd94cda85 ?
> >
> > stop_machine: introduce stop_machine_create/destroy.
>
> That is later fixed in a0e280e0f33f6c859a235fb69a875ed8f3420388.
>
> Ca
* Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> What about 9ea09af3bd3090e8349ca2899ca2011bd94cda85 ?
>
> stop_machine: introduce stop_machine_create/destroy.
That is later fixed in a0e280e0f33f6c859a235fb69a875ed8f3420388.
Can you please verify if 2.6.29 works for you? Your bisects ar
On Thursday 02 of April 2009, Rafael J. Wysocki wrote:
> On Thursday 02 April 2009, Ingo Molnar wrote:
> > * Rafael J. Wysocki wrote:
> > > On Thursday 02 April 2009, Chris Wright wrote:
> > > > * Rafael J. Wysocki (r...@sisk.pl) wrote:
> > > > > Sorry for the misunderstanding, I thought the break
On Thursday 02 April 2009, Ingo Molnar wrote:
>
> * Rafael J. Wysocki wrote:
>
> > On Thursday 02 April 2009, Chris Wright wrote:
> > > * Rafael J. Wysocki (r...@sisk.pl) wrote:
> > > > Sorry for the misunderstanding, I thought the breakage might be
> > > > introduced
> > > > between 15f7176eb1
* Rafael J. Wysocki wrote:
> On Thursday 02 April 2009, Chris Wright wrote:
> > * Rafael J. Wysocki (r...@sisk.pl) wrote:
> > > Sorry for the misunderstanding, I thought the breakage might be introduced
> > > between 15f7176eb1cccec0a332541285ee752b935c1c85 and
> > > 0a0c5168df270a50e3518e4f12bd
On Thursday 02 April 2009, Chris Wright wrote:
> * Rafael J. Wysocki (r...@sisk.pl) wrote:
> > Sorry for the misunderstanding, I thought the breakage might be introduced
> > between 15f7176eb1cccec0a332541285ee752b935c1c85 and
> > 0a0c5168df270a50e3518e4f12bddb31f8f5f38f, so I thought it would be a
On Wednesday 01 of April 2009, Chris Wright wrote:
> * Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> > and this as bad commit:
> >
> > 7f7ace0cda64c99599c23785f8979a072e118058 is first bad commit
>
> Does it make any difference if you roll fwd a couple commits to:
>
> 802bf931f2688ad125b73
* Rafael J. Wysocki (r...@sisk.pl) wrote:
> Sorry for the misunderstanding, I thought the breakage might be introduced
> between 15f7176eb1cccec0a332541285ee752b935c1c85 and
> 0a0c5168df270a50e3518e4f12bddb31f8f5f38f, so I thought it would be a good
> idea to verify if 0a0c5168df270a50e3518e4f12bdd
On Thursday 02 April 2009, Chris Wright wrote:
> * Rafael J. Wysocki (r...@sisk.pl) wrote:
> > On Wednesday 01 April 2009, Chris Wright wrote:
> > > * Rafael J. Wysocki (r...@sisk.pl) wrote:
> > > > This may be caused by the recent PM changes. Can you please test if
> > > > commit
> > > > 8efb8c7
* Rafael J. Wysocki (r...@sisk.pl) wrote:
> On Wednesday 01 April 2009, Chris Wright wrote:
> > * Rafael J. Wysocki (r...@sisk.pl) wrote:
> > > This may be caused by the recent PM changes. Can you please test if
> > > commit
> > > 8efb8c76fcdccf5050c0ea059dac392789baaff2 is fine?
> >
> > I just
On Wednesday 01 April 2009, Chris Wright wrote:
> * Rafael J. Wysocki (r...@sisk.pl) wrote:
> > This may be caused by the recent PM changes. Can you please test if commit
> > 8efb8c76fcdccf5050c0ea059dac392789baaff2 is fine?
>
> I just tested on my t400, it's not[1]. See same symptoms as Arkadiu
* Rafael J. Wysocki (r...@sisk.pl) wrote:
> This may be caused by the recent PM changes. Can you please test if commit
> 8efb8c76fcdccf5050c0ea059dac392789baaff2 is fine?
I just tested on my t400, it's not[1]. See same symptoms as Arkadiusz.
Seems as if it responds to initial apci event, I see s
On Wednesday 01 April 2009, Arkadiusz Miskiewicz wrote:
>
> Hi,
>
> After some recent merge to Linus tree resume from ram on my thinkpad t400
> stopped working. My latest test was done on today Linus git master tree.
>
> I'm closing lid, it suspends according to "moon" led. When I open lid I se
* Arkadiusz Miskiewicz (a.miskiew...@gmail.com) wrote:
> and this as bad commit:
>
> 7f7ace0cda64c99599c23785f8979a072e118058 is first bad commit
Does it make any difference if you roll fwd a couple commits to:
802bf931f2688ad125b73db597ce63cc842fb27a
That fixes a possible problem with the cpum
19 matches
Mail list logo
