From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sebastian Kuzminsky <seb@highlab.com>
Cc: Arkadiusz Miskiewicz <arekm@pld-linux.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: sata_mv important note
Date: Thu, 19 Jan 2006 12:35:40 +0100 [thread overview]
Message-ID: <58cb370e0601190335w51bb1d25pb5ae575632cedbad@mail.gmail.com> (raw)
In-Reply-To: <E1EyxRD-0007Nd-U5@highlab.com>
On 1/17/06, Sebastian Kuzminsky <seb@highlab.com> wrote:
> Arkadiusz Miskiewicz <arekm@pld-linux.org> wrote:
> > On Tuesday 17 January 2006 17:24, Sebastian Kuzminsky wrote:
> > > Jeff Garzik <jgarzik@pobox.com> wrote:
> > > > For sata_mv users, you should be aware of three things:
> > > >
> > > > 1) The Marvell driver is experimental, and not yet considered ready for
> > > > production use. As Kconfig notes: HIGHLY EXPERIMENTAL.
> > >
> > > Right, understood.
> >
> > I'm using:
> >
> > 03:03.0 SCSI storage controller: Marvell Technology Group Ltd. MV88SX6041=20
> > 4-port SATA II PCI-X Controller (rev 07)
> >
> > but with http://www.keffective.com/mvsata/FC3/mvSata-3.4.2a-patched.tbz driver
> > and it works nicely (+ 2.8GHz Xeon HT, smp kernel). I was quite suprised to
> > see that there are no problems with it in typical usage (while I'm sure that
> > this driver is far away from kernel standards).
>
> I'm using:
>
> 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?
> The problem goes away and everything works if I turn on all the debugging
> options in the kernel config (but I dont get any debug output from
> the kernel).
Could you find the specific option which makes the hang go away?
Bartlomiej
next prev parent reply other threads:[~2006-01-19 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 15:05 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 [this message]
2006-01-20 19:49 ` Sebastian Kuzminsky
2006-01-17 19:34 ` Mark Lord
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=58cb370e0601190335w51bb1d25pb5ae575632cedbad@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=arekm@pld-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seb@highlab.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
all inboxes | Powered by JetHome®