From: Domenico Andreoli <cavokz@gmail.com>
To: linux-parisc@vger.kernel.org
Subject: Re: my usual problem with 64bit kernel
Date: Tue, 15 Dec 2009 21:25:47 +0100 [thread overview]
Message-ID: <20091215202547.GA18193@raptus.dandreoli.com> (raw)
In-Reply-To: <20091209235038.GA12806@raptus.dandreoli.com>
On Thu, Dec 10, 2009 at 12:50:38AM +0100, Domenico Andreoli wrote:
> On Tue, Dec 08, 2009 at 12:44:04AM +0100, Domenico Andreoli wrote:
> > On Sat, Dec 05, 2009 at 09:35:11AM +0100, Domenico Andreoli wrote:
> > > On Fri, Dec 04, 2009 at 07:50:10PM +0100, Helge Deller wrote:
> > >
> > > > I just want to make sure, that you have more or less a correct kernel
> > > > configuration setup (.config)....
> > >
> > > there is at least a configuration glitch which makes my kernel hang
> > > and the debian one continue in degraded mode. i attached also the
> > > configuration, just in case i forgot something important.
> >
> > i found the configuration glitch, it is CONFIG_DEBUG_MUTEXES. if it is
> > set, 64bit hangs right after "Releasing cpu 1 now, hpa=...", otherwise
> > the 64bit boot continues with a "SMP: CPU:1 is stuck."
>
> i was wrong, it's again CONFIG_DEBUG_SPINLOCK. if it is set, the
> boot hangs.
i bisected something, commit 44048d700bcbfaf4bcca6e2e0a73d89d01ec0878
breaks my SMP parisc64. before it, kernel boots with 2 CPUs
(as did 2.6.22). after it, it hangs at "Releasing cpu 1 now,
hpa=fffffffffffa2000" but CONFIG_DEBUG_SPINLOCK is _not_ set, the
opposite i reported in this thread at 64bit and consistently with
current 2.6.32 at 32bit.
i'm pretty confused by the whole thing but i'm sure about this bisection,
i double-checked it. here is the diff.
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -749,23 +749,6 @@ int move_freepages_block(struct zone *zone, struct page *page, int migratetype)
return move_freepages(zone, start_page, end_page, migratetype);
}
-/* Return the page with the lowest PFN in the list */
-static struct page *min_page(struct list_head *list)
-{
- unsigned long min_pfn = -1UL;
- struct page *min_page = NULL, *page;;
-
- list_for_each_entry(page, list, lru) {
- unsigned long pfn = page_to_pfn(page);
- if (pfn < min_pfn) {
- min_pfn = pfn;
- min_page = page;
- }
- }
-
- return min_page;
-}
next prev parent reply other threads:[~2009-12-15 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 17:28 my usual problem with 64bit kernel Domenico Andreoli
2009-12-04 18:50 ` Helge Deller
2009-12-05 8:35 ` Domenico Andreoli
2009-12-07 23:44 ` Domenico Andreoli
2009-12-09 23:50 ` Domenico Andreoli
2009-12-10 17:08 ` Kyle McMartin
2009-12-10 18:42 ` Domenico Andreoli
2009-12-10 18:47 ` Domenico Andreoli
2009-12-15 20:25 ` Domenico Andreoli [this message]
2009-12-16 3:37 ` Kyle McMartin
2009-12-16 4:21 ` John David Anglin
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=20091215202547.GA18193@raptus.dandreoli.com \
--to=cavokz@gmail.com \
--cc=linux-parisc@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