Comment 7 for bug 925760

Revision history for this message
Neal McBurnett (nealmcb) wrote :

I do not see the bug when booting in precise using the oneiric kernel 3.0.0-16-generic

I do see the same bug in 3.1: ~kernel-ppa/mainline/v3.1.10-precise - the Ubuntu build of the mainline 3.1.10 kernel: 3.1.10-030110-generic #201201181135

So it looks like a regression in the mainline kernel 3.1

And I hate it when my logs and consoles get filled up with stuff that doesn't otherwise matter :/

The code that prints the KERN_NOTICE messages is in linux/drivers/scsi/sd.c, and says it is only called when sd_revalidate_disk() is called. Why would that be called every 52 seconds? Here are some snippets from around each of the three messages:

* ... read write protect setting, if possible - called only in sd_revalidate_disk()
sd_read_write_protect_flag(struct scsi_disk *sdkp, unsigned char *buffer)
{....
  if (sdp->skip_ms_page_3f) {
  sd_printk(KERN_NOTICE, sdkp, "Assuming Write Enabled\n");
...
 if (!scsi_status_is_good(res)) {
  sd_printk(KERN_WARNING, sdkp,
     "Test WP failed, assume Write Enabled\n");

...
sd_read_cache_type - called only from sd_revalidate_disk()
....
 if (scsi_sense_valid(&sshdr) &&
     sshdr.sense_key == ILLEGAL_REQUEST &&
     sshdr.asc == 0x24 && sshdr.ascq == 0x0)
  /* Invalid field in CDB */
  sd_printk(KERN_NOTICE, sdkp, "Cache data unavailable\n");
 else
  sd_printk(KERN_ERR, sdkp, "Asking for cache data failed\n");