public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-mmc@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
	bugme-daemon@bugzilla.kernel.org, pioto@pioto.org
Subject: Re: [Bugme-new] [Bug 18602] New: mmc_block / tifm_sd not completely registering when a new sd card is inserted
Date: Wed, 15 Sep 2010 12:38:54 -0700	[thread overview]
Message-ID: <20100915123854.e36e432c.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-18602-10286@https.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Wed, 15 Sep 2010 13:48:30 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=18602
> 
>            Summary: mmc_block / tifm_sd not completely registering when a
>                     new sd card is inserted
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.35.4
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: MMC/SD
>         AssignedTo: drivers_mmc-sd@kernel-bugs.osdl.org
>         ReportedBy: pioto@pioto.org
>         Regression: No
> 
> 
> After I insert an SD card once after booting, mount it, unmount it, then pop
> out the card, if I try to insert the card again, the /dev/mmcblk* devices do
> not show again. I have to unload the mmc_block and tifm_sd (and mmc_core)
> modules, then reload them, in order for the device node to apear again. I don't
> think this was always the case, but I can't remember the specific version that
> this problem first occurred.
> 
> On the first insertion cycle, dmsg looks like this:
> 
>   [204702.558153] tifm_core: MMC/SD card detected in socket 0:1
>   [204702.834915] mmc0: new SD card at address 4f9a
>   [204702.878743] mmcblk0: mmc0:4f9a SD02G 1.83 GiB 
>   [204702.878802]  mmcblk0: p1
>   # ... do stuff with the card
>   [204908.381864] tifm0 : demand removing card from socket 0:1
>   [204908.381936] mmc0: card 4f9a removed
> 
>   # now, insert the card again
>   [204913.581176] tifm_core: MMC/SD card detected in socket 0:1
>   # and remove it again
>   [204926.188570] tifm0 : demand removing card from socket 0:1
> 
> lspci identifies my SD card reader as:
> 
>   0f:06.3 SD Host controller: Texas Instruments PCIxx12 SDA Standard Compliant
> SD Host Controller
> 
> Any advice would be appreciated. Thanks.
> 


       reply	other threads:[~2010-09-15 19:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-18602-10286@https.bugzilla.kernel.org/>
2010-09-15 19:38 ` Andrew Morton [this message]
2010-09-17 13:54   ` [Bugme-new] [Bug 18602] New: mmc_block / tifm_sd not completely registering when a new sd card is inserted Matt Fleming
2010-09-18  7:23     ` Alex Dubov
2010-09-18  9:01       ` Mike Kelly
2010-09-19  5:19         ` Alex Dubov
2010-09-19 14:56           ` Mike Kelly
2010-09-20  0:50             ` Alex Dubov
2010-09-21  3:25               ` Mike Kelly
2010-09-21  3:50                 ` Alex Dubov

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=20100915123854.e36e432c.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=pioto@pioto.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