From: tabris <tabris@tabris.net>
To: Eric Mudama <edmudama@gmail.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org
Subject: Re: undecoded slave?
Date: Fri, 24 Sep 2004 04:26:08 -0400 [thread overview]
Message-ID: <200409240426.09861.tabris@tabris.net> (raw)
In-Reply-To: <311601c90409231841774f5168@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 23 September 2004 9:41 pm, Eric Mudama wrote:
> On Fri, 24 Sep 2004 02:09:13 +0200, Bartlomiej Zolnierkiewicz
>
> <bzolnier@elka.pw.edu.pl> wrote:
> > On Thursday 23 September 2004 22:30, tabris wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > On Thursday 23 September 2004 7:14 am, Bartlomiej Zolnierkiewicz
wrote:
> > > > [ use linux-ide@vger.kernel.org for ATA stuff ]
> > > >
> > > > On Thursday 23 September 2004 05:57, tabris wrote:
> > > > > Probing IDE interface ide3...
> > > > > hdg: Maxtor 4D060H3, ATA DISK drive
> > > > > hdh: Maxtor 4D060H3, ATA DISK drive
> > > > > ide-probe: ignoring undecoded slave
> > > > >
> > > > > Booted 2.6.9-rc2-mm2, and I no longer have an hdh. the error
> > > > > above seems to be the only [stated] reason why.
> > > >
> > > > Please send hdparm -I output for both drives.
> > >
> > > As you can see, both drives are the same brand/size/model.
> > > Both are connected to the PDC20265 on my ASUS A7V266-E
> > > motherboard.
> > >
> > > /dev/hdg:
> > >
> > > ATA device, with non-removable media
> > > Model Number: Maxtor 4D060H3
> > > Serial Number: D3000000
> > > Firmware Revision: DAK019K0
> >
> > Thanks.
> > It seems we will need to add this Serial Number to "undecoded
> > slave" fixup.
> >
> > Please also send /proc/ide/hd?/identify to exclude kernel/hdparm
> > parsing bug.
>
> I'm confused, and I think something else must be going on... to have
> 2 different drives, with two completely different ASICs in them (and
> therefore significantly different object code), have identical
> corruption of the same 6 bytes of their configuration block is just
> not likely. I'm pretty sure they don't even have the same utility
> zone layout.
>
> Is that how the drive IDs when connected via other controllers, in
> another system, etc?
I'd have to get back to you on that, as I had no intention of taking my
machine down for such a purpose. But if you truly would need this info,
it could be provided within a day or two.
>
> hrm...
>
> eric
- --
tabris
- -
Reinhart was never his mother's favorite -- and he was an only child.
-- Thomas Berger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBU9og1U5ZaPMbKQcRApBDAJ9zDlviuLYzN9HEEn8LimDmfnECpQCeNXOE
n9Qpr+Et1G73rInipBEiDG8=
=N5Oc
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-09-24 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409222357.39492.tabris@tabris.net>
[not found] ` <200409231630.49153.tabris@tabris.net>
[not found] ` <200409240209.13884.bzolnier@elka.pw.edu.pl>
2004-09-24 8:24 ` undecoded slave? tabris
[not found] ` <311601c90409231841774f5168@mail.gmail.com>
2004-09-24 8:26 ` tabris [this message]
2004-09-24 16:29 ` Eric Mudama
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=200409240426.09861.tabris@tabris.net \
--to=tabris@tabris.net \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@elka.pw.edu.pl \
--cc=edmudama@gmail.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).