[Asterisk-bugs] [Zaptel 0010182]: Bug in zaptel driver with wctdm24xxp in linux with serial console at 9600 bauds

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10182 
====================================================================== 
Reported By:                nito
Assigned To:                mattf
====================================================================== 
Project:                    Zaptel
Issue ID:                   10182
Category:                   wctdm24xxp
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.4 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             07-11-2007 11:44 CDT
Last Modified:              07-19-2007 09:11 CDT
====================================================================== 
Summary:                    Bug in zaptel driver with wctdm24xxp in linux with
serial console at 9600 bauds
Description: 
When you specify the console as a serial port at 9600 bauds the wctdm24xxp
driver does not load the FXS or the FXO modules.

The exact way to reproduce this is to connect via serial console to linux
and boot the kernel with the following kernel argument (console=ttyS0)

An example grub entry would be:

title           Debian GNU/Linux, kernel 2.6.18
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.18 root=/dev/sda1 ro console=ttyS0
initrd          /boot/initrd.img-2.6.18
savedefault

Tested also with versions 1.2.21 and 1.4.3.
====================================================================== 

---------------------------------------------------------------------- 
 tzafrir - 07-19-07 09:11  
---------------------------------------------------------------------- 
So maybe this is a timing-related issue: it has to start fast enough, or
else something bad happens. And printing messages to the slow console makes
this bad thing happen before the modules initialize.

Can you try adding some sleeps at various places?

Can you try a newer version of zaptel?

Any comments from someone who is actually familiar with the specific
driver? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-19-07 09:11  tzafrir        Note Added: 0067583                          
======================================================================