From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755927AbYEZVOT (ORCPT ); Mon, 26 May 2008 17:14:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753528AbYEZVOK (ORCPT ); Mon, 26 May 2008 17:14:10 -0400 Received: from valhalla.ausics.net ([58.96.38.4]:54468 "EHLO valhalla.ausics.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752762AbYEZVOI (ORCPT ); Mon, 26 May 2008 17:14:08 -0400 X-AIS-Watermark: 1212441244.53555@tSL1ncB0ybqJxVR4kZrMQA Subject: PROBLEM: Serial error From: "Noel (Sourceforge)" To: linux-kernel@vger.kernel.org Content-Type: text/plain Organization: Supporting Open Source Message-Id: <1211836442.5745.1.camel@roswell.ausics.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Tue, 27 May 2008 07:14:02 +1000 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org serial comms error with smsclient >2.6.25 , worked fine up until and including 2.6.24.7 smsclient a command line client for sending sms's, worked fine for all previous versions but as of 2.6.25, I get errors "waiting for ACK" this has been confirmed as a kernel related error, smsmclient worked fine for years, carrier (Telstra) has been very helpful with assisting in debugging, confirms no change, error kernel related verified by rolling back to kernel 2.6.24.7, as of 2.6.25 something in the serial comms area was altered and broke smsclient ability to send SMS's, it will connect but not login to send, with timeout waiting for ID, been working on this for weeks and again its confirmed to some change in the kernel versions mentioned. Only changes made were kernel upgrades. Slackware 12.0, kernel from kernel.org, same .config file copied through all upgrades, GCC version 4.1.2 00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- 00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- IOBus Bridge (rev 01) (prog-if 00 [8250]) Subsystem: Stallion Technologies, Inc. Unknown device f010 Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate= Stallion Multiport Serial Driver: version 5.6.0 Stallion Intelligent Multiport Serial Driver: version 5.6.0 0000:01:0c.0: ttyS4 at I/O 0xd880 (irq = 6) is a ST16654 0000:01:0c.0: ttyS5 at I/O 0xd888 (irq = 6) is a ST16654 0000:01:0c.0: ttyS6 at I/O 0xd890 (irq = 6) is a ST16654 0000:01:0c.0: ttyS7 at I/O 0xd898 (irq = 6) is a ST16654 0000:01:0c.0: ttyS8 at I/O 0xd8a0 (irq = 6) is a ST16654 0000:01:0c.0: ttyS9 at I/O 0xd8a8 (irq = 6) is a ST16654 0000:01:0c.0: ttyS10 at I/O 0xd8b0 (irq = 6) is a ST16654 0000:01:0c.0: ttyS11 at I/O 0xd8b8 (irq = 6) is a ST16654 <-- phone line in this port suggestions or assistance appreciated. Noel