linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Vinod Koul <vkoul@kernel.org>,
	dmaengine@vger.kernel.org, Angelo Dureghello <angelo@sysam.it>
Cc: Dan Williams <dan.j.williams@intel.com>,
	linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch>
Subject: Re: [BUG] Serial/dma stall/failure after "dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)"
Date: Wed, 4 Jul 2018 18:10:56 -0700	[thread overview]
Message-ID: <0f3e3ba4-d9fc-ee66-23c2-319db48cd622@infradead.org> (raw)
In-Reply-To: <CAJKOXPcVFrkEA4YV3gi-gPYhtTXHeKtv4CvL29gstfTacz2sMg@mail.gmail.com>

On 07/04/18 01:54, Krzysztof Kozlowski wrote:
> Hi,
> 
> The commit 6ad069123f03bebe4315dea13d44845854ca6043 ("dmaengine:
> fsl-edma: extract common fsl-edma code (no changes in behavior
> intended)"), even though marked as no changes in behavior intended...
> make serial console with DMA broken after boot. The console just hangs
> - is not responsive even to SysRq. Usually after finishing boot -
> before or after login prompt. Sometimes login is allowed and then it
> hangs during printing dmesg.
> 
> Board: Toradex Colibri VF50 (NXP VF500, Cortex A5, serial configured
> with DMA) on Iris Carrier.
> 
> Commit found with bisect:
> git bisect start
> # bad: [bce40927669338cc4a361fc97d46bf650573ce5c] Add linux-next
> specific files for 20180704
> git bisect bad bce40927669338cc4a361fc97d46bf650573ce5c
> # good: [410da1e12ffed61129d61df5b7adce4d08c7f17c] net/smc: fix up
> merge error with poll changes
> git bisect good 410da1e12ffed61129d61df5b7adce4d08c7f17c
> # good: [decd57900d6fd743f7ddc1329400f4bd9cf54284] Merge
> remote-tracking branch 'crypto/master'
> git bisect good decd57900d6fd743f7ddc1329400f4bd9cf54284
> # good: [e9484bb660753ca8a35d219db000fff967b70a2c] Merge
> remote-tracking branch 'tip/auto-latest'
> git bisect good e9484bb660753ca8a35d219db000fff967b70a2c
> # bad: [20adee487b5f252d3f38197d43487c004273d3d0] Merge
> remote-tracking branch 'slave-dma/next'
> git bisect bad 20adee487b5f252d3f38197d43487c004273d3d0
> # good: [2df2577dce1d5fd98cac342fe857677a0556421b] Merge
> remote-tracking branch 'tty/tty-next'
> git bisect good 2df2577dce1d5fd98cac342fe857677a0556421b
> # good: [03b17ed8410a61f4f337c7bcfded1f744182edd5] spi: spi-fsl-dspi:
> Fix imprecise abort on VF500 during probe
> git bisect good 03b17ed8410a61f4f337c7bcfded1f744182edd5
> # good: [85e1d42663a0c163002961d2685be952067b0dc2] staging:
> mt7621-eth: Fix memory leak in mtk_add_mac() error path
> git bisect good 85e1d42663a0c163002961d2685be952067b0dc2
> # good: [b244f917acb7e1f492c40f6f4cf7be860a5065a5] staging: rtl8188eu:
> remove blank lines
> git bisect good b244f917acb7e1f492c40f6f4cf7be860a5065a5
> # good: [b244f917acb7e1f492c40f6f4cf7be860a5065a5] staging: rtl8188eu:
> remove blank lines
> git bisect good b244f917acb7e1f492c40f6f4cf7be860a5065a5
> # good: [b244f917acb7e1f492c40f6f4cf7be860a5065a5] staging: rtl8188eu:
> remove blank lines
> git bisect good b244f917acb7e1f492c40f6f4cf7be860a5065a5
> # good: [6c796f514b7f8d0fef4733b971a5ded9e9a74490] Merge
> remote-tracking branch 'staging/staging-next'
> git bisect good 6c796f514b7f8d0fef4733b971a5ded9e9a74490
> # good: [14dfa379ffd3ffd73729a72c289e9db6780a60ab] Merge branch
> 'topic/ste' into next
> git bisect good 14dfa379ffd3ffd73729a72c289e9db6780a60ab
> # good: [c1199875d327a9b3bbb3fb1cca0d467d3e625fbb] dmaengine:
> imx-sdma: Use GFP_NOWAIT for dma allocations
> git bisect good c1199875d327a9b3bbb3fb1cca0d467d3e625fbb
> # bad: [15efb0b488596a929bc00ce23aeb746ee6a7c14d] dmaengine: fsl-edma:
> fix trailing whitespace
> git bisect bad 15efb0b488596a929bc00ce23aeb746ee6a7c14d
> # bad: [5c1355ad87a2c138049bfafa753b44046492aebc] dmaengine: fsl-edma:
> add ColdFire mcf5441x edma support
> git bisect bad 5c1355ad87a2c138049bfafa753b44046492aebc
> # bad: [6ad069123f03bebe4315dea13d44845854ca6043] dmaengine: fsl-edma:
> extract common fsl-edma code (no changes in behavior intended)
> git bisect bad 6ad069123f03bebe4315dea13d44845854ca6043
> # first bad commit: [6ad069123f03bebe4315dea13d44845854ca6043]
> dmaengine: fsl-edma: extract common fsl-edma code (no changes in
> behavior intended)
> 
> Defconfig and boot log attached. I could not find any obvious error in boot log.
> 
> Let me know if you need more data.
> 
> Best regards,
> Krzysztof


BTW, there is also this warning in linux-next:
WARNING: modpost: missing MODULE_LICENSE() in drivers/dma/fsl-edma-common.o


-- 
~Randy

  reply	other threads:[~2018-07-05  1:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  8:54 [BUG] Serial/dma stall/failure after "dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)" Krzysztof Kozlowski
2018-07-05  1:10 ` Randy Dunlap [this message]
2018-07-05  7:37   ` Vinod
2018-07-05  7:35 ` Vinod
2018-07-05  8:12   ` Angelo Dureghello
2018-07-05 12:45     ` Angelo Dureghello
2018-07-05 14:29       ` Stefan Agner
2018-07-05 15:55       ` Stefan Agner
2018-07-05 16:23         ` Angelo Dureghello
2018-07-06  6:05           ` Vinod
2018-07-06  6:16             ` Krzysztof Kozlowski
2018-07-06  8:55               ` Angelo Dureghello

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=0f3e3ba4-d9fc-ee66-23c2-319db48cd622@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=angelo@sysam.it \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan@agner.ch \
    --cc=vkoul@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).