On Tue, Jul 28 2015 at 3:23pm -0400, Andreas Hartmann <andihartmann@xxxxxxxxxx> wrote: > On 07/28/2015 at 08:58 PM, Mike Snitzer wrote: > > On Tue, Jul 28 2015 at 2:20pm -0400, > > Andreas Hartmann <andihartmann@xxxxxxxxxx> wrote: > > > >> On 07/28/2015 at 07:50 PM, Mike Snitzer wrote: > >> [..] > >>> Are your SATA devcies using NCQ? > >> > >> Yes. It's enabled: > >> > >> dmesg| grep -i ncq > >> ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part > >> ata2.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA > >> ata3.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA > >> ata1.00: 468862128 sectors, multi 16: LBA48 NCQ (depth 31/32), AA > >> > >> As the errors already come up on boot (during mount of partitions or > >> even before the password for the disk has been provided): How can I > >> disable NCQ during boot of the kernel? Is there a kernel option? > > > > See: > > https://ata.wiki.kernel.org/index.php/Libata_FAQ#Enabling.2C_disabling_and_checking_NCQ > > > > alternatively, and likely easier, set this on the kernel commandline: > > libata.force=noncq > > ata2.00: FORCE: horkage modified (noncq) > ata2.00: 5860533168 sectors, multi 0: LBA48 NCQ (not used) > ata3.00: FORCE: horkage modified (noncq) > ata3.00: 5860533168 sectors, multi 0: LBA48 NCQ (not used) > ata5.00: FORCE: horkage modified (noncq) > ata1.00: FORCE: horkage modified (noncq) > ata1.00: 468862128 sectors, multi 16: LBA48 NCQ (not used) > > > Perfectly. Seems to work w/ 3.19.8 and your mentioned patches. But now, > I'm getting another error, which I didn't see before w/ 3.x-kernels: > > [drm:btc_dpm_set_power_state [radeon]] *ERROR* > rv770_restrict_performance_levels_before_switch failed > > It seams that your patches do have some unwanted side effects :-). That is a completely different issue. drm and radeon is a graphics issue. > Could you please reexamine your patch "dm crypt: don't allocate > pages for a partial request" - after applying this patch all the > problems are coming up here. More likely than not your hardware isn't very good. -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
