Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: Linux MIPS List <linux-mips@linux-mips.org>
Cc: akpm@osdl.org
Subject: Commit 78eef01b0fae087c5fadbd85dd4fe2918c3a015f (on_each_cpu(): disable local interrupts) Breaks SGI IP32
Date: Sat, 27 May 2006 17:13:21 -0400	[thread overview]
Message-ID: <4478C0F1.8000006@gentoo.org> (raw)


Finally managed to track down the git commit causing SGI IP32 (O2) systems to 
lock up really early in the boot cycle, but I'm at a loss to understand why.

Effect:
It appears the system silently hangs somewhere in the void between function 
calls when trying to invoke the memset() call in __alloc_bootmem_core() in 
mm/bootmem.c.  This puts the machine hardware in a state such that a simple soft 
reset doesn't clear it -- the machine has to be cold booted to get it to boot a 
working kernel again.

Determined Cause:
It seems this commit:
78eef01b0fae087c5fadbd85dd4fe2918c3a015f
	[PATCH] on_each_cpu(): disable local interrupts

Is the cause.  I've verified this by reversing this one change on a 2.6.17-rc4 
tree, and it'll boot to a mini-userland (initramfs-based) and appears to 
function normally.


But this is as far as I can trace this.  I'm not sure what this change is doing 
internally that's triggering this lockup on O2 systems.  It doesn't appear to 
affect Octane (IP30) systems or Origin (IP27).  I haven't test-ran it on 
IP22/IP28 hardware yet, so only IP32 is known to be affected.  Unsure about 
non-SGI MIPS hardware.

Thoughts?


--Kumba

-- 
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees

"Such is oft the course of deeds that move the wheels of the world: small hands 
do them because they must, while the eyes of the great are elsewhere."  --Elrond

             reply	other threads:[~2006-05-27 21:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-27 21:13 Kumba [this message]
2006-05-28  1:06 ` Commit 78eef01b0fae087c5fadbd85dd4fe2918c3a015f (on_each_cpu(): disable local interrupts) Breaks SGI IP32 Ralf Baechle
2006-05-28  2:42   ` Andrew Morton
2006-05-28  4:20     ` Kumba
2006-05-28  4:31       ` Andrew Morton
2006-05-28  7:42         ` Kumba
2006-05-28 10:50       ` Ralf Baechle
2006-06-21  9:51         ` Domen Puncer
2006-06-21 12:11           ` Ralf Baechle
2006-06-22  6:49             ` Domen Puncer
2006-06-27  8:19               ` Domen Puncer

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=4478C0F1.8000006@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=akpm@osdl.org \
    --cc=linux-mips@linux-mips.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