[ale] OS or Hardware issue?

[Phil Turmel]

Under no circumstances should you ever place first-level block device 
names into your config files (like fstab).  Though not likely, any 
kernel update can change the order.  And in some cases, kernel 
parallelism can mix the sequence from multiple PCI devices.  (Also not 
likely, but I've seen it.)  Use a LABEL or UUID instead of /dev/sdXY. 
Names based on LVM group and volume names are fine.

On 4/20/21 6:20 AM, Leam Hall via Ale 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
>