* Re: QemuARM Boot Failure
2011-01-17 7:53 QemuARM Boot Failure Saul Wold
@ 2011-01-17 8:46 ` Zhao Yi
2011-01-17 13:42 ` Bruce Ashfield
` (2 subsequent siblings)
3 siblings, 0 replies; 8+ messages in thread
From: Zhao Yi @ 2011-01-17 8:46 UTC (permalink / raw)
To: Saul Wold; +Cc: poky@yoctoproject.org
Hi Saul,
I tested the recent build images from the autobuilder.
The build images from both 2011011-1 and 20110112-1 can not boot. With
the build image from 20110110-1, it can boot.
于 2011年01月17日 15:53, Saul Wold 写道:
>
> Bruce,
>
> Did you test the latest systemtap update on ARM? I am just curious
> based on the current failure that we are having with qemuarm. If so,
> against what revision of master? This might help us narrow down the
> issue.
>
>
> I tried both the systemtap version and the older version and both
> failed. The last known good qemuarm was 2 weeks ago, there have been a
> number of kernel updates in that time along with a loads of userspace
> changes, but no qemu updates since the first of the year. I am not
> sure about the userspace changes yet, need to review them more deeply.
>
> I will be tied up tomorrow, but will try bisecting tomorrow evening if
> there is no update before then.
>
> Thanks
> Sau!
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: QemuARM Boot Failure
2011-01-17 7:53 QemuARM Boot Failure Saul Wold
2011-01-17 8:46 ` Zhao Yi
@ 2011-01-17 13:42 ` Bruce Ashfield
2011-01-17 15:13 ` Bruce Ashfield
2011-01-17 15:26 ` Tom Zanussi
2011-01-17 17:35 ` Bruce Ashfield
3 siblings, 1 reply; 8+ messages in thread
From: Bruce Ashfield @ 2011-01-17 13:42 UTC (permalink / raw)
To: Saul Wold; +Cc: poky@yoctoproject.org
On Mon, Jan 17, 2011 at 2:53 AM, Saul Wold <saul.wold@intel.com> wrote:
>
> Bruce,
>
> Did you test the latest systemtap update on ARM? I am just curious based on
> the current failure that we are having with qemuarm. If so, against what
> revision of master? This might help us narrow down the issue.
The systemtap updates are generic, just configuration items that wouldn't
trigger a boot error .. at least not in any normal stretch of the imagination.
I booted all arches when I updated to the full 2.6.37 release, which was about
a week ago. Nothing of significance has changed since then.
I'll do some builds and booting today and see what's up.
Bruce
>
>
> I tried both the systemtap version and the older version and both failed.
> The last known good qemuarm was 2 weeks ago, there have been a number of
> kernel updates in that time along with a loads of userspace changes, but no
> qemu updates since the first of the year. I am not sure about the userspace
> changes yet, need to review them more deeply.
>
> I will be tied up tomorrow, but will try bisecting tomorrow evening if there
> is no update before then.
>
> Thanks
> Sau!
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: QemuARM Boot Failure
2011-01-17 13:42 ` Bruce Ashfield
@ 2011-01-17 15:13 ` Bruce Ashfield
0 siblings, 0 replies; 8+ messages in thread
From: Bruce Ashfield @ 2011-01-17 15:13 UTC (permalink / raw)
To: Saul Wold; +Cc: poky@yoctoproject.org
On Mon, Jan 17, 2011 at 8:42 AM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Mon, Jan 17, 2011 at 2:53 AM, Saul Wold <saul.wold@intel.com> wrote:
>>
>> Bruce,
>>
>> Did you test the latest systemtap update on ARM? I am just curious based on
>> the current failure that we are having with qemuarm. If so, against what
>> revision of master? This might help us narrow down the issue.
>
> The systemtap updates are generic, just configuration items that wouldn't
> trigger a boot error .. at least not in any normal stretch of the imagination.
>
> I booted all arches when I updated to the full 2.6.37 release, which was about
> a week ago. Nothing of significance has changed since then.
>
> I'll do some builds and booting today and see what's up.
An update.
I've bisected to my last known good boot .. and it fails the same way
as the latest. I'll continue looking at the kernel, but this doesn't look
to be isolated to any kernel change in particular.
Bruce
>
> Bruce
>
>>
>>
>> I tried both the systemtap version and the older version and both failed.
>> The last known good qemuarm was 2 weeks ago, there have been a number of
>> kernel updates in that time along with a loads of userspace changes, but no
>> qemu updates since the first of the year. I am not sure about the userspace
>> changes yet, need to review them more deeply.
>>
>> I will be tied up tomorrow, but will try bisecting tomorrow evening if there
>> is no update before then.
>>
>> Thanks
>> Sau!
>>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: QemuARM Boot Failure
2011-01-17 7:53 QemuARM Boot Failure Saul Wold
2011-01-17 8:46 ` Zhao Yi
2011-01-17 13:42 ` Bruce Ashfield
@ 2011-01-17 15:26 ` Tom Zanussi
2011-01-17 15:33 ` Tom Zanussi
2011-01-17 17:35 ` Bruce Ashfield
3 siblings, 1 reply; 8+ messages in thread
From: Tom Zanussi @ 2011-01-17 15:26 UTC (permalink / raw)
To: Saul Wold; +Cc: poky@yoctoproject.org
On Sun, 2011-01-16 at 23:53 -0800, Saul Wold wrote:
> Bruce,
>
> Did you test the latest systemtap update on ARM? I am just curious
> based on the current failure that we are having with qemuarm. If so,
> against what revision of master? This might help us narrow down the issue.
>
Just one thing - at this point, systemtap doesn't need to be tested on
arm, since it didn't work and therefore isn't one of the compatible
machines.
That doesn't explain why qemuarm doesn't boot for - anything
systemtap-related would be orthogonal. I was able to boot it though,
only to find out that systemtap doesn't work on it...
Tom
>
> I tried both the systemtap version and the older version and both
> failed. The last known good qemuarm was 2 weeks ago, there have been a
> number of kernel updates in that time along with a loads of userspace
> changes, but no qemu updates since the first of the year. I am not sure
> about the userspace changes yet, need to review them more deeply.
>
> I will be tied up tomorrow, but will try bisecting tomorrow evening if
> there is no update before then.
>
> Thanks
> Sau!
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: QemuARM Boot Failure
2011-01-17 15:26 ` Tom Zanussi
@ 2011-01-17 15:33 ` Tom Zanussi
0 siblings, 0 replies; 8+ messages in thread
From: Tom Zanussi @ 2011-01-17 15:33 UTC (permalink / raw)
To: Wold, Saul; +Cc: poky@yoctoproject.org
On Mon, 2011-01-17 at 07:26 -0800, Tom Zanussi wrote:
> On Sun, 2011-01-16 at 23:53 -0800, Saul Wold wrote:
> > Bruce,
> >
> > Did you test the latest systemtap update on ARM? I am just curious
> > based on the current failure that we are having with qemuarm. If so,
> > against what revision of master? This might help us narrow down the issue.
> >
>
> Just one thing - at this point, systemtap doesn't need to be tested on
> arm, since it didn't work and therefore isn't one of the compatible
> machines.
>
> That doesn't explain why qemuarm doesn't boot for - anything
> systemtap-related would be orthogonal. I was able to boot it though,
> only to find out that systemtap doesn't work on it...
>
Actually, that's not true, got confused with something else - I never
got to the point of booting it, since it was a compile failure...
Tom
> Tom
>
> >
> > I tried both the systemtap version and the older version and both
> > failed. The last known good qemuarm was 2 weeks ago, there have been a
> > number of kernel updates in that time along with a loads of userspace
> > changes, but no qemu updates since the first of the year. I am not sure
> > about the userspace changes yet, need to review them more deeply.
> >
> > I will be tied up tomorrow, but will try bisecting tomorrow evening if
> > there is no update before then.
> >
> > Thanks
> > Sau!
> >
> > _______________________________________________
> > poky mailing list
> > poky@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/poky
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: QemuARM Boot Failure
2011-01-17 7:53 QemuARM Boot Failure Saul Wold
` (2 preceding siblings ...)
2011-01-17 15:26 ` Tom Zanussi
@ 2011-01-17 17:35 ` Bruce Ashfield
2011-01-17 21:41 ` Bruce Ashfield
3 siblings, 1 reply; 8+ messages in thread
From: Bruce Ashfield @ 2011-01-17 17:35 UTC (permalink / raw)
To: Saul Wold; +Cc: poky@yoctoproject.org
On Mon, Jan 17, 2011 at 2:53 AM, Saul Wold <saul.wold@intel.com> wrote:
>
> Bruce,
>
> Did you test the latest systemtap update on ARM? I am just curious based on
> the current failure that we are having with qemuarm. If so, against what
> revision of master? This might help us narrow down the issue.
>
>
> I tried both the systemtap version and the older version and both failed.
> The last known good qemuarm was 2 weeks ago, there have been a number of
> kernel updates in that time along with a loads of userspace changes, but no
> qemu updates since the first of the year. I am not sure about the userspace
> changes yet, need to review them more deeply.
Problem solved, there were some configuration values being
dropped. I'm putting together a fix now.
root@qemuarm:~# uname -a
Linux qemuarm 2.6.37-yocto-standard+ #2 PREEMPT Mon Jan 17 12:35:56
EST 2011 armv5tejl GNU/Linux
Cheers,
Bruce
>
> I will be tied up tomorrow, but will try bisecting tomorrow evening if there
> is no update before then.
>
> Thanks
> Sau!
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: QemuARM Boot Failure
2011-01-17 17:35 ` Bruce Ashfield
@ 2011-01-17 21:41 ` Bruce Ashfield
0 siblings, 0 replies; 8+ messages in thread
From: Bruce Ashfield @ 2011-01-17 21:41 UTC (permalink / raw)
To: Saul Wold; +Cc: poky@yoctoproject.org
On Mon, Jan 17, 2011 at 12:35 PM, Bruce Ashfield
<bruce.ashfield@gmail.com> wrote:
> On Mon, Jan 17, 2011 at 2:53 AM, Saul Wold <saul.wold@intel.com> wrote:
>>
>> Bruce,
>>
>> Did you test the latest systemtap update on ARM? I am just curious based on
>> the current failure that we are having with qemuarm. If so, against what
>> revision of master? This might help us narrow down the issue.
>>
>>
>> I tried both the systemtap version and the older version and both failed.
>> The last known good qemuarm was 2 weeks ago, there have been a number of
>> kernel updates in that time along with a loads of userspace changes, but no
>> qemu updates since the first of the year. I am not sure about the userspace
>> changes yet, need to review them more deeply.
>
> Problem solved, there were some configuration values being
> dropped. I'm putting together a fix now.
>
> root@qemuarm:~# uname -a
> Linux qemuarm 2.6.37-yocto-standard+ #2 PREEMPT Mon Jan 17 12:35:56
> EST 2011 armv5tejl GNU/Linux
pull request just sent.
Cheers,
Bruce
>
>
> Cheers,
>
> Bruce
>
>>
>> I will be tied up tomorrow, but will try bisecting tomorrow evening if there
>> is no update before then.
>>
>> Thanks
>> Sau!
>>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
^ permalink raw reply [flat|nested] 8+ messages in thread