From: "Arend van Spriel" <arend@broadcom.com>
To: Philip Rakity <prakity@marvell.com>
Cc: linux-mmc@vger.kernel.org
Subject: Re: v3.6-rc1: modprobe hangs with sdhci failure on dell e6410
Date: Sun, 26 Aug 2012 10:03:55 +0200 [thread overview]
Message-ID: <5039D86B.5040208@broadcom.com> (raw)
In-Reply-To: <35709C36-C251-4701-965A-D3B5DBD6B66A@marvell.com>
On 08/24/2012 10:10 PM, Philip Rakity wrote:
>
> Arend,
>
> Are you saying issue has nothing to do with mmc ?
Nope. What I meant to be saying is:
1. the issue occurs regardless whether the slot is populated or not.
2. it occurs on multiple machine so it seems not a hardware issue on a
single machine.
3. the issue is not seen on same laptop model running 64-bit kernel.
Gr. AvS
> Philip
> On Aug 24, 2012, at 12:58 PM, Arend van Spriel <arend@broadcom.com> wrote:
>
>> On 08/24/2012 10:24 AM, Arend van Spriel wrote:
>>> On 08/23/2012 04:58 PM, Aaron Lu wrote:
>>>> On Wed, Aug 22, 2012 at 10:11 PM, Arend van Spriel
>>>> <arend@broadcom.com> wrote:
>>>>> A quick search using google did not provide clues. Regardless if
>>>>> there is
>>>>> anything inserted the hang occurs.
>>>>>
>>>>> Gr. AvS
>>>>
>>>> Also, your .config might be helpful.
>>>
>>> True. Here it is.
>>>
>>> Gr. AvS
>>
>> Inspected the logs on another machine running the same kernel and it has
>> the same issue. I was not using the mmc slot on that machine so I was
>> not aware. On x86_64 I am not seeing the issue (so far).
>>
>> Gr. AvS
>>
>
>
prev parent reply other threads:[~2012-08-26 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 14:11 v3.6-rc1: modprobe hangs with sdhci failure on dell e6410 Arend van Spriel
2012-08-23 5:10 ` Aaron Lu
2012-08-23 14:58 ` Aaron Lu
2012-08-24 8:24 ` Arend van Spriel
2012-08-24 19:58 ` Arend van Spriel
[not found] ` <35709C36-C251-4701-965A-D3B5DBD6B66A@marvell.com>
2012-08-26 8:03 ` Arend van Spriel [this message]
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=5039D86B.5040208@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-mmc@vger.kernel.org \
--cc=prakity@marvell.com \
/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