From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org
Subject: Regression? 2.6.23.16 -> 2.6.32.9: ide/libata HD recognition
Date: Wed, 10 Mar 2010 15:16:15 +1100 [thread overview]
Message-ID: <20100310041614.GG2657@zip.com.au> (raw)
Hi,
Just had a strange situation with the above upgrade. It was done on an
old server that used the serverworks ide driver. The IDE hw config under
2.6.23.16 was:
hda: HD
hdb: CDROM
hdc: empty
hdd: HD
After upgrade, using either IDE or libata the config changed to:
hda: HD
hdb: CDROM
hdc: empty
hdd: empty
The BIOS recognised the disk. I went through 3 disks and it wasn't until
I made the second HD a master that it was recognised. So now I have a
2.6.32.9 server, using the IDE subsystem with the following config:
hda: HD
hdb: CDROM
hdc: HD
hdd: empty
Otherwise it does not work.
I had an outage window that I already blew so I was not able to do
any more diagnosis than what it took to get the system up.
If anyone wants the full config I'll send. Otherwise:
IDE subsystem (no libata subsystem configured):
CONFIG_HAVE_IDE=y
CONFIG_IDE=y
CONFIG_IDE_XFER_MODE=y
CONFIG_IDE_ATAPI=y
CONFIG_IDE_GD=y
CONFIG_IDE_GD_ATA=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
CONFIG_BLK_DEV_IDEACPI=y
CONFIG_IDE_PROC_FS=y
CONFIG_BLK_DEV_IDEDMA_SFF=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_PCIBUS_ORDER=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_LEDS_TRIGGER_IDE_DISK=y
libata kernel (no IDE subsystem configured):
CONFIG_ATA=y
CONFIG_ATA_VERBOSE_ERROR=y
CONFIG_ATA_ACPI=y
CONFIG_SATA_PMP=y
CONFIG_ATA_SFF=y
CONFIG_PATA_SERVERWORKS=y
--
"A search of his car uncovered pornography, a homemade sex aid, women's
stockings and a Jack Russell terrier."
- http://www.news.com.au/story/0%2C27574%2C24675808-421%2C00.html
next reply other threads:[~2010-03-10 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 4:16 CaT [this message]
2010-03-10 18:47 ` Regression? 2.6.23.16 -> 2.6.32.9: ide/libata HD recognition Bill Davidsen
2010-03-11 22:54 ` CaT
2010-03-12 0:04 ` Robert Hancock
2010-03-13 7:39 ` CaT
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=20100310041614.GG2657@zip.com.au \
--to=cat@zip.com.au \
--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