The computer keeps crashing during the compilation process of chromium-123.0.6312.58_1, but never crashed when I was building version 123.0.6312.58!

Today, I set powerd++ to -H 110:115 -a max, ran "poudriere ports -u", and after setting the number of make jobs to 8, setting USE_TMPFS to all, and keeping ccache enabled, I ran "poudriere bulk -j 15amd64 -v www/chromium". Poudriere was required to rebuild 24 ports, including chromium itself (exactly the same version that I built yesterday). After poudriere built 23 ports and started building chromium, the computer crashed a few minutes later because of the "page fault" panic. I set the number of make jobs to 7 and kept all the other settings the same. There was no panic this time and poudriere finished building chromium after 2 hours and 33 minutes.

Crivens said:
Or you monitor the core temperature
Click to expand...

I gotta read some manual page to figure out how to do it.

Crivens said:
maybe you simply need to clean the fans and some new thermal paste
Click to expand...

Oh boy... To do this, I would need to open the desktop case harboring computer components. I am slightly afraid I will damage something... Why can't they just build PCs containing cooling systems that always do their job properly?
 
Oleg_NYC said:
Why can't they just build PCs containing cooling systems that always do their job properly?
Click to expand...

You have not verified that you are actually looking at a heat problem. You need some actual hardware testing. Playing with load and power will not fix your broken computer.
 
Try sysctrl -a|grep temp. With bash you can use the internal 'watch' command.
 
Crivens said:
The CPU will force a hard stop before it catches fire when the temperature sensor on die tell it to.
Click to expand...
Older CPUs made a nice sound and smell instead 😏. I've never seen one "catch fire" though 😉

Seriously, how about "fix the cooling of that system"? Start with simple mechanical checks (I once had some plastic holding the CPU cooler and fan broken...). Probably not a thing any more today, but I've seen people applying literal TONS of thermal grease (the more the better, right? 🤦‍♂️) ...

It's a shame that with many notebooks, "overheating" on 100% CPU is a "normal" thing nowadays. I like my systems designed to run on full power 24/7 if necessary. That's how you designed cooling "back in the days"....
 
cracauer@ said:
You have not verified that you are actually looking at a heat problem. You need some actual hardware testing. Playing with load and power will not fix your broken computer.
Click to expand...

Earlier you mentioned the possibility of memory corruption. But this type of problem will very likely still prevent you from compiling something even if you lower the number of make jobs used for your compilation process... Memtest86+ refused to run after I escaped to the loader prompt and tried to load it... Mprime kept running for a long time, but since I wasn't even sure what I wanted to find with it, I stopped it. I kept seeing "passed" messages when I was running it. Do some of these tools have a test that puts stress on a CPU to find out how likely it is to overheat?
 
Oleg_NYC said:
Do some of these tools have a test that puts stress on a CPU to find out how likely it is to overheat?
Click to expand...
Put stress on it the same way you did before: Run a (massively parallel and large) build job.

Observe temperatures, e.g. simply by logging them once a second.

Analyze "post mortem" 😉
 
Oleg_NYC said:
Earlier you mentioned the possibility of memory corruption. But this type of problem will very likely still prevent you from compiling something even if you lower the number of make jobs used for your compilation process... Memtest86+ refused to run after I escaped to the loader prompt and tried to load it... Mprime kept running for a long time, but since I wasn't even sure what I wanted to find with it, I stopped it. I kept seeing "passed" messages when I was running it. Do some of these tools have a test that puts stress on a CPU to find out how likely it is to overheat?
Click to expand...

Ah, so you did run mprime. However, the trick is that you need to run one instance of mprime for every CPU core you have. Mprime puts a lot worse load than compilation, it is a very good stress test.

If memtest86+ doesn't load try memtest86 or try to find a new version of +. Sometimes takes a bit of fiddling.

As see above, the sysctl for the temperature. You want to know at what temperature you crash. If it is a purely thermal problem.
 
Oleg_NYC said:
Why can't they just build PCs containing cooling systems that always do their job properly?
Click to expand...
There are some prebuilt ones on the market if you know where to look... but cooling systems are aimed primarily at enthusiasts who can put their own machine together from aftermarket parts.
 
cracauer@ said:
Ah, so you did run mprime. However, the trick is that you need to run one instance of mprime for every CPU core you have. Mprime puts a lot worse load than compilation, it is a very good stress test.
Click to expand...
You mean, if I have 10 cores, 10 instances of mprime have to run simultaneously? By the way, this computer has the Asus z590-p Wifi motherboard with the i9-10900K cpu and 64 gb of ram... Can mprime test how likely it is for the RAM to overheat? I don't know what command I should type if I want to test either the CPU or the RAM how likely they are to overheat, etc.
 
zirias@ said:
Seriously, how about "fix the cooling of that system"? Start with simple mechanical checks (I once had some plastic holding the CPU cooler and fan broken...). Probably not a thing any more today, but I've seen people applying literal TONS of thermal grease (the more the better, right? 🤦‍♂️) ...
Click to expand...
I'd imagine your typical aftermarket heat sink mount will just squeeze any excessive thermal paste from the CPU heat spreader. (I don't want to test it.)
 
Oleg_NYC said:
You mean, if I have 10 cores, 10 instances of mprime have to run simultaneously? By the way, this computer has the Asus z590-p Wifi motherboard with the i9-10900K cpu and 64 gb of ram... Can mprime test how likely it is for the RAM to overheat? I don't know what command I should type if I want to test either the CPU or the RAM how likely they are to overheat, etc.
Click to expand...

RAM is better stressed with SuperPi.

If you have hyperthreading I would make runs with both 10 and 20 instances of mprime. SuperPi only needs one instance.
 
Oleg_NYC said:
You mean, if I have 10 cores, 10 instances of mprime have to run simultaneously? By the way, this computer has the Asus z590-p Wifi motherboard with the i9-10900K cpu and 64 gb of ram...
Click to expand...
That's what I was curious to know. (20 vcore is not a very common configuration for a desktop)
That thing runs at 125W.

"cooling systems", i.e. is these funny towers on top of the cpu, or even watercooled stuff, is for gamers.
Running full power full system sustained for hours, that is a different thing, that is server usecase.
And cooling a server is a simple question: how many cu ft per minute can be pushed through? Because if they don't get through, the things inside will slowly get hotter and hotter - and that concerns all the things inside. The fancy cpu cooler doesn't help, the thermal paste quality is unimportant - real servers may not even have fans on the cpus, they're cooled solely by the airstream.
So, this requires strong and fast fans, and it will always get noisy. But nobody wants a noisy desktop, so you don't easily get a readymade machine that can run 125W server load sustained, unless it's marketed as server.
 
Oh, please. Those K models come without the pathetic Intel cooler, because even Intel realizes it won't cut it. 125 Intel watts is a 1+ kg dual-tower heat sink territory (for air coolers).
 
cracauer@ said:
If memtest86+ doesn't load try memtest86 or try to find a new version of +. Sometimes takes a bit of fiddling.
Click to expand...
Wow, the port version of memtest86+ refused to load, but I found an easy solution to this problem: I downloaded an efi file from memtest.org (version 7 of 64-bit memtest86+), and now memtest86+ is running and checking my memory. Does it only check for memory corruption or can it also run a test that checks how likely it is for the RAM to overheat?.. The test has been running for 23 minutes already. I wonder when it concludes. I will explore mprime's possibilities later. Its menu options are not easy to understand.
 
Hint: if you suspect RAM problems, memtest86+ should run a long time, at least 4 hours, or overnight if you can.
 
tingo said:
at least 4 hours
Click to expand...

4 hours?.. I added memtest64.efi to the boot menu using the command efibootmgr -c -a -l /mnt/memtest64.efi -L memtest and after rebooting, I selected memtest from the boot menu. After I did it, the testing program didn't ask me any questions; it immediately started testing the memory and after less than 1 hour and 30 minutes of testing it, it printed PASS in big letters.

Crivens said:
Try sysctrl -a|grep temp
Click to expand...

I disabled ccache in poudriere.conf, added the -C option to "poudriere bulk -C -j 15amd64 -v www/chromium" (after making sure MAKE_JOBS_NUMBER=20 and USE_TMPFS=all were mentioned in the configuration files), and by the time the computer crashed due to the panic, I saw values such as these:
Code: 
dev.cpu.19.temperature: 93.0C
dev.cpu.17.temperature: 92.0C
dev.cpu.15.temperature: 100.0C
dev.cpu.13.temperature: 98.0C
dev.cpu.11.temperature: 96.0C
dev.cpu.9.temperature: 98.0C
dev.cpu.7.temperature: 93.0C
dev.cpu.5.temperature: 98.0C
dev.cpu.3.temperature: 84.0C
dev.cpu.1.temperature: 89.0C
dev.cpu.18.temperature: 94.0C
dev.cpu.16.temperature: 93.0C
dev.cpu.14.temperature: 99.0C
dev.cpu.12.temperature: 99.0C
dev.cpu.10.temperature: 96.0C
dev.cpu.8.temperature: 98.0C
dev.cpu.6.temperature: 93.0C
dev.cpu.4.temperature: 100.0C
dev.cpu.2.temperature: 85.0C
dev.cpu.0.temperature: 89.0C

I guess because of dev.cpu.*coretemp.tjmax's value equaling 100.0C, none of the cores were allowed to become hotter than 100 degrees. By the way, I solved the problem of not being able to save core.txt files into /var/crash, so, after the computer crashed, this is what I saw in core.txt:

Code: 
__curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
57        __asm("movq %%gs:%P1,%0" : "=r" (td) : "n" (offsetof(struct pcpu,
(kgdb) #0  __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
        td = <optimized out>
#1  doadump (textdump=textdump@entry=1)
    at /usr/src/sys/kern/kern_shutdown.c:403
        error = 0
        coredump = <optimized out>
#2  0xffffffff80b519e9 in kern_reboot (howto=260)
    at /usr/src/sys/kern/kern_shutdown.c:521
        once = 0
#3  0xffffffff80b51ef2 in vpanic (fmt=0xffffffff8118c3b4 "%s",
    ap=ap@entry=0xfffffe0233a1da30) at /usr/src/sys/kern/kern_shutdown.c:973
        buf = "page fault", '\000' <repeats 245 times>
        __pc = <optimized out>
        __pc = <optimized out>
        __pc = <optimized out>
        other_cpus = {__bits = {1048447, 0 <repeats 15 times>}}
        td = 0xfffff80f6d6c1740
        bootopt = <unavailable>
        newpanic = <optimized out>
#4  0xffffffff80b51d43 in panic (fmt=<unavailable>)
    at /usr/src/sys/kern/kern_shutdown.c:889
        ap = {{gp_offset = 16, fp_offset = 48,
            overflow_arg_area = 0xfffffe0233a1da60,
            reg_save_area = 0xfffffe0233a1da00}}
#5  0xffffffff8102d5ff in trap_fatal (frame=0xfffffe0233a1db20, eva=4466)
    at /usr/src/sys/amd64/amd64/trap.c:950
        __pc = <optimized out>
        __pc = <optimized out>
        __pc = <optimized out>
        softseg = {ssd_base = 0, ssd_limit = 1048575, ssd_type = 27,
          ssd_dpl = 0, ssd_p = 1, ssd_long = 1, ssd_def32 = 0, ssd_gran = 1}
        code = 2
        ss = 0
        type = <optimized out>
        gdt = <optimized out>
        handled = <optimized out>
#6  0xffffffff8102d64f in trap_pfault (frame=0xfffffe0233a1db20,
    usermode=false, signo=<optimized out>, ucode=<optimized out>)
    at /usr/src/sys/amd64/amd64/trap.c:758
        __pc = <optimized out>
        __pc = <optimized out>
        __pc = <optimized out>
        td = 0xfffff80f6d6c1740
        p = <optimized out>
        eva = 4466
        map = <optimized out>
        ftype = <optimized out>
        rv = <optimized out>
#7  <signal handler called>
No locals.
#8  0xffffffff80ecd549 in vm_fault_allocate (fs=fs@entry=0xfffffe0233a1dc88)
    at /usr/src/sys/vm/vm_fault.c:1230
        res = <optimized out>
        dset = <optimized out>
#9  0xffffffff80ecc2b6 in vm_fault_object (fs=0xfffffe0233a1dc88,
    behindp=0xfffffe0233a1dc7c, aheadp=0xfffffe0233a1dc80)
    at /usr/src/sys/vm/vm_fault.c:1502
        res = <optimized out>
        dead = <optimized out>
        _v = <optimized out>
        _v = <optimized out>
        _tid = <optimized out>
        _v = <optimized out>
#10 vm_fault (map=map@entry=0xfffff806bf8814d0,
    vaddr=vaddr@entry=62497257566208, fault_type=fault_type@entry=2 '\002',
    fault_flags=fault_flags@entry=0, m_hold=m_hold@entry=0x0)
    at /usr/src/sys/vm/vm_fault.c:1636
        ahead = 7
        behind = -2048
        fs = {vaddr = 62497257566208, m_hold = 0x0, fault_type = 2 '\002',
          prot = <optimized out>, fault_flags = 0, wired = 0,
          oom_start_time = {tv_sec = -2135393480, tv_usec = -8729832712384},
          oom_started = false, nera = -1, can_read_lock = true, m_cow = 0x0,
          object = 0xfffff80e9999b420, pindex = 4451, m = 0x0,
          first_object = 0xfffff80e9999b420, first_pindex = 4451,
          first_m = 0x0, map = 0xfffff806bf8814d0, entry = 0xfffff80c60882de0,
          map_generation = 496, lookup_still_valid = true, vp = 0x0}
        faultcount = <optimized out>
        hardfault = <optimized out>
        rv = <optimized out>
        res = <optimized out>
        res_next = <optimized out>
#11 0xffffffff80ecbdcb in vm_fault_trap (map=0xfffff806bf8814d0,
    vaddr=vaddr@entry=62497257568512, fault_type=<optimized out>,
    fault_flags=fault_flags@entry=0, signo=0xfffffe0233a1df00,
    ucode=0xfffffe0233a1df04) at /usr/src/sys/vm/vm_fault.c:710
        result = <optimized out>
#12 0xffffffff8102d7d6 in trap_pfault (frame=frame@entry=0xfffffe0233a1df40,
    usermode=true, signo=0x8a7a7, signo@entry=0xfffffe0233a1df00,
    ucode=0xfffffe0233a1dcf0, ucode@entry=0xfffffe0233a1df04)
    at /usr/src/sys/amd64/amd64/trap.c:843
        __pc = <optimized out>
        __pc = <optimized out>
        __pc = <optimized out>
        td = 0xfffff80f6d6c1740
        p = <optimized out>
        eva = 62497257568512
        map = 0xfffff80e9999b428
        ftype = 99 'c'
        rv = <optimized out>
#13 0xffffffff8102cd6d in trap (frame=0xfffffe0233a1df40)
    at /usr/src/sys/amd64/amd64/trap.c:382
        __pc = <optimized out>
        __pc = <optimized out>
        __pc = <optimized out>
        ksi = {ksi_link = {tqe_next = 0xfffff80f6d6c1740, tqe_prev = 0x0},
          ksi_info = {si_signo = 70, si_errno = 0, si_code = 1837691904,
            si_pid = -512, si_uid = 1835800384, si_status = -2033,
            si_addr = 0xfffffe0233a1de80, si_value = {sival_int = -2136097926,
              sival_ptr = 0xffffffff80adbb7a <statclock+314>,
              sigval_int = -2136097926,
              sigval_ptr = 0xffffffff80adbb7a <statclock+314>}, _reason = {
              _fault = {_trapno = 0}, _timer = {_timerid = 0, _overrun = 0},
              _mesgq = {_mqd = 0}, _poll = {_band = 0}, _capsicum = {
                _syscall = 0}, __spare__ = {__spare1__ = 0, __spare2__ = {70,
                  0, 0, 0, 7, 0, 866246336}}}}, ksi_flags = -2136094690,
          ksi_sigq = 0xc074d7b40bf}
        signo = 0
        ucode = 0
        td = 0xfffff80f6d6c1740
        p = 0xfffffe01e97d2040
        dr6 = 0
        type = 12
        addr = 61200482867872
        pf = <optimized out>
        i = <optimized out>
#14 <signal handler called>
No locals.
#15 0x000037a9590a9aa0 in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x37a97fc80730
(kgdb) (kgdb) Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146874 (CPU 0)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xffffffff81a400c0 <nmi0_stack+3888>)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a958ff6ea4 in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a96d3b74a0

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146884 (CPU 1)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d833f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a95706a2ea in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a982d947c0

Tracing command "c++", '\000' <repeats 16 times> pid 18803 tid 105172 (CPU 2)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d842f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000000000478df49 in ?? ()
Backtrace stopped: Cannot access memory at address 0x827566f60

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146876 (CPU 3)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d851f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a95817761f in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a972248a50

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146880 (CPU 4)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d860f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a9583f7f70 in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a97eeaba50

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146879 (CPU 5)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d86ff30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a9571dec15 in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a97762ea88

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146886 (CPU 6)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d87ef30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a958ff6d1f in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a983c671a0

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146882 (CPU 7)
#0  __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:57
#1  doadump (textdump=textdump@entry=1)
    at /usr/src/sys/kern/kern_shutdown.c:403
#2  0xffffffff80b519e9 in kern_reboot (howto=260)
    at /usr/src/sys/kern/kern_shutdown.c:521
#3  0xffffffff80b51ef2 in vpanic (fmt=0xffffffff8118c3b4 "%s",
    ap=ap@entry=0xfffffe0233a1da30) at /usr/src/sys/kern/kern_shutdown.c:973
#4  0xffffffff80b51d43 in panic (fmt=<unavailable>)
    at /usr/src/sys/kern/kern_shutdown.c:889
#5  0xffffffff8102d5ff in trap_fatal (frame=0xfffffe0233a1db20, eva=4466)
    at /usr/src/sys/amd64/amd64/trap.c:950
#6  0xffffffff8102d64f in trap_pfault (frame=0xfffffe0233a1db20,
    usermode=false, signo=<optimized out>, ucode=<optimized out>)
    at /usr/src/sys/amd64/amd64/trap.c:758
#7  <signal handler called>
#8  0xffffffff80ecd549 in vm_fault_allocate (fs=fs@entry=0xfffffe0233a1dc88)
    at /usr/src/sys/vm/vm_fault.c:1230
#9  0xffffffff80ecc2b6 in vm_fault_object (fs=0xfffffe0233a1dc88,
    behindp=0xfffffe0233a1dc7c, aheadp=0xfffffe0233a1dc80)
    at /usr/src/sys/vm/vm_fault.c:1502
#10 vm_fault (map=map@entry=0xfffff806bf8814d0,
    vaddr=vaddr@entry=62497257566208, fault_type=fault_type@entry=2 '\002',
    fault_flags=fault_flags@entry=0, m_hold=m_hold@entry=0x0)
    at /usr/src/sys/vm/vm_fault.c:1636
#11 0xffffffff80ecbdcb in vm_fault_trap (map=0xfffff806bf8814d0,
    vaddr=vaddr@entry=62497257568512, fault_type=<optimized out>,
    fault_flags=fault_flags@entry=0, signo=0xfffffe0233a1df00,
    ucode=0xfffffe0233a1df04) at /usr/src/sys/vm/vm_fault.c:710
#12 0xffffffff8102d7d6 in trap_pfault (frame=frame@entry=0xfffffe0233a1df40,
    usermode=true, signo=0x8a7a7, signo@entry=0xfffffe0233a1df00,
    ucode=0xfffffe0233a1dcf0, ucode@entry=0xfffffe0233a1df04)
    at /usr/src/sys/amd64/amd64/trap.c:843
#13 0xffffffff8102cd6d in trap (frame=0xfffffe0233a1df40)
    at /usr/src/sys/amd64/amd64/trap.c:382
#14 <signal handler called>
#15 0x000037a9590a9aa0 in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a97fc80730

Tracing command "idle\000l", '\000' <repeats 13 times> pid 11 tid 100011 (CPU 8)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d89cf30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  acpi_cpu_idle_mwait (mwait_hint=0)
    at /usr/src/sys/x86/x86/cpu_machdep.c:292
#5  0xffffffff804cc1d8 in acpi_cpu_idle (sbt=<optimized out>)
    at /usr/src/sys/dev/acpica/acpi_cpu.c:1155
#6  0xffffffff80fed546 in cpu_idle_acpi (sbt=3171716845)
    at /usr/src/sys/x86/x86/cpu_machdep.c:588
#7  0xffffffff80fed5fd in cpu_idle (busy=0)
    at /usr/src/sys/x86/x86/cpu_machdep.c:677
#8  0xffffffff80b88596 in sched_idletd (dummy=dummy@entry=0x0)
    at /usr/src/sys/kern/sched_ule.c:3061
#9  0xffffffff80b0a54f in fork_exit (
    callout=0xffffffff80b88020 <sched_idletd>, arg=0x0,
    frame=0xfffffe006ab83f40) at /usr/src/sys/kern/kern_fork.c:1157
#10 <signal handler called>
#11 0x5bdf1663ba427cf0 in ?? ()
Backtrace stopped: Cannot access memory at address 0xa78e5f11ff9233f0

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146883 (CPU 9)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d8abf30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a95913e75e in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a9825388b0

Tracing command "c++", '\000' <repeats 16 times> pid 18531 tid 101457 (CPU 10)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d8baf30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x00000000048a9357 in ?? ()
Backtrace stopped: Cannot access memory at address 0x8274a2080

Tracing command "idle\000l", '\000' <repeats 13 times> pid 11 tid 100014 (CPU 11)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d8c9f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  acpi_cpu_idle_mwait (mwait_hint=0)
    at /usr/src/sys/x86/x86/cpu_machdep.c:292
#5  0xffffffff804cc1d8 in acpi_cpu_idle (sbt=<optimized out>)
    at /usr/src/sys/dev/acpica/acpi_cpu.c:1155
#6  0xffffffff80fed546 in cpu_idle_acpi (sbt=2882949011)
    at /usr/src/sys/x86/x86/cpu_machdep.c:588
#7  0xffffffff80fed5fd in cpu_idle (busy=0)
    at /usr/src/sys/x86/x86/cpu_machdep.c:677
#8  0xffffffff80b88596 in sched_idletd (dummy=dummy@entry=0x0)
    at /usr/src/sys/kern/sched_ule.c:3061
#9  0xffffffff80b0a54f in fork_exit (
    callout=0xffffffff80b88020 <sched_idletd>, arg=0x0,
    frame=0xfffffe006ab92f40) at /usr/src/sys/kern/kern_fork.c:1157
#10 <signal handler called>
#11 0x6b00f12563229a81 in ?? ()
Backtrace stopped: Cannot access memory at address 0x2a7cc03a16dbeba4

Tracing command "idle\000l", '\000' <repeats 13 times> pid 11 tid 100015 (CPU 12)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d8d8f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  acpi_cpu_idle_mwait (mwait_hint=0)
    at /usr/src/sys/x86/x86/cpu_machdep.c:292
#5  0xffffffff804cc1d8 in acpi_cpu_idle (sbt=<optimized out>)
    at /usr/src/sys/dev/acpica/acpi_cpu.c:1155
#6  0xffffffff80fed546 in cpu_idle_acpi (sbt=386491735)
    at /usr/src/sys/x86/x86/cpu_machdep.c:588
#7  0xffffffff80fed5fd in cpu_idle (busy=0)
    at /usr/src/sys/x86/x86/cpu_machdep.c:677
#8  0xffffffff80b88596 in sched_idletd (dummy=dummy@entry=0x0)
    at /usr/src/sys/kern/sched_ule.c:3061
#9  0xffffffff80b0a54f in fork_exit (
    callout=0xffffffff80b88020 <sched_idletd>, arg=0x0,
    frame=0xfffffe006ab97f40) at /usr/src/sys/kern/kern_fork.c:1157
#10 <signal handler called>
#11 0x241762df007c77f7 in ?? ()
Backtrace stopped: Cannot access memory at address 0xac8aacd78fe9bf1d

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146885 (CPU 13)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d8e7f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a958a8b361 in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a983283db0

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146881 (CPU 14)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d8f6f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a95874b07f in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a97f7510f0

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146875 (CPU 15)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d905f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a958ff3b15 in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a9707ea188

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146877 (CPU 16)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d914f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a958bd9d09 in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a973dcd608

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146878 (CPU 17)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d923f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a95930b3cb in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a975414448

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146873 (CPU 18)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d932f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a9568e0461 in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a967e5f670

Tracing command "rustc", '\000' <repeats 14 times> pid 19183 tid 146888 (CPU 19)
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1527
#1  0xffffffff80ff8458 in ipi_nmi_handler ()
    at /usr/src/sys/x86/x86/mp_x86.c:1484
#2  0xffffffff8102c94f in trap (frame=0xfffffe006d941f30)
    at /usr/src/sys/amd64/amd64/trap.c:235
#3  <signal handler called>
#4  0x000037a958a7ace9 in ?? ()
Backtrace stopped: Cannot access memory at address 0x37a9666e8020

(kgdb)
 
You must log in or register to reply here.
Back
Top