[DragonFlyBSD - Bug #2971] kernel 4.7: buildworld causes panic: Bad link elm 0xffffffe1c766d500 prev->next != elm

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #2971 has been updated by peeter.


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

--




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

* Author: peeter
* Status: Feedback
* 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