From: Jens Axboe <axboe@suse.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jason Lunz <lunz@gehennom.net>, Jiri Slaby <jirislaby@gmail.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, andre@linux-ide.org, pavel@suse.cz,
linux-pm@osdl.org, linux-ide@vger.kernel.org
Subject: Re: swsusp regression [Was: 2.6.18-rc3-mm2]
Date: Tue, 8 Aug 2006 10:41:16 +0200 [thread overview]
Message-ID: <20060808084116.GF4025@suse.de> (raw)
In-Reply-To: <200608072247.59184.rjw@sisk.pl>
On Mon, Aug 07 2006, Rafael J. Wysocki wrote:
> On Monday 07 August 2006 18:23, Jason Lunz wrote:
> > In gmane.linux.kernel, you wrote:
> > >> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc3/2.6.18-rc3-mm2/
> > >
> > > I tried it and guess what :)... swsusp doesn't work :@.
> > >
> > > This time I was able to dump process states with sysrq-t:
> > > http://www.fi.muni.cz/~xslaby/sklad/ide2.gif
> > >
> > > My guess is ide2/2.0 dies (hpt370 driver), since last thing kernel prints is
> > > suspending device 2.0
> >
> > Does it go away if you revert this?
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc3/2.6.18-rc3-mm2/broken-out/ide-reprogram-disk-pio-timings-on-resume.patch
> >
> > That should only affect resume, not suspend, but it does mess around
> > with ide power management. Is this maybe happening on the *second*
> > suspend?
> >
> > > -hdc: ATAPI 63X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
> > > +hdc: ATAPI CD-ROM drive, 0kB Cache, UDMA(33)
> >
> > This looks suspicious. -mm does have several ide-fix-hpt3xx patches.
>
> I found that git-block.patch broke the suspend for me. Still have no idea
> what's up with it.
Can you apply this on top of -mm and see if that fixes it?
diff --git a/drivers/ide/ide-io.c b/drivers/ide/ide-io.c
index d2339e9..db647a9 100644
--- a/drivers/ide/ide-io.c
+++ b/drivers/ide/ide-io.c
@@ -390,7 +390,7 @@ void ide_end_drive_cmd (ide_drive_t *dri
args[5] = hwif->INB(IDE_HCYL_REG);
args[6] = hwif->INB(IDE_SELECT_REG);
}
- } else if (rq->cmd_type & REQ_TYPE_ATA_TASKFILE) {
+ } else if (rq->cmd_type == REQ_TYPE_ATA_TASKFILE) {
ide_task_t *args = (ide_task_t *) rq->special;
if (rq->errors == 0)
rq->errors = !OK_STAT(stat,READY_STAT,BAD_STAT);
--
Jens Axboe
next prev parent reply other threads:[~2006-08-08 8:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060806030809.2cfb0b1e.akpm@osdl.org>
2006-08-07 9:28 ` swsusp regression [Was: 2.6.18-rc3-mm2] Jiri Slaby
2006-08-07 16:23 ` Jason Lunz
2006-08-07 20:47 ` Rafael J. Wysocki
2006-08-08 8:41 ` Jens Axboe [this message]
2006-08-08 9:49 ` Jiri Slaby
2006-08-08 10:43 ` Jens Axboe
2006-08-08 10:08 ` Jiri Slaby
2006-08-08 10:43 ` Jens Axboe
2006-08-08 10:59 ` Rafael J. Wysocki
2006-08-08 11:04 ` Jens Axboe
2006-08-08 11:07 ` Jens Axboe
2006-08-08 11:16 ` Rafael J. Wysocki
2006-08-08 11:19 ` Jens Axboe
2006-08-08 13:50 ` Rafael J. Wysocki
2006-08-08 14:06 ` Jens Axboe
2006-08-08 16:41 ` Jiri Slaby
2006-08-08 17:53 ` Jens Axboe
2006-08-07 21:09 ` Jiri Slaby
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=20060808084116.GF4025@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=andre@linux-ide.org \
--cc=jirislaby@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=lunz@gehennom.net \
--cc=pavel@suse.cz \
--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).