From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, linux-samsung-soc@vger.kernel.org,
kernel-build-reports@lists.linaro.org,
Sangbeom Kim <sbkim73@samsung.com>, Kukjin Kim <kgene@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [alsa-devel] next/master boot: 148 boots: 10 failed, 136 passed with 2 untried/unknown (next-20200129)
Date: Wed, 29 Jan 2020 19:29:18 +0100 [thread overview]
Message-ID: <20200129182918.GA13626@kozik-lap> (raw)
In-Reply-To: <20200129161113.GE3928@sirena.org.uk>
On Wed, Jan 29, 2020 at 04:11:13PM +0000, Mark Brown wrote:
> On Wed, Jan 29, 2020 at 07:54:18AM -0800, kernelci.org bot wrote:
>
> Today's -next fails to boot on Odroid X2 and XU3 with exynos_defconfig
> or multi_v7_defconfig with SMP=n. It appears to get stuck in a loop
> probing the I2S secondary DAI for some reason:
>
> 12:07:05.997409 <6>[ 6.421596] exynos-bus: new bus device registered: soc:bus_mscl ( 84000 KHz ~ 666000 KHz)
> 12:07:05.997653 <4>[ 6.429763] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
> 12:07:06.006838 <4>[ 6.439652] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
> 12:07:06.015764 <4>[ 6.448666] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
>
> and so on ad infinitum. Vanilla multi_v7_defconfig is fine and just
> displays a saingle copy of that log message. Full logs and other
> details here:
>
> https://kernelci.org/boot/id/5e3176467f121dbdef2824fc/
> https://kernelci.org/boot/id/5e317b7322dcdaa3e5282500/
> https://kernelci.org/boot/id/5e317c0f6bfd765fb42824f1/
> https://kernelci.org/boot/id/5e317517be8559c7542824f1/
>
> I don't *think* it's an audio issue as mainline seems fine and all the
> ASoC changes have already landed in mainline for this merge window.
Thanks for the report.
Marek spotted it as well and sent a patch
Best regards,
Krzysztof
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Kukjin Kim <kgene@kernel.org>, Sangbeom Kim <sbkim73@samsung.com>,
kernel-build-reports@lists.linaro.org,
linux-samsung-soc@vger.kernel.org, alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: next/master boot: 148 boots: 10 failed, 136 passed with 2 untried/unknown (next-20200129)
Date: Wed, 29 Jan 2020 19:29:18 +0100 [thread overview]
Message-ID: <20200129182918.GA13626@kozik-lap> (raw)
In-Reply-To: <20200129161113.GE3928@sirena.org.uk>
On Wed, Jan 29, 2020 at 04:11:13PM +0000, Mark Brown wrote:
> On Wed, Jan 29, 2020 at 07:54:18AM -0800, kernelci.org bot wrote:
>
> Today's -next fails to boot on Odroid X2 and XU3 with exynos_defconfig
> or multi_v7_defconfig with SMP=n. It appears to get stuck in a loop
> probing the I2S secondary DAI for some reason:
>
> 12:07:05.997409 <6>[ 6.421596] exynos-bus: new bus device registered: soc:bus_mscl ( 84000 KHz ~ 666000 KHz)
> 12:07:05.997653 <4>[ 6.429763] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
> 12:07:06.006838 <4>[ 6.439652] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
> 12:07:06.015764 <4>[ 6.448666] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
>
> and so on ad infinitum. Vanilla multi_v7_defconfig is fine and just
> displays a saingle copy of that log message. Full logs and other
> details here:
>
> https://kernelci.org/boot/id/5e3176467f121dbdef2824fc/
> https://kernelci.org/boot/id/5e317b7322dcdaa3e5282500/
> https://kernelci.org/boot/id/5e317c0f6bfd765fb42824f1/
> https://kernelci.org/boot/id/5e317517be8559c7542824f1/
>
> I don't *think* it's an audio issue as mainline seems fine and all the
> ASoC changes have already landed in mainline for this merge window.
Thanks for the report.
Marek spotted it as well and sent a patch
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, linux-samsung-soc@vger.kernel.org,
kernel-build-reports@lists.linaro.org,
Sangbeom Kim <sbkim73@samsung.com>, Kukjin Kim <kgene@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: next/master boot: 148 boots: 10 failed, 136 passed with 2 untried/unknown (next-20200129)
Date: Wed, 29 Jan 2020 19:29:18 +0100 [thread overview]
Message-ID: <20200129182918.GA13626@kozik-lap> (raw)
In-Reply-To: <20200129161113.GE3928@sirena.org.uk>
On Wed, Jan 29, 2020 at 04:11:13PM +0000, Mark Brown wrote:
> On Wed, Jan 29, 2020 at 07:54:18AM -0800, kernelci.org bot wrote:
>
> Today's -next fails to boot on Odroid X2 and XU3 with exynos_defconfig
> or multi_v7_defconfig with SMP=n. It appears to get stuck in a loop
> probing the I2S secondary DAI for some reason:
>
> 12:07:05.997409 <6>[ 6.421596] exynos-bus: new bus device registered: soc:bus_mscl ( 84000 KHz ~ 666000 KHz)
> 12:07:05.997653 <4>[ 6.429763] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
> 12:07:06.006838 <4>[ 6.439652] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
> 12:07:06.015764 <4>[ 6.448666] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
>
> and so on ad infinitum. Vanilla multi_v7_defconfig is fine and just
> displays a saingle copy of that log message. Full logs and other
> details here:
>
> https://kernelci.org/boot/id/5e3176467f121dbdef2824fc/
> https://kernelci.org/boot/id/5e317b7322dcdaa3e5282500/
> https://kernelci.org/boot/id/5e317c0f6bfd765fb42824f1/
> https://kernelci.org/boot/id/5e317517be8559c7542824f1/
>
> I don't *think* it's an audio issue as mainline seems fine and all the
> ASoC changes have already landed in mainline for this merge window.
Thanks for the report.
Marek spotted it as well and sent a patch
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-29 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5e31aaaa.1c69fb81.a7667.f187@mx.google.com>
2020-01-29 16:11 ` [alsa-devel] next/master boot: 148 boots: 10 failed, 136 passed with 2 untried/unknown (next-20200129) Mark Brown
2020-01-29 16:11 ` Mark Brown
2020-01-29 16:11 ` Mark Brown
2020-01-29 18:29 ` Krzysztof Kozlowski [this message]
2020-01-29 18:29 ` Krzysztof Kozlowski
2020-01-29 18:29 ` Krzysztof Kozlowski
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=20200129182918.GA13626@kozik-lap \
--to=krzk@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sbkim73@samsung.com \
/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.