From: Sebastian Kuzminsky <seb@highlab.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Arkadiusz Miskiewicz <arekm@pld-linux.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: sata_mv important note
Date: Fri, 20 Jan 2006 12:49:37 -0700 [thread overview]
Message-ID: <E1F02GP-0004IR-O2@highlab.com> (raw)
In-Reply-To: <58cb370e0601190335w51bb1d25pb5ae575632cedbad@mail.gmail.com>
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> On 1/17/06, Sebastian Kuzminsky <seb@highlab.com> wrote:
> > 0000:02:01.0 IDE interface: Marvell Technology Group Ltd. MV88SX6081 8-port SATA II PCI-X Controller (rev 09)
> >
> > I'm running the stock 2.6.15 kernel & the in-kernel driver. I have four
> > disks on this controller. The controller and disks seem perfectly stable,
> > I've been running four parallel "badblocks -n" processes (one on each
> > disk) for almost 5 days now. Using the disks as PVs in LVM works fine,
> > and building a RAID-6 out of them also works fine.
> >
> > But when I build a RAID-6 out of them, and use the array as a PV
> > for LVM, the system locks up within seconds (no errors, no sysrq,
> > no CapsLock-blinky, no network-pingy). This behavior is perfectly
> > repeatable.
>
> Have you tried using "nmi_watchdog=1" kernel parameter?
I just tried this and it hung again, with nothing in the logs or on
the console.
Pretty wierd.
I just had another hard lockup with sata_mv -> Raid-6, but without LVM.
This is new for me, first time I've seen it lock up without LVM. I was
resyncing the raid array and running 'badblocks -svn' on it (/dev/md1)
at the same time, and it locked.
I'm going to shelve the Marvell 6081 controller for a while, and go buy
something else...
--
Sebastian Kuzminsky
next prev parent reply other threads:[~2006-01-20 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 15:05 sata_mv important note Jeff Garzik
2006-01-17 16:24 ` Sebastian Kuzminsky
2006-01-17 16:34 ` Arkadiusz Miskiewicz
2006-01-17 20:28 ` Sebastian Kuzminsky
2006-01-18 0:50 ` Mark Lord
2006-01-19 11:35 ` Bartlomiej Zolnierkiewicz
2006-01-20 19:49 ` Sebastian Kuzminsky [this message]
2006-01-17 19:34 ` Mark Lord
2006-01-18 10:53 ` Erik Slagter
2006-01-18 16:14 ` Jeff Garzik
2006-01-18 19:45 ` Erik Slagter
2006-01-19 17:05 ` Mark Lord
2006-01-19 17:08 ` Randy.Dunlap
2006-01-19 17:11 ` Mark Lord
2006-01-19 17:13 ` Erik Slagter
2006-01-19 17:09 ` Erik Slagter
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=E1F02GP-0004IR-O2@highlab.com \
--to=seb@highlab.com \
--cc=arekm@pld-linux.org \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.