FreeBSD 13 system crashed, please help to remedy the error!!!

[kaladhari]

Hi FreeBSD Forum,

Pls help,

attached is /var/crash/core.txt.2

Regards,
Paramjeet Singh

 

[kaladhari]

hi everyone,

I am still waiting for reply.....

 

[Andrey Lanin]

a quick google search gives this - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266315

 

[Alain De Vos]

What is the hardware ?
Normally it is as this moment 13.2

 

[kaladhari]

....


Hardware is Dell system, with core i5

FreeBSD 13.1-RELEASE-p6 GENERIC amd64

Request a solution if any...

 

[SirDice]

Hardware is Dell system, with core i5

You're going to need to provide more details, which Dell model? And which Core i5? There are 13 generations of the Core based Intel CPUs.

 

[Charlie_]

which Core i5?

According to core.2.txt, it's i5-2540M.

Maybe it's Sandybridge's known bug.
https://www.spinics.net/lists/intel-gfx/msg314710.html
https://www.phoronix.com/news/Intel-SNB-Disable-RC6p-Again
It' in drm-510-kmod.

 

[ralphbsz]

Is the crash repeatable?

Does the crash happen if you disable X, and run the system in text mode from the console?

 

[Alain De Vos]

What's in your loader.conf ?

 

[gpw928]

A page fault in kernel mode may have many causes. It could be a bug. Or it could be flaky hardware.

Faced with this problem, I would take note of the advice above. Do the tests and gather the details requested.

There are also quite a few things you can do to help your self. Stress test your system, identify the specific components, systematically reduce the test surface, and try to reproduce the problem reliably.

The steps you should consider repeating (singly, and in combinations) are:

• sysctl -a | grep temperature. It should be under 60C, and anything over 80C is definitely a problem.
• If that doesn't work, google "FreeBSD check temperature" and load the required kernel modules.
• Stress test by flogging all the CPUs as hard as you can with simple Bourne shell infinite loops:

  n=0
  while :
  do  
      n=$((n + 1))
  done&

• Run enough instances to have every CPU 100% active.
• Stress test the video components by continuous screen rendering.
• Shut the system down, put on an anti-static strap, and re-seat all the memory modules.

Keep a written record of the circumstances and results of each test.

If the problem persists, download a Linux bootable ISO onto a thumb drive. Boot your system into a recovery shell and repeat the tests. This may well give you a sense of whether your problem is generic hardware or FreeBSD specific bug.