It seems to me that kernel errors, specifically those from the scsi driver, are being wrapped, which confounds automated log monitoring.
Example from dmesg -- the lines I marked with X are being printed on separate lines where they previously weren't.
[6461080.699629] sd 0:2:2:0: [sdc] Unhandled sense code [6461080.699646] sd 0:2:2:0: [sdc] [6461080.699650] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE X [6461080.699653] sd 0:2:2:0: [sdc] [6461080.699655] Sense Key : Medium Error [current] X [6461080.699661] sd 0:2:2:0: [sdc] [6461080.699663] Add. Sense: No additional sense information X [6461080.699667] sd 0:2:2:0: [sdc] CDB: [6461080.699669] Read(16): 88 00 00 00 00 00 0c 23 92 e0 00 00 00 08 00 00 X [6461080.699684] end_request: I/O error, dev sdc, sector 203657952
I'm fairly certain this affects 3.2 to pre-4.1, and was sane in lucid. I'm certain it affects quantal to utopic, and vivid is partially mitigated.
It seems to me that kernel errors, specifically those from the scsi driver, are being wrapped, which confounds automated log monitoring.
Example from dmesg -- the lines I marked with X are being printed on separate lines where they previously weren't.
[6461080.699629] sd 0:2:2:0: [sdc] Unhandled sense code DRIVER_ SENSE X
[6461080.699646] sd 0:2:2:0: [sdc]
[6461080.699650] Result: hostbyte=DID_OK driverbyte=
[6461080.699653] sd 0:2:2:0: [sdc]
[6461080.699655] Sense Key : Medium Error [current] X
[6461080.699661] sd 0:2:2:0: [sdc]
[6461080.699663] Add. Sense: No additional sense information X
[6461080.699667] sd 0:2:2:0: [sdc] CDB:
[6461080.699669] Read(16): 88 00 00 00 00 00 0c 23 92 e0 00 00 00 08 00 00 X
[6461080.699684] end_request: I/O error, dev sdc, sector 203657952
I'm fairly certain this affects 3.2 to pre-4.1, and was sane in lucid. I'm certain it affects quantal to utopic, and vivid is partially mitigated.