Date: Sat, 23 Nov 2019 19:01:10 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en Message-ID: <bug-241639-227-etQCZDr9rd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241639-227@https.bugs.freebsd.org/bugzilla/> References: <bug-241639-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #11 from Michael <michael.adm@gmail.com> --- After applying the 4a46b2449c63e010014dc0fb2a3caa5e20b97933 commit, the kern.cam.boot_delay="10000" parameter in /boot/loader.conf stopped working. Catastrophe! Now I have to load mlx4en.ko in firewall rules! (in /etc/rc.firewall adding at end "kldload mlx4en") Please correct the situation. committer mav <mav@FreeBSD.org> Fri, 22 Nov 2019 20:39:51 +0200 (18:39 +0000) commit 4a46b2449c63e010014dc0fb2a3caa5e20b97933 Make CAM use root_mount_hold_token() to delay boot. Before this change CAM used config_intrhook_establish() for this purpose, but that approach does not allow to delay it again after releasing once. USB stack uses root_mount_hold() to delay boot until bus scan is complete. But once it is, CAM had no time to scan SCSI bus, registered by umass(4), if it already done other scans and called config_intrhook_disestablish(). The new approach makes it work smooth, assuming the USB device is found during the initial bus scan. Devices appearing on USB bus later may still require setting kern.cam.boot_delay, but hopefully those are minority. MFC after: 2 weeks Sponsored by: iXsystems, Inc. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241639-227-etQCZDr9rd>