From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752507AbdI2Rxe (ORCPT ); Fri, 29 Sep 2017 13:53:34 -0400 Received: from mail-lf0-f67.google.com ([209.85.215.67]:36543 "EHLO mail-lf0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752157AbdI2Rxd (ORCPT ); Fri, 29 Sep 2017 13:53:33 -0400 X-Google-Smtp-Source: AOwi7QC2sYxsJALgpm2e9qX292aCoQaQlS7gbA5OVpy7CK2Tb9EmzqCaZ3hBreOJvzpr1dYEEqILd5Dlk0VtDXQW/2Q= MIME-Version: 1.0 In-Reply-To: References: <159555.1506688878@turing-police.cc.vt.edu> <1506690885.1771.6.camel@icloud.com> From: Pintu Kumar Date: Fri, 29 Sep 2017 23:23:31 +0530 Message-ID: Subject: Re: How to verify linux-next To: Damian Tometzki Cc: Valdis Kletnieks , linux-kernel@vger.kernel.org, kernelnewbies@kernelnewbies.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by nfs id v8THrdxq008345 On Fri, Sep 29, 2017 at 7:56 PM, Pintu Kumar wrote: > On Fri, Sep 29, 2017 at 6:44 PM, Damian Tometzki > wrote: >> Hello, >> >> Ubuntu 16.04 with current linux-next Kernel workson virtualbox 5.1.28 >> >> Host: Windows 10 >> Guest: Ubuntu 16.04 >> >> Best regards >> Damian >> >> >> Am Freitag, den 29.09.2017, 08:41 -0400 schrieb >> valdis.kletnieks@vt.edu: >>> On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said: >>> >>> > >>> > I have a general question. >>> > How do we normally verify linux-next tree? >>> The same exact way you "verify" any other Linux kernel, for whatever >>> definition of "verify" you plan to use. >>> >>> > >>> > 1) For Oracle virtual box 5.1.26 with ubuntu-32 bit, the linux-next >>> > kernel is not booting. >>> Does an Ubuntu kernel boot correctly under VirtualBox? If not, fix >>> that issue first. Also, "is not booting" isn't detailed enough for >>> anybody >>> to make even a guess as to what's wrong. >>> >>> Also, note that 5.1.28 is out. > > Ok, I just updated to 5.1.28. And my Ubuntu version is already 16.04. > Let me try again if it works. > Thanks all for your reply. > Now, with vbox 5.1.28, I am getting below build failure with linux-next. Any quick pointers on this, if anybody faced similar issue. In file included from ./arch/x86/include/asm/atomic.h:7:0, from ./include/linux/atomic.h:4, from ./include/linux/mm_types_task.h:12, from ./include/linux/mm_types.h:4, from arch/x86/kvm/irq.h:25, from arch/x86/kvm/vmx.c:19: arch/x86/kvm/vmx.c: In function ‘__pi_post_block’: ./arch/x86/include/asm/cmpxchg.h:129:2: warning: ‘__ret’ is used uninitialized in this function [-Wuninitialized] __ret; \ ^ ./arch/x86/include/asm/cmpxchg.h:86:21: note: ‘__ret’ was declared here __typeof__(*(ptr)) __ret; \ ^ ./arch/x86/include/asm/cmpxchg.h:133:2: note: in expansion of macro ‘__raw_cmpxchg’ __raw_cmpxchg((ptr), (old), (new), (size), LOCK_PREFIX) ^ ./arch/x86/include/asm/cmpxchg.h:148:2: note: in expansion of macro ‘__cmpxchg’ __cmpxchg(ptr, old, new, sizeof(*(ptr))) ^ arch/x86/kvm/vmx.c:11732:11: note: in expansion of macro ‘cmpxchg’ } while (cmpxchg(&pi_desc->control, old.control, ^ CC kernel/trace/trace_seq.o CC kernel/trace/trace_stat.o In function ‘__pi_post_block’, inlined from ‘pi_post_block’ at arch/x86/kvm/vmx.c:11831:2, inlined from ‘vmx_post_block’ at arch/x86/kvm/vmx.c:11840:2: ./arch/x86/include/asm/cmpxchg.h:127:3: error: call to ‘__cmpxchg_wrong_size’ declared with attribute error: Bad argument size for cmpxchg __cmpxchg_wrong_size(); \ ^ > BTW, I am more interested in my another query about QEMU arm. > This will be much quicker and easy for me. > But the problem is I wanted to use multiple ssh shell on qemu. > Also I needed a pre-built rootfs image for qemu-arm, cortex-a9 > versatilepb machine. > It should have networking and ssh built-in so that I can connect to it > using PUTTY client. > Note that I could able to build my own minimal busybox and boot qemu > using linux-next (non graphical mode). > But I could able to get only one shell. > I need to test some client/server problem, so I need multiple shell. > I am not able to configure net/ssh on this qemu system. > > So, I have 2 things to ask: > 1) If you have pointers on how to setup ssh/net connection on QEMU > with busybox, do let me know. > 2) Let, please point me to a pre-built qemu-arm busy box image with > full features. > > > Thanks, > Pintu