<html><head></head><body>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.<br><br>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.<br><br>Of course any conductive dust is sn obvious problem. Tiny metal slivers from sliding drive carriers around can wreak havoc in stability.<br><br>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).<br><br><div class="gmail_quote">On April 20, 2021 6:20:42 AM EDT, Leam Hall via Ale <ale@ale.org> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">I haven't kept up with the low level processes, not sure where today's <br>issues came from. Using Void Linux, updated Sunday, and multiple planned <br>boots since updating. Refurb Dell 960.<br><br>This morning:<br><br> 1. Drive letter re-org, it tried to boot from the back-up drive. <br>/dev/sdc was labelled as /dev/sdb.<br><br> 2. Did a hard reboot, and then the keyboard wouldn't input.<br><br> 3. Shutdown via mouse, and things seem to work.<br><br><br>Looks like BIOS, according to dmesg:<br><br>dmesg |egrep -i "error|warning"<br>[ 0.019961] ACPI BIOS Warning (bug): 32/64X length mismatch in <br>FADT/Gpe0Block: 128/64 (20201113/tbfadt-564)<br>[ 2.655673] ACPI BIOS Warning (bug): Incorrect checksum in table <br>[TCPA] - 0x00, should be 0x7F (20201113/tbprint-173)<br>[ 5.659170] random: 6 urandom warning(s) missed due to ratelimiting<br>[ 9.513809] ACPI Warning: SystemIO range <br>0x0000000000000828-0x000000000000082F conflicts with OpRegion <br>0x0000000000000828-0x000000000000082D (\GLBC) (20201113/utaddress-204)<br>[ 9.513820] ACPI Warning: SystemIO range <br>0x0000000000000828-0x000000000000082F conflicts with OpRegion <br>0x000000000000082A-0x000000000000082A (\SACT) (20201113/utaddress-204)<br>[ 9.513826] ACPI Warning: SystemIO range <br>0x0000000000000828-0x000000000000082F conflicts with OpRegion <br>0x0000000000000828-0x0000000000000828 (\SSTS) (20201113/utaddress-204)<br>[ 9.513836] ACPI Warning: SystemIO range <br>0x00000000000008B0-0x00000000000008BF conflicts with OpRegion <br>0x00000000000008B8-0x00000000000008BB (\GIC2) (20201113/utaddress-204)<br>[ 9.513844] ACPI Warning: SystemIO range <br>0x0000000000000880-0x00000000000008AF conflicts with OpRegion <br>0x000000000000088C-0x000000000000088F (\GIC1) (20201113/utaddress-204)<br>[ 11.394756] udevd[657]: Error calling EVIOCSKEYCODE on device node <br>'/dev/input/event2' (scan code 0xc022d, key code 103): Invalid argument<br>[ 11.394862] udevd[657]: Error calling EVIOCSKEYCODE on device node <br>'/dev/input/event2' (scan code 0xc022e, key code 108): Invalid argument<br>[ 16.285931] platform regulatory.0: Direct firmware load for <br>regulatory.db failed with error -2<br><br>It works for the moment, so I'll get some more backups and research. And <br>work on a BIOS update. Suggestions welcome.<br><br>Leam<br></pre></blockquote></div><br>-- <br>Computers amplify human error<br>Super computers are really cool</body></html>