From: Manfred <manfred@domain.hid>
To: xenomai@xenomai.org.
Subject: [Xenomai-help] Omap3630, rtserial, xeno_16550A: crash on insmod
Date: Thu, 12 Jan 2012 18:53:39 +0100 [thread overview]
Message-ID: <4F0F1E23.5060400@domain.hid> (raw)
Dear Xenomai-Developers/Users,
I am trying to get xenomai running on an omap3630 device (gumstix overo).
xenomai 2.6.0/kernel: linux-omap3-2.6.38 / i-pipe patch 2.6.38.8-arm-1.18.04
I would like to use the UART devices in a RT-application,
and I was following the following guidelines:
http://www.xenomai.org/index.php/16550A
I had to do some changes to Kconfig in arch/arm/mach-omap2:Kconfig,
so that the omap_serial driver would not be compiled-in and so that
I could actually disable the driver with setserial
(and correspondingly had to make some changes here and there because the
devices are now called /dev/ttySx and not /dev/ttyOx, as in the
omap_serial driver...)
dmesg then reports:
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
serial8250.3: ttyS3 at MMIO 0x49042000 (irq = 80) is a ST16654
Anyway, finally I was able to the following:
>setserial /dev/ttyS0 uart none
>modprobe xeno_16550A mem=0x4806a000 irq=72 baud_base=3000000
(parameters same as here:
http://www.mail-archive.com/xenomai@xenomai.org
)
And then I immediately get the following Error:
--------------------
Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa06a002
Internal error: : 1028 [#1]
last sysfs file:
/sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/mmc0:aaaa/...
.../block/mmcblk0/size
Modules linked in:
xeno_16550A(+) ipv6 libertas_sdio libertas option ads7846 cfg80211 usb_wwan
lib80211 usbserial firmware_class
CPU: 0 Not tainted (2.6.38 #1)
PC is at init_module+0x170/0x284 [xeno_16550A]
LR is at init_module+0x11c/0x284 [xeno_16550A]
pc : [<bf0f0170>] lr : [<bf0f011c>] psr: 60000013
sp : dda0ff28 ip : 4806a000 fp : bf0ece4c
r10: bf0eced0 r9 : bf0ece6c r8 : bf0ece90
r7 : defeb380 r6 : 00000000 r5 : 00000000 r4 : defeb38c
r3 : 00000000 r2 : fa06a000 r1 : 00000001 r0 : fa06a000
Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 10c5387d Table: 9e558019 DAC: 00000015
Process insmod (pid: 4467, stack limit = 0xdda0e2f0)
Stack: (0xdda0ff28 to 0xdda10000)
<snip>
[<bf0f0170>] (init_module+0x170/0x284 [xeno_16550A]) from
[<c003a494>] (do_one_initcall+0xc8/0x19c)
[<c003a494>] (do_one_initcall+0xc8/0x19c) from
[<c0096f98>] (sys_init_module+0x94/0x1b4)
[<c0096f98>] (sys_init_module+0x94/0x1b4) from
[<c0040400>] (ret_fast_syscall+0x0/0x30)
Code: 1a000002 e5d23002 f57ff05f ea000003 (e5d23002)
---[ end trace 260381790a98f885 ]---
overo Internal error: : 1028 [#1]
overo last sysfs file: /sys/devices/platform/mmci-omap-hs.0/mmc_host/mmc0/
mmc0:aaaa/block/mmcblk0/size
overo Process insmod (pid: 4467, stack limit = 0xdda0e2f0)
Segmentation fault
----------------------
Has anyone seen something similar?
Is this possibly a bug in the xeno16550A driver module,
or perhaps a bug in the omap3 kernel?
How can I debug this? (is there a way to run gdb on insmod?)
Any help with this issue is highly appreciated.
Regards
Manfred
next reply other threads:[~2012-01-12 17:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 17:53 Manfred [this message]
2012-01-12 18:44 ` [Xenomai-help] Omap3630, rtserial, xeno_16550A: crash on insmod Gilles Chanteperdrix
2012-01-12 19:36 ` Manfred
2012-01-12 19:53 ` Gilles Chanteperdrix
2012-01-12 18:52 ` Wolfgang Grandegger
[not found] <4F1080E8.6020408@domain.hid>
2012-01-13 19:15 ` Manfred
2012-01-15 19:35 ` Wolfgang Grandegger
2012-01-18 16:15 ` Fabrice Gasnier
2012-01-18 16:32 ` Wolfgang Grandegger
2012-01-19 17:09 ` Fabrice Gasnier
2012-01-20 12:03 ` Manfred
2012-01-20 14:41 ` Fabrice Gasnier
2012-01-20 15:58 ` Felipe Brandão Cavalcanti
2012-01-22 19:04 ` Manfred
2012-02-23 19:00 ` Felipe Brandão Cavalcanti
2012-01-20 18:03 ` Wolfgang Grandegger
2012-01-20 18:46 ` Gilles Chanteperdrix
2012-01-20 19:04 ` Wolfgang Grandegger
2012-01-26 10:20 ` Fabrice Gasnier
2012-01-19 19:43 ` Manfred
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=4F0F1E23.5060400@domain.hid \
--to=manfred@domain.hid \
--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.