On Sun, 1 Mar 1998, Paul Gortmaker wrote:
> I don't think that J. Random Luser should be allowed to do this:
This is a harmless message -- it just means that we tried to read
the S.M.A.R.T thresholds/values, and the drive simply reported that
it doesn't support S.M.A.R.T.
Gadi
> -----------------------------------------------------
> wallace:/proc/ide/ide0/hda> cat smart_thresholds
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> wallace:/proc/ide/ide0/hda> cat smart_values
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> wallace:/proc/ide/ide0/hda>
> -----------------------------------------------------
Not harmless at all.
First of all a random user has no business approaching the hardware
like this.
Secondly, a random user must not be able to produce an infinite
stream of kernel error messages, possibly making the console unusable,
possibly filling up the kernel log.
If the situation is harmless, the kernel *must not* complain.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu