That is a good hint,
i have build several kernels ... but all newer ones arent booting..
i guess i will build another one with CONFIG_DEBUG_SPINLOCK enabled.
I am on vacation right now and have no physical access to the affected
machine right now. Will try it next week.
I would like to know if
On 09.07.19 11:52, Kinky Nekoboi wrote:
> Tested it both with microcode and without microcode. It doesent changes
> the behaviour.
Did you also test it w/ recent mainline kernel ?
(w/ CONFIG_DEBUG_SPINLOCK enabled)
(personally, I've long given up walking through Debian's kernel mess,
just use
Addional info:
linux 4.19 works flawless on corebooted F2A85m, thinkpad x220, w520,
x60, t60, apu2
Am 09.07.19 um 12:04 schrieb Kinky Nekoboi:
> Vendor firmware i did not, and i guess cannot anymore test.
>
> Tested in my case (KGPE-D16) with libreboot (coreboot 4.6) with and
> without
Hi!
Tested it both with microcode and without microcode. It doesent changes
the behaviour.
Uh, that's indeed not good then. Have you tried if this also happens with older
coreboot versions or when running under the vendor firmware?
Regards
Felix
--
Felix Held
c/o cyberkombinat23
Tested it both with microcode and without microcode. It doesent changes
the behaviour.
Am 09.07.19 um 11:43 schrieb Felix Held:
> Hi!
>
> Since I didn't see that being mentioned in the bug reports: Is this
> with or without microcode updates being applied in coreboot? If the
> crashes only
Hi!
Since I didn't see that being mentioned in the bug reports: Is this with or
without microcode updates being applied in coreboot? If the crashes only
happens without those being applied, it's not a coreboot problem.
Maybe we should add a "-no_ucode" or simply a "-tainted" to the bios
6 matches
Mail list logo
