← Back to context

Comment by Aurornis

3 days ago

Yeah, I agree. This just feels like an appeal to anti-Microsoft clicks

From the article:

> It won’t get past the Snapdragon boot logo before rebooting or powering off… again, seemingly at random.

Random freezing at different points of the boot process suggests a hardware failure, not something broken in the software boot chain.

11 comments

Aurornis

Reply
colechristensen  3 days ago

It could very well be something poorly configured in the boot chain leading to random failures. There are plenty of hardware things configured in software which can lead to plenty of different kinds of random failures.

numpad0  3 days ago

Or something hit max program-erase cycle counts and are returning corrupt/old data. Flash ROMs tend to become "sticky" with previous states as you write more to them. I think it's possible that ROMs used for early SoC boot firmware or peripherals firmware still don't have wear leveling that they could become unusable after just a hundred or so of writes.

ErroneousBosh  3 days ago

> Random freezing at different points of the boot process suggests a hardware failure, not something broken in the software boot chain.

Power issues all day long. It'll be fine until the SoC enables enough peripherals for one of the rails to sag down.

That being said, it's a hell of a coincidence that it failed exactly when a software update failed.

  • nottorp  3 days ago

    Firmware update changed the order in which power is enabled to peripherals?

    • ErroneousBosh  2 days ago

      Maybe! I could certainly see something like the firmware switches on something way heavier that pulls down an already marginal supply.

      Remember the very early Raspberry Pis that had the polyfuses that dropped a little too much voltage from the "5V" supply, so a combination of shitty phone charger, shitty charging cable, and everything just being a little too warm/cold/wrong kind of moonlight would just make them not boot at all?

      1 reply →