Bug 250240 - Linux mathematica causes kernel page fault
Summary: Linux mathematica causes kernel page fault
Status: Closed Unable to Reproduce
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.1-RELEASE
Hardware: Any Any
: --- Affects Only Me
Assignee: Edward Tomasz Napierala
URL:
Keywords:
Depends on:
Blocks: 247219
  Show dependency tree / graph
 
Reported: 2020-10-10 04:05 UTC by elronnd
Modified: 2021-07-26 11:15 UTC (History)
2 users (show)

See Also:

Attachments
Output following crash (1.04 KB, text/plain)
2020-10-10 06:34 UTC, elronnd 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description elronnd 2020-10-10 04:05:38 UTC 
Running the linux version of mathematica (a free trial version of which can be acquired at https://www.wolfram.com/mathematica/trial/) consistently causes a crash in drm.  Running intel HD 5500 graphics, and drm-fbsd12.0-kmod-4.16.g20200221.

After finishing with the installer (may need to kill a stalled xdg-related script), run:

env SystemIDList='Linux-x86-64 Linux' PATH=/compat/linux/bin /path/to/mathematica
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2020-10-10 05:02:00 UTC 
We will need more specific information about the exact crash message.
Comment 2 elronnd 2020-10-10 06:34:25 UTC 
Created attachment 218638 [details]
Output following crash
Comment 3 elronnd 2020-10-10 06:36:06 UTC 
(In reply to Mark Linimon from comment #1)

Apologies - the crash isn't in drm after all; there were just some drm-related log messages cluttering up the screen.  The output following the crash is in the attachment (manually transcribed so excuse any typos).  There's also a crash dump at https://elronnd.net/vmcore.bz2
Comment 4 Martin Filla 2020-10-13 08:18:04 UTC 
(In reply to elronnd from comment #0)

You must add backtrace from kernel with debug symbols
sudo kgdb /usr/lib/debug/boot/kernel/kernel.debug /var/crash/vmcore.last
Comment 5 Edward Tomasz Napierala freebsd_committer freebsd_triage 2020-10-13 16:40:49 UTC 
I've just tried it (just a smoke test with "2+2 <shift+enter"), and it appears to work, at least on 13.0-CURRENT.  I wonder... would it be possible for you to test on a newer FreeBSD release, eg 12.2-RC2?
Comment 6 Edward Tomasz Napierala freebsd_committer freebsd_triage 2021-03-11 19:28:34 UTC 
Ping?  Can you reproduce the problem on eg 12.2-RELEASE or 13.0-RC1?