Control: reassign -1 src:linux 3.12.6-1 On Mon, 2013-12-30 at 07:13 +0800, jidanni@xxxxxxxxxxx wrote: > Package: linux-image-3.12-1-686-pae > > Currently any such devices as below that are attached during boot still > produce the below SIX messages per device when they should only produce > TWO: > > # dmesg |egrep Caching\|Assuming > [ 3.960663] sd 3:0:0:0: [sdb] No Caching mode page found > [ 3.960701] sd 3:0:0:0: [sdb] Assuming drive cache: write through > [ 3.978659] sd 3:0:0:0: [sdb] No Caching mode page found > [ 3.978694] sd 3:0:0:0: [sdb] Assuming drive cache: write through > [ 3.998652] sd 3:0:0:0: [sdb] No Caching mode page found > [ 3.998689] sd 3:0:0:0: [sdb] Assuming drive cache: write through > [ 4.174630] sd 2:0:0:2: [sde] No Caching mode page found > [ 4.174669] sd 2:0:0:2: [sde] Assuming drive cache: write through > [ 4.196628] sd 2:0:0:2: [sde] No Caching mode page found > [ 4.196664] sd 2:0:0:2: [sde] Assuming drive cache: write through > [ 4.220624] sd 2:0:0:2: [sde] No Caching mode page found > [ 4.220661] sd 2:0:0:2: [sde] Assuming drive cache: write through > > Please confirm that you also see the six messages right there on the > console stderr. I'm not seeing it at all here as my SSD apparently does implement the caching mode page. I can see that it is emitted by sd_read_cache_type(), which is called by sd_revalidate_disk(), and that is apparently now called 3 times during probe. Which is quite ridiculous. And I wonder whether this situation (no caching mode page) is really serious enough to deserve logging at ERR severity? Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky
Attachment:
signature.asc
Description: This is a digitally signed message part
