All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Jens Axboe <axboe@suse.de>
Cc: Sander <sander@humilis.net>, Jeff Garzik <jgarzik@pobox.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.16-rc3 kernel BUG at drivers/scsi/sata_mv.c:1018
Date: Wed, 15 Feb 2006 17:31:35 +0100	[thread overview]
Message-ID: <20060215163135.GA20806@favonius> (raw)
In-Reply-To: <20060215145925.GU4203@suse.de>

Jens Axboe wrote (ao):
> On Wed, Feb 15 2006, Sander wrote:
> > I get a kernel BUG message when I try to create a raid1 or raid5 over
> > nine 64MB partitions located on nine sata disks (Maxtor Pro 500) on a
> > fresh setup. The system locks hard: no sysrq.
> > 
> > The onboard controller is an nVidia nForce with three disks.
> > The six other disks are connected to a Marvell 88SX6081 controller.

> It's barfing on a barrier write, I bet. The attached patch should fix
> it.

Your patch does indeed fix the hang. The raid1 is done, and raid5 over
the second partition is building.

Thanks a lot Jens!!

	Sander


> [PATCH] Add missing FUA write to sata_mv dma command list
> 
> Signed-off-by: Jens Axboe <axboe@suse.de>
> 
> diff --git a/drivers/scsi/sata_mv.c b/drivers/scsi/sata_mv.c
> index 6fddf17..2770005 100644
> --- a/drivers/scsi/sata_mv.c
> +++ b/drivers/scsi/sata_mv.c
> @@ -997,6 +997,7 @@ static void mv_qc_prep(struct ata_queued
>  	case ATA_CMD_READ_EXT:
>  	case ATA_CMD_WRITE:
>  	case ATA_CMD_WRITE_EXT:
> +	case ATA_CMD_WRITE_FUA_EXT:
>  		mv_crqb_pack_cmd(cw++, tf->hob_nsect, ATA_REG_NSECT, 0);
>  		break;
>  #ifdef LIBATA_NCQ		/* FIXME: remove this line when NCQ added */
> 
> -- 
> Jens Axboe

-- 
Humilis IT Services and Solutions
http://www.humilis.net

      reply	other threads:[~2006-02-15 16:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15 13:16 2.6.16-rc3 kernel BUG at drivers/scsi/sata_mv.c:1018 Sander
2006-02-15 14:33 ` Sander
2006-02-15 14:59 ` Jens Axboe
2006-02-15 16:31   ` Sander [this message]

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=20060215163135.GA20806@favonius \
    --to=sander@humilis.net \
    --cc=axboe@suse.de \
    --cc=jgarzik@pobox.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.