tip/master cros-ec: 10 runs, 2 regressions (v6.4-rc6-330-g0f2eeb20bbb85)

[Mark Brown]

On Mon, Jun 12, 2023 at 11:29:22AM +0200, Borislav Petkov wrote:
> On Mon, Jun 12, 2023 at 02:19:59AM -0700, kernelci.org bot wrote:

> > tip/master cros-ec: 10 runs, 2 regressions (v6.4-rc6-330-g0f2eeb20bbb85)

> So as far as I can use that web interface, the error is:

>  3649 08:46:19.915046  auto-login-action failed: 1 of 1 attempts. 'wait for prompt timed out'
>  3651 08:46:19.915828  end: 2.2.5 auto-login-action (duration 00:04:20) [common]
>  3653 08:46:19.916858  depthcharge-retry failed: 1 of 1 attempts. 'wait for prompt timed out'

> and the only warnings in that log are:

> <4>[    2.437968] mtu3 11201000.usb: supply vbus not found, using dummy regulator
> <4>[    2.470840] xhci-mtk 11200000.usb: supply vbus not found, using dummy regulator
> <4>[    2.536866] onboard-usb-hub 11200000.usb:hub at 1: supply vdd not found, using dummy regulator
> <4>[    2.743384] i2c_hid_of 2-002c: supply vdd not found, using dummy regulator
> <4>[    2.757753] i2c_hid_of 2-002c: supply vddl not found, using dummy regulator
> <4>[    2.793475] mmc1: queuing unknown CIS tuple 0x01 [d9 01 ff] (3 bytes)
> <4>[    2.813935] mmc1: queuing unknown CIS tuple 0x1a [01 01 00 02 07] (5 bytes)
> <4>[    2.826621] mmc1: queuing unknown CIS tuple 0x1b [c1 41 30 30 ff ff 32 00] (8 bytes)
> <4>[    2.834802] mmc1: queuing unknown CIS tuple 0x14 [] (0 bytes)

> which don't tell me anything.

Current -next oopses a couple of times on boot trying to probe some
nvmem of various kinds, there's something off with the platform:

   https://storage.kernelci.org/next/master/next-20230714/arm64/defconfig+arm64-chromebook/gcc-10/lab-collabora/cros-ec-mt8183-kukui-jacuzzi-juniper-sku16.txt

> Can we get this fixed pls so that I don't have to ignore those reports?

In general if a platform is just not booting like this it's best to
chase it up with people who work on that platform - they'll at least
hopefully have the hardware and be able to drill down into things.  The
CI correctly identified a problem, it doesn't really have the ability to
understand where it came from.  I've added some Mediatek/ChromeOS
people, and also nvmem since the two oopses are both there.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-mediatek/attachments/20230715/d17094d7/attachment.sig>