From: Tejun Heo <htejun@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: davidsen@tmr.com, linux-kernel@vger.kernel.org,
pm list <linux-pm@lists.linux-foundation.org>,
linux-ext4@vger.kernel.org
Subject: Re: 2.6.33-rc6 crashes on resume
Date: Tue, 09 Feb 2010 12:32:42 +0900 [thread overview]
Message-ID: <4B70D75A.7010600@gmail.com> (raw)
In-Reply-To: <201002090016.18027.rjw@sisk.pl>
On 02/09/2010 08:16 AM, Rafael J. Wysocki wrote:
> On Tuesday 09 February 2010, Bill Davidsen wrote:
>> Pretty simple to reproduce, boot, suspend, press shift
>>
>> Acer Aspire 1681, Celeron, 2.6.33-rc6. Trace and config attached.
>
> This looks suspicious:
>
> Feb 8 17:32:47 roadwarrior3 kernel: ata2.00: ACPI cmd 03/42:00:00:00:a0:ef (CFA REQUEST EXTENDED ERROR) rejected by device (Stat=0x51 Err=0x04)
> Feb 8 17:32:47 roadwarrior3 kernel: sd 0:0:0:0: [sda] Starting disk
> Feb 8 17:32:47 roadwarrior3 kernel: ata2.00: ACPI cmd 00/0c:00:00:00:a0:ef (NOP) rejected by device (Stat=0x51 Err=0x04)
> Feb 8 17:32:47 roadwarrior3 kernel: ata2.00: configured for UDMA/33
> Feb 8 17:32:47 roadwarrior3 kernel: firewire_core: rediscovered device fw0
> Feb 8 17:32:47 roadwarrior3 kernel: ata1.00: ACPI cmd 03/45:00:00:00:a0:ef (CFA REQUEST EXTENDED ERROR) rejected by device (Stat=0x51 Err=0x04)
> Feb 8 17:32:47 roadwarrior3 kernel: ata1.00: ACPI cmd 00/0c:00:00:00:a0:ef (NOP) rejected by device (Stat=0x51 Err=0x04)
> Feb 8 17:32:47 roadwarrior3 kernel: ata1.00: configured for UDMA/100
These aren't harmful in themselves. It just means that the device
failed commands BIOS requested via ACPI. Just in case, does
"libata.noacpi=1" make any difference to the oops?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-02-09 3:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B70982F.8090208@roadwarrior3.tmr.com>
2010-02-08 23:16 ` 2.6.33-rc6 crashes on resume Rafael J. Wysocki
2010-02-09 3:32 ` Tejun Heo [this message]
2010-02-09 15:05 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B70D75A.7010600@gmail.com \
--to=htejun@gmail.com \
--cc=davidsen@tmr.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).