Date: Tue, 12 Nov 2019 20:05:03 +0200 From: Daniel Braniss <danny@cs.huji.ac.il> To: Ian Lepore <ian@freebsd.org> Cc: Peter Jeremy <peter@rulingia.com>, stable@freebsd.org Subject: Re: linker.hints not being update for ARMs Message-ID: <6F633E65-1359-4B57-9B47-18AD593C2612@cs.huji.ac.il> In-Reply-To: <b3140a6d1a8fd59712a3e6f0a304f85f9e046165.camel@freebsd.org> References: <7AB987DF-4A11-4948-BE55-04A2E2A3B8FD@cs.huji.ac.il> <20191112093256.GD50716@server.rulingia.com> <A246A2ED-CA7F-434F-A257-9A827FE974E3@cs.huji.ac.il> <b3140a6d1a8fd59712a3e6f0a304f85f9e046165.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 12 Nov 2019, at 18:41, Ian Lepore <ian@freebsd.org> wrote: >=20 > On Tue, 2019-11-12 at 12:03 +0200, Daniel Braniss wrote: >>> On 12 Nov 2019, at 11:32, Peter Jeremy <peter@rulingia.com> wrote: >>>=20 >>> On 2019-Nov-12 10:30:21 +0200, Daniel Braniss <danny@cs.huji.ac.il> >>> wrote: >>>> warning: KLD '/boot/kernel/wlan.ko' is newer than the >>>> linker.hints file >>>> warning: KLD '/boot/kernel/rtwn.ko' is newer than the >>>> linker.hints file >>>=20 >>> ... >>>> the link.hints is indeed very old : >>>> neo-000# ls -ls /boot/kernel/linker.hints=20 >>>> 224 -rw-r--r-- 1 root wheel 228972 Jan 1 2010 >>>> /boot/kernel/linker.hints >>>=20 >>> Well, that's a nonsense timestamp because FreeBSD didn't support >>> AllWinner >>> in 2010. My guess is that your system clock was wrong. >>>=20 >>>> how can this be fixed? >>>=20 >>> Try rerunning kldxref (with the clock set correctly). >>=20 >> the file is created before the date gets updated! >> it seems that on allwinner epoch is 1st of Jan 2010! (after a power >> cycle) >> so =E2=80=98kldxref=E2=80=99 runs but the time stamp is wrong, >> probably touch /boot/kernel/linker.hints after the clock is corrected >> solves the problem >>=20 >> thanks, >> danny >>=20 >=20 > There doesn't appear to be anything date-sensitive about creating the > xref files. If there is no file in a given directory that contains > modules, the file is created. It's also created if you've set > kldxref_clobber=3DYES in rc.conf (it will rebuild on every boot).=20 > Otherwise if an xref file exists, no work is done. >=20 > Since a normal installkernel renames the old directory then populates = a > clean new directory, there's no need for dates to be involved=E2=80=A6 I=E2=80=99m cross building and in the arm case no file is created (I did = the same for amd64 an one was created) > the > first boot after installing a new kernel should see no xref file and > build one. If you do something like hand-install just the kernel or > just an updated module, then the file won't get rebuilt. >=20 > I've always wished that "service kldxref restart" would just force- > rebuild the files. I have kldxref_enable=3Dyes so it got rebuild the first time after a power cycle it got created with = an old date, a reboot did not help since i didn=E2=80=99t know about the clobber = stuff. >=20 > Even better, if we could make kldxref usable as a cross-tool, the = xrefs > could be generated during a crossbuild rather than on firstboot. I thought this was too tricky, in any case it is rather fast to = re-create it, so i guess the clobber stuff should work, In any case the modules where loaded, so the complain was just that, a warning. danny >=20 > -- Ian >=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6F633E65-1359-4B57-9B47-18AD593C2612>