From: Matt Darcy <kernel-lists@projecthugo.co.uk>
To: Matt Darcy <kernel-lists@projecthugo.co.uk>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: [git patches] 2.6.x libata updates
Date: Wed, 04 Jan 2006 22:25:15 +0000 [thread overview]
Message-ID: <43BC4B4B.8050900@projecthugo.co.uk> (raw)
In-Reply-To: <43BC3186.8060103@projecthugo.co.uk>
Matt Darcy wrote:
> Jeff Garzik wrote:
>
>> Please pull from 'upstream' branch of
>> master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>>
>> to receive the following updates:
>>
>>
> <snip>
>
> Well I've been using this update now for a few days.
>
> For my own personal problem (sata_mv stability) I see both positive
> and negative results over both 2.6.15-rc5-mm3 and 2.6.15
>
> First postitive:
>
> The bug I was experiening of a raid array 5 array not being visiable
> or startable due to array disks being not being seen as part of the
> array after a reboot appears to have gone. I say appears to as I can't
> test this %100 due to the negative aspect of this kernel. the array
> starts building - no problems gets about %35 through, and the whole
> machine just hangs total lock up.
>
> The reason this is still positive is because when I reboot the box,
> the unfinished md starts rebuilding again, suggesting that this kernel
> actually sees all the disks in the array after a reboot (which
> 2.6.15-rc5-mm3 wasn't)
>
> the hang of the system is pretty fatal though.
>
> I'd be interested in what other people are seeing with this kernel tree.
>
> I'm about to test a theroy of building the array with 2.6.15-rc5-mm3
> which can build the array fine, but it dissapears after a reboot, but
> on reboot I'll reboot into the latest libata-git kernel to see if the
> disks are visible.
>
> thoughts or personal experiences (or requests for info on solving some
> of these problems) welcome.
>
> Thanks,
>
> Matt
>
Hi all,
managed to catch some output from the hang this time around
Managed to catch some output from the crash this time
Jan 4 22:22:10 berger kernel: [<c0512aeb>] schedule+0x31b/0x6a0
Jan 4 22:22:10 berger kernel: [<c03fb2b0>] scsi_error_handler+0x0/0xb0
Jan 4 22:22:10 berger kernel: [<c041327a>] mv_stop_and_reset+0x3a/0x60
Jan 4 22:22:10 berger kernel: [<c041374f>] mv_eng_timeout+0x6f/0xb0
Jan 4 22:22:10 berger kernel: [<c040b4b7>] ata_scsi_error+0x17/0x30
Jan 4 22:22:10 berger kernel: [<c03fb33b>] scsi_error_handler+0x8b/0xb0
Jan 4 22:22:10 berger kernel: [<c01325e6>] kthread+0xb6/0xc0
Jan 4 22:22:10 berger kernel: [<c0132530>] kthread+0x0/0xc0
Jan 4 22:22:10 berger kernel: [<c0101389>] kernel_thread_helper+0x5/0xc
Jan 4 22:22:10 berger kernel: ata5: status=0x50 { DriveReady SeekComplete }
Jan 4 22:22:10 berger kernel: ata5: error=0x01 { AddrMarkNotFound }
Jan 4 22:22:10 berger kernel: Assertion failed! qc->flags &
ATA_QCFLAG_ACTIVE,drivers/scsi/libata-core.c,ata_qc_complete,line=3735
Jan 4 22:22:10 berger kernel: ata5: status=0x50 { DriveReady SeekComplete }
Jan 4 22:22:10 berger kernel: ata5: error=0x01 { AddrMarkNotFound }
Jan 4 22:22:10 berger kernel: sdd: Current: sense key=0x0
Jan 4 22:22:10 berger kernel: ASC=0x0 ASCQ=0x0
Jan 4 22:22:10 berger kernel: Assertion failed! ((in_ptr >>
EDMA_REQ_Q_PTR_SHIFT) & MV_MAX_Q_DEPTH_MASK) == ((readl(port_mmio +
EDMA_REQ_Q_OUT_PTR_OFS) >> EDMA_REQ_Q_PTR_SHIFT) &
MV_MAX_Q_DEPTH_MASK),drivers/scsi/sata_mv.c,mv_qc_issue,line=1067
Jan 4 22:22:11 berger kernel: ata5: translated ATA stat/err 0xd0/00 to
SCSI SK/ASC/ASCQ 0xb/47/00
Jan 4 22:22:11 berger kernel: ata5: status=0xd0 { Busy }
Jan 4 22:22:11 berger kernel: Assertion failed! ((in_ptr >>
EDMA_REQ_Q_PTR_SHIFT) & MV_MAX_Q_DEPTH_MASK) == ((readl(port_mmio +
EDMA_REQ_Q_OUT_PTR_OFS) >> EDMA_REQ_Q_PTR_SHIFT) &
MV_MAX_Q_DEPTH_MASK),drivers/scsi/sata_mv.c,mv_qc_issue,line=1067
Jan 4 22:22:11 berger kernel: Assertion failed! EDMA_EN & readl(base +
EDMA_CMD_OFS),drivers/scsi/sata_mv.c,mv_start_dma,line=582
Any thoughts / input ?
Matt
next prev parent reply other threads:[~2006-01-04 22:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 16:43 [git patches] 2.6.x libata updates Jeff Garzik
2006-01-03 16:51 ` Bartlomiej Zolnierkiewicz
2006-01-03 16:56 ` Jeff Garzik
2006-01-03 17:32 ` Alan Cox
2006-01-03 17:43 ` Jeff Garzik
2006-01-03 18:35 ` Bartlomiej Zolnierkiewicz
2006-01-03 18:50 ` Alan Cox
2006-01-04 14:02 ` Alan Cox
2006-01-04 20:35 ` Matt Darcy
2006-01-04 22:25 ` Matt Darcy [this message]
2006-01-05 18:44 ` Terrence Martin
2006-01-05 20:29 ` Roman Gischig
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 2:15 Jeff Garzik
2006-01-18 2:33 ` Andrew Morton
2006-01-18 5:18 ` Jeff Garzik
2005-11-11 16:23 Jeff Garzik
2005-11-09 6:54 Jeff Garzik
2005-10-29 18:22 Jeff Garzik
2005-10-29 19:14 ` Andrew Morton
2005-10-29 19:20 ` Jeff Garzik
2005-10-29 19:37 ` Linus Torvalds
2005-10-29 20:09 ` Al Viro
2005-10-29 20:16 ` Jeff Garzik
2005-10-29 22:21 ` Andrew Morton
2005-10-29 22:30 ` Linus Torvalds
2005-10-30 0:55 ` Tony Luck
2005-10-30 2:28 ` Horst von Brand
2005-10-30 12:44 ` Rob Landley
2005-10-30 22:36 ` Linus Torvalds
2005-10-30 23:31 ` Rob Landley
2005-10-31 0:58 ` Linus Torvalds
2005-10-31 2:35 ` Rob Landley
2005-11-10 0:36 ` Matthias Urlichs
2005-10-30 23:59 ` Rob Landley
2005-10-31 0:16 ` Randy.Dunlap
2005-10-30 13:11 ` Pavel Machek
2005-10-31 3:55 ` David Lang
2005-10-28 0:49 Jeff Garzik
2005-10-28 16:08 ` Linus Torvalds
2005-08-29 0:25 Jeff Garzik
2005-06-28 16:59 Jeff Garzik
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=43BC4B4B.8050900@projecthugo.co.uk \
--to=kernel-lists@projecthugo.co.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).