Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, 2017-01-31 at 18:49 +0100, Borislav Petkov wrote: > On Tue, Jan 31, 2017 at 01:31:00PM +0100, Borislav Petkov wrote: > > On Tue, Jan 31, 2017 at 12:31:17PM +0100, Mike Galbraith wrote: > > > (bisect fingered irqdomain: Avoid activating interrupts more than once) > > > > Yeah, that one is

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, 2017-01-31 at 18:49 +0100, Borislav Petkov wrote: > On Tue, Jan 31, 2017 at 01:31:00PM +0100, Borislav Petkov wrote: > > On Tue, Jan 31, 2017 at 12:31:17PM +0100, Mike Galbraith wrote: > > > (bisect fingered irqdomain: Avoid activating interrupts more than once) > > > > Yeah, that one is

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, 31 Jan 2017, Mike Galbraith wrote: > On Tue, 2017-01-31 at 11:01 +0100, Borislav Petkov wrote: > > On Tue, Jan 31, 2017 at 08:43:55AM +0100, Ingo Molnar wrote: > > > (Cc:-ed Mike as this could explain his early boot crash/hang? > > > Mike: please try -tip f18a8a0143b1 that I just

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, 31 Jan 2017, Mike Galbraith wrote: > On Tue, 2017-01-31 at 11:01 +0100, Borislav Petkov wrote: > > On Tue, Jan 31, 2017 at 08:43:55AM +0100, Ingo Molnar wrote: > > > (Cc:-ed Mike as this could explain his early boot crash/hang? > > > Mike: please try -tip f18a8a0143b1 that I just

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, Jan 31, 2017 at 01:31:00PM +0100, Borislav Petkov wrote: > On Tue, Jan 31, 2017 at 12:31:17PM +0100, Mike Galbraith wrote: > > (bisect fingered irqdomain: Avoid activating interrupts more than once) > > Yeah, that one is not kosher on x86. It broke IO-APIC timer on a box > here. Mike,

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, Jan 31, 2017 at 01:31:00PM +0100, Borislav Petkov wrote: > On Tue, Jan 31, 2017 at 12:31:17PM +0100, Mike Galbraith wrote: > > (bisect fingered irqdomain: Avoid activating interrupts more than once) > > Yeah, that one is not kosher on x86. It broke IO-APIC timer on a box > here. Mike,

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

* Borislav Petkov wrote: > On Tue, Jan 31, 2017 at 08:43:55AM +0100, Ingo Molnar wrote: > > (Cc:-ed Mike as this could explain his early boot crash/hang? > > Mike: please try -tip f18a8a0143b1 that I just pushed out. ) > > One other thing to try, Mike, is boot with

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

* Borislav Petkov wrote: > On Tue, Jan 31, 2017 at 08:43:55AM +0100, Ingo Molnar wrote: > > (Cc:-ed Mike as this could explain his early boot crash/hang? > > Mike: please try -tip f18a8a0143b1 that I just pushed out. ) > > One other thing to try, Mike, is boot with "dis_ucode_ldr". See

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, Jan 31, 2017 at 12:31:17PM +0100, Mike Galbraith wrote: > (bisect fingered irqdomain: Avoid activating interrupts more than once) Yeah, that one is not kosher on x86. It broke IO-APIC timer on a box here. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, Jan 31, 2017 at 12:31:17PM +0100, Mike Galbraith wrote: > (bisect fingered irqdomain: Avoid activating interrupts more than once) Yeah, that one is not kosher on x86. It broke IO-APIC timer on a box here. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, 2017-01-31 at 11:01 +0100, Borislav Petkov wrote: > On Tue, Jan 31, 2017 at 08:43:55AM +0100, Ingo Molnar wrote: > > (Cc:-ed Mike as this could explain his early boot crash/hang? > > Mike: please try -tip f18a8a0143b1 that I just pushed out. ) > > One other thing to try, Mike, is

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, 2017-01-31 at 11:01 +0100, Borislav Petkov wrote: > On Tue, Jan 31, 2017 at 08:43:55AM +0100, Ingo Molnar wrote: > > (Cc:-ed Mike as this could explain his early boot crash/hang? > > Mike: please try -tip f18a8a0143b1 that I just pushed out. ) > > One other thing to try, Mike, is

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, Jan 31, 2017 at 08:43:55AM +0100, Ingo Molnar wrote: > (Cc:-ed Mike as this could explain his early boot crash/hang? > Mike: please try -tip f18a8a0143b1 that I just pushed out. ) One other thing to try, Mike, is boot with "dis_ucode_ldr". See whether that makes it go away. >

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Tue, Jan 31, 2017 at 08:43:55AM +0100, Ingo Molnar wrote: > (Cc:-ed Mike as this could explain his early boot crash/hang? > Mike: please try -tip f18a8a0143b1 that I just pushed out. ) One other thing to try, Mike, is boot with "dis_ucode_ldr". See whether that makes it go away. >

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

(Cc:-ed Mike as this could explain his early boot crash/hang? Mike: please try -tip f18a8a0143b1 that I just pushed out. ) * Borislav Petkov wrote: > On Mon, Jan 30, 2017 at 09:46:32AM +0100, Ingo Molnar wrote: > > Ok, I have applied this to tip:x86/urgent. > > > >

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

(Cc:-ed Mike as this could explain his early boot crash/hang? Mike: please try -tip f18a8a0143b1 that I just pushed out. ) * Borislav Petkov wrote: > On Mon, Jan 30, 2017 at 09:46:32AM +0100, Ingo Molnar wrote: > > Ok, I have applied this to tip:x86/urgent. > > > > Note that there are

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Mon, Jan 30, 2017 at 09:46:32AM +0100, Ingo Molnar wrote: > Ok, I have applied this to tip:x86/urgent. > > Note that there are new conflicts with your pending work in > tip:x86/microcode, and > I fixed them up in: > > 7c5b4112040e Merge branch 'x86/urgent' into x86/microcode, to resolve

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Mon, Jan 30, 2017 at 09:46:32AM +0100, Ingo Molnar wrote: > Ok, I have applied this to tip:x86/urgent. > > Note that there are new conflicts with your pending work in > tip:x86/microcode, and > I fixed them up in: > > 7c5b4112040e Merge branch 'x86/urgent' into x86/microcode, to resolve

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

* Borislav Petkov wrote: > On Fri, Jan 27, 2017 at 11:14:06AM +0300, Andrey Ryabinin wrote: > > Works for me as well. > > Tested-by: Andrey Ryabinin > > Thanks! Ok, I have applied this to tip:x86/urgent. Note that there are new conflicts with your

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

* Borislav Petkov wrote: > On Fri, Jan 27, 2017 at 11:14:06AM +0300, Andrey Ryabinin wrote: > > Works for me as well. > > Tested-by: Andrey Ryabinin > > Thanks! Ok, I have applied this to tip:x86/urgent. Note that there are new conflicts with your pending work in tip:x86/microcode, and I

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Fri, Jan 27, 2017 at 11:14:06AM +0300, Andrey Ryabinin wrote: > Works for me as well. > Tested-by: Andrey Ryabinin Thanks! -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On Fri, Jan 27, 2017 at 11:14:06AM +0300, Andrey Ryabinin wrote: > Works for me as well. > Tested-by: Andrey Ryabinin Thanks! -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On 01/26/2017 07:58 PM, Borislav Petkov wrote: > On Wed, Jan 25, 2017 at 08:23:36PM +0100, Borislav Petkov wrote: >> On Wed, Jan 25, 2017 at 10:14:50PM +0300, Andrey Ryabinin wrote: Does that help? >>> >>> Yup. >>> Tested-by: Andrey Ryabinin >> >> Thanks, I'll run

Re: [PATCH] x86/microcode: Do not access the initrd after it has been freed

On 01/26/2017 07:58 PM, Borislav Petkov wrote: > On Wed, Jan 25, 2017 at 08:23:36PM +0100, Borislav Petkov wrote: >> On Wed, Jan 25, 2017 at 10:14:50PM +0300, Andrey Ryabinin wrote: Does that help? >>> >>> Yup. >>> Tested-by: Andrey Ryabinin >> >> Thanks, I'll run it through the test boxes

[PATCH] x86/microcode: Do not access the initrd after it has been freed

On Wed, Jan 25, 2017 at 08:23:36PM +0100, Borislav Petkov wrote: > On Wed, Jan 25, 2017 at 10:14:50PM +0300, Andrey Ryabinin wrote: > > > Does that help? > > > > Yup. > > Tested-by: Andrey Ryabinin > > Thanks, I'll run it through the test boxes here too. Yeah, the fix

[PATCH] x86/microcode: Do not access the initrd after it has been freed

On Wed, Jan 25, 2017 at 08:23:36PM +0100, Borislav Petkov wrote: > On Wed, Jan 25, 2017 at 10:14:50PM +0300, Andrey Ryabinin wrote: > > > Does that help? > > > > Yup. > > Tested-by: Andrey Ryabinin > > Thanks, I'll run it through the test boxes here too. Yeah, the fix isn't that simple, I had