* I think my kernel image just went back in time...
@ 2012-12-09 23:17 Chris Tapp
2012-12-21 17:30 ` McClintock Matthew-B29882
2012-12-21 18:17 ` Tomas Frydrych
0 siblings, 2 replies; 5+ messages in thread
From: Chris Tapp @ 2012-12-09 23:17 UTC (permalink / raw)
To: Yocto Discussion Mailing List
In tmp/deploy/images:
1) bzImage had a timestamp of 2012-12-09 21:49 and the file ended -20121209214459.bin
2) Cleaned the image and the task it contained (to pick up some changes on rebuild) and deleted the image files (.hddimg, etc.) in tmp/deploy/images making sure to leave the kernel files intact.
3) Rebuilt the image. The bzImage now has a timestamp of 2012-12-09 11:13 and the name ends -20121209105420.bin
This looks to me like the kernel image has reverted to an earlier one! It is certainly behaving as if this is the case, because a kernel option that I added is no longer in the deployed image...
Chris Tapp
opensource@keylevel.com
www.keylevel.com
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: I think my kernel image just went back in time...
2012-12-09 23:17 I think my kernel image just went back in time Chris Tapp
@ 2012-12-21 17:30 ` McClintock Matthew-B29882
2012-12-21 18:17 ` Tomas Frydrych
1 sibling, 0 replies; 5+ messages in thread
From: McClintock Matthew-B29882 @ 2012-12-21 17:30 UTC (permalink / raw)
To: Chris Tapp; +Cc: Yocto Discussion Mailing List
On Sun, Dec 9, 2012 at 5:17 PM, Chris Tapp <opensource@keylevel.com> wrote:
> In tmp/deploy/images:
>
> 1) bzImage had a timestamp of 2012-12-09 21:49 and the file ended -20121209214459.bin
>
> 2) Cleaned the image and the task it contained (to pick up some changes on rebuild) and deleted the image files (.hddimg, etc.) in tmp/deploy/images making sure to leave the kernel files intact.
>
> 3) Rebuilt the image. The bzImage now has a timestamp of 2012-12-09 11:13 and the name ends -20121209105420.bin
>
> This looks to me like the kernel image has reverted to an earlier one! It is certainly behaving as if this is the case, because a kernel option that I added is no longer in the deployed image...
Did it redeploy from an older sstate-cache?
-M
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: I think my kernel image just went back in time...
2012-12-09 23:17 I think my kernel image just went back in time Chris Tapp
2012-12-21 17:30 ` McClintock Matthew-B29882
@ 2012-12-21 18:17 ` Tomas Frydrych
2013-01-07 16:26 ` Darren Hart
1 sibling, 1 reply; 5+ messages in thread
From: Tomas Frydrych @ 2012-12-21 18:17 UTC (permalink / raw)
To: yocto
On 09/12/12 23:17, Chris Tapp wrote:
> In tmp/deploy/images:
>
> 1) bzImage had a timestamp of 2012-12-09 21:49 and the file ended
> -20121209214459.bin
>
> 2) Cleaned the image and the task it contained (to pick up some
> changes on rebuild) and deleted the image files (.hddimg, etc.) in
> tmp/deploy/images making sure to leave the kernel files intact.
Did you cleansstate it? I find that without cleaning the state kernel
image gets always pulled out of sstate rather than properly rebuilt.
Tomas
--
http://sleepfive.com
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: I think my kernel image just went back in time...
2012-12-21 18:17 ` Tomas Frydrych
@ 2013-01-07 16:26 ` Darren Hart
2013-01-10 8:12 ` Chris Tapp
0 siblings, 1 reply; 5+ messages in thread
From: Darren Hart @ 2013-01-07 16:26 UTC (permalink / raw)
To: Tomas Frydrych; +Cc: yocto
On 12/21/2012 10:17 AM, Tomas Frydrych wrote:
> On 09/12/12 23:17, Chris Tapp wrote:
>> In tmp/deploy/images:
>>
>> 1) bzImage had a timestamp of 2012-12-09 21:49 and the file ended
>> -20121209214459.bin
>>
>> 2) Cleaned the image and the task it contained (to pick up some
>> changes on rebuild) and deleted the image files (.hddimg, etc.) in
>> tmp/deploy/images making sure to leave the kernel files intact.
>
> Did you cleansstate it? I find that without cleaning the state kernel
> image gets always pulled out of sstate rather than properly rebuilt.
>
> Tomas
Do you still experience this on the master branch?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: I think my kernel image just went back in time...
2013-01-07 16:26 ` Darren Hart
@ 2013-01-10 8:12 ` Chris Tapp
0 siblings, 0 replies; 5+ messages in thread
From: Chris Tapp @ 2013-01-10 8:12 UTC (permalink / raw)
To: Darren Hart; +Cc: yocto
On 7 Jan 2013, at 16:26, Darren Hart wrote:
>
>
> On 12/21/2012 10:17 AM, Tomas Frydrych wrote:
>> On 09/12/12 23:17, Chris Tapp wrote:
>>> In tmp/deploy/images:
>>>
>>> 1) bzImage had a timestamp of 2012-12-09 21:49 and the file ended
>>> -20121209214459.bin
>>>
>>> 2) Cleaned the image and the task it contained (to pick up some
>>> changes on rebuild) and deleted the image files (.hddimg, etc.) in
>>> tmp/deploy/images making sure to leave the kernel files intact.
>>
>> Did you cleansstate it? I find that without cleaning the state kernel
>> image gets always pulled out of sstate rather than properly rebuilt.
It was a while back now and I can't recall for sure. I'm 99.9% certain I used -c cleanall on the image.
>> Tomas
>
> Do you still experience this on the master branch?
I've not had a chance to try and I can't remember the exact steps to reproduce it. I've only seen this happen once for the same work-flow.
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Technical Lead - Linux Kernel
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
Chris Tapp
opensource@keylevel.com
www.keylevel.com
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-01-10 8:12 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-12-09 23:17 I think my kernel image just went back in time Chris Tapp
2012-12-21 17:30 ` McClintock Matthew-B29882
2012-12-21 18:17 ` Tomas Frydrych
2013-01-07 16:26 ` Darren Hart
2013-01-10 8:12 ` Chris Tapp
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.