Failed disk initialization logged as warning `ata3.00: disabled` instead with more severe log level

Failed disk initialization logged as warning `ata3.00: disabled` instead with more severe log level

[Paul Menzel]

Dear Linux folks,


A disk died on an old system, and is not displayed by `lsblk` anymore 
after a reboot. I would have expected such an event be logged with a 
severe level.

     @moppel:~$ dmesg --level=emerg
     @moppel:~$ dmesg --level=alert
     @moppel:~$ dmesg --level=crit
     @moppel:~$ dmesg --level=err
     [   24.450604] ata3.00: failed to set xfermode (err_mask=0x4)
     [   39.810617] ata3.00: failed to set xfermode (err_mask=0x4)
     @moppel:~$ dmesg --level=warn
     [    1.039497] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
     [    2.539408] pci 0000:03:00.0: can't disable ASPM; OS doesn't 
have ASPM control
     [    3.088540] ACPI Warning: SystemIO range 
0x0000000000000428-0x000000000000042F conflicts with OpRegion 
0x0000000000000400-0x000000000000047F (\PMIO) (20200925/utaddress-213)
     [    3.114469] ACPI Warning: SystemIO range 
0x0000000000000540-0x000000000000054F conflicts with OpRegion 
0x0000000000000500-0x0000000000000563 (\GPIO) (20200925/utaddress-213)
     [    3.140390] ACPI Warning: SystemIO range 
0x0000000000000530-0x000000000000053F conflicts with OpRegion 
0x0000000000000500-0x0000000000000563 (\GPIO) (20200925/utaddress-213)
     [    3.166311] ACPI Warning: SystemIO range 
0x0000000000000500-0x000000000000052F conflicts with OpRegion 
0x0000000000000500-0x0000000000000563 (\GPIO) (20200925/utaddress-213)
     [    3.192226] lpc_ich: Resource conflict(s) found affecting gpio_ich
     [    3.900324] i8042: PNP: PS/2 controller doesn't have KBD irq; 
using default 1
     [    9.086414] ata3.00: qc timeout (cmd 0x27)
     [    9.090618] ata3.00: failed to read native max address 
(err_mask=0x4)
     [    9.097155] ata3.00: HPA support seems broken, skipping HPA handling
     [   24.446401] ata3.00: qc timeout (cmd 0xef)
     [   24.456189] ata3: limiting SATA link speed to 1.5 Gbps
     [   24.461423] ata3.00: limiting speed to UDMA/133:PIO3
     [   39.806416] ata3.00: qc timeout (cmd 0xef)
     [   39.816203] ata3.00: disabled

The xfermode message is logged as an error, but I have system, where the 
device is still functional. The actual disabled message is “only” logged 
as a warning.

Is there a way to improve the logging, and log a failed initialization 
of a disk with a higher level? Maybe even critical or alert?


Kind regards,

Paul