From: Clark Williams <williams@redhat.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: boot hang in 2.6.16-rt[7-10]
Date: Tue, 28 Mar 2006 15:38:06 -0600 [thread overview]
Message-ID: <4429ACBE.2060502@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm seeing a boot hang in the latest -rt series (from -rt7 to current
- -rt10), on an Athlon64x2 (3800+). The kernel loads and boots up to
calibrate_migration_costs then hangs. I'd give some console output,
except that in their infinite wisdom, Gateway decided that this system
didn't need a serial port. Gah...
I've prink'ed my way down into where measure_one tries to migrate a
thread from cpu0 to cpu1 and calls set_cpus_allowed, where it then
tries to wake the migration thread by calling wake_up_process, which
just calls try_to_wake_up. Strangely, I see multiple printks from
try_to_wake_up (like it's running multiple times) and the last print I
see is that I'm returning a 1 from wake_up_process. Nothing after that.
I'd really like to see the boot messages before all those printk's
I've scattered in sched.c, so I'm investigating using the parallel
port as a console and just spewing that output into an xterm on the
other end. Never done it before so I'm bumping my head against the
wall a bit. Any advice would be appreciated.
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEKay+Hyuj/+TTEp0RAi8YAJ92U1KHM0BW5nWZWl7lCBBQAZWCQQCg1FWy
8dGHlzkPQBn22Y1pK6lOen8=
=Hr9n
-----END PGP SIGNATURE-----
reply other threads:[~2006-03-28 21:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4429ACBE.2060502@redhat.com \
--to=williams@redhat.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.