LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jose Goncalves <jose.goncalves@inov.pt>
To: Frederik Deweerdt <deweerdt@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops on serial access on kernel 2.6.16.38
Date: Mon, 29 Jan 2007 15:05:40 +0000	[thread overview]
Message-ID: <45BE0D44.1080309@inov.pt> (raw)
In-Reply-To: <20070126212203.GB2990@slug>

Frederik Deweerdt wrote:
> On Fri, Jan 26, 2007 at 06:17:03PM +0000, Jose Goncalves wrote:
>   
>> Frederik Deweerdt wrote:
>>     
>>> On Fri, Jan 26, 2007 at 03:50:25PM +0000, Jose Goncalves wrote:
>>>   
>>>       
>>>> I'm having a problem with the latest 2.6.16 kernel (I've found the
>>>> problem on 2.6.16.37 and 2.6.16.38). I have a application that retreives
>>>> data from a GPS connected on a serial port. From time to time a get a
>>>> kernel Oops, like this:
>>>>
>>>>     
>>>>         
>>> Could you send your .config?
>>>   
>>>       
>> Here it goes...
>>
>>     
> Thanks. It looks like something is wrong with port->ops->startup() in
> uart_startup(), could you apply the following patch and report the
> results? And btw, you're using a plain 8250 serial port, isn't it?
>   

OK. I've applied the patch and I'm now waiting for the kernel Oops...
sometimes it takes two days until it happens.
I'm using a standard 16550A serial controller found on my hardware, that
is a PC/104 SBC:

 http://www.icop.com.tw/products_detail.asp?ProductID=70

We have a custom hardware that has another serial controller (TL16C554A)
with 4 extra serial ports (also, 16550A type), and the problem happens
in a test program that is retreiving data from ttyS0 (from the SBC) and
ttyS3 (from our custom hardware).
The serial ports initialization, as reported by the kernel:

[   15.216847] Serial: 8250/16550 driver $Revision: 1.90 $ 6 ports, IRQ
sharing disabled
[   15.219517] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[   15.221963] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
[   15.223907] serial8250: ttyS2 at I/O 0x3e8 (irq = 5) is a 16550A
[   15.225757] serial8250: ttyS3 at I/O 0x2e8 (irq = 5) is a 16550A
[   15.227644] serial8250: ttyS4 at I/O 0x1a0 (irq = 6) is a 16550A
[   15.229656] serial8250: ttyS5 at I/O 0x1a8 (irq = 6) is a 16550A

With your patch I'm now getting the following for each iteration of my
test program:

<4>[  298.918962] type is 4
<4>[  298.919011] ops is c0292f00
<4>[  298.919033] ops->startup is c01bd777
<4>[  299.436980] type is 4
<4>[  299.437030] ops is c0292f00
<4>[  299.437051] ops->startup is c01bd777

I don't know if it's relevant or not but the kernel is running in
NFS-Root mode.

Best regards,
José Gonçalves

  reply	other threads:[~2007-01-29 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26 15:50 Jose Goncalves
2006-12-26 20:10 ` Frederik Deweerdt
2007-01-26 18:17   ` Jose Goncalves
2007-01-26 21:22     ` Frederik Deweerdt
2007-01-29 15:05       ` Jose Goncalves [this message]
2007-01-30 12:55         ` Jose Goncalves
2007-02-01  0:06           ` Frederik Deweerdt

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=45BE0D44.1080309@inov.pt \
    --to=jose.goncalves@inov.pt \
    --cc=deweerdt@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Oops on serial access on kernel 2.6.16.38' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).