From: Meelis Roos <mroos@linux.ee>
To: Tejun Heo <tj@kernel.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
sparclinux@vger.kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>,
sam@ravnborg.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: OF-related boot crash in 3.3.0-rc3-00188-g3ec1e88
Date: Wed, 22 Feb 2012 02:36:13 +0200 (EET) [thread overview]
Message-ID: <alpine.SOC.1.00.1202220213180.4171@math.ut.ee> (raw)
In-Reply-To: <20120221010537.GA15898@dhcp-172-17-108-109.mtv.corp.google.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 645 bytes --]
> Meelis, can you please apply the following patch before & after the
> offending commit, boot with "memblock=debug" added as kernel param and
> post the boot log? The patch will generate some offset warnings after
> the commit but should work fine.
Before the commit (v3.2-rc3-75-g0ee332c): memblock1.gz (attached)
After the commit (v3.2-rc3-76-g7bd0b0f): memblock2.gz (attached)
In addition, a third type of sparc machines breaks in a third way - V210
and V240 just hang after telling
console [tty0] enabled, bootconsole disabled
and before calibrating the delay loop. Bisect has led to the same commit.
--
Meelis Roos (mroos@linux.ee)
[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 49939 bytes --]
[-- Attachment #3: Type: APPLICATION/octet-stream, Size: 39513 bytes --]
next prev parent reply other threads:[~2012-02-22 0:36 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 20:56 [PATCH v3.3-rc5] memblock: Fix size aligning of memblock_alloc_base_nid() Tejun Heo
2012-02-13 7:45 ` OF-related boot crash in 3.3.0-rc3-00188-g3ec1e88 Meelis Roos
2012-02-13 8:06 ` Grant Likely
2012-02-13 9:20 ` Meelis Roos
2012-02-13 21:46 ` Grant Likely
2012-02-14 0:58 ` David Miller
2012-02-14 2:30 ` Grant Likely
2012-02-14 2:41 ` Grant Likely
2012-02-16 21:08 ` mroos
2012-02-14 5:54 ` mroos
2012-02-16 19:53 ` Meelis Roos
2012-02-16 21:23 ` Sam Ravnborg
2012-02-20 9:11 ` Meelis Roos
2012-02-20 17:06 ` Tejun Heo
2012-02-20 20:04 ` Meelis Roos
2012-02-20 21:01 ` Tejun Heo
2012-02-20 22:32 ` Meelis Roos
2012-02-21 1:05 ` Tejun Heo
2012-02-22 0:36 ` Meelis Roos [this message]
2012-02-22 17:48 ` Tejun Heo
2012-02-22 18:25 ` Meelis Roos
2012-02-23 18:55 ` Tejun Heo
2012-02-23 23:31 ` David Miller
2012-02-24 9:20 ` Meelis Roos
2012-02-27 17:17 ` Meelis Roos
2012-02-27 19:43 ` Sam Ravnborg
2012-02-27 21:25 ` Meelis Roos
2012-02-27 21:30 ` David Miller
2012-02-28 21:10 ` David Miller
2012-02-28 21:36 ` Meelis Roos
2012-02-28 22:56 ` David Miller
2012-02-29 6:15 ` Meelis Roos
2012-02-29 6:27 ` David Miller
2012-02-22 20:44 ` David Miller
2012-02-22 21:00 ` Tejun Heo
2012-02-22 18:22 ` Richard Mortimer
2012-02-22 20:26 ` David Miller
2012-02-22 17:03 ` Sam Ravnborg
2012-02-22 17:12 ` Meelis Roos
2012-02-22 17:21 ` Sam Ravnborg
2012-02-22 17:41 ` Meelis Roos
2012-02-13 9:50 ` Meelis Roos
2012-02-13 9:51 ` Meelis Roos
2012-02-13 10:35 ` Meelis Roos
2012-03-01 12:24 ` [tip:core/urgent] memblock: Fix size aligning of memblock_alloc_base_nid() tip-bot for Tejun Heo
2012-02-28 22:16 ` [PATCH v3.3-rc5] " Sam Ravnborg
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=alpine.SOC.1.00.1202220213180.4171@math.ut.ee \
--to=mroos@linux.ee \
--cc=davem@davemloft.net \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=tj@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
all inboxes | Powered by JetHome®