someuser77
Dabbler
- Joined
- Oct 1, 2011
- Messages
- 12
Hello,
I'm using FreeNAS-8.3.0-RELEASE-p1-x64 (r12825) on an AMD E-350 Processor with 4GB of RAM and 2 2TB HDDs that mirror each other and from time to time usually under heavy load the machine crashes and when attaching a monitor I see the error:
"kernel: panic: spin lock held too long"
Looking online I found out it is usually related to a bug in powerd in version 7 of FreeBSD/NAS.
Considering I'm using version 8 and powerd is disabled for me I find it hard to find the source of the problem.
Usually i'm witnessing it when writing and reading large files simultaneously and today it happened during a zpool scrub operation.
I found some open bugs but for an older version and the fixes there seem unrelated as powerd is disabled and I'm pretty sure AMD doesn't have hyper threading.
The server is rarely under heavy load and is used on occasion so I don't necessarily need the latest and greatest.
Is there anything I can do to resolve this issue?
I'm using FreeNAS-8.3.0-RELEASE-p1-x64 (r12825) on an AMD E-350 Processor with 4GB of RAM and 2 2TB HDDs that mirror each other and from time to time usually under heavy load the machine crashes and when attaching a monitor I see the error:
"kernel: panic: spin lock held too long"
Looking online I found out it is usually related to a bug in powerd in version 7 of FreeBSD/NAS.
Considering I'm using version 8 and powerd is disabled for me I find it hard to find the source of the problem.
Usually i'm witnessing it when writing and reading large files simultaneously and today it happened during a zpool scrub operation.
I found some open bugs but for an older version and the fixes there seem unrelated as powerd is disabled and I'm pretty sure AMD doesn't have hyper threading.
The server is rarely under heavy load and is used on occasion so I don't necessarily need the latest and greatest.
Is there anything I can do to resolve this issue?