From: Andi Kleen <andi@firstfloor.org>
To: "Stephan Sürken" <absurd@olurdix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mmc@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 15836] Commit 6ad696d2cf535772dff659298ec7e7260e344595 breaks my SD card reader [197b:2381]
Date: Sun, 2 May 2010 01:04:43 +0200 [thread overview]
Message-ID: <20100501230443.GB8074@gargoyle.fritz.box> (raw)
In-Reply-To: <1272739661.10538.30.camel@weslok.olx.intra>
> I explicitly confirmed this on top of 2.6.33.2:
Thanks that makes a bit more sense.
>
> config-2.6.33.2.git19f00f0-config-2.6.33-2-amd64.nohiber:CONFIG_MEMORY_HOTPLUG=y
> =>"bad"
> config-2.6.33.2.git19f00f0-config-2.6.33-2-amd64.nohotplug:# CONFIG_MEMORY_HOTPLUG is not set
> =>"good"
>
> So any code enabled by CONFIG_MEMORY_HOTPLUG is the winner, presumable
> somewhere in the mmc code (?).
I doubt the mmc code really knows anything about memory hotplug.
Must be some subtle side effect.
Can send the diff of two boot logs with memory hotplug on and off?
I wonder if you have the same memory layout in both cases.
-Andi
next prev parent reply other threads:[~2010-05-01 23:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15836-27@https.bugzilla.kernel.org/>
[not found] ` <201004262048.o3QKml95025961@demeter.kernel.org>
2010-04-26 20:58 ` [Bug 15836] Commit 6ad696d2cf535772dff659298ec7e7260e344595 breaks my SD card reader [197b:2381] Andrew Morton
2010-04-27 10:59 ` Stephan Suerken
2010-04-28 22:41 ` Matt Fleming
2010-04-30 17:06 ` Andi Kleen
2010-05-01 18:47 ` Stephan Sürken
2010-05-01 23:04 ` Andi Kleen [this message]
[not found] ` <1272912441.7490.6.camel@weslok.olx.intra>
2010-05-04 20:13 ` Andi Kleen
2010-07-20 19:53 ` Stephan Sürken
[not found] <bug-15836-2531@https.bugzilla.kernel.org/>
[not found] ` <201004282338.o3SNcfHW007926@demeter.kernel.org>
2010-04-30 16:53 ` Stephan Sürken
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=20100501230443.GB8074@gargoyle.fritz.box \
--to=andi@firstfloor.org \
--cc=absurd@olurdix.de \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).