Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: unsik Kim <donari75@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: udevd receives SIGILL
Date: Mon, 23 Mar 2009 17:20:18 +0900	[thread overview]
Message-ID: <49C74642.80105@gmail.com> (raw)

Hello?

Recently I started to change development platform poky to oe, but I have some troubles.

machine : custom PXA270 board.
kernel : custom 2.6.29-rc8
oe git : 49c1a7699ac24c580449c13bc3dba425f1d2bb48 (almost current)
image : base-image (use as NFS-root)

udevd receives SIGILL signal.

I found current oe and poky use same source code for udev package (differences are scripts and build env.)
Here's some tries I did.
If I use udev package from poky in oe's base-image, boot well.
If I provide /etc/dev.tar and using oe's udev package also boot well.
If I change nothing(same as first boot), udevd receive SIGILL.

followings are gdb debug results:

Program received signal SIGILL, Illegal instruction.
0x00009a98 in sig_handler (signum=17) at udevd.c:818
818		write(signal_pipe[WRITE_END], "", 1);
(gdb) l 818
813				reload_config = 1;
814				break;
815		}
816	
817		/* write to pipe, which will wakeup select() in our mainloop */
818		write(signal_pipe[WRITE_END], "", 1);
819	}
820	
821	static void udev_done(int pid, int exitstatus)
822	{

and, debug output message (I use --debug --debug-trace option)
[555] get_ctrl_msg: udevd message (ENV) received, set 'STARTUP=1'
[555] msg_queue_insert: seq 372 queued, 'add' 'bus'
[565] pass_env_to_socket: passed -1 bytes to socket '@/org/kernel/udev/monitor',
[565] pass_env_to_socket: passed -1 bytes to socket '/org/kernel/udev/monitor',
[565] udev_event_run: seq 372 finished with 0

-- 
Regards,
unsik Kim



                 reply	other threads:[~2009-03-23  8:22 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=49C74642.80105@gmail.com \
    --to=donari75@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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