On 2010-07-21 at 20:40, Svein Skogen (Listmail account) wrote:
> On 21.07.2010 18:33, Ståle Kristoffersen wrote:
> > I -might- have solved my problem. It has now ran for 24h without timeouts,
> > and with a bit of load on it. I think I might have ran into the seagate +
> >
D17
to firmware SD1B (old SD17) and SD1A (old SD15), and that looks like it has
done the trick. I'll report back in a week or so if the problem has not
reappeared.
--
Ståle Kristoffersen
___
freebsd-current@freebsd.org mailing list
http://lists.fr
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.
I'm trying to update the firmware on some of the drives now to see
nly differed from the
> 8-STABLE one in a cosmetic change at that time.
I have another data-point, I cvsup'ed to the latest current again, and
rebuilt without INVARIANT and WITNESS, and now it seems to survive the
timeouts.
--
Ståle Kristoffersen
___
On 2010-07-16 at 12:31, Ståle Kristoffersen wrote:
> On 2010-07-15 at 19:52, Ståle Kristoffersen wrote:
> > On 2010-07-15 at 18:00, Marius Strobl wrote:
> > > On Thu, Jul 15, 2010 at 02:34:23PM +0200, Stle Kristoffersen wrote:
> > > > Upgraded to from stable to curr
On 2010-07-15 at 19:52, Ståle Kristoffersen wrote:
> On 2010-07-15 at 18:00, Marius Strobl wrote:
> > On Thu, Jul 15, 2010 at 02:34:23PM +0200, Stle Kristoffersen wrote:
> > > Upgraded to from stable to current yesterday and very quickly received a
> > > panic. It did
hat revision I was using, is there an easy way to figure
that out? I ran cvsupdate around 13:00 CEST yesterday.
> Does using current as of r209598 make a difference?
Downgrading now...
--
Ståle Kristoffersen
staal...@ifi.uio.no
___
freebsd-curr
On 2010-07-15 at 14:34, Ståle Kristoffersen wrote:
> Upgraded to from stable to current yesterday and very quickly received a
> panic. It did however not dump it's core, so I was unable to debug it.
> Today it did panic again, and I took a picture: (Sorry about the bad
> q
http://folk.uio.no/stalk/mpt/IMG_1404.JPG
Both times I hade the mpt0: request timed out just before the panic.
I'm not sure why it's not dumping it's core (It was working under stable,
and I have dumpdev="AUTO" and dumpdir="/var/crash&q
