From: Pintu Kumar <pintu.ping@gmail.com> To: Damian Tometzki <damian.tometzki@icloud.com> Cc: Valdis Kletnieks <valdis.kletnieks@vt.edu>, linux-kernel@vger.kernel.org, kernelnewbies@kernelnewbies.org Subject: Re: How to verify linux-next Date: Fri, 29 Sep 2017 23:23:31 +0530 [thread overview] Message-ID: <CAOuPNLjECO0ETryR3PmPiTVsU4NU7DvwdG-XD9+kTychUTLULw@mail.gmail.com> (raw) In-Reply-To: <CAOuPNLj_TXmULGXOEg0iMy_77u4OoLuU4Nx6xxRpOEk8prc9dQ@mail.gmail.com> On Fri, Sep 29, 2017 at 7:56 PM, Pintu Kumar <pintu.ping@gmail.com> wrote: > On Fri, Sep 29, 2017 at 6:44 PM, Damian Tometzki > <damian.tometzki@icloud.com> 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
WARNING: multiple messages have this Message-ID (diff)
From: pintu.ping@gmail.com (Pintu Kumar) To: kernelnewbies@lists.kernelnewbies.org Subject: How to verify linux-next Date: Fri, 29 Sep 2017 23:23:31 +0530 [thread overview] Message-ID: <CAOuPNLjECO0ETryR3PmPiTVsU4NU7DvwdG-XD9+kTychUTLULw@mail.gmail.com> (raw) In-Reply-To: <CAOuPNLj_TXmULGXOEg0iMy_77u4OoLuU4Nx6xxRpOEk8prc9dQ@mail.gmail.com> On Fri, Sep 29, 2017 at 7:56 PM, Pintu Kumar <pintu.ping@gmail.com> wrote: > On Fri, Sep 29, 2017 at 6:44 PM, Damian Tometzki > <damian.tometzki@icloud.com> 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 at 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
next prev parent reply other threads:[~2017-09-29 17:53 UTC|newest] Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-29 9:42 How to verify linux-next Pintu Kumar 2017-09-29 9:46 ` Pintu Kumar 2017-09-29 9:46 ` Pintu Kumar 2017-09-29 10:38 ` Pintu Kumar 2017-09-29 10:38 ` Pintu Kumar 2017-09-29 12:41 ` valdis.kletnieks 2017-09-29 12:41 ` valdis.kletnieks at vt.edu 2017-09-29 13:05 ` Damian Tometzki 2017-09-29 13:05 ` Damian Tometzki 2017-09-29 13:14 ` Damian Tometzki 2017-09-29 13:14 ` Damian Tometzki 2017-09-29 14:26 ` Pintu Kumar 2017-09-29 14:26 ` Pintu Kumar 2017-09-29 15:45 ` valdis.kletnieks 2017-09-29 15:45 ` valdis.kletnieks at vt.edu 2017-10-02 8:11 ` Kamil Konieczny 2017-10-02 8:11 ` Kamil Konieczny 2017-10-02 11:04 ` valdis.kletnieks 2017-10-02 11:04 ` valdis.kletnieks at vt.edu 2017-09-29 17:53 ` Pintu Kumar [this message] 2017-09-29 17:53 ` Pintu Kumar 2017-09-29 21:50 ` Theodore Ts'o 2017-09-29 21:50 ` Theodore Ts'o 2017-09-30 3:58 ` Pintu Kumar 2017-09-30 3:58 ` Pintu Kumar 2017-09-30 5:25 ` Theodore Ts'o 2017-09-30 5:25 ` Theodore Ts'o 2017-10-01 16:28 ` Pintu Kumar 2017-10-01 16:28 ` Pintu Kumar 2017-10-01 16:44 ` Damian Tometzki 2017-10-01 16:44 ` Damian Tometzki 2017-10-01 16:48 ` Randy Dunlap 2017-10-01 16:48 ` Randy Dunlap 2017-10-01 17:03 ` Mike Galbraith 2017-10-01 17:03 ` Mike Galbraith 2017-10-01 18:47 ` Pintu Kumar 2017-10-01 18:47 ` Pintu Kumar 2017-10-01 16:47 ` Theodore Ts'o 2017-10-01 16:47 ` Theodore Ts'o
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAOuPNLjECO0ETryR3PmPiTVsU4NU7DvwdG-XD9+kTychUTLULw@mail.gmail.com \ --to=pintu.ping@gmail.com \ --cc=damian.tometzki@icloud.com \ --cc=kernelnewbies@kernelnewbies.org \ --cc=linux-kernel@vger.kernel.org \ --cc=valdis.kletnieks@vt.edu \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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.