From: Adrian McMenamin <adrian@mcmen.demon.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Continued problems with pthreads
Date: Mon, 23 Jan 2006 22:49:38 +0000 [thread overview]
Message-ID: <1138056578.9140.4.camel@localhost.localdomain> (raw)
I decided to rebuild my buildroot installation from scratch but the
problem was replicated. I couldn't get a bash (ie sh -> bash) based nfs
root to get anywhere near a user shell, and got this with a busybox (ie
sh -> busysbox):
[4294671.462000] Freeing unused kernel memory: 72k freed
\uffff\uffff\uffffRunning init.d
running /etc/init.d/S10udev
BusyBox v1.1.1-pre0 (2006.01.23-00:38+0000) multi-call binary
Usage: uname [OPTION]...
Print certain system information. With no OPTION, same as -s.
Options:
-a print all information
-m the machine (hardware) type
-n print the machine's network node hostname
-r print the operating system release
-s print the operating system name
-p print the host processor type
-v print the operating system version
running /etc/init.d/S20urandom
Initializing random number generator... done.
running /etc/init.d/S30hotplug
** can't synthesize pci hotplug events
whereupon it freezes. Has anyone been able to get a pthread based
install to work on SH?
Adrian
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2006-01-23 22:49 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=1138056578.9140.4.camel@localhost.localdomain \
--to=adrian@mcmen.demon.co.uk \
--cc=linux-hotplug@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).