Bug #2560

latest 3.5 is now locking up consistently with cache_lock: blocked messages

Added by marino over 1 year ago. Updated over 1 year ago.

Status:ClosedStart date:05/14/2013
Priority:HighDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

My i386 machine is now unstable. After a few minutes of heavy use (lots of disk action) it freezes and can't be coaxed out.
Alt-Fx changes to another tty still work, cntl-t still works.
verbose boot is set, there are repeating messages periodically:
[diagnostic] cache_lock: blocked on 0xde0684a8 80000001 ""

I was able to break into ddb and create a dump with "call dumpsys"
I will upload that in a bit.

This all started after recent kernel/world updates.

History

#1 Updated by marino over 1 year ago

After 3 times on the latest kernel, I tried again on the last of Release 3.4 branch.
Same thing.
It's starting to look like a hardware issue. The symptoms are similar to what happened when the Crucial M4 firmware bug was hit.

I uploaded the core.txt here:
http://leaf.dragonflybsd.org/~marino/core/core.cache-lock-block.txt

Core itself available upon request (71M, I can upload to leaf quickly)

#2 Updated by marino over 1 year ago

  • Status changed from New to Closed

I love the smell of nailed bug in the morning....
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/6a92f264327c02148673ae2da128dce5c7366029
Thanks, Matt.

Also available in: Atom PDF