Ubuntu
linux package

OX16PCI954 ttyS0 non-functional regression

Bug #698099 reported by Andy Buchanan on 2011-01-06

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	High	Unassigned

Bug Description

Binary package hint: linux-image-2.6.35-24-generic

Under linux-image-2.6.35-23-generic, all four serial ports on Serial controller: Oxford Semiconductor Ltd OX16PCI954 (Quad 16950 UART) work correctly.

Under linux-image-2.6.35-24-generic, ttyS1, 2 and 3 all work, but accessing ttyS0 with minicom gives "cannot open /dev/ttyS0: No such device" error message, and the kernel logs "ttyS0: LSR safety check engaged!".

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-24-generic 2.6.35-24.42
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: VT1828S Analog [VT1828S Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: abuchanan 1691 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf5ff8000 irq 52'
   Mixer name : 'VIA VT1828S'
   Components : 'HDA:11064441,104383d0,00100100'
   Controls : 35
   Simple ctrls : 20
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xf79fc000 irq 17'
   Mixer name : 'Nvidia GPU 14 HDMI/DP'
   Components : 'HDA:10de0014,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
Date: Thu Jan 6 12:42:36 2011
HibernationDevice: RESUME=UUID=e3d40ed2-77c5-4665-8711-b8c7efaca315
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IwConfig:
lo no wireless extensions.

eth0 no wireless extensions.

vboxnet0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=0c6446dd-7681-4811-a659-247f778d3c18 ro quiet splash
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:

SourcePackage: linux
dmi.bios.date: 08/27/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D-E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd08/27/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Tags:

Revision history for this message

Andy Buchanan (andy-buchanans) wrote on 2011-01-06:

AcpiTables.txt Edit (315.4 KiB, text/plain; charset="utf-8")
AlsaDevices.txt Edit (993 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (783 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (62.3 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (4.0 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (14.9 KiB, text/plain; charset="utf-8")
Card1.Amixer.values.txt Edit (502 bytes, text/plain; charset="utf-8")
Card1.Codecs.codec.0.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.1.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.2.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Card1.Codecs.codec.3.txt Edit (1.2 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (831 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (20.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (403 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.1 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (116.8 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (243.7 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (110.0 KiB, text/plain; charset="utf-8")

Brian Murray (brian-murray) on 2011-01-06

Changed in linux (Ubuntu):
assignee:	nobody → Canonical Kernel Team (canonical-kernel-team)
importance:	Undecided → High

Revision history for this message

Andy Buchanan (andy-buchanans) wrote on 2011-01-07:

Just to clarify, in case it's not obvious, the bug was reported after booting into the previous version of the kernel, linux-image-2.6.35-23-generic, under which this bug does /not/ occur, so that I can get on with my work using all four serial ports.

If you need me to boot back into the kernel under which the bug does occur, and post log files from there, please let me know what you need. This can be done 0900–1730 Mon–Fri Europe/London.

Revision history for this message

Andy Buchanan (andy-buchanans) wrote on 2011-01-18:

An update on this bug.

I had to reboot my machine this morning due to an electrical outage overnight. I selected the previous kernel (linux-image-2.6.35-23-generic) rather than the default latest kernel (linux-image-2.6.35-24-generic), as I still require all four serial ports and I believed that they would all work under 2.6.35-23-generic.

However, the problem reported above has now also occurred under this same, older kernel.

Therefore, I conclude that this bug is not a regression after all, but is in fact caused by some other factor which appears to be unrelated to the kernel version. I am going to reboot into 2.6.35-24-generic to see if the problem goes away, and to see if any pattern can be established.

Any help with debugging this would be most appreciated.

Revision history for this message

Lee Jones (lag) wrote on 2011-04-01:

Are you still having issues with this bug?

Are you saying that all four ports did work and now they don't with the same kernel version? If so, it could be a HW issue rather than a kernel one, as there is almost certainly no problem with the driver it's using (Serial: 8250).

Revision history for this message

Andy Buchanan (andy-buchanans) wrote on 2011-04-01: Re: [Bug 698099] Re: OX16PCI954 ttyS0 non-functional regression

On 1 April 2011 16:46, Lee Jones <email address hidden> wrote:
> Are you still having issues with this bug?
>
> Are you saying that all four ports did work and now they don't with the
> same kernel version? If so, it could be a HW issue rather than a kernel
> one, as there is almost certainly no problem with the driver it's using
> (Serial: 8250).

There seems to be some sort of hardware problem or race condition
because this problem only seems to happen when I turn the computer on
from cold, no matter which kernel version I use. If I do a warm reboot
then it almost never happens.

I've never known the problem to go away without a reboot once it has
manifested itself, nor for that matter to manifest itself without a
reboot if it hasn't at the start.

It's not causing me serious issues any more because I just check it
works when I first boot up and, if not, reboot again and 9 times out
of 10 it fixes it, but it's still a little annoying, and my curiosity
would like to get to the bottom of what's causing it!

--
Andy Buchanan
e-mail: <email address hidden>
tel.: 020 8651 1886
mob.: 07940 525 612

Brad Figg (brad-figg) on 2011-04-06

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2012-07-26:

Andy Buchanan, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

apport-collect -p linux <replace-with-bug-number>

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Changed in linux (Ubuntu):
assignee:	Canonical Kernel Team (canonical-kernel-team) → nobody
status:	Confirmed → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-09-25:

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

OX16PCI954 ttyS0 non-functional regression

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package