Maciej Rutecki wrote:
quoted text
> I have this message when resume from suspend to disk:
> 
> hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
> hda: MWDMA2 mode selected
> sd 0:0:0:0: [sda] Starting disk
> [...]
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
> ata1.00: ACPI cmd b1/c1:00:00:00:00:a0 filtered out
> ata1.00: ACPI cmd c6/00:10:00:00:00:a0 succeeded
> ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded
> ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out
> ata1.00: ACPI cmd b1/c1:00:00:00:00:a0 filtered out
> ata1.00: ACPI cmd c6/00:10:00:00:00:a0 succeeded
> ata1.00: ACPI cmd ef/10:03:00:00:00:a0 succeeded
> ata1.00: configured for UDMA/133
> ata1: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x9 t4
> ata1: irq_stat 0x00400040, connection status changed
> ata1.00: configured for UDMA/133
> ata1: EH complete
> sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
> sd 0:0:0:0: [sda] Write Protect is off
> sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> 
> Suspend to disk works fine without any problems.

Those are newly added ACPI command filtering and KERN_DEBUG messages.
As we're following what BIOS is telling us, we definitely want to filter
and log what rubbish it tells us.  :-)

Thanks.

-- 
tejun
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/