From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: cb-lkml@fish.zetnet.co.uk
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] IDE: Fix Power Management request race on resume
Date: Wed, 10 Sep 2003 11:30:58 +0200 [thread overview]
Message-ID: <1063186257.642.67.camel@gaston> (raw)
In-Reply-To: <20030910092522.GA1916@fish.zetnet.co.uk>
On Wed, 2003-09-10 at 11:25, cb-lkml@fish.zetnet.co.uk wrote:
> On Wed, Sep 10, 2003 at 11:16:15AM +0200, Benjamin Herrenschmidt wrote:
> > On Wed, 2003-09-10 at 11:04, cb-lkml@fish.zetnet.co.uk wrote:
> > > I applied this patch to 2.6.0-test5 and still have this problem:
> > >
> > > http://marc.theaimsgroup.com/?l=linux-kernel&m=106218353005043&w=2
> >
> > There are a couple of other fixes pending though I don't thing
> > they are related to your problem. Do you have a slave drive on
> > this channel ? What driver are you using for the host controller ?
> > Does it have a dma_check() function ?
>
> It's a laptop, so there's no slave drive.
Some laptops have the CD/DVD as a slave
>
> The host controller is a PIIX4, using CONFIG_BLK_DEV_PIIX. (Presumably
> drivers/ide/pci/piix.c)
>
> $ grep dma_check piix.c
> hwif->ide_dma_check = &piix_config_drive_xfer_rate;
Can you put some printk in there to verify it's properly called on
wakeup and that it actually does something ?
Note that problem may be unrelated to the IDE driver, it could also
be some APIC problem messing with interrupts...
Ben.
next prev parent reply other threads:[~2003-09-10 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 9:04 [PATCH] IDE: Fix Power Management request race on resume cb-lkml
2003-09-10 9:16 ` Benjamin Herrenschmidt
2003-09-10 9:25 ` cb-lkml
2003-09-10 9:30 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-09 18:39 Benjamin Herrenschmidt
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=1063186257.642.67.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=cb-lkml@fish.zetnet.co.uk \
--cc=linux-kernel@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