Re: This may crash or hang your system

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear Tapan,

Your stty output seems to NOT come from the 536EP/537EP driver !!!!
There is still a driver conflict between serial8250 and the 537EP.

My intuition goes to those lines. Your Silicon 537 [Winmodem] ought to be recognized as
ttyS1 (16450 chip), ttyS2 (8250 chip) and ttyS3 (16450 chip). And this comes early after kernel boot.

Jun 16 16:53:18 localhost kernel: 0000:04:00.0: ttyS1 at I/O 0x1008 (irq = 21) is a 16450
Jun 16 16:53:18 localhost kernel: 0000:04:00.0: ttyS2 at I/O 0x1010 (irq
= 21) is a 8250
Jun 16 16:53:18 localhost kernel: 0000:04:00.0: ttyS3 at I/O 0x1018 (irq
= 21) is a 16450

I have NO idea of getting rid from this except filling in a bug report
at Red Hat's bugzilla.

Warmest regards to you.
-  
http://vouters.dyndns.org:8080/
Philippe Vouters (Fontainebleau/France)


Le jeudi 18 juin 2009 à 22:13 +0530, Tapan Chugh a écrit :
> Philippe Vouters wrote:
> > Dear Tapan,
> >
> > Could you try the following ? This may crash or hang your system. If it
> > does not, send me the dmesg output
> >
> > [root@victor intel-536-537]# stty -a -F /dev/modem 
> > speed 115200 baud; rows 0; columns 0; line = 0;
> > intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
> > eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt
> > = ^R;
> > werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
> > -parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
> > -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon
> > -ixoff
> > -iuclc -ixany -imaxbel -iutf8
> > opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0
> > vt0 ff0
> > isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop
> > -echoprt
> > echoctl echoke
> >
> > -  
> > http://vouters.dyndns.org:8080/
> > Philippe Vouters (Fontainebleau/France)
> >
> >
> >
> >   
> Dear Philippe,
> 
> When i executed
> 
>  stty -a -F /dev/modem 
> 
> it did not hang. However it did not give output matching yours.
> Here is the output -
> 
> stty: /dev/modem: Bad address
> 
> This happened for the first time. The second time i executed the same command it gave a segmentation fault. And whem i executed the command, I got correct output. Here is the output
> 
> speed 19200 baud; rows 0; columns 0; line = 0;
> intr = <undef>; quit = <undef>; erase = <undef>; kill = <undef>; eof = <undef>;
> eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S;
> susp = <undef>; rprnt = <undef>; werase = <undef>; lnext = <undef>;
> flush = <undef>; min = 1; time = 0;
> -parenb -parodd cs8 -hupcl -cstopb cread clocal -crtscts
> ignbrk -brkint ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon -ixoff
> -iuclc -ixany -imaxbel -iutf8
> -opost -olcuc -ocrnl -onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
> -isig -icanon -iexten -echo -echoe -echok -echonl -noflsh -xcase -tostop -echoprt
> -echoctl -echoke
> 
> Then when i executed efax, it also started working correctly.
> Thanks for helping me out. However i would like to understand what happened when it started working without any editing 
>  
> 
> 



[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux