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 ** Attachment added: "oops.tar" http://launchpadlibrarian.net/18270605/oops.tar ** Summary changed: - kernel oops on boot with splash + kernel oops on boot with "quiet" option -- kernel oops on boot with "quiet" option https://bugs.launchpad.net/bugs/279186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
