From: Jim Paris <jim@jtan.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, muthas@mit.edu, fragmede@gmail.com
Subject: sata_sis only recognizing primary drive in 2.6.18
Date: Fri, 6 Oct 2006 02:58:16 -0400 [thread overview]
Message-ID: <20061006065816.GA5782@jim.sh> (raw)
Hi Tejun,
My friend has a motherboard with a SIS182 chipset (1039:0182), with
four ports on the motherboard. BIOS sees it as two controllers,
"IDE2" and "IDE3" with two ports apiece: "IDE2 Primary", "IDE2
Secondary", etc.
If we plug drives into both the IDE2 Primary and IDE2 Secondary ports,
BIOS correctly sees and identifies both drives, and they're both
visible to grub, but sata_sis only sees the primary drive. The second
drive just never shows up; no errors are reported. This is with
Debian kernel 2.6.18 (same thing happens in .15, .16, .17). Changing
various SATA-related BIOS settings doesn't help.
I don't have any logs on me at the moment, but I'm trying to get a
hold of this machine for a few days so I can put in a PATA root disk
and build/test custom libata modules with more debugging info. Is
there anything in particular I should look for or try?
If I request warmplug with
echo 0 0 0 > /sys/class/scsi_host/host1/scan
or
echo 0 1 0 > /sys/class/scsi_host/host1/scan
then there is a soft-reset and the primary disk is rediscovered in
both cases, but neither causes the secondary disk to be discovered.
Also, hotplug polling doesn't seem to work. Removed disks aren't
recognized as gone until I/O is attempted, and I have to request
warmplug to get an inserted disk recognized. It's otherwise working
fine.
-jim
next reply other threads:[~2006-10-06 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 6:58 Jim Paris [this message]
2006-10-06 10:57 ` sata_sis only recognizing primary drive in 2.6.18 Uwe Koziolek
2006-10-06 21:22 ` Jim Paris
2006-10-08 4:24 ` Tejun Heo
2006-10-21 21:04 ` Uwe Koziolek
2006-10-23 2:14 ` Tejun Heo
2006-10-23 8:45 ` Uwe Koziolek
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=20061006065816.GA5782@jim.sh \
--to=jim@jtan.com \
--cc=fragmede@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=muthas@mit.edu \
/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).