From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Failed disk initialization logged as warning `ata3.00: disabled` instead with more severe log level
Date: Wed, 18 Aug 2021 14:58:40 +0200 [thread overview]
Message-ID: <e5cc55d4-ef08-cd57-f1b0-cd15df43dc8b@molgen.mpg.de> (raw)
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
reply other threads:[~2021-08-18 12:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5cc55d4-ef08-cd57-f1b0-cd15df43dc8b@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=axboe@kernel.dk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).