Reproducibility can be variable. As noted, I only really note it following a reboot and normally, this is only because of apt update to a kernel.
I don't think we have narrowed down specifics on how to reproduce beyond it occurring on boot, for my output to be declarable as reliable. That said, I am pretty much happy to assist where needed. I have added my fstab section for my mounts to my report. Let me know if the rest is needed, but that only covers the system gen portion from install. 192.168.0.200 is a SAMBA setup with linux extensions enabled (by default cannot disable them) 192.168.0.199 is a SAMBA setup with linux extensions disabled (can be enabled, but never had to) My mount config is derived from the Ubuntu Wiki pages. Let me know exactly what is needed and I will try. Status as of now. I have not updated or rebooted following submitting my report (except rebooting out of the problem). Updates are pending, but no Kernel. I await any suggestions from you or debug requests -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070256 Title: mount.cifs occasionally causes GPF error/kernel panic when mounting at boot [crypto_larval_kill+0x2b/0x90] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070256/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
