Fwd: Subject: Re: kern/52126

[Jaromír Doleček <jaromir.dolecek%gmail.com@localhost>]

The following reply was made to PR kern/52126; it has been noted by GNATS.

From: =?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?= <jaromir.dolecek%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Fwd: Subject: Re: kern/52126
Date: Sun, 20 Aug 2017 00:29:29 +0200

 --001a11471ce06c41e2055722c70f
 Content-Type: text/plain; charset="UTF-8"
 
 (once more in plain text for record)
 
 I've changed the sleep/delay code on jdolecek-ncq branch so that the sleep
 is always at least 1 tick. You might give it a try - if that is really the
 only issue, this might help. Increasing the timeouts however did not fix
 the issue for me on 60xx, at least not with the brief testing I did so far.
 
 I've experienced the EDMA timeout on 6048 just while booting or some light
 use, while it almost never happened on 70xxx. It usually happened when the
 chip was wedged for other reasons, like unrecovered NCQ error or some such.
 So I think that there might be something else we do wrong for 60xx, and the
 EDMA disable problem is just consequence.
 
 60xx was however not really focus of the NCQ branch, and I won't do
 anything further for it on the branch. My focus is now on completing my
 branch and merge, and some RL stuff. Then I may start looking on the 60xx
 issue, but that won't be before late September.
 
 Jaromir
 
 --001a11471ce06c41e2055722c70f
 Content-Type: text/html; charset="UTF-8"
 Content-Transfer-Encoding: quoted-printable
 
 <div dir=3D"ltr">(once more in plain text for record)<br><br>I&#39;ve chang=
 ed the sleep/delay code on jdolecek-ncq branch so that the sleep is always =
 at least 1 tick. You might give it a try - if that is really the only issue=
 , this might help. Increasing the timeouts however did not fix the issue fo=
 r me on 60xx, at least not with the brief testing I did so far.<br><br>I&#3=
 9;ve experienced the EDMA timeout on 6048 just while booting or some light =
 use, while it almost never happened on 70xxx. It usually happened when the =
 chip was wedged for other reasons, like unrecovered NCQ error or some such.=
  So I think that there might be something else we do wrong for 60xx, and th=
 e EDMA disable problem is just consequence.<br><br>60xx was however not rea=
 lly focus of the NCQ branch, and I won&#39;t do anything further for it on =
 the branch. My focus is now on completing my branch and merge, and some RL =
 stuff. Then I may start looking on the 60xx issue, but that won&#39;t be be=
 fore late September.<br><br>Jaromir</div>
 
 --001a11471ce06c41e2055722c70f--