From: Julien Aube <julien.aube@smile.fr>
To: xenomai@lists.linux.dev
Subject: Question about a freeze under Xenomai 3.2.1
Date: Wed, 3 May 2023 15:43:23 +0200 [thread overview]
Message-ID: <5a8afa1e-d6d7-df9f-2895-6832ffa9673f@smile.fr> (raw)
Hello,
I'm currently porting an old code from Xenomai 2 to Xenomai 3/Dovetail.
I'm using kernel 5.10.177-dovetail1 as this is the latest version I
could work with xenomai 3.2.1.
The driver I'm porting makes heavy use of RTDM.
The platform is a Zynq 7030 (dual cortex-9).
I uses buildroot 2022.11 to build.
I hit a strange issue and ask for an advice before having to setup JTAG
/ opencd , as you may have seen
the same issue before.
On the aforementioned platform , everything goes well as long as I do
not enable SMP.
If I do, what happens is that Ethernet's phy detection hangup forever :
> Registering platform device 'Fixed MDIO bus.0'. Parent at platform
> device: 'Fixed MDIO bus.0': device_add
> bus: 'platform': add device Fixed MDIO bus.0
> device: 'fixed-0': device_add
> bus: 'mdio_bus': add driver Micrel KS8737
> [...]
> bus: 'mdio_bus': add driver Microchip KSZ9477
> bus: 'platform': add driver macb
> bus: 'platform': driver_probe_device: matched device e000c000.ethernet
> with driver macb
> bus: 'platform': really_probe: probing driver macb with device
> e000c000.ethernet
> macb e000c000.ethernet: no pinctrl handle
> device: 'e000c000.ethernet-ffffffff': device_add
If I disable SMP in the linux config kernel , here is what I have :
> Registering platform device 'Fixed MDIO bus.0'. Parent at platform
> device: 'Fixed MDIO bus.0': device_add
> bus: 'platform': add device Fixed MDIO bus.0
> device: 'fixed-0': device_add
> bus: 'mdio_bus': add driver Micrel KS8737
> [...]
> bus: 'mdio_bus': add driver Microchip KSZ9477
> bus: 'platform': add driver macb
> bus: 'platform': driver_probe_device: matched device e000c000.ethernet
> with driver macb
> bus: 'platform': really_probe: probing driver macb with device
> e000c000.ethernet
> macb e000c000.ethernet: no pinctrl handle
> device: 'e000c000.ethernet-ffffffff': device_add
> device: 'e000c000.ethernet-ffffffff:01': device_add
> bus: 'mdio_bus': add device e000c000.ethernet-ffffffff:01
> bus: 'mdio_bus': driver_probe_device: matched device
> e000c000.ethernet-ffffffff:01 with driver Micrel KSZ9031 Gigabit PHY
> bus: 'mdio_bus': really_probe: probing driver Micrel KSZ9031 Gigabit
> PHY with device e000c000.ethernet-ffffffff:01
> Micrel KSZ9031 Gigabit PHY e000c000.ethernet-ffffffff:01: no pinctrl
> handle
> driver: 'Micrel KSZ9031 Gigabit PHY': driver_bound: bound to device
> 'e000c000.ethernet-ffffffff:01'
> bus: 'mdio_bus': really_probe: bound device
> e000c000.ethernet-ffffffff:01 to driver Micrel KSZ9031 Gigabit PHY
> device: 'eth0': device_add
> macb e000c000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000c000
> irq 24 (xx:xx:xx:xx:xx:xx)
Kernel command line is rather simple :
> console=ttyPS0,115200 earlyprintk root=/dev/nfs rw
nfsroot=192.168.101.56:/home/rootfs/rootfs_2022,vers=4,tcp ip=dhcp
=> Is this something you already faced ?
If not , do you have any insight on debugging method besides JTAG ?
Thanks
Julien Aube
next reply other threads:[~2023-05-03 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 13:43 Julien Aube [this message]
2023-05-03 14:57 ` Question about a freeze under Xenomai 3.2.1 Jan Kiszka
2023-05-04 13:33 ` Julien Aube
2023-05-04 14:17 ` Jan Kiszka
2023-05-04 14:27 ` Julien Aube
2023-05-04 15:00 ` Greg Gallagher
2023-05-04 15:50 ` Julien Aube
2023-05-05 7:36 ` Schuman Eelco (DC-AE/ESW5)
2023-05-05 13:21 ` Jan Kiszka
2023-05-05 13:31 ` Julien Aube
2023-05-08 17:49 ` Julien Aube
2023-05-10 8:19 ` Schuman Eelco (DC-AE/ESW5)
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=5a8afa1e-d6d7-df9f-2895-6832ffa9673f@smile.fr \
--to=julien.aube@smile.fr \
--cc=xenomai@lists.linux.dev \
/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).