Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Jun 2009 18:45:56 +0400
From:      pluknet <pluknet@gmail.com>
To:        Ed Maste <emaste@freebsd.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: 6.2 sporadically locks up
Message-ID:  <a31046fc0906170745i51583493kf8b0d9a8bdd6b631@mail.gmail.com>
In-Reply-To: <20090617142952.GA73887@sandvine.com>
References:  <a31046fc0906160323s3e4ec60bxb585bb29f9f3a02a@mail.gmail.com> <200906160830.29721.jhb@freebsd.org> <a31046fc0906160803n284604bcs741e6b038079ed12@mail.gmail.com> <20090617142952.GA73887@sandvine.com>

next in thread | previous in thread | raw e-mail | index | archive | help
2009/6/17 Ed Maste <emaste@freebsd.org>:
> On Tue, Jun 16, 2009 at 07:03:34PM +0400, pluknet wrote:
>
>> As for allpcpu, I often see the picture, when one CPU runs the "irq17:
>> bce1 aacu0" thread
>> and another one runs arcconf. I wonder if that might be a source of
>> bad locking or races, or..
>> The arcconf utility uses ioctl that goes into aac/aacu(4) internals.
>
> Do you see the same result w/ the in-tree aac(4) driver as opposed to
> Adaptec's version?
>
> -Ed
>

[It's quite hard to move back to aac(4) as that requires fstab update
[ aacdu0 -> aacd0]
 and instant reboot, because we use quotas and quotacheck looks into /etc/fstab.
Such preparations as fstab update and commenting out load_aacu="YES" will give
discrepancy between fstab and actual mount points.]

I will try anyway. Thank you for your help.

-- 
wbr,
pluknet



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0906170745i51583493kf8b0d9a8bdd6b631>