public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: hdc (cdrom) irq timeout after awaking from sleep on powerbook
Date: Thu, 10 Jun 2004 11:08:20 -0500	[thread overview]
Message-ID: <1086883699.2975.141.camel@gaston> (raw)
In-Reply-To: <1086847896.24317.41.camel@localhost>

On Thu, 2004-06-10 at 01:11, Soeren Sonnenburg wrote:
> Hi...
> 
> When I insert + mount a cdrom and then put this powerbook to sleep mode,
> I keep getting these messages in the kernel log when the machine wakes
> up. However I can still access the cdrom on its mount point as if
> everything was ok... but is it ?

Well... at least it lost the DMA which isn't good. But our driver tends
to be a bit nasty for that. We may probably want a smarter wakeup
sequence for ide-cd that the current one that does nothing (just use the
default IDE one which is to wait for BUSY to be gone). I suspect some
ATAPIs would love getting a new WIN_PIDENTIFY at least, and I've seen
some take time before actually _raising_ BUSY ... I'll look into it.

> This is kernel 2.6.7-rc2 on powerbook g4 1Ghz.
> 
> Please comment,
> Regards,
> Soeren.
> 
> VFS: busy inodes on changed media.
> hdc: irq timeout: status=0xc0 { Busy }
> hdc: irq timeout: error=0xc0LastFailedSense 0x0c 
> hdc: DMA disabled
> hdc: ATAPI reset complete
> VFS: busy inodes on changed media.
-- 
Benjamin Herrenschmidt <benh@kernel.crashing.org>


      reply	other threads:[~2004-06-10 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10  6:11 hdc (cdrom) irq timeout after awaking from sleep on powerbook Soeren Sonnenburg
2004-06-10 16:08 ` Benjamin Herrenschmidt [this message]

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=1086883699.2975.141.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=kernel@nn7.de \
    --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