On 03/17/21 06:38 PM, Apostolos Syropoulos via openindiana-discuss wrote:
And here is the output from the fmdump command:
TIME UUID SUNW-MSG-ID
Μαρ 08 2021 09:31:41.982815000 fea0efbd-8079-c363-9d1d-a74d6124b14a
SUNOS-8000-KL
TIME CLASS ENA
Μαρ 08 09:31:26.3304 ireport.os.sunos.panic.dump_pending_on_device
0x0000000000000000
nvlist version: 0
version = 0x0
class = list.suspect
uuid = fea0efbd-8079-c363-9d1d-a74d6124b14a
code = SUNOS-8000-KL
diag-time = 1615188701 457254
de = fmd:///module/software-diagnosis
fault-list-sz = 0x1
fault-list = (array of embedded nvlists)
(start fault-list[0])
nvlist version: 0
version = 0x0
class = defect.sunos.kernel.panic
certainty = 0x64
asru =
sw:///:path=/var/crash/victoria/.fea0efbd-8079-c363-9d1d-a74d6124b14a
resource =
sw:///:path=/var/crash/victoria/.fea0efbd-8079-c363-9d1d-a74d6124b14a
savecore-succcess = 0
os-instance-uuid = fea0efbd-8079-c363-9d1d-a74d6124b14a
panicstr = hat_devload: loading a mapping to free page fffffe0000207920
panicstack = unix:hat_devload+1ba () |
gfx_private:gfxp_map_kernel_space+b5 () | nvidia:_nv028850rm+57 () |
crashtime = 1615188620
panic-time = 8 Μαρτίου 2021 - 09:30:20 π.μ. EET EET
(end fault-list[0])
fault-status = 0x1
severity = Major
__ttl = 0x1
__tod = 0x6045d2dd 0x3a949118
Best regards,
A.S.
----------------------
Apostolos Syropoulos
Xanthi, Greece
On Sunday, March 14, 2021, 11:00:06 AM GMT+2, Apostolos Syropoulos via
openindiana-discuss <openindiana-discuss@openindiana.org> wrote:
As was suggested by a frequent poster of this list,
I saved the core dump and "viewed" with fmadm faulty.
Here is what I see:
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
--------------- ------------------------------------ -------------- ---------
Μαρ 08 09:31:41 fea0efbd-8079-c363-9d1d-a74d6124b14a SUNOS-8000-KL Major
Host : victoria
Platform : AB350M-HD3 Chassis_id : Default-string
Product_sn :
Fault class : defect.sunos.kernel.panic
Affects :
sw:///:path=/var/crash/victoria/.fea0efbd-8079-c363-9d1d-a74d6124b14a
faulted but still in service
Problem in :
sw:///:path=/var/crash/victoria/.fea0efbd-8079-c363-9d1d-a74d6124b14a
faulted but still in service
Description : The system has rebooted after a kernel panic. Refer to
http://illumos.org/msg/SUNOS-8000-KL for more information.
Response : The failed system image was dumped to the dump device. If
savecore is enabled (see dumpadm(1M)) a copy of the dump will be
written to the savecore directory .
Impact : There may be some performance impact while the panic is copied to
the savecore directory. Disk space usage by panics can be
substantial.
Action : If savecore is not enabled then please take steps to preserve the
crash image.
Use 'fmdump -Vp -u fea0efbd-8079-c363-9d1d-a74d6124b14a' to view
more panic detail. Please refer to the knowledge article for
additional information.
Is this helpful in any way?
A.S.
_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
Ok.
gfx_private is involved. You may have some misconfiguration after the
"pkg update",
because gfx_private is delivered vie a pkg
$ pkg search gfx_private
INDEX ACTION VALUE PACKAGE
basename file platform/i86pc/kernel/misc/amd64/gfx_private
pkg:/system/kernel/platform@0.5.11-2020.0.1.20397
basename file platform/i86xpv/kernel/misc/amd64/gfx_private
pkg:/system/kernel/platform@0.5.11-2020.0.1.20397
and via the NVIDIA drivers itself
$ find . -name gfx_private -exec ls -l {} \;
-rw-r--r-- 1 steven staff 51088 Jul 23 2019
./nvidia-390/NVIDIA-Solaris-x86-390.129/gfx_private/SunOS-5.10/amd64/gfx_private
-rw-r--r-- 1 steven staff 62744 Jul 23 2019
./nvidia-390/NVIDIA-Solaris-x86-390.129/gfx_private/SunOS-5.10/gfx_private
-rw-r--r-- 1 steven staff 30576 Jul 23 2019
./nvidia-390/NVIDIA-Solaris-x86-390.129/gfx_private/SunOS-5.11/gfx_private
-rw-r--r-- 1 steven staff 49032 Jul 23 2019
./nvidia-390/NVIDIA-Solaris-x86-390.129/gfx_private/SunOS-5.11/amd64/gfx_private
-rw-r--r-- 1 steven staff 49032 Dec 11 2019
./nvidia-340/NVIDIA-Solaris-x86-340.108/gfx_private/SunOS-5.11/amd64/gfx_private
-rw-r--r-- 1 steven staff 30576 Dec 11 2019
./nvidia-340/NVIDIA-Solaris-x86-340.108/gfx_private/SunOS-5.11/gfx_private
-rw-r--r-- 1 steven staff 51088 Dec 11 2019
./nvidia-340/NVIDIA-Solaris-x86-340.108/gfx_private/SunOS-5.10/amd64/gfx_private
-rw-r--r-- 1 steven staff 62744 Dec 11 2019
./nvidia-340/NVIDIA-Solaris-x86-340.108/gfx_private/SunOS-5.10/gfx_private
So, maybe you have the "wrong" gfx_private"?
You could try:
a) re-install the NVIDIA driver.
Verify that gfx_private is now the one from the NVIDIA package,
and reboot if it does help
b) uninstall the NVIDIA-driver
# pkgrm NVDAgraphics NVDAgraphicsr
and check one of our newly packaged OI drivers
# pkg install nvidia-390
or
# pkg install nvidia-460
Please be sure not to be on 4K resolution as there is a memory issue.
Does your card+monitor support 4K or other very high resolution?
Stephan
_______________________________________________
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
