kldload: Unsupported file type
Bruce M Simpson
It is printed whenever a kernel module is loaded.
The modules load OK. Nothing special or different about them.
It seems to be harmless, but any idea why it's started happening since
the release?
Cheers
BMS
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
Daniel O'Connor
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Wed, 30 Jan 2008, Bruce M Simpson wrote:
> Since updating to 6.3-RELEASE on two machines I see this message a
> lot.
Hooray I am not alone!
I have a thread in stable called ' kldstat causes kernel to print odd=20
message' (not the best subject since it's wrong AND undescriptive),=20
message ID is 200801171410....@gsoft.com.au.
> It is printed whenever a kernel module is loaded.
> The modules load OK. Nothing special or different about them.
>
> It seems to be harmless, but any idea why it's started happening
> since the release?
It is printed by sys/kern/link_elf.c - amd64 uses this for historical=20
reasons.=20
The issue is that it is being called before the stuff in link_elf_obj.c=20
and printing an error, the kernel then tries _obj and it works.
I tried #ifdef'ing out link_elf.c but it panicd my machine on boot and I=20
haven't had time to find out why.
The good news is that it's a purely cosmetic problem.
=2D-=20
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
--nextPart1444192.3CA22XZiui
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQBHoBdT5ZPcIHs/zowRAsmaAKCV4f+OezBBKRw1OvOqhDKDJoQqgQCgg+rr
t1mHuSdJ7UXVH7fhyLqtQi0=
=9056
-----END PGP SIGNATURE-----
--nextPart1444192.3CA22XZiui--
John Baldwin
> On Wed, 30 Jan 2008, Bruce M Simpson wrote:
> > Since updating to 6.3-RELEASE on two machines I see this message a
> > lot.
>
> Hooray I am not alone!
> I have a thread in stable called ' kldstat causes kernel to print odd
>
> > It is printed whenever a kernel module is loaded.
> > The modules load OK. Nothing special or different about them.
> >
> > It seems to be harmless, but any idea why it's started happening
> > since the release?
>
> It is printed by sys/kern/link_elf.c - amd64 uses this for historical
> The issue is that it is being called before the stuff in link_elf_obj.c
>
> I tried #ifdef'ing out link_elf.c but it panicd my machine on boot and I
The kernel is a link_elf type object I believe, so you have to have it.
--
John Baldwin
Daniel O'Connor
Content-Type: text/plain;
charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Thu, 31 Jan 2008, John Baldwin wrote:
> > I tried #ifdef'ing out link_elf.c but it panicd my machine on boot
> > and I haven't had time to find out why.
>
> The kernel is a link_elf type object I believe, so you have to have
> it.
Ahah..
No easy answer there then :)
=2D-=20
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
--nextPart3339882.nBHI8rtmep
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQBHoS6y5ZPcIHs/zowRAgn3AJ0auBjNPH4KAX05JasAG15haAPgHgCfZ1Tv
hA9PCb8TQ4vsJ+vMEpIs6/U=
=HfGi
-----END PGP SIGNATURE-----
--nextPart3339882.nBHI8rtmep--
Bruce M Simpson
>>> It is printed whenever a kernel module is loaded.
>>> The modules load OK. Nothing special or different about them.
>>>
>>>
> The kernel is a link_elf type object I believe, so you have to have it.
>
>
That follows (I was reading this the other day 'cause we don't support
weak ELF symbols in the kernel for C++) however, why is the message
being triggered now?
Could it be ET_REL ?
There have been no major changes to linking for the 6.3 buildkernel
target IIRC.
BTW only my amd64 system appears to be affected.
later
BMS
John Baldwin
> John Baldwin wrote:
> >>> It is printed whenever a kernel module is loaded.
> >>> The modules load OK. Nothing special or different about them.
> >>>
> >>>
> ...
> > The kernel is a link_elf type object I believe, so you have to have it.
> >
> >
>
> That follows (I was reading this the other day 'cause we don't support
> weak ELF symbols in the kernel for C++) however, why is the message
> being triggered now?
>
> Could it be ET_REL ?
> There have been no major changes to linking for the 6.3 buildkernel
> target IIRC.
>
>
> BTW only my amd64 system appears to be affected.
The problem is that .ko's on amd64 are handled by link_elf_obj.c and not
link_elf.c, thus if link_elf.c is first in the list of linker file handlers,
then every .ko on amd64 is first going to try link_elf.c which fails and
emits the error and then get loaded successfully by link_elf_obj.c. Probably
what should happen is that the linker error message should be cached somehow
and only print out the last error if the overall load fails.
--
John Baldwin