From: Meelis Roos <mroos@linux.ee>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: CMD646 & cdrom: drive appears confused & drive not ready for command
Date: Mon, 17 Dec 2007 13:08:01 +0200 (EET) [thread overview]
Message-ID: <Pine.SOC.4.64.0712171306350.23091@math.ut.ee> (raw)
In-Reply-To: <20071217025952.ad1017fa.akpm@linux-foundation.org>
> > So when did thi start? Is 2.6.23 OK?
I have 2.6.23 running now and will see if something happens.
> > Are there any other consequences apart from log spam?
Any CD communication seems to be impossible after this starts. Will
retest when it happens again.
--
Meelis Roos (mroos@linux.ee)
prev parent reply other threads:[~2007-12-17 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOC.4.64.0712162015210.27847@math.ut.ee>
[not found] ` <20071217025903.cef552f1.akpm@linux-foundation.org>
2007-12-17 10:59 ` CMD646 & cdrom: drive appears confused & drive not ready for command Andrew Morton
2007-12-17 11:08 ` Meelis Roos [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=Pine.SOC.4.64.0712171306350.23091@math.ut.ee \
--to=mroos@linux.ee \
--cc=akpm@linux-foundation.org \
--cc=linux-ide@vger.kernel.org \
--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