If anyone misses agp they can still kldload at their own peril?https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/OPNsense-24.7.2-vga-amd64.img.bz2https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/OPNsense-24.7.2-vga-amd64.img.sighttps://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/OPNsense-24.7.2-dvd-amd64.iso.bz2https://pkg.opnsense.org/FreeBSD:14:amd64/snapshots/misc/OPNsense-24.7.2-dvd-amd64.iso.sigI will replace the kernel on the mirror when someone confirmed this on one of the images with the actual hardware that the driver attaches to. ZPOOL_IMPORT_PATH has not been reverted, only agp removed from kernel so it cannot hit the bad agp_close(). If this works for the people reporting the crash we have our answer. Cheers,Franco
My HP/Compaq, so I was told, does not have an AGP-slot on the mobo. (I have not checked myself.)Does that make any sense to anyone?
dmesg | grep agp
Quote from: mifi42 on August 25, 2024, 10:48:16 amMy HP/Compaq, so I was told, does not have an AGP-slot on the mobo. (I have not checked myself.)Does that make any sense to anyone?Can attach to some unused on-board junk. Code: [Select]dmesg | grep agpand see what it detects.
dmesg | grep agp:agp0: <Intel Q35 SVGA controller> on vgapci0WARNING: Device "agp" is Giant locked and may be deleted before FreeBSD 15.0.agp0: aperture size is 256M, detected 6140k stolen memory
agp0: <Intel Q35 SVGA controller> on vgapci0
Is it time to scrap the hardware?
Are you actually using the VGA console? I.e., do you have monitor connected to the box itself?
pciconf -lv
Do we have a fix yet
Hi Robert,I hope not. It looks like a fringe kernel issue with the OP's hardware (AGP slot in particular) that doesn't surface on FreeBSD because ZPOOL_IMPORT_PATH wasn't bootstrapped ever since FreeBSD changed ZFS implementations in version 13 so this will likely remain to go unnoticed.We do have a debug kernel, but it requires the system to boot up first. If we can manage to get a core dump we can probably apply a bandaid and report to FreeBSD.That being said I see no reason to revoke the ZPOOL_IMPORT_PATH. All hell would have broken loose already if it was a major problem. But even then I still don't think an environment variable should crash a user system ever.Cheers,Franco
Based on this - it's time to move away from the product - 100% experienced the same issue and to think it wont be fixed.....
Quote from: Penetr8or on August 25, 2024, 10:51:06 pmDo we have a fix yetHelps to read the thread... Start here and follow up with the next post.