I have tested this even more. It looks like I can 100% reproduce OOPS (but with different stack traces) when I use "quiet" boot option. It seems that "splash" boot option is not an option, as I can reliably boot without problem if I remove "quiet", but leave "splash" option.
Will change bug description to match this.
I have also attached more oops photos where you can see different stack traces reported. It looks like there are at least three distinct functions where I get oops:
I have tested this even more. It looks like I can 100% reproduce OOPS (but with different stack traces) when I use "quiet" boot option. It seems that "splash" boot option is not an option, as I can reliably boot without problem if I remove "quiet", but leave "splash" option.
Will change bug description to match this.
I have also attached more oops photos where you can see different stack traces reported. It looks like there are at least three distinct functions where I get oops:
1. run_timer_softirq / clockevents_ program_ event / __do_softirq ... / smp_apic_ apic_timer_ interrupt
2. neigh_periodic_ timer / clockevents_ program_ event / __do_softirq ... / smp_apic_ apic_timer_ interrupt
3. oops_begin / do_page_fault / enqueue_task_fair ... / error_exit / _i8042_interrupt