From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Tupshin Harper1 <tupshin@tupshin.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: /dev/hdl not showing up because of fix-ide-probe-double-detection patch
Date: Thu, 05 Aug 2004 16:36:08 +0100 [thread overview]
Message-ID: <1091720165.8041.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20040804224709.3c9be248.akpm@osdl.org>
On Iau, 2004-08-05 at 06:47, Andrew Morton wrote:
> > Well, I found the source of the problem. Dmesg gives a "ignoring
> > undecoded slave" message, which is coming from the
> > fix-ide-probe-double-detection patch.
>
> Ah, thanks for working that out.
>
> Did you know that Cc: stands for "copy culprit"?
>
> > Both /dev/hdk and /dev/hdl are the same model of hard drive, and
> > unfortunately, they both report that they are Model
> > M0000000000000000000, which triggers the double detection removal.
I need the real model and serial number information not "MOOO" to debug
this kind of thing
> > Also, what is in /proc/ide/hd?/identity besides serial number. The two
> > drives have very similar identity files, but they are slightly
> > different. Could that additional info be used to check for duplicates?
Two disks are not permitted to have the same serial number. If you can
give me the full ident data I'll take a detailed look - could be I'm not
comparing enough bytes if its only different on the last digit.
Alan
next prev parent reply other threads:[~2004-08-05 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 22:38 /dev/hdl not showing up with 2.6.8-rc2-mm1 Tupshin Harper1
2004-08-04 22:37 ` /dev/hdl not showing up because of fix-ide-probe-double-detection patch Tupshin Harper1
2004-08-05 5:47 ` Andrew Morton
2004-08-05 15:36 ` Alan Cox [this message]
2004-08-05 23:04 ` Mark Lord
2004-08-05 23:58 ` Alan Cox
2004-08-09 18:19 ` Tupshin Harper
2004-08-09 19:06 ` Alan Cox
2004-08-09 20:39 ` Joel Jaeggli
2004-08-09 20:18 ` 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=1091720165.8041.4.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tupshin@tupshin.com \
/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