linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Windisch <eric@grokthis.net>
To: htejun@gmail.com
Cc: linux-ide@vger.kernel.org
Subject: Libata PMP patch /w sil3124... 'device or resource busy'
Date: Thu, 03 Aug 2006 18:58:16 -0400	[thread overview]
Message-ID: <44D27F88.1070807@grokthis.net> (raw)

I've attempted to use the patch here, against 2.6.17.7 (it patched 
cleanly)...
  
http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17.4-20060710.tar.bz2

While I can partition the disks and see my created partitions, when 
attempting to use 'mdadm --create' or mkfs.ext3, I get the error:
"Device or resource busy".

The disks are not mounted or otherwise being accessed (such as via 
software raid or lvm).  My hardware is a sil3124 controller, 5 sata 
drives, and a couple Sil 3726 PMP's (embedded in a Norco 1220 disk array).

I plan to further test against 2.6.18-rc3 and 2.6.17.4 /w patch.

Any initial suggestions before I try the other kernels?

Thank you.

                 reply	other threads:[~2006-08-03 22:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=44D27F88.1070807@grokthis.net \
    --to=eric@grokthis.net \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).