On Thu, 14 Mar 2024, Manuel Bouyer wrote:
It could also be some sensors I guess. Any chance to see what attaches
at dwiic0 ? Maybe entering ddb before the console gets spammed ?
The error messages start immediately after attaching the dwiic. I
have waited for several minutes and the timeout
On Thu, Mar 14, 2024 at 08:42:47AM -0700, Paul Goyette wrote:
> On Thu, 14 Mar 2024, Michael van Elst wrote:
>
> > p...@whooppee.com (Paul Goyette) writes:
> >
> > > as soon as you proceed past this point (including normal non-single-
> > > user boot), the dwiic starts spewing time-out messages.
On Thu, 14 Mar 2024, Michael van Elst wrote:
p...@whooppee.com (Paul Goyette) writes:
as soon as you proceed past this point (including normal non-single-
user boot), the dwiic starts spewing time-out messages. These
messages come every 0.5 second or so, and there's usually a hundred
or more
p...@whooppee.com (Paul Goyette) writes:
>as soon as you proceed past this point (including normal non-single-
>user boot), the dwiic starts spewing time-out messages. These
>messages come every 0.5 second or so, and there's usually a hundred
>or more messages before they stop; in some cases
Well, another issue to deal with on my new build. This time, it is
the dwiic0 device at fault.
Booting single user gets as far as the ``which shell'' prompt, but
as soon as you proceed past this point (including normal non-single-
user boot), the dwiic starts spewing time-out messages. These
