From: "Berck E. Nash" <flyboy@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] ahci: do not powerdown during initialization
Date: Fri, 24 Nov 2006 10:53:39 -0700 [thread overview]
Message-ID: <456731A3.8070807@gmail.com> (raw)
In-Reply-To: <20061120064236.GM2184@htj.dyndns.org>
Tejun Heo wrote:
> This patch moves power up/down out of port init/deinit and call them
> only when needed.
> ---
>
> Berck, can you please test this patch? This might fix your problem
> too. Jeff, this patch is necessary regardless of Berck's repsonse. I
> think this should go into #usptream-fixes too after some testing in
> #upstream (and in -mm).
Nope, that doesn't do it. All along I've also been getting weird
messages on system power-downs. I just now set up a serial console to
capture them. I dunno if they're of any significance, but they're on
the same device that pauses on boot, so perhaps they're related.
Berck
Will now halt.
[ 538.178188] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.191083] ata2.00: (irq_stat 0x40000001)
[ 538.199288] ata2.00: tag 0 cmd 0xe0 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.222873] ata2.00: configured for UDMA/133
[ 538.231432] ata2: EH complete
[ 538.237406] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.250289] ata2.00: (irq_stat 0x40000001)
[ 538.258497] ata2.00: tag 0 cmd 0xe0 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.282048] ata2.00: configured for UDMA/133
[ 538.290606] ata2: EH complete
[ 538.296580] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.309465] ata2.00: (irq_stat 0x40000001)
[ 538.317672] ata2.00: tag 0 cmd 0xe0 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.341206] ata2.00: configured for UDMA/133
[ 538.349764] ata2: EH complete
[ 538.355738] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.368621] ata2.00: (irq_stat 0x40000001)
[ 538.376834] ata2.00: tag 0 cmd 0xe0 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.400367] ata2.00: configured for UDMA/133
[ 538.408920] ata2: EH complete
[ 538.414894] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.427783] ata2.00: (irq_stat 0x40000001)
[ 538.435987] ata2.00: tag 0 cmd 0xe0 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.459528] ata2.00: configured for UDMA/133
[ 538.468077] ata2: EH complete
[ 538.474054] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.486941] ata2.00: (irq_stat 0x40000001)
[ 538.495144] ata2.00: tag 0 cmd 0xe0 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.518681] ata2.00: configured for UDMA/133
[ 538.527242] ata2: EH complete
[ 538.533219] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.546113] ata2.00: (irq_stat 0x40000001)
[ 538.554319] ata2.00: tag 0 cmd 0x94 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.577860] ata2.00: configured for UDMA/133
[ 538.586410] ata2: EH complete
[ 538.592387] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.605269] ata2.00: (irq_stat 0x40000001)
[ 538.613475] ata2.00: tag 0 cmd 0x94 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.637015] ata2.00: configured for UDMA/133
[ 538.645566] ata2: EH complete
[ 538.651540] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.664425] ata2.00: (irq_stat 0x40000001)
[ 538.672634] ata2.00: tag 0 cmd 0x94 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.696179] ata2.00: configured for UDMA/133
[ 538.704742] ata2: EH complete
[ 538.710716] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.723601] ata2.00: (irq_stat 0x40000001)
[ 538.731807] ata2.00: tag 0 cmd 0x94 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.755349] ata2.00: configured for UDMA/133
[ 538.763900] ata2: EH complete
[ 538.769873] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.782765] ata2.00: (irq_stat 0x40000001)
[ 538.790965] ata2.00: tag 0 cmd 0x94 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.814513] ata2.00: configured for UDMA/133
[ 538.823073] ata2: EH complete
[ 538.829047] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 538.841933] ata2.00: (irq_stat 0x40000001)
[ 538.850140] ata2.00: tag 0 cmd 0x94 Emask 0x1 stat 0x51 err 0x4
(device error)
[ 538.873679] ata2.00: configured for UDMA/133
[ 538.882233] ata2: EH complete
[ 538.888199] SCSI device sdd: 640 512-byte hdwr sectors (0 MB)
[ 538.890404] Synchronizing SCSI cache for disk sde:
[ 538.909477] sdd: Write Protect is off
[ 538.916822] SCSI device sdd: drive cache: write through
[ 538.927285] SCSI device sdd: 640 512-byte hdwr sectors (0 MB)
[ 538.938797] Synchronizing SCSI cache for disk sdc:
[ 538.948561] sdd: Write Protect is off
[ 538.949171] Synchronizing SCSI cache for disk sdb:
[ 538.949424] Synchronizing SCSI cache for disk sda:
[ 538.975451] SCSI device sdd: drive cache: write through
[ 539.441444] Shutdown: hdg
[ 539.446910] Shutdown: hde
[ 539.452716] Power down.
[ 539.457706] acpi_power_off called
next prev parent reply other threads:[~2006-11-24 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 6:42 [PATCH] ahci: do not powerdown during initialization Tejun Heo
2006-11-24 17:53 ` Berck E. Nash [this message]
2006-11-28 9:15 ` Jeff Garzik
2006-11-29 3:52 ` Tejun Heo
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=456731A3.8070807@gmail.com \
--to=flyboy@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
/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).