DragonFlyBSD

I'd suggest to run memtest on your system, I'd suspect bad memory sticks.

On Wed, Dec 21, 2016 at 7:46 PM,
<bugtracker-admin@leaf.dragonflybsd.org> wrote:

Issue #2971 has been reported by peeter.

----------------------------------------
Bug #2971: kernel 4.7: buildworld causes panic: Bad link elm 0xffffffe1c766d500 prev->next != elm
http://bugs.dragonflybsd.org/issues/2971

• Author: peeter
• Status: New
• Priority: Normal
• Assignee:
• Category:
• Target version:
  ----------------------------------------
  The panic happened while doing buildworld. I am not entirely sure that the panic is not caused by a hardware error since prior to the panic two CRC errors showed up in /var/log/messages. On the other hand, it seems they might not be caused by a hardware error since prior to the panic I had seen CRC errors a couple of times and reinstalling the system got rid of them. In more detail, the machine has gone the following cycle of couple of times:

1 - system has a panic (related to the kernel module I'm developing)
2 - hammer checkmap starts reporting errors occasionally
3 - then CRC errors show up /var/log/messages
4 - re-install the system and all errors vanish
5 - go back to 1

However, the last time after step 3 "make buildworld" led to this panic.

---Files--------------------------------
hammer-crc-error-crash.txt (9.48 KB)

--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

--
Tomorrow Will Never Die

I ran memtest86 V7.2 from a USB stick and it tested all of the 8GB RAM: so far no errors. I did one pass. Will do another four passes tomorrow when I get back to office.

Another three passes of memtest86 on 8GB RAM: no errors. Seems RAM is fine.

Hello

I believe you can close this. I have no means of testing any more, I've long migrated to HAMMER2. Also, DragonFly has undergone many changes since the report.

Cheers

Peeter

--

I should note that this was not a memory issue. I tested memory very thoroughly. Also, the system has been running very reliably over the recent 1.5 yrs, definitely not a memory problem.

--