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

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?

Regards,
Frederik


diff --git a/drivers/serial/serial_core.c b/drivers/serial/serial_core.c
index cc1faa3..08772dc 100644
--- a/drivers/serial/serial_core.c
+++ b/drivers/serial/serial_core.c
@@ -171,6 +171,10 @@ static int uart_startup(struct uart_state *state, int init_hw)
 		uart_circ_clear(&info->xmit);
 	}
 
+	printk("type is %d\n", port->type);
+	printk("ops is %p\n", port->ops);
+	printk("ops->startup is %p\n", port->ops->startup);
+
 	retval = port->ops->startup(port);
 	if (retval == 0) {
 		if (init_hw) {

  reply	other threads:[~2007-01-26 21:22 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 [this message]
2007-01-29 15:05       ` Jose Goncalves
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=20070126212203.GB2990@slug \
    --to=deweerdt@free.fr \
    --cc=jose.goncalves@inov.pt \
    --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).