From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-qa0-f54.google.com ([209.85.216.54]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SKEzF-0007zI-5A for openembedded-devel@lists.openembedded.org; Tue, 17 Apr 2012 22:26:53 +0200 Received: by qao25 with SMTP id 25so757336qao.6 for ; Tue, 17 Apr 2012 13:17:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=7Qpnq+tLngdVazpDyZmrBRUPExnoQ2SMpdAvf3cPGcI=; b=Jb7bnqjtIGHuMen1ipvnZ3TxVl3h5Kl3b2vnoE2gitKRKrhub9pSZME/zq4zlDrvsB DDwSkze+o9wAZxHNGPKU44IVWtG8NPG4aNn0vbXfkSKfxgGKuef6b1QV6nb6o4lRFsRK FDlcnVcQgb9nlL7zyQ9Y6I1knTiHWsrWO5hrtAqtmX35V1lVd97Ry6rlCmAsygc9TrMA Y0+Au/YV78KzofE8Puyq/BVNLInl5nl6ohjXn2hUfLfWMTBKtvJTUJa3G2BN5ft8W6eM jxZtcflB+SR1tf+Msm+5kBllhsxwp2H9x8GO519W9eahL8FGPQAaBP+JXpfiyPKe6Dum fCpQ== Received: by 10.224.196.131 with SMTP id eg3mr52070qab.63.1334693846112; Tue, 17 Apr 2012 13:17:26 -0700 (PDT) Received: from [192.168.1.3] (dpc674485156.direcpc.com. [67.44.85.156]) by mx.google.com with ESMTPS id gy7sm19779199qab.22.2012.04.17.13.17.18 (version=SSLv3 cipher=OTHER); Tue, 17 Apr 2012 13:17:25 -0700 (PDT) Message-ID: <4F8DCFC4.9010508@gmail.com> Date: Tue, 17 Apr 2012 13:17:08 -0700 From: j User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120406 Thunderbird/11.0.1 MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <4F88ACCE.1030202@gmail.com> <4F88ADA3.5030804@gmail.com> <4F8C9902.8020904@gmail.com> <4F8C9D26.9050500@mlbassoc.com> <4F8C9E68.9050106@gmail.com> <4F8CCAAA.6050406@gmail.com> <4F8D9245.3080908@mlbassoc.com> <4F8DBFF3.2060508@gmail.com> <4F8DC5B5.600@windriver.com> <4F8DC939.90208@gmail.com> In-Reply-To: <4F8DC939.90208@gmail.com> Subject: Re: [oe-core] ld segfault cant figure it out X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2012 20:26:53 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 04/17/2012 12:49 PM, j wrote: > On 04/17/2012 12:34 PM, Mark Hatle wrote: >> On 4/17/12 2:09 PM, j wrote: >>> On 04/17/2012 09:13 AM, J. L. wrote: >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> I went for a build on the borrowed machine again but this time I did >>> not >>> go into X just stayed in RL3. Then ran bitbake perl, on a clean build >>> dir. It is just about to finish building a few steps away but where I >>> normally get the segfaults, it has not spit those out. There are no QA >>> logs being generated either. So looks like it had/has something to do >>> with running X, both systems are running nvidia graphics cards. The >>> laptop has a new mobile one, borrowed an old one that is nouveau >>> compatible. So both open and closed nvidia drivers were tried. But >>> something when in the graphical environment is giving the segfault >>> issues I have been seeing. I have not yet verified if killing X on the >>> laptop builds and eliminates the issues as well. >>> >>> Will post back once I have built the kernel on both machines with no X >>> running. >> >> There is a known issue w/ nvidia drivers, segfaulting and QEMU. Is >> something in perl (or elsewhere) trying to run qemu to finish up a task? >> >> --Mark > Not that I can tell, but that does not mean it is not (still learning > things), but possible one of threads is working on something perl > related when it happens and I am not seeing it or realizing it. If you > are willing to post the commands I could run to check, I can post the > results. But when I do just a bitbake -c compile perl on a clean build > dir all I would see was the segfault in dmesg and the results in QA > log. Nothing would show up on the command line that was not in the QA > log, after doing each step one by one. > > But it must be related to this known issue with nvidia. Should be a > couple hours before both machines finish building the kernel and perl, > will post the results after. But looks promising for my laptop so far > as no segfaults yet. Borrowed machine is on to building the kernel now > and nothing posted yet. > > Thank you for your response very appreciated. I will also read more > about the issue you stated. > > From what I am reading about this is its related to libgl. But on the machine I borrowed I used nouveau driver's which uses the libgl that is expected not the nvidia's supplied version. So maybe that is not fully it. But still all seems related to being in an X environment for me when building. Which is at least easy to work around. Will post if it segfaults again on either machine once they are done.