Date: Fri, 05 Jul 2024 01:40:54 +0000 From: jonc@chen.org.nz To: "Tomoaki AOKI" <junchoon@dec.sakura.ne.jp>, freebsd-stable@freebsd.org Subject: Re: x11/nvidia-driver fails on 14-STABLE/amd64 Message-ID: <7c7cd0411f6c7102e5f054c6e36eaab9@chen.org.nz> In-Reply-To: <5811fe64-43ab-4922-934c-e2f78c4ffc36@chen.org.nz> References: <5811fe64-43ab-4922-934c-e2f78c4ffc36@chen.org.nz> <2458ffc88ffac503076c06cccafa0dc0@chen.org.nz> <20240703082414.572553dabee65d0f6dd129a1@dec.sakura.ne.jp> <20240704091007.5dc5f7a41bf12f8f764a896d@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
July 4, 2024 7:49 PM, "Jonathan Chen" <jonc@chen.org.nz> wrote: > On 4/07/24 12:10, Tomoaki AOKI wrote: > [...] >=20 >>=20If you start X from command line with startx and the cause was as ab= ove, >> you should see the panic on loading the module. >=20 >=20For simplicity, I'm just using startx. However, the panic is a bit mo= re subtle than a panic from a > simple kldload. I'm currently working thru' with git bisect to determin= e the commit causing the > issue. I tracked the problematic commit to: c5e0b035d9eb14e73fc17899cd007a31e0d1edc8 libutil: move ftime to libuti= l It appears that building a kernel with a world prior to that commit will = result in a usable kernel+userland, but which crashes (a newly rebuilt) n= vidia-driver. I'm pretty sure that I used "make buildworld buildkernel in= stallkernel installworld" to put everything in; but everything resolved a= fter forcing another kernel rebuild using the toolset after that particul= ar commit. ports-mgmt/synth also wasn't happy, but I managed to resolve that by rebu= ilding lang/gcc12, lang/gnat12 and then ports-mgmt/synth. Cheers. -- Jonathan Chen <jonc@chen.org.nz>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7c7cd0411f6c7102e5f054c6e36eaab9>