Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1401164 > unrolled thread

Re: Builtin early microcode breaks s2ram v4.6-rcX

Started byBorislav Petkov <bp@suse.de>
First post2016-05-16 04:10 +0200
Last post2016-05-16 04:10 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Builtin early microcode breaks s2ram v4.6-rcX Borislav Petkov <bp@suse.de> - 2016-05-16 04:10 +0200
    Re: Builtin early microcode breaks s2ram v4.6-rcX Jim Bos <jim876@xs4all.nl> - 2016-05-16 04:10 +0200
      Re: Builtin early microcode breaks s2ram v4.6-rcX Borislav Petkov <bp@suse.de> - 2016-05-16 04:10 +0200

#1401164 — Re: Builtin early microcode breaks s2ram v4.6-rcX

FromBorislav Petkov <bp@suse.de>
Date2016-05-16 04:10 +0200
SubjectRe: Builtin early microcode breaks s2ram v4.6-rcX
Message-ID<rzg8P-u7-51@gated-at.bofh.it>
On Sun, May 15, 2016 at 02:16:28PM +0200, Jim Bos wrote:
> However, after suspend to ram, trying to resume results in total
> lockup of the machine: no ping, no sysrq-keys, only hard reset works.

Does it work when you add "dis_ucode_ldr" to the kernel command line?

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
-- 

[toc] | [next] | [standalone]


#1401182

FromJim Bos <jim876@xs4all.nl>
Date2016-05-16 04:10 +0200
Message-ID<rzg8R-u7-113@gated-at.bofh.it>
In reply to#1401164
On 05/15/2016 04:48 PM, Borislav Petkov wrote:
> On Sun, May 15, 2016 at 02:16:28PM +0200, Jim Bos wrote:
>> However, after suspend to ram, trying to resume results in total
>> lockup of the machine: no ping, no sysrq-keys, only hard reset works.
> 
> Does it work when you add "dis_ucode_ldr" to the kernel command line?
> 

Yes,  it boots  / suspends  / resumes  just fine.
(but no microcode updates in dmesg)

Jim

[toc] | [prev] | [next] | [standalone]


#1401268

FromBorislav Petkov <bp@suse.de>
Date2016-05-16 04:10 +0200
Message-ID<rzg90-u7-325@gated-at.bofh.it>
In reply to#1401182
On Sun, May 15, 2016 at 05:45:49PM +0200, Jim Bos wrote:
> Yes,  it boots  / suspends  / resumes  just fine.
> (but no microcode updates in dmesg)

Ok, I'll take a look.

Btw, is there a particular reason why you're not doing microcode updates
through the initrd? Or you're running without one?

Also, can you send me your .config. Privately is fine too.

Thanks.

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
-- 

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web