Re: Static build of rtnet
On 17.09.19 10:29, Lange Norbert wrote: -Original Message- From: Jan Kiszka Sent: Dienstag, 17. September 2019 09:42 To: Lange Norbert ; Xenomai (xenomai@xenomai.org) Subject: Re: Static build of rtnet NON-ANDRITZ SOURCE: BE CAUTIOUS WITH CONTENT, LINKS OR ATTACHMENTS. On 16.09.19 11:13, Lange Norbert via Xenomai wrote: Hello, I havent tested this in a while, but building rtnet static will crash the kernel when this module initializes. With the various fixes and cleanups in master/next (like rtdm_available) that might be worth a look? I would hope to build a static kernel one day, and so far there are 2 roadblocks: - rtnet (+ rtpacket) crashing when built statically - symbol nameclashes with linux + rt drivers enabled (I could work on fixing that for rt_igb atleast) Do you mean removing the "depends on m"? Yes, ideally I would use a kernel without loadable modules, so kernel upgrades/changes don’t affect the rootfs (ideally read-only apart from few places). Possibly, that moves the initialization order in a way that causes troubles. I also just added another case that exploits the module [1], but that would be solvable. More critical is understanding the crashes. I had a quick test removing the "depends on m" about a year ago, I brought this up now because it might be fitting with the recent cleanups. I don't think recent cleanups have changed the situation. Someone has to sit down, analyze the crashes, resolve them, and propose all changes for upstream. Also, startup scripts need to be adjusted to accept non-module RTnet. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
RE: Static build of rtnet
> -Original Message- > From: Jan Kiszka > Sent: Dienstag, 17. September 2019 09:42 > To: Lange Norbert ; Xenomai > (xenomai@xenomai.org) > Subject: Re: Static build of rtnet > > NON-ANDRITZ SOURCE: BE CAUTIOUS WITH CONTENT, LINKS OR > ATTACHMENTS. > > > On 16.09.19 11:13, Lange Norbert via Xenomai wrote: > > Hello, > > > > I havent tested this in a while, but building rtnet static will crash the > > kernel > when this module initializes. > > With the various fixes and cleanups in master/next (like rtdm_available) > > that > might be worth a look? > > > > I would hope to build a static kernel one day, and so far there are 2 > roadblocks: > > > > - rtnet (+ rtpacket) crashing when built statically > > > > - symbol nameclashes with linux + rt drivers enabled (I could work on > > fixing > that for rt_igb atleast) > > > > Do you mean removing the "depends on m"? Yes, ideally I would use a kernel without loadable modules, so kernel upgrades/changes don’t affect the rootfs (ideally read-only apart from few places). > Possibly, that moves the > initialization order in a way that causes troubles. I also just added another > case > that exploits the module [1], but that would be solvable. More critical is > understanding the crashes. I had a quick test removing the "depends on m" about a year ago, I brought this up now because it might be fitting with the recent cleanups. Regards, Norbert This message and any attachments are solely for the use of the intended recipients. They may contain privileged and/or confidential information or other information protected from disclosure. If you are not an intended recipient, you are hereby notified that you received this email in error and that any review, dissemination, distribution or copying of this email and any attachment is strictly prohibited. If you have received this email in error, please contact the sender and delete the message and any attachment from your system. ANDRITZ HYDRO GmbH Rechtsform/ Legal form: Gesellschaft mit beschränkter Haftung / Corporation Firmensitz/ Registered seat: Wien Firmenbuchgericht/ Court of registry: Handelsgericht Wien Firmenbuchnummer/ Company registration: FN 61833 g DVR: 0605077 UID-Nr.: ATU14756806 Thank You
Re: Static build of rtnet
On 16.09.19 11:13, Lange Norbert via Xenomai wrote: Hello, I havent tested this in a while, but building rtnet static will crash the kernel when this module initializes. With the various fixes and cleanups in master/next (like rtdm_available) that might be worth a look? I would hope to build a static kernel one day, and so far there are 2 roadblocks: - rtnet (+ rtpacket) crashing when built statically - symbol nameclashes with linux + rt drivers enabled (I could work on fixing that for rt_igb atleast) Do you mean removing the "depends on m"? Possibly, that moves the initialization order in a way that causes troubles. I also just added another case that exploits the module [1], but that would be solvable. More critical is understanding the crashes. Jan [1] https://xenomai.org/pipermail/xenomai/2019-September/041583.html -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
