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

[Thomas E. Spanjaard]

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20100924/d1df05c4/signature.pgp