panic: attempt to execute user address 0x0 in supervisor mode

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

panic: attempt to execute user address 0x0 in supervisor mode

Olivier ANTOINE-2
Hi,

A few weeks ago, on June 5th to be precise, I had a crash giving this
message on my Thinkpad E130:
"panic: attempt to execute user address 0x0 in supervisor mode"

While I was playing with VMD(8).

 I updated to the most recent snapshot and a few days went by without
any problems. I thought the problem fixed.

Then on August 12 again a crash with the same message but I can't
remember the circumstances.

Then on August 18 by doing OPENRSYNC(1), then another by doing X11
Forwarding on a VM

Seeing no link between my uses and crashes, I looked for a method to
reproduce the problem.

I noticed that I had a good chance of success by launching a
GLXGEARS(1) in an XEPHYR(1) in X11 Forward on a VM. After a few
minutes (less than a quarter of an hour), I get the message:
"panic: attempt to execute user address 0x0 in supervisor mode"

I launch:
$ ssh -X myvm 'startx -- /usr/X11R6/bin/Xephyr +iglx -fullscreen'
And in a Xterm launch glxgears and wait the hypervisor panic

Sometimes I only have this message, sometimes I have a DDB and some information.

Now I take pictures and I finally noticed that almost every time,
there is a mention of "pagedaemon".

I tried to reproduce this panic on a Thinkpad X220i but without
success. On the other hand, on this machine the VM reboots silently
after a few minutes. This could be the subject of another report.

Here is the last panic from the following kernel (from photo):
kern.version=OpenBSD 6.6-beta (GENERIC.MP) #247: Sat Aug 24 16:41:52 MDT 2019
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP

panic: attempt to execute user address 0x0 in supervisor mode
Stopped at db_enter+0x10: popq %rbp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*513883 29076 0 0x14000 0x200 0K pagedaemon
 504082 32534 0 0x14000 0x200 2  drmwq
db_enter() at db_enter+0x10
panic() at panic+0x128
pageflttrap() at pageflttrap+0x2db
kerntrap(ffff800022710bb0) at kerntrap+0x91
alltraps_kern_meltdown(6,ffffffff81f2ff00,0,10,fffffd8108746180,ffff800022710e34)
at alltraps_kern_meltdown+0x7b
0(ffffffff81f6f780,fffffd8108746180,ffff800022710e20,ffff800022710e34,90,0) at 0
uvmpd_scan_inactive(ffffffff81fd6320) at uvmpd_scan_inactive+0x4af
uvmpd_scan() at uvmpd_scan+0xc0
uvm_pageout(ffff8000ffff4500) at uvm_pageout+0x385
end trace frame: 0x0, count: 6

Since it seems hardware related here is a pcidump:
Domain /dev/pci0:
 0:0:0: Intel Core 3G Host
 0:2:0: Intel HD Graphics 4000
 0:20:0: Intel 7 Series xHCI
 0:22:0: Intel 7 Series MEI
 0:26:0: Intel 7 Series USB
 0:27:0: Intel 7 Series HD Audio
 0:28:0: Intel 7 Series PCIE
 0:28:1: Intel 7 Series PCIE
 0:28:2: Intel 7 Series PCIE
 0:28:5: Intel 7 Series PCIE
 0:29:0: Intel 7 Series USB
 0:31:0: Intel HM77 LPC
 0:31:2: Intel 7 Series AHCI
 0:31:3: Intel 7 Series SMBus
 3:0:0: Realtek 8188CE
 4:0:0: Realtek RTS5209 Card Reader
 9:0:0: Realtek 8168

inteldrm issue like this one?
https://marc.info/?l=openbsd-bugs&m=155612010109416

Attached: dmesg from thinkpad E130 and a few pictures showing panic

Cheers,

dmesg (11K) Download Attachment
IMG_20190826_221309_r.jpg (189K) Download Attachment
IMG_20190818_110349_r.jpg (219K) Download Attachment
IMG_20190818_223922_r.jpg (203K) Download Attachment