Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
scsi: 3w-sas: Correct log level of several messages
On a Dell PowerEdge T630, Linux logs some 3w-sas warnings: $ dmesg | grep DMI: [ 0.000000] DMI: Dell Inc. PowerEdge T630/0W9WXC, BIOS 2.5.4 08/17/2017 $ dmesg --level=warn | grep 3w [ 22.449617] 3w-sas: scsi12: AEN: INFO (0x04:0x0053): Battery capacity test is overdue:. [ 22.680618] 3w-sas: scsi12: Found an LSI 3ware 9750-8e Controller at 0xc8040000, IRQ: 117. [ 23.001611] 3w-sas: scsi12: Firmware FH9X 5.12.00.016, BIOS BE9X 5.11.00.007, Phys: 8. These are obviously no warnings, and just informational messages. Look through the file, and adapt the log level of several messages mostly according to the level string in the message. The message below is the only tricky change, as the log level actually depends on the AEN severity determined by `twl_aen_severity_lookup()`. printk(KERN_INFO "3w-sas:%s AEN: %s (0x%02X:0x%04X): %s:%s.\n", host, twl_aen_severity_lookup(TW_SEV_OUT(header->status_block.severity__reserved)), TW_MESSAGE_SOURCE_CONTROLLER_EVENT, aen, error_str, header->err_specific_desc); The AEN severity levels below exist. /* AEN severity table */ static char *twl_aen_severity_table[] = { "None", "ERROR", "WARNING", "INFO", "DEBUG", NULL }; It’s demoted from a warning to an informational message nevertheless to avoid adding if-else statements. Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
- Loading branch information