All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Regression? 2.6.23.16 -> 2.6.32.9: ide/libata HD recognition
Date: Wed, 10 Mar 2010 13:47:49 -0500	[thread overview]
Message-ID: <hn8pgl$eqd$1@dough.gmane.org> (raw)
In-Reply-To: <20100310041614.GG2657@zip.com.au>

CaT wrote:
> 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:
> 
Could you "ls /sys/block" and post? And /var/log/messages from the start to the 
last device found? Thanks.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot


  reply	other threads:[~2010-03-10 18:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  4:16 Regression? 2.6.23.16 -> 2.6.32.9: ide/libata HD recognition CaT
2010-03-10 18:47 ` Bill Davidsen [this message]
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='hn8pgl$eqd$1@dough.gmane.org' \
    --to=davidsen@tmr.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.