[Bug 738952] New: ttyS5 is blocked
https://bugzilla.novell.com/show_bug.cgi?id=738952 https://bugzilla.novell.com/show_bug.cgi?id=738952#c0 Summary: ttyS5 is blocked Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: chusty@attglobal.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101 Firefox/9.0 ref: pciE serial card mythtv 0.24 dct-channel v 1.7 HDPVR Motorola cable box Problem: the channel change script to use the serial port connected to the STB does not work. /dev/tty5 is present, permissions are OK, when call it to change channels hangs before DCT. Basically dct-channel use a serial connection between the computer and the Motorola cable box to change channels. $ channel -p /dev/ttyS5 -vv 12 cursor moves to the next line and it blocks ttyS5, no errors and stays there for ever. The expected behavior is to change the channel and return the new channel number (-p is to select the ttyS5 otherwise the default would be ttyS0, -vv verbose and 12 is the channel to be changed to) If I $ channel Communication failed after 5 tries 0 more verbose $ channel -vv Attempting to initialize DCT SENT: type 0x70, len 2, id 0x04, seq 0x03 Serial timeout No response to packet No response to init_1; trying to continue ---snip-- Which show channel script is working but /dev/ttyS0 (default) is not connected which is correct. Description. I have a machine with dual boot, having opensuse 11.4 and opensuse 12.1 in two different HD. Everything works Ok under opensuse 11.4 which ruled out BIOS setup as a problem. I did 2 clean installation in 12.1 with the same results. The pciE serial card is recognized # dmesg | grep Oxford [ 1.726854] 2 ports detected on Oxford PCI Express device - ttyS5 is present in both (<both> means opensuse 11.4 and opensuse 12.1) - setserial gives the same result in both :~> setserial /dev/ttyS5 /dev/ttyS5, UART: 16950/954, Port: 0x0000, IRQ: 18 - the udev info is ALMOST the same in both #udevadm info -a -p $(udevadm info -q path -n /dev/ttyS5) every line in both OS is the same with ONE exception that the following line is present only in 11.4 ATTRS{modalias}=="pci:v00001415d0000C158sv00001415sd0000C158bc07sc00i02" but i do not think makes any difference ? # dmesg | grep serial [ 1.569725] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.720562] serial 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [ 1.752498] serial 0000:07:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 same in both OS versions # dmesg | grep ttyS* [ 0.000000] console [tty0] enabled [ 1.555551] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.700413] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [ 1.708991] ttyS4: detected caps 00000700 should be 00000500 [ 1.708995] 0000:04:00.0: ttyS4 at MMIO 0xfb601000 (irq = 18) is a 16C950/954 [ 1.724857] ttyS5: detected caps 00000700 should be 00000500 [ 1.724861] 0000:04:00.0: ttyS5 at MMIO 0xfb601200 (irq = 18) is a 16C950/954 [ 1.761550] 0000:08:01.0: ttyS6 at I/O 0xc080 (irq = 19) is a 16550A ttyS6 correspond to a pci modem that is working well. In summary the serial ports are recognized and udev produces the device but when channel tries to access ttyS5 it is blocked like nothing is attach to it. During the many trials one time worked but after reboot the problem reoccur. The only time it worked OK, the behavior change after the following error (which may be unrelated) <1. linux-npu4:/dev # Message from syslogd@linux-npu4 at Dec 4 05:53:07 ... kernel:[ 1702.129463] Disabling IRQ #19 ?? but this is the one (modem) [ 1.637228] 0000:08:01.0: ttyS6 at I/O 0xc080 (irq = 19) is a 16550A
I have posted messages in mythtv forum and opensuse without any replies. I reinstall 12.1 clean 3 times all with the same result. Reproducible: Always Steps to Reproduce: 1.Req:serial port+cable setup box Get the scrip from here http://www.mythtv.org/wiki/Dct-channel 2.#channel -p /dev/ttyS3 Actual Results: the cursor seat there forever. No error. Expected Results: Return the channel number. I do understand very well that it will be hard for you to reproduce because the extra equipment needed (cable setup box and serial port). I will be glad to test any suggestions you may have. I do believe there is a problem with the serial port. I wonder if the problem is related to udev? Comparing opensuse 11.4 and 12.1 in the same machine the only difference I found was with one line in udev. The fact that one time run OK under 12.1 after that error message also suggest that something is blocking ttyS5 in my case. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738952 https://bugzilla.novell.com/show_bug.cgi?id=738952#c1 --- Comment #1 from Teruel de Campo MD <chusty@attglobal.net> 2012-01-01 23:01:18 UTC --- To be sure that the problem it was not hardware related in some way. 1. I removed the pciE serial card 2 I install an usb-serial gadget that I connect to the setup comcast box 3. I booted opensue 11.4 and a new device was created USBS0 (iirc) and there was no problem to change channels. It worked well. 4 I booted opensuse 12.1 in the same machine. The device was created USBS0 but it behaves as described above. So the problem I have is not hardware related. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738952 https://bugzilla.novell.com/show_bug.cgi?id=738952#c zj jia <zjjia@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@suse.com AssignedTo|bnc-team-screening@forge.pr |pth@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738952 https://bugzilla.novell.com/show_bug.cgi?id=738952#c3 Greg Kroah-Hartman <gregkh@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |chusty@attglobal.net --- Comment #3 from Greg Kroah-Hartman <gregkh@suse.com> 2012-01-13 01:13:59 UTC --- So, something in the tty layer is blocking your signal from getting through, very odd. Does any serial port work on 12.1? Do you have a "loopback" device you could test a port with? Something to see if the data really is getting out the device? The fact that a usb serial device worked with 11.4 and didn't with 12.1 is very odd, does any userspace program have the port open somehow? You can check that with the output of 'lsof' -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738952 https://bugzilla.novell.com/show_bug.cgi?id=738952#c4 --- Comment #4 from Teruel de Campo MD <chusty@attglobal.net> 2012-01-15 18:05:47 UTC --- Greg Thxs 1. ttyS6 which is connected to the modem works OK. 2. I do not have a loopback device 3. lsof is above my head? what should I look for? should I add any options to the lsof command? Here an interesting finding : If I run one of the modem programs (wvdial) first, then ttyS5 works, so it looks like you impression of <something is blocking the tty layer> is correct. I wonder what /etc/wvdial.conf does to unblock it? The following shows: - the first channel command does not work and hangs for ever so I killed them with Ctrl-C - second I run the wvdialconf it works as it should recognizing and configuring the modem - third I run again channel and now it works OK changing the channel to 42 and echoing the result. -------------------------------- linux-44xr:/home/tdec # channel -p /dev/ttyS5 42 ^C linux-44xr:/home/tdec # wvdialconf /etc/wvdial.conf Editing `/etc/wvdial.conf'. Scanning your serial ports for a modem. ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Modem Port Scan<*1>: S1 S2 S3 ttyS4<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS4<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS4<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. ttyS5<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS5<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS5<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. ttyS6<*1>: ATQ0 V1 E1 -- OK ttyS6<*1>: ATQ0 V1 E1 Z -- OK ttyS6<*1>: ATQ0 V1 E1 S0=0 -- OK ttyS6<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK ttyS6<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK ttyS6<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK ttyS6<*1>: Modem Identifier: ATI -- 5601 ttyS6<*1>: Speed 4800: AT -- OK ttyS6<*1>: Speed 9600: AT -- OK ttyS6<*1>: Speed 19200: AT -- OK ttyS6<*1>: Speed 38400: AT -- OK ttyS6<*1>: Speed 57600: AT -- OK ttyS6<*1>: Speed 115200: AT -- OK ttyS6<*1>: Max speed is 115200; that should be safe. ttyS6<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK Found a modem on /dev/ttyS6. Modem configuration written to /etc/wvdial.conf. ttyS6<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" linux-44xr:/home/tdec # channel -p /dev/ttyS5 42 42 -------------------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738952 https://bugzilla.novell.com/show_bug.cgi?id=738952#c7 Jan Engelhardt <jengelh@medozas.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED CC| |jengelh@medozas.de Component|Basesystem |Kernel Resolution|NORESPONSE | AssignedTo|bnc-team-screening@forge.pr |gregkh@suse.com |ovo.novell.com | --- Comment #7 from Jan Engelhardt <jengelh@medozas.de> 2012-03-10 09:00:44 UTC --- Revert bogus close. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738952 https://bugzilla.novell.com/show_bug.cgi?id=738952#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |jslaby@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738952 https://bugzilla.novell.com/show_bug.cgi?id=738952#c9 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |chusty@attglobal.net --- Comment #9 from Jiri Slaby <jslaby@suse.com> 2012-03-22 09:45:55 UTC --- Do you still experience the behavior? If so, do you have ModemManager installed? If so, uninstall it and try if it helps. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=738952 https://bugzilla.novell.com/show_bug.cgi?id=738952#c10 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|chusty@attglobal.net | Resolution| |NORESPONSE --- Comment #10 from Jiri Slaby <jslaby@suse.com> 2012-04-11 21:20:29 UTC --- Closing due to lack of response. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com