Re: current + mpt = panic: Bad link elm 0xffffff80002d6480 next->prev != elm

From: Thomas E. Spanjaard <tgen_at_deepbone.net>
Date: Fri, 24 Sep 2010 22:41:34 +0000
On 09/24/2010 16:42, Marius Strobl wrote:
> On Tue, Jul 20, 2010 at 01:55:28PM +0200, Stle Kristoffersen wrote:
>> I got the timeouts with STABLE as well, that was the reason for me to
>> try out CURRENT. I'm sorry I didn't mention that earlier.
>>
>> My main concern is to get rid of the timeouts, but a panic on one can't be
>> right. How can I debug this further? I can get timeout fairly consistent by
>> putting a bit of load on the drives. If it would help I can also provide
>> remote access.
>>
> 
> FYI, that panic is fixed with r213105.

That doesn't build as module at least. It errors out, because of an
implicit declaration warning of mpt_req_on_pending_list, followed by a
warning of a nested extern declaration of the same (line 853 of
sys/dev/mpt/mpt.c).

Cheers,
-- 
	Thomas E. Spanjaard
	tgen_at_netphreax.net
	tgen_at_deepbone.net


Received on Fri Sep 24 2010 - 20:41:43 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:07 UTC