Claudia: >> marmarek: >> For this particular case (microcode included in BIOS newer than in OS), I >> see two options: make >> BIOS (coreboot, right?) apply microcode update on resume too, or include >> newer microcode in OS. > > I want to make one thing clear: I am **not** suggesting this check be removed > altogether. I am suggesting adding an **optional**, even undocumented, > override parameter which defaults to the **current behavior** which is to > panic. > > I've found the patch to be quite stable so far. Unpatched is guaranteed to > cause a crash (xen > panic) at resume; patched so far has not caused any noticeable stability > issues for the four of us > using it, afaik. Just saying. > > Also, not everyone has the option of coreboot. And we're not even completely > certain this a > post-resume microcode update issue, either.
FWIW, my corebooted AMD has the same issue and resolution. Of course, much of the source code came from AMD so it could be something common to most/all. I wonder if there's a fix that could be made at that level. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a4dc0396-7404-821e-529f-f63110c0e560%40danwin1210.me.
