Re: Kernel panic on PowerEdge 1950 under certain stress load
- From: Kris Kennaway <kris@xxxxxxxxxxx>
- Date: Mon, 24 Sep 2007 21:15:44 +0200
Ivan Voras wrote:
Benjie Chen wrote:
Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin
c066c7b4 T _mtx_lock_spin
c066c85c T _mtx_unlock_sleep
So this could mean that independent stress tests will not result in panic if
there aren't enough concurrency to cause the problem.
When you get a kernelbacktrace, see if it's the same as the one mentioned here:
http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.html
Surely it cannot be since it involves a different function ;-)
Kris
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Kernel panic on PowerEdge 1950 under certain stress load
- From: Ivan Voras
- Re: Kernel panic on PowerEdge 1950 under certain stress load
- References:
- Kernel panic on PowerEdge 1950 under certain stress load
- From: Benjie Chen
- Re: Kernel panic on PowerEdge 1950 under certain stress load
- From: Ivan Voras
- Kernel panic on PowerEdge 1950 under certain stress load
- Prev by Date: Re: linuxolator problem on i386
- Next by Date: Re: Kernel panic on PowerEdge 1950 under certain stress load
- Previous by thread: Re: Kernel panic on PowerEdge 1950 under certain stress load
- Next by thread: Re: Kernel panic on PowerEdge 1950 under certain stress load
- Index(es):