Re: moxa serial driver testing

2006-12-29 Thread Sergei Organov
Jiri Slaby <[EMAIL PROTECTED]> writes: [...] >> # rmmod mxser_new >> Trying to free already-free IRQ 58 >> Trying to free nonexistent resource <9000-903f> >> Trying to free nonexistent resource <8800-8800> > > Thanks, I'll fix this and let you know.

Re: moxa serial driver testing

2006-12-28 Thread Jiri Slaby
Sergei Organov wrote: > Hi, Jiri! Hi. > I'm so sorry, I don't know what I smoked yesterday, but the latest > version you've sent me does not have this problem anymore! I think I YES! > copied compiled module to modules directory for different kernel and > thus tested old code all the time. BTW,

Re: moxa serial driver testing

2006-12-28 Thread Sergei Organov
Jiri Slaby <[EMAIL PROTECTED]> writes: >> Jiri Slaby <[EMAIL PROTECTED]> writes: >> >> > Could you test the patch below, if something changes? >> >> Just tested with low_latency commented out. Still oopses: >> >> BUG: unable to handle kernel NULL pointer dereference at virtual address >> 0

Re: moxa serial driver testing

2006-12-27 Thread Sergei Organov
Jiri Slaby <[EMAIL PROTECTED]> writes: >> Jiri Slaby <[EMAIL PROTECTED]> writes: >> >> > Could you test the patch below, if something changes? >> >> Just tested with low_latency commented out. Still oopses: >> >> BUG: unable to handle kernel NULL pointer dereference at virtual address >> 0

Re: moxa serial driver testing

2006-12-27 Thread Sergei Organov
Jiri Slaby <[EMAIL PROTECTED]> writes: >> Jiri Slaby <[EMAIL PROTECTED]> writes: >> >> > Could you test the patch below, if something changes? >> >> Just tested with low_latency commented out. Still oopses: >> >> BUG: unable to handle kernel NULL pointer dereference at virtual address >> 0

Re: moxa serial driver testing

2006-12-27 Thread Jiri Slaby
> Jiri Slaby <[EMAIL PROTECTED]> writes: > > > Could you test the patch below, if something changes? > > Just tested with low_latency commented out. Still oopses: > > BUG: unable to handle kernel NULL pointer dereference at virtual address > 0008 > printing eip: > f8f1730f > *pde = 000

Re: moxa serial driver testing

2006-12-27 Thread Sergei Organov
Jiri Slaby <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: >> Hi Jiri, >> >> I've figured out that both old and new mxser drivers have two similar >> problems: >> >> 1. When there are data coming to a port, sometimes opening of the port >>entirely locks the box. This is quite reproduc

Re: moxa serial driver testing

2006-12-27 Thread Sergei Organov
Jiri Slaby <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: >> Hi Jiri, >> >> I've figured out that both old and new mxser drivers have two similar >> problems: >> >> 1. When there are data coming to a port, sometimes opening of the port >>entirely locks the box. This is quite reproduci

Re: moxa serial driver testing

2006-12-25 Thread Sergei Organov
Jiri Slaby <[EMAIL PROTECTED]> writes: > Sergei Organov wrote: >> Jiri Slaby <[EMAIL PROTECTED]> writes: >> >>> [EMAIL PROTECTED] wrote: Hi Jiri, I've figured out that both old and new mxser drivers have two similar problems: 1. When there are data coming to a port,

Re: moxa serial driver testing

2006-12-25 Thread Jiri Slaby
Sergei Organov wrote: > Jiri Slaby <[EMAIL PROTECTED]> writes: > >> [EMAIL PROTECTED] wrote: >>> Hi Jiri, >>> >>> I've figured out that both old and new mxser drivers have two similar >>> problems: >>> >>> 1. When there are data coming to a port, sometimes opening of the port >>>entirely locks

Re: moxa serial driver testing (oopses)

2006-12-25 Thread Sergei Organov
Jiri Slaby <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: >> Hi Jiri, >> >> I've figured out that both old and new mxser drivers have two similar >> problems: >> >> 1. When there are data coming to a port, sometimes opening of the port >>entirely locks the box. This is quite reproduci

Re: moxa serial driver testing

2006-12-25 Thread Sergei Organov
Jiri Slaby <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: >> Hi Jiri, >> >> I've figured out that both old and new mxser drivers have two similar >> problems: >> >> 1. When there are data coming to a port, sometimes opening of the port >>entirely locks the box. This is quite reproduc

Re: moxa serial driver testing

2006-12-25 Thread Sergei Organov
Jiri Slaby <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: >> Hi Jiri, >> >> I've figured out that both old and new mxser drivers have two similar >> problems: >> >> 1. When there are data coming to a port, sometimes opening of the port >>entirely locks the box. This is quite reproduc

Re: moxa serial driver testing

2006-12-23 Thread Sergei Organov
Jiri, Jiri Slaby <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: >> Hi Jiri, >> >> I've figured out that both old and new mxser drivers have two similar >> problems: >> >> 1. When there are data coming to a port, sometimes opening of the port >>entirely locks the box. This is quite re

Re: moxa serial driver testing

2006-12-22 Thread Jiri Slaby
[EMAIL PROTECTED] wrote: > Hi Jiri, > > I've figured out that both old and new mxser drivers have two similar > problems: > > 1. When there are data coming to a port, sometimes opening of the port >entirely locks the box. This is quite reproducible. Any idea what's >wrong and how can I he

Re: moxa serial driver testing

2006-12-22 Thread Jiri Slaby
Jiri Slaby wrote: > [EMAIL PROTECTED] wrote: >> Hi Jiri, >> >> I've figured out that both old and new mxser drivers have two similar >> problems: >> >> 1. When there are data coming to a port, sometimes opening of the port >>entirely locks the box. This is quite reproducible. Any idea what's >>

Re: moxa serial driver testing

2006-12-22 Thread Jiri Slaby
[EMAIL PROTECTED] wrote: > Hi Jiri, > > I've figured out that both old and new mxser drivers have two similar > problems: > > 1. When there are data coming to a port, sometimes opening of the port >entirely locks the box. This is quite reproducible. Any idea what's >wrong and how can I he