From: Jan Kiszka <jan.kiszka@siemens.com>
To: gopi ratnakaram <gopi.ratnakaram@svayarobotics.com>, xenomai@xenomai.org
Subject: Re: Regarding SMBus
Date: Wed, 9 Sep 2020 10:02:10 +0200 [thread overview]
Message-ID: <5a43908e-817b-bcbc-867d-7284fa07e9fc@siemens.com> (raw)
In-Reply-To: <CAF_6MazWZnuJ3v4XjLLfAWMxrgSKsE2qt_60LLp0ifkC=fqoAQ@mail.gmail.com>
On 09.09.20 07:23, gopi ratnakaram via Xenomai wrote:
> Team,
>
> I am working with xenomai patched with kernel 4.19.59 on an Industrial
> motherboard which has an SMBus. After patching during my testing it was
> observed that the SMbus got some issues and the bus is locking immediately
> after running my application and the error log is as follows. But, when I
> run my SMbus based application in the kernel 4.15.0 without RT patching it
> was working fine. Is there any configuration setting while patching xenomai
> is causing this issue?
>
> --best regards,
> R Gopi Krishna,
> Svaya Robotics Pvt., Ltd.,
> Hyderabad, India.
> T: +91 40 2354 6019
> F: +91 40 2354 7901
>
>
> *DISCLAIMER :This e-mail and any files transmitted with it may contain
> privileged, undisclosed, or otherwise confidential information of Svaya
> Robotics Pvt. Ltd., and are intended solely for the use of the individual
> or entity to whom they are addressed, shall be maintained in confidence and
> not disclosed to third parties without the written consent of the sender.
> If you have received this E-mail in error, you are hereby notified that any
> review, copying, printing or distribution of it is strictly prohibited.
> Please immediately notify the sender by return e-mail and destroy the
> original transmittal. Thank you for your cooperation.*
> -------------- next part --------------
> [ 1.291726] i801_smbus 0000:00:1f.4: SPD Write Disable is set
> [ 1.291801] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
> [ 366.625686] i801_smbus 0000:00:1f.4: Timeout waiting for interrupt!
The Linux interrupt is not making it through. Is it shared with another
device that happens to be managed by an RTDM driver? Does the issue
disappear when keeping the kernel version, just turning of Xenomai and
I-pipe in the kernel configuration?
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-09-09 8:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 5:23 Regarding SMBus gopi ratnakaram
2020-09-09 5:27 ` Greg Gallagher
2020-09-09 5:35 ` gopi ratnakaram
2020-09-09 8:02 ` Jan Kiszka [this message]
2020-09-09 10:20 ` gopi ratnakaram
2020-09-10 5:49 ` Meng, Fino
2020-09-10 8:41 ` gopi ratnakaram
2020-09-11 5:22 ` Meng, Fino
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=5a43908e-817b-bcbc-867d-7284fa07e9fc@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gopi.ratnakaram@svayarobotics.com \
--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.