Serial Port Woes

[twodogs]

I finally got my serial card sorted, so I'm trying to get some devices to work. I installed my Denon amp and a CM11A yesterday and all seemed fine. Last night I tried to play a movie and my Denon was not responding. I opened a terminal and typed "dmesg" to see if my serial ports were all being recognized. Seems there is a problem. Here is part of the output from var/log/messages. This repeats over and over. I deleted the CM11A device that was using the D1 port. I also reinstalled the driver. Somewhere during my messing about and rebooting, the Denon started to work, but I'm still getting all these references to ttyD1.

Code: [Select]

Oct 14 08:06:39 dcerouter kernel: [75076.544586] XFS mounting filesystem sdb1
Oct 14 08:06:39 dcerouter kernel: [75076.753193] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:40 dcerouter kernel: [75077.777151] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:41 dcerouter kernel: [75078.779142] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:42 dcerouter kernel: [75079.792568] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:43 dcerouter kernel: [75080.793697] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:44 dcerouter kernel: [75081.816763] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:45 dcerouter kernel: [75082.505570] XFS mounting filesystem sdb1
Oct 14 08:06:46 dcerouter kernel: [75082.853319] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:47 dcerouter kernel: [75083.855263] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:48 dcerouter kernel: [75084.900651] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:49 dcerouter kernel: [75085.902643] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:50 dcerouter kernel: [75086.917194] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:51 dcerouter kernel: [75087.918317] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:51 dcerouter kernel: [75088.455561] XFS mounting filesystem sdb1
Oct 14 08:06:52 dcerouter kernel: [75088.919411] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0
Oct 14 08:06:53 dcerouter kernel: [75089.932475] No of Errors In ttyD1 brake=0 frame=0 parity=0 overrun=0


[twodogs]

Does the "DCErouter kernel" mean that this is a LinuxMCE fault, or should I suspect hardware issues?

[merkur2k]

thats just a reference to what the logfile is (system hostname is dcerouter, and its the kernel log)

[twodogs]

My XFS storage drive and serial card appear in the message log, so I deleted them from MCE admin, then physically removed the drive and serial card. Now I'm getting this in var/log/messages.

Code: [Select]

Oct 15 08:21:20 dcerouter kernel: [  228.920108] type=1503 audit(1318688480.067:11): operation="inode_permission" requested_mask="::rw" denied_mask="::rw" fsuid=7 name="/dev/tty" pid=19247 profile="/usr/sbin/cupsd"

[twodogs]

I'm still trying to track this down. It looks like the ttyD0 and ttyD1 ports might have a permissions issue. I thought that the problem was caused by apparmor, so I removed it entirely with no effect. Now I'm wondering if the problem is related to a cron job. Syslog starts to complain about the ttyD0 port once every second, right after the line with "/usr/bin/crontab". Does this make sense to anyone?

Code: [Select]

Oct 20 12:12:49 dcerouter /usr/sbin/cron[9210]: (CRON) INFO (pidfile fd = 3)
Oct 20 12:12:49 dcerouter /usr/sbin/cron[9211]: (CRON) STARTUP (fork ok)
Oct 20 12:12:49 dcerouter /usr/sbin/cron[9211]: (CRON) INFO (Running @reboot jobs)
Oct 20 12:12:54 dcerouter kernel: [  160.257846] ip6_tables: (C) 2000-2006 Netfilter Core Team
Oct 20 12:12:55 dcerouter kernel: [  161.144736] Zapata Telephony Interface Registered on major 196
Oct 20 12:12:55 dcerouter kernel: [  161.144745] Zaptel Version: 1.4.11
Oct 20 12:12:55 dcerouter kernel: [  161.144747] Zaptel Echo Canceller: MG2
Oct 20 12:12:55 dcerouter kernel: [  161.157885] ztdummy: Trying to load High Resolution Timer
Oct 20 12:12:55 dcerouter kernel: [  161.157893] ztdummy: Initialized High Resolution Timer
Oct 20 12:12:55 dcerouter kernel: [  161.157896] ztdummy: Starting High Resolution Timer
Oct 20 12:12:55 dcerouter kernel: [  161.157903] ztdummy: High Resolution Timer started, good to go
Oct 20 12:13:02 dcerouter acpid: client connected from 12532[0:0]
Oct 20 12:13:03 dcerouter acpid: client connected from 12532[0:0]
Oct 20 12:13:19 dcerouter /usr/bin/crontab[15046]: (root) LIST (root)
Oct 20 12:13:38 dcerouter kernel: [  204.673100] No of Errors In ttyD0 brake=0 frame=0 parity=0 overrun=0
Oct 20 12:13:39 dcerouter kernel: [  205.674002] No of Errors In ttyD0 brake=0 frame=0 parity=0 overrun=0
Oct 20 12:13:40 dcerouter kernel: [  206.674764] No of Errors In ttyD0 brake=0 frame=0 parity=0 overrun=0
Oct 20 12:13:41 dcerouter kernel: [  207.708753] No of Errors In ttyD0 brake=0 frame=0 parity=0 overrun=0
Oct 20 12:13:42 dcerouter kernel: [  208.790813] No of Errors In ttyD0 brake=0 frame=0 parity=0 overrun=0
Oct 20 12:13:43 dcerouter kernel: [  209.800563] No of Errors In ttyD0 brake=0 frame=0 parity=0 overrun=0
Oct 20 12:13:44 dcerouter kernel: [  210.801408] No of Errors In ttyD0 brake=0 frame=0 parity=0 overrun=0
Oct 20 12:13:45 dcerouter kernel: [  211.849254] No of Errors In ttyD0 brake=0 frame=0 parity=0 overrun=0
Oct 20 12:13:47 dcerouter kernel: [  212.873162] No of Errors In ttyD0 brake=0 frame=0 parity=0 overrun=0

[merkur2k]

most likely not related, that just happens to be about the same time something goes wrong with the serial card.
if i were you, i would install the serial card in a system with a freshly installed copy of ubuntu (0810 or 1004, as matches the linuxmce version you intend to use) and see if you can reproduce the problem there. I suspect it is not anything lmce specific that is causing it.

[twodogs]

I'll give that a try.