diff options
| author | Nikanth Karthikesan <knikanth@suse.de> | 2011-03-17 11:04:14 +0530 |
|---|---|---|
| committer | Jiri Kosina <jkosina@suse.cz> | 2011-04-10 17:01:03 +0200 |
| commit | 1dd45aae79b821620ce45765e6210d77173fcecd (patch) | |
| tree | f4f505e1a9f318139451e6e4fa1d9ea22d0dd5a4 /fs | |
| parent | 853a1378ed6d6c9214d3a8f62d33186c6283cb51 (diff) | |
| download | linux-3.10-1dd45aae79b821620ce45765e6210d77173fcecd.tar.gz linux-3.10-1dd45aae79b821620ce45765e6210d77173fcecd.tar.bz2 linux-3.10-1dd45aae79b821620ce45765e6210d77173fcecd.zip | |
ldm: Silence "ldm_validate_partition_table(): Disk read failed" when booting with "quiet"
When the kernel does partition detection, on certain configurations with
external fibre channel raid systems (e.g. clariion from EMC) the read
would fail. And "ldm_validate_partition_table(): Disk read failed"
messages are printed to the console.
But the failure to read is not a critical error. Now since the message
is flagged as KERN_CRIT, it gets printed even when booting with the
"quiet" kernel parameter. Fix it by using KERN_INFO, as the failure to
read here is not really an error.
Signed-off-by: Nikanth Karthikesan <knikanth@suse.de>
Reported-by : Klaus Hartmann <Klaus.Hartmann@ts.fujitsu.com>
Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'fs')
| -rw-r--r-- | fs/partitions/ldm.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/partitions/ldm.c b/fs/partitions/ldm.c index b10e3540d5b..ea648b913be 100644 --- a/fs/partitions/ldm.c +++ b/fs/partitions/ldm.c @@ -565,7 +565,7 @@ static bool ldm_validate_partition_table(struct parsed_partitions *state) data = read_part_sector(state, 0, §); if (!data) { - ldm_crit ("Disk read failed."); + ldm_info ("Disk read failed."); return false; } |