[Bug 265266] Random sudden reboots laptop running FreeBSD

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265266

--- Comment #2 from Jaskie <jiangjun12321@gmail.com> ---
(In reply to Graham Perrin from comment #1)

OK I uploaded the vmcore.1 file at: https://www.filemail.com/d/uqrqycpedopzkhl
(And also at https://filetransfer.io/data-package/3NjHx9bK#link as a backup)


% freebsd-version -kru ; uname -aKU                                             
13.1-RELEASE
13.1-RELEASE
13.1-RELEASE
FreeBSD freebsd.asus 13.1-RELEASE FreeBSD 13.1-RELEASE
releng/13.1-n250148-fc952ac2212 GENERIC amd64 1301000 1301000


% pkg -vv | grep -e url -e version
url             :
"pkg+http://mirrors.ustc.edu.cn/freebsd-pkg/FreeBSD:13:amd64/latest",

% pkg prime-origins | sort | grep -e drm -e gpu
(Returns nothing)

% pkg info |grep nvidia
nvidia-driver-340-340.108_3    NVidia graphics card binary drivers for hardware
OpenGL rendering
nvidia-xconfig-470.86          Tool to manipulate X configuration files for the
NVidia driver

% pciconf -lv |grep VGA -B 4                                                   
                      @22:02
vgapci0@pci0:1:0:0:     class=0x030000 rev=0xa1 hdr=0x00 vendor=0x10de
device=0x0654 subvendor=0x1043 subdevice=0x14a2
    vendor     = 'NVIDIA Corporation'
    device     = 'G96CM [GeForce GT 220M]'
    class      = display
    subclass   = VGA



I have a small script I use to turn on/off my second monitor connect via a HDMI
cable as:

% cat ~/bin/hdmi.sh 

#! /usr/bin/env bash
if xrandr --listmonitors |grep -q HDMI; then
    xrandr --output HDMI-0 --off
else
  xrandr --output HDMI-0 --off
  xrandr --output HDMI-0 --auto
  xrandr --output HDMI-0 --right-of LVDS-0
  xrandr --output HDMI-0 --brightness 1.25
fi



And last night just before I went to bed I tried to turn off the 2nd moniter by
running the script as I usually did, my laptop went straight into a reboot
again the second I ran it. I ended up with another crash report at
/var/crash/{info.2,vmcore.2,core.txt.2} and compared it with crash 1 (the one I
reported here). I found the two were almost the same except for general message
such as dumptime, dumplength and addr in info file and :

% doas diff /var/crash/info.2 /var/crash/info.1
4c4
<   Dump Length: 524226560
---
>   Dump Length: 970711040
7c7
<   Dumptime: 2022-07-17 23:51:04 +0000
---
>   Dumptime: 2022-07-15 22:34:53 +0000
11,13c11,13
<   Panic String: vm_fault_lookup: fault on nofault entry, addr:
0xfffffe00acd45000
<   Dump Parity: 583238499
<   Bounds: 2
---
>   Panic String: vm_fault_lookup: fault on nofault entry, addr: 0xfffffe00acd87000
>   Dump Parity: 3347612783
>   Bounds: 1

% doas diff /var/crash/core.txt.1 /var/crash/core.txt.2
3c3
< Unable to find matching kernel for /var/crash/vmcore.1
---
> Unable to find matching kernel for /var/crash/vmcore.2


Hope the information helps.

-- 
You are receiving this mail because:
You are the assignee for the bug.