From: Andrew Morton <akpm@osdl.org>
To: Tupshin Harper1 <tupshin@tupshin.com>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: /dev/hdl not showing up because of fix-ide-probe-double-detection patch
Date: Wed, 4 Aug 2004 22:47:09 -0700 [thread overview]
Message-ID: <20040804224709.3c9be248.akpm@osdl.org> (raw)
In-Reply-To: <4111651E.1040406@tupshin.com>
Tupshin Harper1 <tupshin@tupshin.com> wrote:
>
> Tupshin Harper1 wrote:
>
> > I have an x86 setup with a large(9) number of ide hard drives. With
> > 2.6.8-rc2, all of them show up (as a,b,d,e,f,g,h,i,j,k, and l), but on
> > 2.6.8-rc2-mm1, the last one (hdl) does not show up, even though it's a
> > slave on the same controller as hdk. Everything about the config is
> > identical between the two. Is there some default limit or other
> > restriction in the current mm kernels that's preventing that drive
> > from showing up? I haven't tried any other recent mm kernels, so I
> > don't know when this was introduced.
> >
> > -Tupshin
>
> 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.
>
> Does anybody have a suggestion (besides maintaining my own kernel
> without this patch)? Is the serial number settable? Is there a boot
> param I can use?
>
> 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?
>
> -Tupshin
>
> ---snippet from dmesg---
> PDC20276: IDE controller at PCI slot 0000:00:0c.0
> ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 19 (level, low) -> IRQ 19
> PDC20276: chipset revision 1
> PDC20276: 100% native mode on irq 19
> ide4: BM-DMA at 0xdc00-0xdc07, BIOS settings: hdi:pio, hdj:pio
> ide5: BM-DMA at 0xdc08-0xdc0f, BIOS settings: hdk:pio, hdl:pio
> hdi: SAMSUNG SV8004H, ATA DISK drive
> hdj: Maxtor 6Y250P0, ATA DISK drive
> ide4 at 0xec00-0xec07,0xe802 on irq 19
> hdk: Maxtor 4R120L0, ATA DISK drive
> hdl: Maxtor 4R120L0, ATA DISK drive
> ide-probe: ignoring undecoded slave
> ide5 at 0xe400-0xe407,0xe002 on irq 19
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-08-05 5:49 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 [this message]
2004-08-05 15:36 ` Alan Cox
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=20040804224709.3c9be248.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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
Powered by JetHome