[ale] OS or Hardware issue?

[Jim Kinney]

First thing to suspect is heat and second is power. Is any heat sink loose? The "rate limiting" line in the urandom error could come from a cpu throttling back bue to heat. Secondarily it improved after reboot.  Run a stress test. Failure is strong heat indicator.

Power supplies failing cause bizarre issues with parts being under powered. But not all power issues are a failing power supply.  Some carpet fiber accumulation can alter timing due its minute dielectric capabilities. Put another way, a bit of plastic fiber dust can act to make a capacitor out of adjacent traces. This can scramble time sensitive logic events.

Of course any conductive dust is sn obvious problem. Tiny metal slivers from sliding drive carriers around can wreak havoc in stability.

I once pulled a dead insect from a cpu fan. It was blocking the fan from turning. System ran ok until moderate use needed that fan on. Then it would throttle back until it would finally shutdown. A literal computer bug. Customer was happy they didn't need a new system but unhappy with building manager (doctors office).

On April 20, 2021 6:20:42 AM EDT, Leam Hall via Ale <ale at ale.org> wrote:
>I haven't kept up with the low level processes, not sure where today's 
>issues came from. Using Void Linux, updated Sunday, and multiple
>planned 
>boots since updating. Refurb Dell 960.
>
>This morning:
>
>   1. Drive letter re-org, it tried to boot from the back-up drive. 
>/dev/sdc was labelled as /dev/sdb.
>
>   2. Did a hard reboot, and then the keyboard wouldn't input.
>
>   3. Shutdown via mouse, and things seem to work.
>
>
>Looks like BIOS, according to dmesg:
>
>dmesg |egrep -i "error|warning"
>[    0.019961] ACPI BIOS Warning (bug): 32/64X length mismatch in 
>FADT/Gpe0Block: 128/64 (20201113/tbfadt-564)
>[    2.655673] ACPI BIOS Warning (bug): Incorrect checksum in table 
>[TCPA] - 0x00, should be 0x7F (20201113/tbprint-173)
>[    5.659170] random: 6 urandom warning(s) missed due to ratelimiting
>[    9.513809] ACPI Warning: SystemIO range 
>0x0000000000000828-0x000000000000082F conflicts with OpRegion 
>0x0000000000000828-0x000000000000082D (\GLBC) (20201113/utaddress-204)
>[    9.513820] ACPI Warning: SystemIO range 
>0x0000000000000828-0x000000000000082F conflicts with OpRegion 
>0x000000000000082A-0x000000000000082A (\SACT) (20201113/utaddress-204)
>[    9.513826] ACPI Warning: SystemIO range 
>0x0000000000000828-0x000000000000082F conflicts with OpRegion 
>0x0000000000000828-0x0000000000000828 (\SSTS) (20201113/utaddress-204)
>[    9.513836] ACPI Warning: SystemIO range 
>0x00000000000008B0-0x00000000000008BF conflicts with OpRegion 
>0x00000000000008B8-0x00000000000008BB (\GIC2) (20201113/utaddress-204)
>[    9.513844] ACPI Warning: SystemIO range 
>0x0000000000000880-0x00000000000008AF conflicts with OpRegion 
>0x000000000000088C-0x000000000000088F (\GIC1) (20201113/utaddress-204)
>[   11.394756] udevd[657]: Error calling EVIOCSKEYCODE on device node 
>'/dev/input/event2' (scan code 0xc022d, key code 103): Invalid argument
>[   11.394862] udevd[657]: Error calling EVIOCSKEYCODE on device node 
>'/dev/input/event2' (scan code 0xc022e, key code 108): Invalid argument
>[   16.285931] platform regulatory.0: Direct firmware load for 
>regulatory.db failed with error -2
>
>It works for the moment, so I'll get some more backups and research.
>And 
>work on a BIOS update. Suggestions welcome.
>
>Leam
>
>-- 
>Site Reliability Engineer  (reuel.net/resume)
>Chronicler: The Domici War (domiciwar.net)
>General Ne'er-do-well      (github.com/LeamHall)
>_______________________________________________
>Ale mailing list
>Ale at ale.org
>https://mail.ale.org/mailman/listinfo/ale
>See JOBS, ANNOUNCE and SCHOOLS lists at
>http://mail.ale.org/mailman/listinfo

-- 
Computers amplify human error
Super computers are really cool
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.ale.org/pipermail/ale/attachments/20210420/bdfe5644/attachment.htm>