Messages in this thread | | | Date | Thu, 01 Mar 2007 15:24:34 +0000 | From | Jose Goncalves <> | Subject | Re: Serial related oops |
| |
Russell King wrote: > On Thu, Mar 01, 2007 at 01:33:28PM +0000, Jose Goncalves wrote: > >> I've also done your suggestion and I've inserted "msleep(10);" just >> before the "And clear the interrupt registers again for luck." and my >> application is now running without problems fore more than 24H! So, >> inserting a delay in this point definitely makes some difference (has >> was with adding some extra printk() in several points of >> serial8250_startup()). >> >> This said, for me, this is definitely a software problem. The question >> is were? >> > > I'm personally convinced it's hardware because according to my analysis > your CPU behaving in a way that the code is not asking it to do so. >
It's not possible that a interrupt is hitting just after enabling interrupts with "serial_outp(up, UART_IER, up->ier);" which triggers the execution of some code that is not reported by the Oops dump (at least with my current configuration) ?
José Gonçalves
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |