Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / Atom feed
From: Robin Gong <yibin.gong@nxp.com>
To: "Petr Štetiar" <ynezz@true.cz>, "Vinod Koul" <vkoul@kernel.org>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	Fabio Estevam <festevam@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Lucas Stach <l.stach@pengutronix.de>
Subject: RE: imx-uart DMA transaction error leading to OOPS on 4.14.95
Date: Tue, 12 Feb 2019 06:39:30 +0000
Message-ID: <VI1PR04MB4543B9D3A40D6BCD3E83959B89650@VI1PR04MB4543.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <VI1PR04MB454392326A1394AA678090F289650@VI1PR04MB4543.eurprd04.prod.outlook.com>

Sorry, please ignore my information, sdma didn't use virt-dma on 4.14....

> -----Original Message-----
> From: Robin Gong
> Sent: 2019年2月12日 11:42
> To: 'Petr Štetiar' <ynezz@true.cz>; Vinod Koul <vkoul@kernel.org>
> Cc: Fabio Estevam <festevam@gmail.com>; Lucas Stach
> <l.stach@pengutronix.de>; dmaengine@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org
> Subject: RE: imx-uart DMA transaction error leading to OOPS on 4.14.95
> 
> Hi Petr,
> 	Could you check the below patch set which is not in v4.14.98?
> https://patchwork.kernel.org/patch/10057791/
> 
> > -----Original Message-----
> > From: Petr Štetiar <ynezz@true.cz>
> > Sent: 2019年2月11日 17:28
> > To: Vinod Koul <vkoul@kernel.org>
> > Cc: Fabio Estevam <festevam@gmail.com>; Lucas Stach
> > <l.stach@pengutronix.de>; Robin Gong <yibin.gong@nxp.com>;
> > dmaengine@vger.kernel.org; linux-arm-kernel@lists.infradead.org
> > Subject: Re: imx-uart DMA transaction error leading to OOPS on 4.14.95
> >
> > Vinod Koul <vkoul@kernel.org> [2019-02-11 17:36:16]:
> >
> > Hi,
> >
> > > > I've just encountered following OOPS on 4.14.95:
> > > >
> > > >   imx-uart 21f0000.serial: DMA transaction error.
> > >
> > > Do you see this on mainline as well, bit of fixes went into this
> > > driver recently...
> >
> > I've hit it only once on 4.14 so far, it's quite hard to reproduce it,
> > so no big deal, but I've just thought, that someone might be
> > interested. Once I find some way to reproduce it, I'll try to test it on some
> recent kernel.
> >
> > BTW, any idea which of those fixes might be related to this Oops and
> > might be worth backporting to 4.14?
> >
> > > >   Unable to handle kernel paging request at virtual address a0ee501a
> > > >   pgd = 9d7d4000
> > > >   [a0ee501a] *pgd=2d8d1811, *pte=00000000, *ppte=00000000
> > > >   Internal error: Oops: 7 [#1] SMP ARM
> > ...
> > > >   CPU: 0 PID: 2536 Comm: sh Not tainted 4.14.95 #0
> > > >   Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
> > > >   task: 9f67ca00 task.stack: 9b642000
> > > >   PC is at sdma_int_handler+0x7c/0x17c
> > >
> > > So we get an interrupt while doing shutdown.. That is interesting..
> >
> > I'm using serial console on ttymxc0 (115200,8n1) and UHF RFID reader
> > on
> > ttymxc3(921600,8n1) which is sending reports asynchronously and it was
> > active during the shutdown as I was testing new hardware revision during
> that time.
> >
> > > >   PC is at sdma_int_handler+0x7c/0x17c
> > > >   LR is at console_unlock+0x480/0x4ec
> >
> > I'm not sure how to interpret this, but is it possible, that there
> > might be some race while sdma_int_handler could be processing
> > interrupt on ttymxc3 while the system is doing some console output on
> > ttymxc0? I just use the console for observation, so I wasn't typing or
> > otherwise utilizing it, so probably no reason for interrupt from ttymxc0.
> >
> > -- ynezz
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06  8:13 Petr Štetiar
2019-02-11 12:06 ` Vinod Koul
2019-02-11  9:28   ` Petr Štetiar
2019-02-12  3:42     ` Robin Gong
2019-02-12  6:39       ` Robin Gong [this message]

Reply instructions:

You may reply publically 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=VI1PR04MB4543B9D3A40D6BCD3E83959B89650@VI1PR04MB4543.eurprd04.prod.outlook.com \
    --to=yibin.gong@nxp.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=vkoul@kernel.org \
    --cc=ynezz@true.cz \
    /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

Linux-ARM-Kernel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-arm-kernel/0 linux-arm-kernel/git/0.git
	git clone --mirror https://lore.kernel.org/linux-arm-kernel/1 linux-arm-kernel/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-arm-kernel linux-arm-kernel/ https://lore.kernel.org/linux-arm-kernel \
		linux-arm-kernel@lists.infradead.org infradead-linux-arm-kernel@archiver.kernel.org
	public-inbox-index linux-arm-kernel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.infradead.lists.linux-arm-kernel


AGPL code for this site: git clone https://public-inbox.org/ public-inbox