Date: Tue, 10 Jul 2018 16:37:25 +0200 From: Michael Tuexen <tuexen@freebsd.org> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: Loading modules from /boot/loader.conf Message-ID: <F7B92249-4A1E-4C9C-9856-3CFFEFA3B96C@freebsd.org> In-Reply-To: <20180710134948.GA2655@FreeBSD.org> References: <6DB7ABD4-8C04-46B3-8C07-FC591FC16F71@freebsd.org> <20180626053314.GA30244@FreeBSD.org> <E25A34A1-D249-4F48-A322-C80992A507F3@freebsd.org> <20180710123325.GA34541@FreeBSD.org> <D941A2B8-D6A8-4FAB-9526-CB02191B6A69@freebsd.org> <20180710134948.GA2655@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 10. Jul 2018, at 15:49, Alexey Dokuchaev <danfe@FreeBSD.org> wrote: >=20 > On Tue, Jul 10, 2018 at 03:11:37PM +0200, Michael Tuexen wrote: >>> On 10. Jul 2018, at 14:33, Alexey Dokuchaev <danfe@FreeBSD.org> = wrote: >>>=20 >>> On Tue, Jul 10, 2018 at 01:12:35PM +0200, Michael Tuexen wrote: >>>> can you run on your G4: >>>>=20 >>>> readelf -x set_modmetadata_set /boot/kernel/kernel >>>>=20 >>>> This should provide a list of non-NULL pointers. However, on my G4 = system >>>> this section only contains NULL pointers. >>>=20 >>> Mine is also all NULLs. >>=20 >> OK. You said that you can't reproduce the problem. >=20 > I meant that I didn't try yet because the box is used as a database = server > for our pet project at $work, and I didn't want to reboot it. I'll = try to > find a chance to do this though. >=20 >> So you are able to load a kernel module via /boot/loader.conf? >> If yes, which one? >=20 > I've put xhci_load=3D"YES" there and report upon the next reboot. Great! I tested it with my machine and it shows the problem: * xhci will not be loaded via /boot/loader.conf * xhci can be loaded via kldload after the system is up. Best regards Michael >=20 > ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F7B92249-4A1E-4C9C-9856-3CFFEFA3B96C>