From: Emmanuel Florac <eflorac@intellique.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: kernel panic-xfs errors
Date: Tue, 7 Dec 2010 22:52:26 +0100 [thread overview]
Message-ID: <20101207225226.55be2b4d@galadriel.home> (raw)
In-Reply-To: <4CFE7A89.2010307@hardwarefreak.com>
Le Tue, 07 Dec 2010 12:18:49 -0600 vous écriviez:
> The answer for the one server is simple: back out the firmware--flash
> it with the previously installed version.
>
> BTW, what need prompted the new flash in the first place? I _never_
> flash controller firmware unless absolutely necessary. You've
> demonstrated today why I practice that faith.
I've experienced myself some very convincing reasons, for instance a
RAID array with a performance varying by 1000% with a new firmware.
However the kernel panic occured on another that apparently wasn't
firmware-flashed.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-07 21:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 15:42 kernel panic-xfs errors blacknred
2010-12-07 15:59 ` Emmanuel Florac
2010-12-07 17:20 ` blacknred
2010-12-07 18:00 ` Emmanuel Florac
2010-12-07 18:18 ` Stan Hoeppner
2010-12-07 21:52 ` Emmanuel Florac [this message]
2010-12-07 22:25 ` Dave Chinner
2010-12-08 9:39 ` blacknred
2010-12-08 10:57 ` Emmanuel Florac
2010-12-08 14:01 ` blacknred
2010-12-08 14:34 ` Emmanuel Florac
2010-12-09 0:59 ` Dave Chinner
2010-12-09 4:44 ` Eric Sandeen
2010-12-09 13:17 ` blacknred
2010-12-09 14:56 ` Eric Sandeen
2010-12-09 13:23 ` blacknred
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101207225226.55be2b4d@galadriel.home \
--to=eflorac@intellique.com \
--cc=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox