mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Remy Bohmer" <linux@bohmer.net>
To: "Haavard Skinnemoen" <hskinnemoen@atmel.com>
Cc: "Andrew Victor" <linux@maxim.org.za>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	"Russell King" <linux@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org, kernel@avr32linux.org
Subject: Re: [PATCH v2 0/6] atmel_serial: Cleanups, irq handler splitup & DMA
Date: Wed, 19 Dec 2007 17:40:44 +0100	[thread overview]
Message-ID: <3efb10970712190840m39876762yb4d31c36723c3b8a@mail.gmail.com> (raw)
In-Reply-To: <20071219170935.4df62471@dhcp-252-066.norway.atmel.com>

Hello Haavard,

> Could you try the patch below? It's a bit strange that you got an oops
> though...

It is not really strange... spinlocks are mutexes on preempt-rt, and
recursive mutex locking is not allowed, this is one differences with
the mainline spinlock.

But... I tried that patch, and it works a lot better, no oopses
anymore, but I noticed that I sometimes get an input overrun (ttyS0: 1
input overrun(s) ) during stress conditions.
This is something I did not notice before, maybe it was already there,
or has something changed in this area that it is now more sensitive
for this?

Kind Regards,

Remy

2007/12/19, Haavard Skinnemoen <hskinnemoen@atmel.com>:
> On Wed, 19 Dec 2007 16:57:04 +0100
> "Remy Bohmer" <linux@bohmer.net> wrote:
>
> > Hello Haavard,
> >
> > Sorry.. But I get an Oops on Preempt-RT with the latest set of
> > patches. I did not see it earlier today with the other set of patches.
>
> Hmm...from the backtrace, it looks like lock recursion -- port->lock is
> held for the whole duration of the tasklet, but we somehow end up in
> uart_start(), which grabs the lock again.
>
> Could you try the patch below? It's a bit strange that you got an oops
> though...
>
> Haavard
>
> diff --git a/drivers/serial/atmel_serial.c b/drivers/serial/atmel_serial.c
> index 7967054..948c643 100644
> --- a/drivers/serial/atmel_serial.c
> +++ b/drivers/serial/atmel_serial.c
> @@ -666,7 +666,13 @@ static void atmel_rx_from_ring(struct uart_port *port)
>                 uart_insert_char(port, status, ATMEL_US_OVRE, c.ch, flg);
>         }
>
> +       /*
> +        * Drop the lock here since it might end up calling
> +        * uart_start(), which takes the lock.
> +        */
> +       spin_unlock(&port->lock);
>         tty_flip_buffer_push(port->info->tty);
> +       spin_lock(&port->lock);
>  }
>
>  static void atmel_rx_from_dma(struct uart_port *port)
>

  reply	other threads:[~2007-12-19 16:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19 15:12 Haavard Skinnemoen
2007-12-19 15:12 ` [PATCH v2 1/6] atmel_serial: Clean up the code Haavard Skinnemoen
2007-12-19 15:12   ` [PATCH v2 2/6] atmel_serial: Use cpu_relax() when busy-waiting Haavard Skinnemoen
2007-12-19 15:12     ` [PATCH v2 3/6] atmel_serial: Use existing console options only if BRG is running Haavard Skinnemoen
2007-12-19 15:12       ` [PATCH v2 4/6] atmel_serial: Fix bugs in probe() error path and remove() Haavard Skinnemoen
2007-12-19 15:12         ` [PATCH v2 5/6] atmel_serial: Split the interrupt handler Haavard Skinnemoen
2007-12-19 15:12           ` [PATCH v2 6/6] atmel_serial: Add DMA support Haavard Skinnemoen
2007-12-19 15:57 ` [PATCH v2 0/6] atmel_serial: Cleanups, irq handler splitup & DMA Remy Bohmer
2007-12-19 16:09   ` Haavard Skinnemoen
2007-12-19 16:40     ` Remy Bohmer [this message]
2007-12-19 16:47       ` Haavard Skinnemoen
2007-12-19 16:59         ` Remy Bohmer
2007-12-19 17:19           ` Haavard Skinnemoen
2007-12-19 20:32             ` Remy Bohmer
2007-12-22 15:56               ` Haavard Skinnemoen
2007-12-19 22:13 ` Ulf Samuelsson

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=3efb10970712190840m39876762yb4d31c36723c3b8a@mail.gmail.com \
    --to=linux@bohmer.net \
    --cc=hskinnemoen@atmel.com \
    --cc=kernel@avr32linux.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=linux@maxim.org.za \
    /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

all inboxes | Powered by JetHome®