From: Eric Mudama <edmudama@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Kernel 2.6.9 undecoded slave problem, fixed in 2.6.10-rc2-bk8!
Date: Thu, 2 Dec 2004 14:53:39 -0700 [thread overview]
Message-ID: <311601c904120213533b67ed3a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0412020925040.25494@p500>
Um... if it happens on one controller and not another, the bug
shouldn't be in the drives themselves. Every Maxtor drive ever made
has a unique serial number, and the ones people are seeing are
completely invalid.
This issue should be root caused, something is getting stomped on, and
it may affect more than just the ID of the drive. I fear that these
are bandaids covering some underlying issue.
--eric
On Thu, 2 Dec 2004 09:27:20 -0500 (EST), Justin Piszcz
<jpiszcz@lucidpixels.com> wrote:
> The interesting part of all of this is that this only occurs when I have
> the two cdroms on a promise controller, on the same IDE channel, normally
> I have them both on the motherboard as master and slave. I wanted to make
> sure the card worked however, so switched the connection over to the
> promise board and then I am getting the same error as the guy above,
> except in my case it is with two identical CDROMS and not hard drives.
>
> The problem occurs with 2.6.9.
>
> -------------------------------------------------------------------------
>
> Update: With 2.6.10-rc2-bk8, it has fixed the problem!
>
> hde: SAMSUNG SC-140B, ATAPI CD/DVD-ROM drive
> hdf: SAMSUNG SC-140B, ATAPI CD/DVD-ROM drive
> ide2 at 0xd8f8-0xd8ff,0xd8f2 on irq 11
> hde: ATAPI 40X CD-ROM drive, 128kB Cache
> Uniform CD-ROM driver Revision: 3.20
> hdf: ATAPI 40X CD-ROM drive, 128kB Cache
> Probing IDE interface ide3...
>
> root@p500b:~# mount /dev/hde /mnt/cd1
> mount: block device /dev/hde is write-protected, mounting read-only
> root@p500b:~# mount /dev/hdf /mnt/cd2
> mount: block device /dev/hdf is write-protected, mounting read-only
> root@p500b:~#
parent reply other threads:[~2004-12-02 21:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.61.0412020925040.25494@p500>]
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=311601c904120213533b67ed3a@mail.gmail.com \
--to=edmudama@gmail.com \
--cc=jpiszcz@lucidpixels.com \
--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;
as well as URLs for NNTP newsgroup(s).