public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: cbou@mail.ru
Cc: kernel-discuss@handhelds.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genhd fix or ide workaround -- choose one
Date: Thu, 19 Oct 2006 13:05:52 +0100	[thread overview]
Message-ID: <1161259553.17335.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20061018221506.GA4187@localhost>

Ar Iau, 2006-10-19 am 02:15 +0400, ysgrifennodd Anton Vorontsov:
> Hi all,
> 
> I've caught deadlock inside IDE layer using IDE-CS: after accessing
> to IDE disk placed in PCMCIA (CF card really), it will never probe
> again after pulling it from PCMCIA/CF.

Works for me, and has done for a long time and I've also had no other
reports of this in the past couple of years so I'm curious what trips it
in your case ?

> The kernel is stuck at
> drivers/ide/ide.c:ide_unregister():604:
> 
>         602                 spin_unlock_irq(&ide_lock);
>         603                 device_unregister(&drive->gendev);
>         604                 wait_for_completion(&drive->gendev_rel_comp);
>         605                 spin_lock_irq(&ide_lock);

We need to know all the references have gone away, if someone has a disk
referenced and you pull it out we can't clean up immediately so this is
the right place to get stuck both on a refcounting bug and if you've got
something holding a reference for real (eg HAL)




  reply	other threads:[~2006-10-19 12:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 22:15 [PATCH] genhd fix or ide workaround -- choose one Anton Vorontsov
2006-10-19 12:05 ` Alan Cox [this message]
2006-10-19 12:25   ` Anton Vorontsov
2006-10-19 13:08     ` Alan Cox
2006-10-19 13:33       ` Anton Vorontsov
2006-10-19 14:16         ` Anton Vorontsov

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=1161259553.17335.30.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=cbou@mail.ru \
    --cc=kernel-discuss@handhelds.org \
    --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