* Re: next/master boot: 171 boots: 6 failed, 162 passed with 3 offline (next-20180724) [not found] <5b5757ee.1c69fb81.411a5.52e2@mx.google.com> @ 2018-07-25 16:11 ` Mark Brown 2018-07-26 7:09 ` Stefan Wahren 2018-07-31 15:52 ` Mark Brown 0 siblings, 2 replies; 5+ messages in thread From: Mark Brown @ 2018-07-25 16:11 UTC (permalink / raw) To: Eric Anholt, Stefan Wahren, Kevin Hilman, clabbe Cc: linux-next, linux-rpi-kernel, linux-arm-kernel, kernel-build-reports [-- Attachment #1.1: Type: text/plain, Size: 1440 bytes --] On Tue, Jul 24, 2018 at 09:46:38AM -0700, kernelci.org bot wrote: For a little while now the RPi B has been failing to boot using the bcm2835 defconfig in -next: > bcm2835_defconfig: > bcm2835-rpi-b: > lab-baylibre-seattle: failing since 5 days (last pass: next-20180718 - first fail: next-20180719) > bcm2837-rpi-3-b: > lab-baylibre: failing since 5 days (last pass: next-20180718 - first fail: next-20180719) It's working fine on arm64, whatever's going on appears to be specific to this config (it's not getting booted with any other 32 bit configs). Full info and boot logs for one of the boards here: https://kernelci.org/boot/id/5b58416759b514139596baae/ it looks like it hangs somewhere shortly after or during initializing MMC so never makes it to the console, the tail of the failing logs looks like: | 09:18:36.332120 [ 1.459801] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) | 09:18:36.345711 [ 1.467585] mmcblk0: mmc0:59b4 USD 7.51 GiB | 09:18:36.346169 [ 1.474834] mmcblk0: p1 | 09:18:36.410184 [ 1.539600] random: fast init done | 09:18:36.458065 [ 1.578056] mmc1: new high speed SDIO card at address 0001 | 09:20:39.745370 ShellCommand command timed out.: Sending # in case of corruption. Connection timeout 00:04:10, retry in 00:02:05 | 09:20:39.846848 # but like I say the same -next boots with arm64 defconfig. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --] [-- Attachment #2: Type: text/plain, Size: 176 bytes --] _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: next/master boot: 171 boots: 6 failed, 162 passed with 3 offline (next-20180724) 2018-07-25 16:11 ` next/master boot: 171 boots: 6 failed, 162 passed with 3 offline (next-20180724) Mark Brown @ 2018-07-26 7:09 ` Stefan Wahren 2018-07-31 15:52 ` Mark Brown 1 sibling, 0 replies; 5+ messages in thread From: Stefan Wahren @ 2018-07-26 7:09 UTC (permalink / raw) To: Mark Brown, Eric Anholt, Kevin Hilman, clabbe Cc: linux-next, linux-rpi-kernel, linux-arm-kernel, kernel-build-reports Hi Mark, thanks for forwarding. Unfortunately i don't have the time for real investigation until next week, so here some remote diagnostics. Am 25.07.2018 um 18:11 schrieb Mark Brown: > On Tue, Jul 24, 2018 at 09:46:38AM -0700, kernelci.org bot wrote: > > For a little while now the RPi B has been failing to boot using the > bcm2835 defconfig in -next: > >> bcm2835_defconfig: >> bcm2835-rpi-b: >> lab-baylibre-seattle: failing since 5 days (last pass: next-20180718 - first fail: next-20180719) >> bcm2837-rpi-3-b: >> lab-baylibre: failing since 5 days (last pass: next-20180718 - first fail: next-20180719) > It's working fine on arm64, whatever's going on appears to be specific > to this config (it's not getting booted with any other 32 bit configs). > Full info and boot logs for one of the boards here: > > https://kernelci.org/boot/id/5b58416759b514139596baae/ > > it looks like it hangs somewhere shortly after or during initializing > MMC so never makes it to the console, the tail of the failing logs looks > like: > > | 09:18:36.332120 [ 1.459801] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) > | 09:18:36.345711 [ 1.467585] mmcblk0: mmc0:59b4 USD 7.51 GiB > | 09:18:36.346169 [ 1.474834] mmcblk0: p1 > | 09:18:36.410184 [ 1.539600] random: fast init done > | 09:18:36.458065 [ 1.578056] mmc1: new high speed SDIO card at address 0001 > | 09:20:39.745370 ShellCommand command timed out.: Sending # in case of corruption. Connection timeout 00:04:10, retry in 00:02:05 > | 09:20:39.846848 # > > but like I say the same -next boots with arm64 defconfig. > There is at least 1 difference between bcm2835_defconfig and arm64 defconfig. bcm2835_defconfig uses DMA [ 1.265671] sdhost-bcm2835 3f202000.mmc: loaded - DMA enabled (>1) while arm64 defconfig uses PIO mode for SD interface mmc0 (please ignore mmc1 since it's the onboard wifi and it uses a different driver): [ 1.907766] sdhost-bcm2835 3f202000.mmc: unable to initialise DMA channel. Falling back to PIO [ 1.995407] sdhost-bcm2835 3f202000.mmc: loaded - DMA disabled The reason for this output is expected, because the DMA driver isn't build-in for this config. I think this issue is DMA related. Regards Stefan ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: next/master boot: 171 boots: 6 failed, 162 passed with 3 offline (next-20180724) 2018-07-25 16:11 ` next/master boot: 171 boots: 6 failed, 162 passed with 3 offline (next-20180724) Mark Brown 2018-07-26 7:09 ` Stefan Wahren @ 2018-07-31 15:52 ` Mark Brown 2018-07-31 17:00 ` Robin Murphy 1 sibling, 1 reply; 5+ messages in thread From: Mark Brown @ 2018-07-31 15:52 UTC (permalink / raw) To: Eric Anholt, Stefan Wahren, Kevin Hilman, clabbe Cc: linux-next, linux-rpi-kernel, linux-arm-kernel, kernel-build-reports [-- Attachment #1.1: Type: text/plain, Size: 1398 bytes --] On Wed, Jul 25, 2018 at 05:11:51PM +0100, Mark Brown wrote: > On Tue, Jul 24, 2018 at 09:46:38AM -0700, kernelci.org bot wrote: > For a little while now the RPi B has been failing to boot using the > bcm2835 defconfig in -next: ... > It's working fine on arm64, whatever's going on appears to be specific > to this config (it's not getting booted with any other 32 bit configs). > Full info and boot logs for one of the boards here: > https://kernelci.org/boot/id/5b58416759b514139596baae/ > it looks like it hangs somewhere shortly after or during initializing > MMC so never makes it to the console, the tail of the failing logs looks > like: This went away for a day or two but it looks like it's back again I'm afraid: https://kernelci.org/boot/id/5b604cd259b514364696baaa/ > > | 09:18:36.332120 [ 1.459801] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) > | 09:18:36.345711 [ 1.467585] mmcblk0: mmc0:59b4 USD 7.51 GiB > | 09:18:36.346169 [ 1.474834] mmcblk0: p1 > | 09:18:36.410184 [ 1.539600] random: fast init done > | 09:18:36.458065 [ 1.578056] mmc1: new high speed SDIO card at address 0001 > | 09:20:39.745370 ShellCommand command timed out.: Sending # in case of corruption. Connection timeout 00:04:10, retry in 00:02:05 > | 09:20:39.846848 # > > but like I say the same -next boots with arm64 defconfig. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 488 bytes --] [-- Attachment #2: Type: text/plain, Size: 176 bytes --] _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: next/master boot: 171 boots: 6 failed, 162 passed with 3 offline (next-20180724) 2018-07-31 15:52 ` Mark Brown @ 2018-07-31 17:00 ` Robin Murphy 2018-07-31 21:35 ` Stefan Wahren 0 siblings, 1 reply; 5+ messages in thread From: Robin Murphy @ 2018-07-31 17:00 UTC (permalink / raw) To: Mark Brown, Eric Anholt, Stefan Wahren, Kevin Hilman, clabbe Cc: linux-next, linux-rpi-kernel, linux-arm-kernel, kernel-build-reports On 31/07/18 16:52, Mark Brown wrote: > On Wed, Jul 25, 2018 at 05:11:51PM +0100, Mark Brown wrote: >> On Tue, Jul 24, 2018 at 09:46:38AM -0700, kernelci.org bot wrote: > >> For a little while now the RPi B has been failing to boot using the >> bcm2835 defconfig in -next: > > ... > >> It's working fine on arm64, whatever's going on appears to be specific >> to this config (it's not getting booted with any other 32 bit configs). >> Full info and boot logs for one of the boards here: > >> https://kernelci.org/boot/id/5b58416759b514139596baae/ > >> it looks like it hangs somewhere shortly after or during initializing >> MMC so never makes it to the console, the tail of the failing logs looks >> like: > > This went away for a day or two but it looks like it's back again I'm > afraid: FWIW, it looks like that blip was due to me completely breaking DMA API functionality for DT devices in next-20180727. Funny that that actually "helped" in this case (unlike all the others...), but it definitely reinforces Stefan's observation. Robin. > > https://kernelci.org/boot/id/5b604cd259b514364696baaa/ > >> >> | 09:18:36.332120 [ 1.459801] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) >> | 09:18:36.345711 [ 1.467585] mmcblk0: mmc0:59b4 USD 7.51 GiB >> | 09:18:36.346169 [ 1.474834] mmcblk0: p1 >> | 09:18:36.410184 [ 1.539600] random: fast init done >> | 09:18:36.458065 [ 1.578056] mmc1: new high speed SDIO card at address 0001 >> | 09:20:39.745370 ShellCommand command timed out.: Sending # in case of corruption. Connection timeout 00:04:10, retry in 00:02:05 >> | 09:20:39.846848 # >> >> but like I say the same -next boots with arm64 defconfig. > > > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: next/master boot: 171 boots: 6 failed, 162 passed with 3 offline (next-20180724) 2018-07-31 17:00 ` Robin Murphy @ 2018-07-31 21:35 ` Stefan Wahren 0 siblings, 0 replies; 5+ messages in thread From: Stefan Wahren @ 2018-07-31 21:35 UTC (permalink / raw) To: Eric Anholt, Kevin Hilman, Robin Murphy, clabbe, Mark Brown Cc: linux-next, linux-rpi-kernel, linux-arm-kernel, kernel-build-reports > Robin Murphy <robin.murphy@arm.com> hat am 31. Juli 2018 um 19:00 geschrieben: > > > On 31/07/18 16:52, Mark Brown wrote: > > On Wed, Jul 25, 2018 at 05:11:51PM +0100, Mark Brown wrote: > >> On Tue, Jul 24, 2018 at 09:46:38AM -0700, kernelci.org bot wrote: > > > >> For a little while now the RPi B has been failing to boot using the > >> bcm2835 defconfig in -next: > > > > ... > > > >> It's working fine on arm64, whatever's going on appears to be specific > >> to this config (it's not getting booted with any other 32 bit configs). > >> Full info and boot logs for one of the boards here: > > > >> https://kernelci.org/boot/id/5b58416759b514139596baae/ > > > >> it looks like it hangs somewhere shortly after or during initializing > >> MMC so never makes it to the console, the tail of the failing logs looks > >> like: > > > > This went away for a day or two but it looks like it's back again I'm > > afraid: > > FWIW, it looks like that blip was due to me completely breaking DMA API > functionality for DT devices in next-20180727. Funny that that actually > "helped" in this case (unlike all the others...), but it definitely > reinforces Stefan's observation. > > Robin. > Sorry, still not much time this week. All i can say that next-20180731 is broken, but dma-mapping/for-next is not. ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-07-31 21:35 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <5b5757ee.1c69fb81.411a5.52e2@mx.google.com> 2018-07-25 16:11 ` next/master boot: 171 boots: 6 failed, 162 passed with 3 offline (next-20180724) Mark Brown 2018-07-26 7:09 ` Stefan Wahren 2018-07-31 15:52 ` Mark Brown 2018-07-31 17:00 ` Robin Murphy 2018-07-31 21:35 ` Stefan Wahren
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).