From: Andreas Galauner <andreas@galauner.de>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Xenomai on Linux 3.18 on Zynq
Date: Fri, 10 Apr 2015 18:06:47 +0200 [thread overview]
Message-ID: <5527F517.1090809@galauner.de> (raw)
In-Reply-To: <20150410152959.GQ20752@hermes.click-hack.org>
On 10.04.2015 17:29, Gilles Chanteperdrix wrote:
> Maybe you already tried since you tried "all kinds of things", but
> better be sure, have you tried enabling Xenomai and I-pipe debugging
> options?
Sorry for that sloppy phrase, it's a side project and I lost track what
exactly I did over the last weekends.
I just enabled the I-pipe debugging features. I didn't know that they
are under "Kernel hacking". The Xenomai debugging features were enabled
all the time.
Sadly, I don't get any messages that may relate to my system behaviour.
Actually no messages at all except the initialization messages of i-pipe
and Xenomai.
What I forgot to mention is, that it's not a complete freeze. It seems
to me, that the system just gets horribly slow. The heartbeat LED stops
blinking and I get occasional terminal output (1-2 lines) until it stops
completely.
There seem to be three points where the kernel may hang:
1) Somewhere in the driver init phase
2) While mounting the rootfs
3) At the login prompt or idle shell
And as I said, sometimes I get a few more lines from the kernel after a
while.
One example:
> [ 1.648675] mmcblk0: mmc0:b368 USD 7.46 GiB
> [ 1.654727] mmcblk0: p1 p2
> [ 1.660107] EXT3-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)
> [ 1.670176] EXT2-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (244)
> [ 64.605360] EXT4-fs (mmcblk0p2): recovery complete
> [ 64.612160] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
> [ 64.620218] VFS: Mounted root (ext4 filesystem) on device 179:2.
> [ 64.635207] devtmpfs: mounted
> [ 64.638469] Freeing unused kernel memory: 276K (c05f7000 - c063c000)
> INIT: version 2.88 booting
>
- Andy
next prev parent reply other threads:[~2015-04-10 16:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 14:35 [Xenomai] Xenomai on Linux 3.18 on Zynq Andreas Galauner
2015-04-10 15:09 ` Stefan Roese
2015-04-10 15:15 ` Andreas Galauner
2015-04-10 15:26 ` Stefan Roese
2015-04-10 15:24 ` Gilles Chanteperdrix
2015-04-10 15:29 ` Gilles Chanteperdrix
2015-04-10 16:06 ` Andreas Galauner [this message]
2015-04-10 16:14 ` Gilles Chanteperdrix
2015-04-10 16:11 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2015-11-05 8:31 Philippe.Corbel
2015-11-05 11:00 ` Stefan Roese
2015-11-05 12:13 ` Philippe.Corbel
2015-11-05 20:46 ` Gilles Chanteperdrix
2015-11-06 10:49 ` Philippe.Corbel
2015-11-06 10:57 ` Gilles Chanteperdrix
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=5527F517.1090809@galauner.de \
--to=andreas@galauner.de \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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.