All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Alexandre Felipe Muller de Souza <alexandrefm@mandriva.com.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mmc@vger.kernel.org
Subject: Re: DRIVERS MMC card freezes at Jmicron controllers.
Date: Wed, 04 May 2011 19:45:21 -0400	[thread overview]
Message-ID: <m3fwou114e.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <1304531944.6868.17.camel@localhost.localdomain> (Alexandre Felipe Muller de Souza's message of "Wed, 04 May 2011 14:59:04 -0300")

Hi Alexandre, adding linux-mmc@ to CC.  (EOF)

On Wed, May 04 2011, Alexandre Felipe Muller de Souza wrote:
> Hi, all.
> I wrote an email minutes ago and I think it could be delivered missing
> half of the content for mistake using email editor. Sorry for that
>
> We have users, reporting problems with MMC cards and JMicron controller
> devices. We have here to test more than one Pc (with Jmicron) with the
> same problem. It freezes completely after the insert of stick. Using
> 2.6.33 to 2.6.39 RC6 the error is the same. I tried many alternatives,
> but with no success. If there is a idea that could make a fix on it
> please copy me on thread.
>
> lspci:
> 02:00.2 SD Host controller: JMicron Technologies, Inc. Standard SD Host
> Controller (rev 80) (prog-if 01)
>         Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device
> 2000                                
>         Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B- DisINTx-
>         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx- 
>         Interrupt: pin B routed to IRQ
> 18                                                                    
>         Region 0: Memory at febff800 (32-bit, non-prefetchable)
> [size=256]                                   
>         Capabilities: [a4] Power Management version
> 3                                                        
>                 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)                   
>                 Status: D0 PME-Enable- DSel=0 DScale=0
> PME-                                                  
>         Capabilities: [80] Express (v1) Endpoint, MSI
> 00                                                     
>                 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
> <64ns, L1 <1us                        
>                         ExtTag- AttnBtn- AttnInd- PwrInd- RBE+
> FLReset-                                      
>                 DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported-                           
>                         RlxdOrd+ ExtTag- PhantFunc- AuxPwr-
> NoSnoop-                                         
>                         MaxPayload 128 bytes, MaxReadReq 128
> bytes                                           
>                 DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr-
> TransPend-                          
>                 LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1,
> Latency L0 unlimited, L1 unlimited    
>                         ClockPM- Surprise- LLActRep-
> BwNot-                                                  
>                 LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
> CommClk+                              
>                         ExtSynch- ClockPM- AutWidDis- BWInt-
> AutBWInt-                                       
>                 LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+
> DLActive- BWMgmt- ABWMgmt-           
>         Capabilities: [94] MSI: Mask- 64bit- Count=1/1
> Enable-                                               
>                 Address: fffffffc  Data:
> 0000                                                                
>         Kernel modules: sdhci-pci
>
> Before death it outputs on log
> mmc0:new MMC card at...
> mmcblk0:mmc0 ...
> ldm_validade_partition_table() Disk read failed
> mmcblk0: retrying using single block read
> error -110 transfering data, sector 0, card status nr8, 0xb00
>
> I'll still trying something, but if anybody knows about it warn me.
> Thanks
> Alexandre

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-05-04 23:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 17:59 DRIVERS MMC card freezes at Jmicron controllers Alexandre Felipe Muller de Souza
2011-05-04 23:45 ` Chris Ball [this message]
2011-05-11 14:47 ` DRM/I915 wrong monitor resolution Alexandre Felipe Muller de Souza

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=m3fwou114e.fsf@pullcord.laptop.org \
    --to=cjb@laptop.org \
    --cc=alexandrefm@mandriva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@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.