lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C854502.8040009@kernel.org>
Date:	Mon, 06 Sep 2010 21:46:10 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Kyle McMartin <kyle@...artin.ca>
CC:	jgarzik@...hat.com, linux-ata@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: libata acpi issue on gateway laptop

On 09/06/2010 09:35 PM, Kyle McMartin wrote:
> Hi Jeff,
> 
> A user is reporting an issue with 2.6.34.6 on a Gateway laptop that
> booting with libata.noacpi=1 resolves.
> 
> Symptom is that their device dumps a lot of messages like this:
> 
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device
> (Stat=0x51 Err=0x04)
> ata1.00: ACPI cmd ef/10:01:00:00:00:a0 (SET FEATURES) succeeded
> ata1.00: ACPI cmd ef/10:02:00:00:00:a0 (SET FEATURES) succeeded
> ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
> ata1.00: ACPI cmd ef/10:04:00:00:00:a0 (SET FEATURES) succeeded
> ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device
> (Stat=0x51 Err=0x04)
> ata1.00: ATA-8: Hitachi HTS545050B9A300, PB4OC60F, max UDMA/133
> ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
> ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device
> (Stat=0x51 Err=0x04)
> ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
> ata1.00: ACPI cmd ef/10:05:00:00:00:a0 (SET FEATURES) rejected by device
> (Stat=0x51 Err=0x04)
> ata1.00: configured for UDMA/133
> 
> on boot and resume from suspend.
> 
> Dmesg is at https://bugzilla.redhat.com/attachment.cgi?id=442529 and the
> full bug report at https://bugzilla.redhat.com/show_bug.cgi?id=629315.
> 
> Any ideas? They say the issue exists all the way back to 2.6.31, so it
> seems like a pretty long-lived bug.

These are debug/info messages.  Just ignore them.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ