Re: Execution of Build Output Failing (Testing)

Re: Execution of Build Output Failing (Testing)

[openembedded]

Yep, this makes complete sense - but I haven't tried to change versions (at least not on purpose ... :-)). Rather, these are what seem to happen by default. Let me look at the config files a bit more, to see if I can force this (or if you know, but all means yell about what I'm missing!).
BTW, on the PREFERRED_VERSION items below - likely a dumb question, but how is someone to know about this?
Thanks!
... Russell



On Fri, Aug 27, 2010 03:16  PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Fri, Aug 27, 2010 at 12:37 PM,  <openembedded@rkmorris.us> wrote:
> > Hi,
> > Thanks for the quick response!
> > What's strange is that watching the boot in QEMU it seems to be looking for 2.6.17-rc3 inside the /lib/modules directory ... but if I mount my initrd (un-gzip, then mount as ext2), and look inside this directory - the directory is 2.6.34 instead! Somewhere / somehow there seems to be a versioning issue perhaps?
> > Thoughts?
> 
> yes because the default kernel for qemuarm machine is 2.6.34 and hence
> the modules which are part of rfs are for that kernel.
> you should use same kernel to boot qemu for best results.
> 
> > Thanks again,... Russell
> >
> >
> > On Fri, Aug 27, 2010 12:41  PM, Khem Raj <raj.khem@gmail.com> wrote:
> >> On Fri, Aug 27, 2010 at 6:46 AM,  <openembedded@rkmorris.us> wrote:
> >> > Hi,
> >> > As I reported recently, I am having issues getting my OE output up and running on my h1940 device. It seems to be some sort of issue between the kernel and initrd files, so to debug this I figured that I'd build and test on QEMU (hoping that the recent udev related issues were my problem, and to make sure that I could build "properly").
> >> > Given this, I went ahead and built console-image (angstrom 2008.1 distro) for qemuarm, to see if it was perhaps just me having issues (which is still possible). However, I took the output from the qemuarm build and tried to run it ... and still have issues (not the same as my h1940, but still fatal).
> >> > On QEMU (verified to work with the QEMU provide example ARM images) I am able to boot, at least part way, but end up with a FATAL message about a missing directory ... /lib/modules/2.6.17-rc3.
> >> > Is this a known issue? Any proposed fixes or workarounds for this?
> >>
> >> oe.dev works well on qemuarm here with
> >>
> >> PREFERRED_VERSION_usbutils_local                = "0.86"
> >> PREFERRED_VERSION_udev_local                    = "151"
> >>
> >> in local.conf and minimal/angstrom distro last time I tried it booted
> >> fine. you can also adapt
> >> contrib/qemu/run-qemu.sh to run OE in qemu.
> >>
> >> > Thanks!
> >> > ... Russell
> >> > _______________________________________________
> >> > Openembedded-devel mailing list
> >> > Openembedded-devel@lists.openembedded.org
> >> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >> >
> >>
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel@lists.openembedded.org
> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >>
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
From openembedded@rkmorris.us Fri Aug 27 23:34:04 2010
Received: from vms173017pub.verizon.net ([206.46.173.17])
	by linuxtogo.org with esmtp (Exim 4.69)
	(envelope-from <openembedded@rkmorris.us>) id 1Op6Yj-0002FI-DW
	for openembedded-devel@lists.openembedded.org;
	Fri, 27 Aug 2010 23:34:04 +0200
Received: from server ([unknown] [71.170.86.183]) by vms173017.mailsrvcs.net
	(Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16
	2009)) with ESMTPA id <0L7T006MBYJJ0V30@vms173017.mailsrvcs.net> for
	openembedded-devel@lists.openembedded.org; Fri,
	27 Aug 2010 16:33:24 -0500 (CDT)
Received: from server [127.0.0.1] by server (Axigen)
	with ESMTPSA id 1AF6F8; Fri, 27 Aug 2010 16:33:18 -0500
Received: from [192.168.1.4] by rkmorris.us with HTTP; Fri,
	27 Aug 2010 16:33:16 -0500
From: <openembedded@rkmorris.us>
Date: Fri, 27 Aug 2010 16:33:16 -0500
X-Mailer: Axigen WebMail
To: openembedded-devel@lists.openembedded.org
Message-id: <1282944796856928500@rkmorris.us>
In-reply-to: <1282944432199625500@rkmorris.us>
References: <1282940782400087500@rkmorris.us> <1282944432199625500@rkmorris.us>
Importance: Normal
MIME-version: 1.0
X-AxigenVirus-Level: 1
X-AxigenSpam-Level: 4
X-SA-Exim-Connect-IP: 206.46.173.17
X-SA-Exim-Mail-From: openembedded@rkmorris.us
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on discovery
X-Spam-Level:
X-Spam-Status: No, score

Re: Execution of Build Output Failing (Testing)

[openembedded]

OK, I checked - and my kernel file actually has 2.6.34 in it's name, so it seems right. 
Hmmm ... where the heck is 2.6.17-rc3 coming from?
... Russell


On Fri, Aug 27, 2010 03:26  PM, <openembedded@rkmorris.us> wrote:
> Yep, this makes complete sense - but I haven't tried to change versions (at least not on purpose ... :-)). Rather, these are what seem to happen by default. Let me look at the config files a bit more, to see if I can force this (or if you know, but all means yell about what I'm missing!).
> BTW, on the PREFERRED_VERSION items below - likely a dumb question, but how is someone to know about this?
> Thanks!
> ... Russell
> 
> 
> 
> On Fri, Aug 27, 2010 03:16  PM, Khem Raj <raj.khem@gmail.com> wrote:
> > On Fri, Aug 27, 2010 at 12:37 PM,  <openembedded@rkmorris.us> wrote:
> > Hi,
> > Thanks for the quick response!
> > What's strange is that watching the boot in QEMU it seems to be looking for 2.6.17-rc3 inside the /lib/modules directory ... but if I mount my initrd (un-gzip, then mount as ext2), and look inside this directory - the directory is 2.6.34 instead! Somewhere / somehow there seems to be a versioning issue perhaps?
> > Thoughts?
> 
> yes because the default kernel for qemuarm machine is 2.6.34 and hence
> the modules which are part of rfs are for that kernel.
> you should use same kernel to boot qemu for best results.
> 
> > Thanks again,... Russell
> >
> >
> > On Fri, Aug 27, 2010 12:41  PM, Khem Raj <raj.khem@gmail.com> wrote:
> >> On Fri, Aug 27, 2010 at 6:46 AM,  <openembedded@rkmorris.us> wrote:
> >> > Hi,
> >> > As I reported recently, I am having issues getting my OE output up and running on my h1940 device. It seems to be some sort of issue between the kernel and initrd files, so to debug this I figured that I'd build and test on QEMU (hoping that the recent udev related issues were my problem, and to make sure that I could build "properly").
> >> > Given this, I went ahead and built console-image (angstrom 2008.1 distro) for qemuarm, to see if it was perhaps just me having issues (which is still possible). However, I took the output from the qemuarm build and tried to run it ... and still have issues (not the same as my h1940, but still fatal).
> >> > On QEMU (verified to work with the QEMU provide example ARM images) I am able to boot, at least part way, but end up with a FATAL message about a missing directory ... /lib/modules/2.6.17-rc3.
> >> > Is this a known issue? Any proposed fixes or workarounds for this?
> >>
> >> oe.dev works well on qemuarm here with
> >>
> >> PREFERRED_VERSION_usbutils_local                = "0.86"
> >> PREFERRED_VERSION_udev_local                    = "151"
> >>
> >> in local.conf and minimal/angstrom distro last time I tried it booted
> >> fine. you can also adapt
> >> contrib/qemu/run-qemu.sh to run OE in qemu.
> >>
> >> > Thanks!
> >> > ... Russell
> >> > _______________________________________________
> >> > Openembedded-devel mailing list
> >> > Openembedded-devel@lists.openembedded.org
> >> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >> >
> >>
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel@lists.openembedded.org
> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >>
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
From GNUtoo@no-log.org Sat Aug 28 00:41:23 2010
Received: from webmail.no-log.org ([80.67.172.39])
	by linuxtogo.org with esmtp (Exim 4.69)
	(envelope-from <GNUtoo@no-log.org>) id 1Op7bv-0000qs-2y
	for openembedded-devel@lists.openembedded.org;
	Sat, 28 Aug 2010 00:41:23 +0200
Received: by webmail.no-log.org (Postfix, from userid 33)
	id 229114BE1B; Sat, 28 Aug 2010 00:33:10 +0200 (CEST)
X-Squirrel-UserHash: c3wyGAAN
X-Squirrel-FromHash: AVNSWFZQUHkMessage-ID: <dd79678279f18baf8ab00a450671a8dc.squirrel@webmail.no-log.org>
Date: Sat, 28 Aug 2010 00:33:10 +0200 (CEST)
From: "Denis 'GNUtoo' Carikli" <GNUtoo@no-log.org>
To: openembedded-devel@lists.openembedded.org
User-Agent: SquirrelMail/1.4.15
MIME-Version: 1.0
Content-Type: text/plain;charset

Re: Execution of Build Output Failing (Testing)

[Martin Jansa]

On Fri, Aug 27, 2010 at 04:33:16PM -0500, openembedded@rkmorris.us wrote:
> Hi,
> 
>  
> 
> I am running a build with Angstrom, and I receive the following error messages - is this expected (and is there a fix for this?)?
> 
>  
> 
> NOTE: Handling BitBake files: \ (0754/7160) [10 %]NOTE: Angstrom DOES NOT support bluez-libs because bluez-libs 3.x has been replaced by bluez4
> NOTE: Handling BitBake files: \ (0960/7160) [13 %]NOTE: Angstrom DOES NOT support bluez-utils because bluez-utils 3.x has been replaced by bluez4
> NOTE: Handling BitBake files: \ (0970/7160) [13 %]NOTE: Angstrom DOES NOT support ipkg because ipkg has been superseded by opkg
> NOTE: Handling BitBake files: | (1191/7160) [16 %]NOTE: Angstrom DOES NOT support libiconv because the glibc builtin iconv replacement is used
> NOTE: Handling BitBake files: \ (1404/7160) [19 %]NOTE: Angstrom DOES NOT support libiconv because the glibc builtin iconv replacement is used
> NOTE: Handling BitBake files: | (4881/7160) [68 %]NOTE: Angstrom DOES NOT support bluez-utils because bluez-utils 3.x has been replaced by bluez4
> NOTE: Handling BitBake files: | (5731/7160) [80 %]NOTE: Angstrom DOES NOT support bluez-libs because bluez-libs 3.x has been replaced by bluez4
> NOTE: Handling BitBake files: \ (5964/7160) [83 %]NOTE: Angstrom DOES NOT support libiconv because the glibc builtin iconv replacement is used
> NOTE: Handling BitBake files: - (6038/7160) [84 %]NOTE: Angstrom DOES NOT support fso-apm because regular apmd is good enough
> NOTE: Handling BitBake files: - (6508/7160) [90 %]NOTE: Angstrom DOES NOT support bluez-libs because bluez-libs 3.x has been replaced by bluez4
> NOTE: Handling BitBake files: \ (7160/7160) [100 %]

Those are not error messages, just note that some packages are
blacklisted, see ie: 
ANGSTROM_BLACKLIST_pn-bluez-libs = "bluez-libs 3.x has been replaced by bluez4"
etc in distro configs like conf/distro/angstrom-2010.x.conf

So it's expected.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

Re: Execution of Build Output Failing (Testing)

[openembedded]

Hi,
It's all working now - thanks! I refreshed the source (via git), and did a complete new rebuild - and now it works.
Now back to my h1940. If anyone has any debugging suggestions I would definitely appreciate it. Unfortunately it seems to just hang, with no real debugging information (when "transferring" from the kernel to initrd, each of which has been confirmed on it's own). Of course I don't have a keyboard either, so it's even more fun ... :-(.
Thanks again,... Russell


On Fri, Aug 27, 2010 04:27  PM, <openembedded@rkmorris.us> wrote:
> OK, I checked - and my kernel file actually has 2.6.34 in it's name, so it seems right. 
> Hmmm ... where the heck is 2.6.17-rc3 coming from?
> ... Russell
> 
> 
> On Fri, Aug 27, 2010 03:26  PM, <openembedded@rkmorris.us> wrote:
> > Yep, this makes complete sense - but I haven't tried to change versions (at least not on purpose ... :-)). Rather, these are what seem to happen by default. Let me look at the config files a bit more, to see if I can force this (or if you know, but all means yell about what I'm missing!).
> > BTW, on the PREFERRED_VERSION items below - likely a dumb question, but how is someone to know about this?
> > Thanks!
> > ... Russell
> > 
> > 
> > 
> > On Fri, Aug 27, 2010 03:16  PM, Khem Raj <raj.khem@gmail.com> wrote:
> > > On Fri, Aug 27, 2010 at 12:37 PM,  <openembedded@rkmorris.us> wrote:
> > > Hi,
> > > Thanks for the quick response!
> > > What's strange is that watching the boot in QEMU it seems to be looking for 2.6.17-rc3 inside the /lib/modules directory ... but if I mount my initrd (un-gzip, then mount as ext2), and look inside this directory - the directory is 2.6.34 instead! Somewhere / somehow there seems to be a versioning issue perhaps?
> > > Thoughts?
> > 
> > yes because the default kernel for qemuarm machine is 2.6.34 and hence
> > the modules which are part of rfs are for that kernel.
> > you should use same kernel to boot qemu for best results.
> > 
> > > Thanks again,... Russell
> > >
> > >
> > > On Fri, Aug 27, 2010 12:41  PM, Khem Raj <raj.khem@gmail.com> wrote:
> > >> On Fri, Aug 27, 2010 at 6:46 AM,  <openembedded@rkmorris.us> wrote:
> > >> > Hi,
> > >> > As I reported recently, I am having issues getting my OE output up and running on my h1940 device. It seems to be some sort of issue between the kernel and initrd files, so to debug this I figured that I'd build and test on QEMU (hoping that the recent udev related issues were my problem, and to make sure that I could build "properly").
> > >> > Given this, I went ahead and built console-image (angstrom 2008.1 distro) for qemuarm, to see if it was perhaps just me having issues (which is still possible). However, I took the output from the qemuarm build and tried to run it ... and still have issues (not the same as my h1940, but still fatal).
> > >> > On QEMU (verified to work with the QEMU provide example ARM images) I am able to boot, at least part way, but end up with a FATAL message about a missing directory ... /lib/modules/2.6.17-rc3.
> > >> > Is this a known issue? Any proposed fixes or workarounds for this?
> > >>
> > >> oe.dev works well on qemuarm here with
> > >>
> > >> PREFERRED_VERSION_usbutils_local                = "0.86"
> > >> PREFERRED_VERSION_udev_local                    = "151"
> > >>
> > >> in local.conf and minimal/angstrom distro last time I tried it booted
> > >> fine. you can also adapt
> > >> contrib/qemu/run-qemu.sh to run OE in qemu.
> > >>
> > >> > Thanks!
> > >> > ... Russell
> > >> > _______________________________________________
> > >> > Openembedded-devel mailing list
> > >> > Openembedded-devel@lists.openembedded.org
> > >> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > >> >
> > >>
> > >> _______________________________________________
> > >> Openembedded-devel mailing list
> > >> Openembedded-devel@lists.openembedded.org
> > >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > >>
> > > _______________________________________________
> > > Openembedded-devel mailing list
> > > Openembedded-devel@lists.openembedded.org
> > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > >
> > 
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
From kergoth@gmail.com Sat Aug 28 16:44:47 2010
Received: from mail-ww0-f43.google.com ([74.125.82.43])
	by linuxtogo.org with esmtp (Exim 4.69)
	(envelope-from <kergoth@gmail.com>) id 1OpMeB-0000r9-0x
	for openembedded-devel@lists.openembedded.org;
	Sat, 28 Aug 2010 16:44:47 +0200
Received: by wwb31 with SMTP id 31so4502677wwb.24
	for <openembedded-devel@lists.openembedded.org>;
	Sat, 28 Aug 2010 07:44:13 -0700 (PDT)
DKIM-Signature: v

Re: Execution of Build Output Failing (Testing)

[openembedded]

Hi,
OK, unfortunately I've exhausted all my thoughts on getting my h1940 up and running - it still fails ... actually, stops, after a console output noting that it has found the compressed RAMDISK image at block 0. After that no more console output ... but it's not completely hung, as I do get a console message about the Ethernet gadget when plugging in the USB.
A admit though, I'm not sure what to try next - as I have no console output after the RAMDISK message, have no keyboard (it's a touchscreen device), no logs (using a ramdisk or SD paritition), and I can't connect to the USB ethernet interface even though I do get a message about it (but can't ping it).
Any debugging suggestions would be greatly appreciated!!!
Thanks,... Russell


On Sat, Aug 28, 2010 08:42  AM, <openembedded@rkmorris.us> wrote:
> Hi,
> It's all working now - thanks! I refreshed the source (via git), and did a complete new rebuild - and now it works.
> Now back to my h1940. If anyone has any debugging suggestions I would definitely appreciate it. Unfortunately it seems to just hang, with no real debugging information (when "transferring" from the kernel to initrd, each of which has been confirmed on it's own). Of course I don't have a keyboard either, so it's even more fun ... :-(.
> Thanks again,... Russell
> 
> 
> On Fri, Aug 27, 2010 04:27  PM, <openembedded@rkmorris.us> wrote:
> > OK, I checked - and my kernel file actually has 2.6.34 in it's name, so it seems right. 
> > Hmmm ... where the heck is 2.6.17-rc3 coming from?
> > ... Russell
> > 
> > 
> > On Fri, Aug 27, 2010 03:26  PM, <openembedded@rkmorris.us> wrote:
> > > Yep, this makes complete sense - but I haven't tried to change versions (at least not on purpose ... :-)). Rather, these are what seem to happen by default. Let me look at the config files a bit more, to see if I can force this (or if you know, but all means yell about what I'm missing!).
> > > BTW, on the PREFERRED_VERSION items below - likely a dumb question, but how is someone to know about this?
> > > Thanks!
> > > ... Russell
> > > 
> > > 
> > > 
> > > On Fri, Aug 27, 2010 03:16  PM, Khem Raj <raj.khem@gmail.com> wrote:
> > > > On Fri, Aug 27, 2010 at 12:37 PM,  <openembedded@rkmorris.us> wrote:
> > > > Hi,
> > > > Thanks for the quick response!
> > > > What's strange is that watching the boot in QEMU it seems to be looking for 2.6.17-rc3 inside the /lib/modules directory ... but if I mount my initrd (un-gzip, then mount as ext2), and look inside this directory - the directory is 2.6.34 instead! Somewhere / somehow there seems to be a versioning issue perhaps?
> > > > Thoughts?
> > > 
> > > yes because the default kernel for qemuarm machine is 2.6.34 and hence
> > > the modules which are part of rfs are for that kernel.
> > > you should use same kernel to boot qemu for best results.
> > > 
> > > > Thanks again,... Russell
> > > >
> > > >
> > > > On Fri, Aug 27, 2010 12:41  PM, Khem Raj <raj.khem@gmail.com> wrote:
> > > >> On Fri, Aug 27, 2010 at 6:46 AM,  <openembedded@rkmorris.us> wrote:
> > > >> > Hi,
> > > >> > As I reported recently, I am having issues getting my OE output up and running on my h1940 device. It seems to be some sort of issue between the kernel and initrd files, so to debug this I figured that I'd build and test on QEMU (hoping that the recent udev related issues were my problem, and to make sure that I could build "properly").
> > > >> > Given this, I went ahead and built console-image (angstrom 2008.1 distro) for qemuarm, to see if it was perhaps just me having issues (which is still possible). However, I took the output from the qemuarm build and tried to run it ... and still have issues (not the same as my h1940, but still fatal).
> > > >> > On QEMU (verified to work with the QEMU provide example ARM images) I am able to boot, at least part way, but end up with a FATAL message about a missing directory ... /lib/modules/2.6.17-rc3.
> > > >> > Is this a known issue? Any proposed fixes or workarounds for this?
> > > >>
> > > >> oe.dev works well on qemuarm here with
> > > >>
> > > >> PREFERRED_VERSION_usbutils_local                = "0.86"
> > > >> PREFERRED_VERSION_udev_local                    = "151"
> > > >>
> > > >> in local.conf and minimal/angstrom distro last time I tried it booted
> > > >> fine. you can also adapt
> > > >> contrib/qemu/run-qemu.sh to run OE in qemu.
> > > >>
> > > >> > Thanks!
> > > >> > ... Russell
> > > >> > _______________________________________________
> > > >> > Openembedded-devel mailing list
> > > >> > Openembedded-devel@lists.openembedded.org
> > > >> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > > >> >
> > > >>
> > > >> _______________________________________________
> > > >> Openembedded-devel mailing list
> > > >> Openembedded-devel@lists.openembedded.org
> > > >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > > >>
> > > > _______________________________________________
> > > > Openembedded-devel mailing list
> > > > Openembedded-devel@lists.openembedded.org
> > > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > > >
> > > 
> > > _______________________________________________
> > > Openembedded-devel mailing list
> > > Openembedded-devel@lists.openembedded.org
> > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > > 
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> > 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
From enrico.scholz@sigma-chemnitz.de Sun Aug 29 16:00:29 2010
Received: from mail.cvg.de ([62.153.82.30])
	by linuxtogo.org with esmtp (Exim 4.69)
	(envelope-from <enrico.scholz@sigma-chemnitz.de>) id 1OpiQu-0007Ji-BC
	for openembedded-devel@lists.openembedded.org;
	Sun, 29 Aug 2010 16:00:29 +0200
Received: from ensc-virt.intern.sigma-chemnitz.de
	(ensc-virt.intern.sigma-chemnitz.de [192.168.3.24])
	by mail.cvg.de (8.14.4/8.14.4) with ESMTP id o7TDxuqq026194
	(version

[RFC] review process

[Frans Meulenbroeks]

It is a good rule that important changes (toolchain, infrastructure)
are reviewed before being committed.
This is e.g. also specified in
http://wiki.openembedded.net/index.php/Commit_Policy

However, recently I've seen some issues that our review process does
not seem to work or is abused.

I see two things happening.
- patches are submitted for review but do not gain any feedback in a
reasonable time. I have several patches in the queue that did not get
any feedback.
- people are abusing their powers by rejecting changes without
motivation. See e.g [1] and [2]. I feel if you reject a patch you have
an obligation to explain why you rejected it.

Seems our review process is flawed.
I propose to introduce the following rules.

1. If a patch does not get any review feedback in X weeks time; it is
ok to apply it. People who need more time to review a patch can
mention that in a short reply. In that case they are granted Y more
weeks to review.
(suggestion: X = Y = 2)
2. If someone NAKs a patch it is obligatory to provide an explanation
why the patch is not good.
Rationale is that
a) people can fix the problem seen by the reviewer
b) people learn from it
c) if there is a disagreement it can be discussed (and if needed
raised to the TSC)
3) NAKs that are not motivated/explained can be ignored as not given.

Your feedback, suggestions, additions, amendments, whatever is appreciated.

Frans

[1] http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-August/023374.html
[2] http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-August/023270.html

Execution of Build Output Failing (Testing)

[openembedded]

Hi,
As I reported recently, I am having issues getting my OE output up and running on my h1940 device. It seems to be some sort of issue between the kernel and initrd files, so to debug this I figured that I'd build and test on QEMU (hoping that the recent udev related issues were my problem, and to make sure that I could build "properly").
Given this, I went ahead and built console-image (angstrom 2008.1 distro) for qemuarm, to see if it was perhaps just me having issues (which is still possible). However, I took the output from the qemuarm build and tried to run it ... and still have issues (not the same as my h1940, but still fatal).
On QEMU (verified to work with the QEMU provide example ARM images) I am able to boot, at least part way, but end up with a FATAL message about a missing directory ... /lib/modules/2.6.17-rc3.
Is this a known issue? Any proposed fixes or workarounds for this?
Thanks!
... Russell

Re: Execution of Build Output Failing (Testing)

[Khem Raj]

On Fri, Aug 27, 2010 at 6:46 AM,  <openembedded@rkmorris.us> wrote:
> Hi,
> As I reported recently, I am having issues getting my OE output up and running on my h1940 device. It seems to be some sort of issue between the kernel and initrd files, so to debug this I figured that I'd build and test on QEMU (hoping that the recent udev related issues were my problem, and to make sure that I could build "properly").
> Given this, I went ahead and built console-image (angstrom 2008.1 distro) for qemuarm, to see if it was perhaps just me having issues (which is still possible). However, I took the output from the qemuarm build and tried to run it ... and still have issues (not the same as my h1940, but still fatal).
> On QEMU (verified to work with the QEMU provide example ARM images) I am able to boot, at least part way, but end up with a FATAL message about a missing directory ... /lib/modules/2.6.17-rc3.
> Is this a known issue? Any proposed fixes or workarounds for this?

oe.dev works well on qemuarm here with

PREFERRED_VERSION_usbutils_local                = "0.86"
PREFERRED_VERSION_udev_local                    = "151"

in local.conf and minimal/angstrom distro last time I tried it booted
fine. you can also adapt
contrib/qemu/run-qemu.sh to run OE in qemu.

> Thanks!
> ... Russell
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: Execution of Build Output Failing (Testing)

[openembedded]

Hi,
Thanks for the quick response!
What's strange is that watching the boot in QEMU it seems to be looking for 2.6.17-rc3 inside the /lib/modules directory ... but if I mount my initrd (un-gzip, then mount as ext2), and look inside this directory - the directory is 2.6.34 instead! Somewhere / somehow there seems to be a versioning issue perhaps?
Thoughts?
Thanks again,... Russell


On Fri, Aug 27, 2010 12:41  PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Fri, Aug 27, 2010 at 6:46 AM,  <openembedded@rkmorris.us> wrote:
> > Hi,
> > As I reported recently, I am having issues getting my OE output up and running on my h1940 device. It seems to be some sort of issue between the kernel and initrd files, so to debug this I figured that I'd build and test on QEMU (hoping that the recent udev related issues were my problem, and to make sure that I could build "properly").
> > Given this, I went ahead and built console-image (angstrom 2008.1 distro) for qemuarm, to see if it was perhaps just me having issues (which is still possible). However, I took the output from the qemuarm build and tried to run it ... and still have issues (not the same as my h1940, but still fatal).
> > On QEMU (verified to work with the QEMU provide example ARM images) I am able to boot, at least part way, but end up with a FATAL message about a missing directory ... /lib/modules/2.6.17-rc3.
> > Is this a known issue? Any proposed fixes or workarounds for this?
> 
> oe.dev works well on qemuarm here with
> 
> PREFERRED_VERSION_usbutils_local                = "0.86"
> PREFERRED_VERSION_udev_local                    = "151"
> 
> in local.conf and minimal/angstrom distro last time I tried it booted
> fine. you can also adapt
> contrib/qemu/run-qemu.sh to run OE in qemu.
> 
> > Thanks!
> > ... Russell
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
From raj.khem@gmail.com Fri Aug 27 22:17:59 2010
Received: from mail-iw0-f175.google.com ([209.85.214.175])
	by linuxtogo.org with esmtp (Exim 4.69)
	(envelope-from <raj.khem@gmail.com>) id 1Op5MY-000859-3Y
	for openembedded-devel@lists.openembedded.org;
	Fri, 27 Aug 2010 22:17:50 +0200
Received: by iwn2 with SMTP id 2so2795409iwn.6
	for <openembedded-devel@lists.openembedded.org>;
	Fri, 27 Aug 2010 13:16:54 -0700 (PDT)
DKIM-Signature: v