From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] ESP driver
Date: Tue, 19 Feb 2008 09:20:10 +0000 [thread overview]
Message-ID: <47BA9F4A.5040600@systella.fr> (raw)
In-Reply-To: <47B9F9E1.8020007@systella.fr>
David Miller wrote:
> From: BERTRAND_Joël <joel.bertrand@systella.fr>
> Date: Mon, 18 Feb 2008 22:34:25 +0100
>
>> I think I have found a bug in esp_scsi.c. Without this patch, my
>> SS20/SMP was not able to rebuild its internal raid1 volume due to esp0
>> DMA errors. With the following patch, same workstation is building a
>> kernel, doing a rsync (between two local directories) and rebuilding a
>> 26 GB raid1 volume without any trouble.
>>
>> Signed-off-by: BERTRAND Joel <joel.bertrand@systella.fr>
>
> It may correct your problem for some reason, but this change
> is not correct (and your email client or your editor used
> spaces instead of tab characters in your change). The FAS100A
> implements the ESP_STAT_INTR bit correctly.
>
> If the FAS100A needed this change, you would get spurious IRQs or
> other state machine errors, not DMA errors.
>
> I think your change merely changes timings, making the DMA problem
> harder to trigger.
>
> I'm sorry I don't have more desirable feedback for your patch, but
> it's the best I can do :-)
David,
Only one question. For you, where can I find this bug ? In arch/sparc,
in shared code or in ESP driver itself ?
I have seen that DMA errors were allways followed by some ESP resets (I
think because I can see an AUTOSENSE command on console) but this ESP
reset command aborts or does not avoid ESP_STAT_INTR flag in esp->sreg.
Why not reset command does not clear this flag ? I'm not sure that it's
a mistake, but I don't understand why this flag remains set.
You said that my patch makes problem harder to trigger. Maybe, but I'm
pretty sure than this bug is close from this ESP_STAT_INTR flag that is
not cleared for some reasons on SS20. I have tested my quick and dirty
patch all night with 6 disks (two internal, four external and a CDROM
reader). Configuration :
/dev/sda1 + /dev/sdb1 => /boot
/dev/sda2 + /dev/sdb2 => swap
/dev/sda4 + /dev/sdb4 => /
/dev/sda8 + /dev/sdb8 => /opt
/dev/sdc1 + /dev/sdd1 + /dev/sde1 + /dev/sdf1 => /export/home (raid5)
and I have stressed ESP chip without any trouble.
Regards,
JKB
next prev parent reply other threads:[~2008-02-19 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 21:34 [PATCH] ESP driver BERTRAND Joël
2008-02-19 4:25 ` David Miller
2008-02-19 9:20 ` BERTRAND Joël [this message]
2008-02-19 9:30 ` David Miller
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=47BA9F4A.5040600@systella.fr \
--to=joel.bertrand@systella.fr \
--cc=sparclinux@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.