From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Michael Anochin <anochin@photo-meter.com>
Cc: linux-can@vger.kernel.org
Subject: Re: can: m_can: tcan4x5x m_can_isr do not handle tx if rx fails
Date: Tue, 22 Feb 2022 17:09:08 +0100 [thread overview]
Message-ID: <874k4qvq77.fsf@hardanger.blackshift.org> (raw)
In-Reply-To: <b946db8c-ac32-afb0-95aa-8658d1176a89@photo-meter.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On 22.02.2022 17:02:14, Michael Anochin wrote:
> > Still any error messages?
> No BUG-Message with <0x0 0 0 16 0 0 1 1>. At least that is positive.
>
> But no other Messages in in kbuf. Simply no netif_wake_queue fires. After
> that no TX possible. But RX is working.
This is good. \o/
| [ 763.651277] tcan4x5x spi6.0 can2: m_can_isr: netif_wake_queue done
| [ 763.651295] tcan4x5x spi6.0 can2: m_can_start_xmit netif_stop_queue done
| [ 763.651462] tcan4x5x spi6.0 can2: m_can_tx_handler m_can_tx_fifo_full
| [ 763.652163] tcan4x5x spi6.0 can2: m_can_isr: netif_wake_queue done
| [ 763.652182] tcan4x5x spi6.0 can2: m_can_start_xmit netif_stop_queue done
| [ 763.652352] tcan4x5x spi6.0 can2: m_can_tx_handler m_can_tx_fifo_full
You're missing a "netif_wake_queue done" here. There's probably an
interrupt associated with this event. Add a print if that IRQ is active
right after reading the IRQ status register.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-22 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 11:14 can: m_can: tcan4x5x m_can_isr do not handle tx if rx fails Michael Anochin
2022-02-22 13:20 ` Marc Kleine-Budde
[not found] ` <c2651e9c-d3e7-815a-6e18-8ddffc04d3d7@photo-meter.com>
2022-02-22 13:44 ` Marc Kleine-Budde
[not found] ` <e3504807-06fc-b6d9-3fb1-bf8d94e2b444@photo-meter.com>
2022-02-22 14:45 ` Marc Kleine-Budde
2022-02-22 14:54 ` Michael Anochin
2022-02-22 15:06 ` Marc Kleine-Budde
2022-02-22 15:40 ` Michael Anochin
2022-02-22 15:43 ` Marc Kleine-Budde
2022-02-22 15:48 ` Michael Anochin
2022-02-22 15:51 ` Marc Kleine-Budde
2022-02-22 16:02 ` Michael Anochin
2022-02-22 16:09 ` Marc Kleine-Budde [this message]
2022-02-22 16:41 ` Michael Anochin
2022-02-22 20:10 ` Marc Kleine-Budde
2022-02-23 8:55 ` Michael Anochin
2022-02-22 16:58 ` Michael Anochin
2022-02-22 16:20 ` Michael Anochin
2022-02-22 15:11 ` Michael Anochin
2022-02-22 15:32 ` Marc Kleine-Budde
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=874k4qvq77.fsf@hardanger.blackshift.org \
--to=mkl@pengutronix.de \
--cc=anochin@photo-meter.com \
--cc=linux-can@vger.kernel.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.