kldref: too many segments on kernel build

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

kldref: too many segments on kernel build

Michael Butler
Any thoughts as to why this is happening when I build a (custom) kernel?

kldxref: /boot/kernel/kernel: too many segments

        imb
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: kldref: too many segments on kernel build

Dustin Marquess
On Tue, Aug 18, 2020 at 3:19 PM Michael Butler
<[hidden email]> wrote:
>
> Any thoughts as to why this is happening when I build a (custom) kernel?
>
> kldxref: /boot/kernel/kernel: too many segments

I'm seeing this too.  I haven't tried actually booting the kernel
because of this.

-Dustin
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: kldref: too many segments on kernel build

Gary Jennejohn-6
On Tue, 18 Aug 2020 23:19:08 -0500
Dustin Marquess <[hidden email]> wrote:

> On Tue, Aug 18, 2020 at 3:19 PM Michael Butler
> <[hidden email]> wrote:
> >
> > Any thoughts as to why this is happening when I build a (custom) kernel?
> >
> > kldxref: /boot/kernel/kernel: too many segments  
>
> I'm seeing this too.  I haven't tried actually booting the kernel
> because of this.
>

Same here, but I was able to boot the kernel (installed to /boot/test)
with no errors.

But Xorg fails to start.  That may not be related to the kldxref error
itself but is perhaps due to other changes in the kernel which cause the
Nvidia driver to fail at startup.  I'm not willing to rebuild the Nvidia
driver to test my hypothesis.

--
Gary Jennejohn
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: kldref: too many segments on kernel build

Michael Tuexen-3
In reply to this post by Dustin Marquess
> On 19. Aug 2020, at 06:19, Dustin Marquess <[hidden email]> wrote:
>
> On Tue, Aug 18, 2020 at 3:19 PM Michael Butler
> <[hidden email]> wrote:
>>
>> Any thoughts as to why this is happening when I build a (custom) kernel?
>>
>> kldxref: /boot/kernel/kernel: too many segments
>
> I'm seeing this too.  I haven't tried actually booting the kernel
> because of this.
I also see this... The kernel boots just fine.

Best regards
Michael
>
> -Dustin
> _______________________________________________
> [hidden email] mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[hidden email]"

_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: kldref: too many segments on kernel build

Ed Maste-2
In reply to this post by Dustin Marquess
On Wed, 19 Aug 2020 at 00:19, Dustin Marquess <[hidden email]> wrote:

>
> On Tue, Aug 18, 2020 at 3:19 PM Michael Butler
> <[hidden email]> wrote:
> >
> > Any thoughts as to why this is happening when I build a (custom) kernel?
> >
> > kldxref: /boot/kernel/kernel: too many segments
>
> I'm seeing this too.  I haven't tried actually booting the kernel
> because of this.

This is fallout from Clang 11. The kernel should boot fine despite the
warnings, and this should be cleaned up in the near future (by
increasing the number of segments supported by kldxref, by changing
the kernel linker script, or a combination of both).
_______________________________________________
[hidden email] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[hidden email]"