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

Bug#391459: marked as done (8250/serial driver conflicts with smsc-ircc2 driver)

Your message dated Mon, 27 Jul 2009 01:21:15 +0200
with message-id <20090726232115.GA22894@galadriel.inutil.org>
and subject line Re: Problem with serial/8250 driver still under 2.6.18
has caused the Debian Bug report #391459,
regarding 8250/serial driver conflicts with smsc-ircc2 driver
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
391459: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391459
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.17-2-686
Version: 2.6.17-9
Severity: important


Hi,

I've seen different bugs related to serial ports and the 8250 driver but
not exactly like mine, so here you get a new report (can it be that the
driver is pretty broken in the 2.6.17 kernel? :-> ).

Anyway, even though everything seems pretty OK (modules loaded, device
files present, kernel recognizes the port), I'm not able anymore to sync
with jpilot on /dev/ttyS0 under kernel 2.6.17 (I tested it: it still works
perfectly under kernel 2.6.16-18), telling me that:
	pi_bind error: /dev/ttyS0 No such device
	Check your serial port and settings
	Exiting with status SYNC_ERROR_BIND
I get similar errors using pilot-link tools, and each time I try to access the
serial port, I get a new "ttyS0: LSR safety check engaged!" message in
dmesg.
I set the bug to important because I will have to rollback to 2.6.16;
without ability to sync PC and Palm, I can't really work.

I put some more info below, don't hesitate to tell me if you need more.

Thanks for your help, have a nice week-end,
Eric

$ dmesg | grep tty
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
00:02: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS0: LSR safety check engaged!
ttyS0: LSR safety check engaged!
ttyS0: LSR safety check engaged!
ttyS2: LSR safety check engaged!
[...]

$ setserial -g /dev/ttyS?
/dev/ttyS0: No such device
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3
/dev/ttyS2, UART: unknown, Port: 0x0000, IRQ: 0
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3

$ ll /dev/ttyS?
crw-rw---- 1 root dialout 4, 64 2006-10-06 20:02 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 2006-10-06 20:02 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 2006-10-06 20:02 /dev/ttyS2
crw-rw---- 1 root dialout 4, 67 2006-10-06 20:02 /dev/ttyS3

$ find /sys -name \*ttyS?
/sys/class/tty/ttyS0
/sys/class/tty/ttyS3
/sys/class/tty/ttyS2
/sys/class/tty/ttyS1
/sys/devices/pnp0/00:02/tty:ttyS0
/sys/devices/platform/serial8250/tty:ttyS3
/sys/devices/platform/serial8250/tty:ttyS2
/sys/devices/platform/serial8250/tty:ttyS1

$ ll /sys/class/tty/ttyS0
total 0
-r--r--r-- 1 root root 4096 2006-10-06 18:17 dev
lrwxrwxrwx 1 root root    0 2006-10-06 20:02 device ->
.../../../devices/pnp0/00:02
--w------- 1 root root 4096 2006-10-06 18:17 uevent

- ttyS2 is set quiet for use by irda-utils (which works)
- parameters of the port are correct as compared with Windows

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.17-2-686 depends on:
ii  initramfs-tools [linux-initra 0.80       tools for generating an initramfs
ii  module-init-tools             3.2.2-3    tools for managing Linux kernel mo

Versions of packages linux-image-2.6.17-2-686 recommends:
ii  libc6-i686                   2.3.6.ds1-4 GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false
  linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk:
  linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686:
  linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686:
  linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686:
  linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false
  linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686:

--- End Message ---
--- Begin Message --- 
On Sat, Nov 29, 2008 at 05:49:39PM +0100, Moritz Muehlenhoff wrote:
> On Tue, Dec 12, 2006 at 11:28:20AM +0100, Eric Lavarde - Debian Bugs wrote:
> > reassign 391459 linux-image-2.6.18-3-686
> > retitle 391459 8250/serial driver conflicts with smsc-ircc2 driver
> > thanks
> > 
> > Hi,
> > 
> > I confirm the observation from Bill, disabling the infrared driver makes
> > the issue disappear (and I have also an nc6000). But I wouldn't call this
> > a solution :-^
> > Again, tell me if I can provide any more information, debug something, etc.
> 
> Does this error still occur with more recent kernel/udev versions, such as
> the ones from Lenny?
> 
> If you're running Etch, could you try to reproduce this bug
> with the 2.6.24 based kernel added in 4.0r4?
> http://packages.qa.debian.org/l/linux-2.6.24.html

No further feedback, closing the bug.

If anyone reencounters the problem, please reopen this bug.

Cheers,
        Moritz

--- End Message ---
Reply to: