Re: CURRENT crashes with nvidia GPU BLOB : vm_radix_insert: key 23c078 is already present

Woo! Tell Jeff! File a PR! Set everything on fire!



-adrian


On 8 August 2013 14:39, Sean Bruno <sean_bruno_at_yahoo.com> wrote:
> On Thu, 2013-08-08 at 11:30 -0700, Adrian Chadd wrote:
>> Can you go over some previous versions in -HEAD and see when it was introduced?
>>
>>
>>
>> -adrian
>>
>> On 8 August 2013 11:10, O. Hartmann <ohartman_at_zedat.fu-berlin.de> wrote:
>> > The most recent CURRENT doesn't work with the x11/nvidia-driver (which
>> > is at 319.25 in the ports and 325.15 from nVidia).
>> >
>> > After build- and installworld AND successfully rebuilding port
>> > x11/nvidia-driver, the system crashes immediately after a reboot as
>> > soon the kernel module nvidia.ko seems to get loaded (in my case, I
>> > load nvidia.ko via /etc/rc.conf.local since the nVidia BLOB doesn't
>> > load cleanly everytime when loaded from /boot/loader.conf).
>> >
>> > The crash occurs on systems with default compilation options set while
>> > building world and with settings like -O3 -march=native. It doesn't
>> > matter.
>> >
>> > FreeBSD and the port x11/nvidia-driver has been compiled with CLANG.
>> >
>> > Most recent FreeBSD revision still crashing is r254097.
>> >
>> > When vmcore is saved, I always see something like
>> >
>> > savecore: reboot after panic: vm_radix_insert: key 23c078 is already
>> > present
>> >
>> >
>> > Does anyone has any idea what's going on?
>> >
>> > Thanks for helping in advance,
>> >
>> > Oliver
>
> I'm seeing a complete deadlock on my T520 with today's current and
> latest portsnap'd versions of ports for the nvidia-driver updates.
>
> A little bisection and help from others seems to point the finger at
> Jeff's r254025
>
> I'm getting a complete deadlock on X starting, but loading the module
> seems to have no ill effects.
>
> Sean