All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Heider <a.heider@gmail.com>
To: Alexander Aring <alex.aring@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: raspberry pi mmc issue
Date: Tue, 15 Oct 2013 20:39:27 +0200	[thread overview]
Message-ID: <20131015183927.GB51758@gmail.com> (raw)
In-Reply-To: <20131015183110.GA20967@omega>

Hi,

On Tue, Oct 15, 2013 at 08:31:11PM +0200, Alexander Aring wrote:
> Hi Sascha,
> 
> On Tue, Oct 15, 2013 at 02:23:32PM +0200, Sascha Hauer wrote:
> > The only thing I realize here is that my 3.6.4 kernel fails to access
> > the SD card when barebox has accessed it before:
> > 
> > [    3.623861] mmc0: SD Status: Invalid Allocation Unit size.
> > [    3.635586] mmc0: error -110 whilst initialising SD card
> > [    3.724743] mmc0: SD Status: Invalid Allocation Unit size.
> > [    3.739073] mmc0: error -110 whilst initialising SD card
> > [    3.836341] mmc0: SD Status: Invalid Allocation Unit size.
> > [    3.847708] mmc0: error -110 whilst initialising SD card
> > [    3.965447] mmc0: read SD Status register (SSR) after 3 attempts
> > [    3.971483] mmc0: SD Status: Invalid Allocation Unit size.
> 
> Mhh, I think my patch would not fix your problem. I successful access
> the sdcard after booting linux, but this was on qemu...

I'm not seeing the issue here either (using Linus' master).

Regards,
Andre

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2013-10-15 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 11:51 raspberry pi mmc issue Alexander Aring
2013-10-15 12:23 ` Sascha Hauer
2013-10-15 18:31   ` Alexander Aring
2013-10-15 18:39     ` Andre Heider [this message]
2013-10-16  7:23       ` Sascha Hauer

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=20131015183927.GB51758@gmail.com \
    --to=a.heider@gmail.com \
    --cc=alex.aring@gmail.com \
    --cc=barebox@lists.infradead.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.