Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Fri, 28 Apr 2017 15:34:06 +0200, Paolo Bonzini wrote: > > > > On 27/04/2017 02:42, Satoru Takeuchi wrote: > > At Wed, 26 Apr 2017 18:58:27 +0200, > >> On 26/04/2017 13:47, Satoru Takeuchi wrote: > >>> OK, here it is. > >> > >> It looks like the cause is that AMD has removed TBM instructions

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Fri, 28 Apr 2017 15:34:06 +0200, Paolo Bonzini wrote: > > > > On 27/04/2017 02:42, Satoru Takeuchi wrote: > > At Wed, 26 Apr 2017 18:58:27 +0200, > >> On 26/04/2017 13:47, Satoru Takeuchi wrote: > >>> OK, here it is. > >> > >> It looks like the cause is that AMD has removed TBM instructions

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On 27/04/2017 02:42, Satoru Takeuchi wrote: > At Wed, 26 Apr 2017 18:58:27 +0200, >> On 26/04/2017 13:47, Satoru Takeuchi wrote: >>> OK, here it is. >> >> It looks like the cause is that AMD has removed TBM instructions >> compared to e.g. Piledriver, so libvirt resorts to a much older base >>

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On 27/04/2017 02:42, Satoru Takeuchi wrote: > At Wed, 26 Apr 2017 18:58:27 +0200, >> On 26/04/2017 13:47, Satoru Takeuchi wrote: >>> OK, here it is. >> >> It looks like the cause is that AMD has removed TBM instructions >> compared to e.g. Piledriver, so libvirt resorts to a much older base >>

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Wed, 26 Apr 2017 18:58:27 +0200, Paolo Bonzini wrote: > > > > On 26/04/2017 13:47, Satoru Takeuchi wrote: > > OK, here it is. > > It looks like the cause is that AMD has removed TBM instructions > compared to e.g. Piledriver, so libvirt resorts to a much older base > model (thanks to Dave

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Wed, 26 Apr 2017 18:58:27 +0200, Paolo Bonzini wrote: > > > > On 26/04/2017 13:47, Satoru Takeuchi wrote: > > OK, here it is. > > It looks like the cause is that AMD has removed TBM instructions > compared to e.g. Piledriver, so libvirt resorts to a much older base > model (thanks to Dave

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On 26/04/2017 13:47, Satoru Takeuchi wrote: > OK, here it is. It looks like the cause is that AMD has removed TBM instructions compared to e.g. Piledriver, so libvirt resorts to a much older base model (thanks to Dave Gilbert for sorting through the list of feature bits). Can you please run

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On 26/04/2017 13:47, Satoru Takeuchi wrote: > OK, here it is. It looks like the cause is that AMD has removed TBM instructions compared to e.g. Piledriver, so libvirt resorts to a much older base model (thanks to Dave Gilbert for sorting through the list of feature bits). Can you please run

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Wed, Apr 26, 2017 at 08:56:24PM +0900, Satoru Takeuchi wrote: > As Paolo said in other mail, The boot also succeeded with "host-passthrough" > mode rather than > "host-model". I'll wait for adding "Ryzen (or Zen?)" model to qemu. Yah, whoever adds it, let's call it "zen" or "Zen". Ryzen is

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Wed, Apr 26, 2017 at 08:56:24PM +0900, Satoru Takeuchi wrote: > As Paolo said in other mail, The boot also succeeded with "host-passthrough" > mode rather than > "host-model". I'll wait for adding "Ryzen (or Zen?)" model to qemu. Yah, whoever adds it, let's call it "zen" or "Zen". Ryzen is

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Tue, 25 Apr 2017 23:58:50 +0900, Masami Hiramatsu wrote: > > Hello, > > 2017-04-24 22:09 GMT+09:00 Satoru Takeuchi : > > At Mon, 24 Apr 2017 14:48:46 +0200, > > Borislav Petkov wrote: > >> > >> On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote: > >> >

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Tue, 25 Apr 2017 23:58:50 +0900, Masami Hiramatsu wrote: > > Hello, > > 2017-04-24 22:09 GMT+09:00 Satoru Takeuchi : > > At Mon, 24 Apr 2017 14:48:46 +0200, > > Borislav Petkov wrote: > >> > >> On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote: > >> > I used the following

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Wed, 26 Apr 2017 09:48:22 +0200, Paolo Bonzini wrote: > > > > On 25/04/2017 11:36, Borislav Petkov wrote: > > Looking at CR4: 003006f0, it doesn't have OSXSAVE set. I.e., bit > > 18. And when that bit is not set, VMOVDQA raises an #UD. > > > > And for some reason qemu doesn't like

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Wed, 26 Apr 2017 09:48:22 +0200, Paolo Bonzini wrote: > > > > On 25/04/2017 11:36, Borislav Petkov wrote: > > Looking at CR4: 003006f0, it doesn't have OSXSAVE set. I.e., bit > > 18. And when that bit is not set, VMOVDQA raises an #UD. > > > > And for some reason qemu doesn't like

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Wed, Apr 26, 2017 at 09:48:22AM +0200, Paolo Bonzini wrote: > The OSXSAVE CPUID bit is not set by QEMU, it is set by the OS itself > (indirectly) when it sets CR4.OSXSAVE. QEMU says it's not available > (probably) because the Opteron_G3 CPU model does not have the 0xD CPUID > leaf. Nope:

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Wed, Apr 26, 2017 at 09:48:22AM +0200, Paolo Bonzini wrote: > The OSXSAVE CPUID bit is not set by QEMU, it is set by the OS itself > (indirectly) when it sets CR4.OSXSAVE. QEMU says it's not available > (probably) because the Opteron_G3 CPU model does not have the 0xD CPUID > leaf. Nope:

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On 25/04/2017 11:36, Borislav Petkov wrote: > Looking at CR4: 003006f0, it doesn't have OSXSAVE set. I.e., bit > 18. And when that bit is not set, VMOVDQA raises an #UD. > > And for some reason qemu doesn't like it even if you request that bit with > +osxsave: > > warning: host doesn't

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On 25/04/2017 11:36, Borislav Petkov wrote: > Looking at CR4: 003006f0, it doesn't have OSXSAVE set. I.e., bit > 18. And when that bit is not set, VMOVDQA raises an #UD. > > And for some reason qemu doesn't like it even if you request that bit with > +osxsave: > > warning: host doesn't

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

Hello, 2017-04-24 22:09 GMT+09:00 Satoru Takeuchi : > At Mon, 24 Apr 2017 14:48:46 +0200, > Borislav Petkov wrote: >> >> On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote: >> > I used the following auto-test tool (its backend is ktest). >> > >> >

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

Hello, 2017-04-24 22:09 GMT+09:00 Satoru Takeuchi : > At Mon, 24 Apr 2017 14:48:46 +0200, > Borislav Petkov wrote: >> >> On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote: >> > I used the following auto-test tool (its backend is ktest). >> > >> >

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Mon, Apr 24, 2017 at 10:09:04PM +0900, Satoru Takeuchi wrote: > At Mon, 24 Apr 2017 14:48:46 +0200, > Borislav Petkov wrote: > > > > On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote: > > > I used the following auto-test tool (its backend is ktest). > > > > > >

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Mon, Apr 24, 2017 at 10:09:04PM +0900, Satoru Takeuchi wrote: > At Mon, 24 Apr 2017 14:48:46 +0200, > Borislav Petkov wrote: > > > > On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote: > > > I used the following auto-test tool (its backend is ktest). > > > > > >

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On 04/24/2017 07:27 AM, Satoru Takeuchi wrote: > At Mon, 24 Apr 2017 15:58:05 +0900, > Satoru Takeuchi wrote: >> >> [1 ] >> Recently I bought a new Ryzen machine. When I tried to test v4.11-rc8 on it, >> it failed to boot >> with the following panic log. Side note - have forwarded to the AMD

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On 04/24/2017 07:27 AM, Satoru Takeuchi wrote: > At Mon, 24 Apr 2017 15:58:05 +0900, > Satoru Takeuchi wrote: >> >> [1 ] >> Recently I bought a new Ryzen machine. When I tried to test v4.11-rc8 on it, >> it failed to boot >> with the following panic log. Side note - have forwarded to the AMD

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Mon, 24 Apr 2017 14:48:46 +0200, Borislav Petkov wrote: > > On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote: > > I used the following auto-test tool (its backend is ktest). > > > > https://github.com/satoru-takeuchi/elkdat > > > > This problem can be reproduced by the

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Mon, 24 Apr 2017 14:48:46 +0200, Borislav Petkov wrote: > > On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote: > > I used the following auto-test tool (its backend is ktest). > > > > https://github.com/satoru-takeuchi/elkdat > > > > This problem can be reproduced by the

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote: > I used the following auto-test tool (its backend is ktest). > > https://github.com/satoru-takeuchi/elkdat > > This problem can be reproduced by the following command on Ubuntu 16.04. > > ``` > $ sudo apt-get install git vagrant

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Mon, Apr 24, 2017 at 09:39:12PM +0900, Satoru Takeuchi wrote: > I used the following auto-test tool (its backend is ktest). > > https://github.com/satoru-takeuchi/elkdat > > This problem can be reproduced by the following command on Ubuntu 16.04. > > ``` > $ sudo apt-get install git vagrant

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Mon, 24 Apr 2017 13:07:53 +0200, Borislav Petkov wrote: > > On Mon, Apr 24, 2017 at 03:58:05PM +0900, Satoru Takeuchi wrote: > > Recently I bought a new Ryzen machine. When I tried to test v4.11-rc8 on > > it, it failed to boot > > with the following panic log. > > > > ``` > > ... > > [

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Mon, 24 Apr 2017 13:07:53 +0200, Borislav Petkov wrote: > > On Mon, Apr 24, 2017 at 03:58:05PM +0900, Satoru Takeuchi wrote: > > Recently I bought a new Ryzen machine. When I tried to test v4.11-rc8 on > > it, it failed to boot > > with the following panic log. > > > > ``` > > ... > > [

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Mon, 24 Apr 2017 15:58:05 +0900, Satoru Takeuchi wrote: > > [1 ] > Recently I bought a new Ryzen machine. When I tried to test v4.11-rc8 on it, > it failed to boot > with the following panic log. > > ``` > ... > [0.227720] raid6: sse2x1 gen() 7985 MB/s > [0.295709] raid6: sse2x1

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

At Mon, 24 Apr 2017 15:58:05 +0900, Satoru Takeuchi wrote: > > [1 ] > Recently I bought a new Ryzen machine. When I tried to test v4.11-rc8 on it, > it failed to boot > with the following panic log. > > ``` > ... > [0.227720] raid6: sse2x1 gen() 7985 MB/s > [0.295709] raid6: sse2x1

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Mon, Apr 24, 2017 at 03:58:05PM +0900, Satoru Takeuchi wrote: > Recently I bought a new Ryzen machine. When I tried to test v4.11-rc8 on it, > it failed to boot > with the following panic log. > > ``` > ... > [0.227720] raid6: sse2x1 gen() 7985 MB/s > [0.295709] raid6: sse2x1

Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Mon, Apr 24, 2017 at 03:58:05PM +0900, Satoru Takeuchi wrote: > Recently I bought a new Ryzen machine. When I tried to test v4.11-rc8 on it, > it failed to boot > with the following panic log. > > ``` > ... > [0.227720] raid6: sse2x1 gen() 7985 MB/s > [0.295709] raid6: sse2x1

[BUG] x86: failed to boot a kernel on a Ryzen machine

Recently I bought a new Ryzen machine. When I tried to test v4.11-rc8 on it, it failed to boot with the following panic log. ``` ... [0.227720] raid6: sse2x1 gen() 7985 MB/s [0.295709] raid6: sse2x1 xor() 8181 MB/s [0.363706] raid6: sse2x2 gen() 17531 MB/s [0.431699]

[BUG] x86: failed to boot a kernel on a Ryzen machine

Recently I bought a new Ryzen machine. When I tried to test v4.11-rc8 on it, it failed to boot with the following panic log. ``` ... [0.227720] raid6: sse2x1 gen() 7985 MB/s [0.295709] raid6: sse2x1 xor() 8181 MB/s [0.363706] raid6: sse2x2 gen() 17531 MB/s [0.431699]