Your message dated Sun, 26 Jul 2009 17:49:57 +0200
with message-id <20090726154957.ga17...@galadriel.inutil.org>
and subject line Re: Bug#380029: (linux-image-2.6.17-1-686: Can not find tty
Serial using 2.6.17)
has caused the Debian Bug report #380029,
regarding linux-image-2.6.17-1-686: Can not find tty Serial using 2.6.17
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 ow...@bugs.debian.org
immediately.)
--
380029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=380029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.17-1-686
Version: 2.6.17-4
Severity: normal
When using linux-image-2.6.17 udev does not recognize and build the
/dev/ttyS* ports for the serial8250 ports on my machine. Booting the
machine with kernel 2.6.16 resolves this issue.
This may be related to Bug#377539. My machine has the same IR SIR issue
and kernel 2.6.16 resolved it as well.
Please let me know if there is a specific area you would like me to
troubleshoot to help resolve this problem.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages linux-image-2.6.17-1-686 depends on:
ii initramfs-tools [linux-initra 0.72 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-1-686 recommends:
ii libc6-i686 2.3.6-15 GNU C Library: Shared libraries [i
-- debconf information:
linux-image-2.6.17-1-686/preinst/bootloader-initrd-2.6.17-1-686: true
linux-image-2.6.17-1-686/postinst/old-dir-initrd-link-2.6.17-1-686: true
linux-image-2.6.17-1-686/postinst/bootloader-test-error-2.6.17-1-686:
linux-image-2.6.17-1-686/postinst/old-initrd-link-2.6.17-1-686: true
linux-image-2.6.17-1-686/preinst/lilo-has-ramdisk:
linux-image-2.6.17-1-686/postinst/depmod-error-2.6.17-1-686: false
linux-image-2.6.17-1-686/prerm/removing-running-kernel-2.6.17-1-686: true
linux-image-2.6.17-1-686/preinst/overwriting-modules-2.6.17-1-686: true
linux-image-2.6.17-1-686/preinst/lilo-initrd-2.6.17-1-686: true
linux-image-2.6.17-1-686/preinst/failed-to-move-modules-2.6.17-1-686:
linux-image-2.6.17-1-686/postinst/create-kimage-link-2.6.17-1-686: true
linux-image-2.6.17-1-686/postinst/kimage-is-a-directory:
linux-image-2.6.17-1-686/postinst/old-system-map-link-2.6.17-1-686: true
linux-image-2.6.17-1-686/preinst/elilo-initrd-2.6.17-1-686: true
linux-image-2.6.17-1-686/preinst/already-running-this-2.6.17-1-686:
linux-image-2.6.17-1-686/preinst/abort-overwrite-2.6.17-1-686:
linux-image-2.6.17-1-686/postinst/bootloader-error-2.6.17-1-686:
linux-image-2.6.17-1-686/preinst/initrd-2.6.17-1-686:
linux-image-2.6.17-1-686/postinst/depmod-error-initrd-2.6.17-1-686: false
linux-image-2.6.17-1-686/preinst/abort-install-2.6.17-1-686:
linux-image-2.6.17-1-686/prerm/would-invalidate-boot-loader-2.6.17-1-686: true
--- End Message ---
--- Begin Message ---
On Fri, Dec 26, 2008 at 11:40:05AM +0100, Moritz Muehlenhoff wrote:
> On Fri, Aug 11, 2006 at 03:18:24PM -0700, Bill Thompson wrote:
> > A quick follow-up on this bug. I have been able to partially resolve
> > this issue by forcing the 8250_pnp module to load at boot.
> > Initially that module did not load by default.
> >
> > However, the first time the module loads, the UART settings for the
> > ttyS* ports are listed as "unknown". This prevents the ports from being
> > used. If I manually remove the 8250_pnp module and load it a second
> > time, the UART is correctly set and the ports become available. It does
> > not matter if the module is initially loaded at boot time or manually
> > loaded after boot, you must load the module, unload it, and load it a
> > second time to properly set the ttyS* ports.
> >
> > I will keep working on this and pass on what I find, but I would
> > appreciate any thoughts or ideas people may have.
>
> Does this error still occur with more recent kernel versions?
No further feedback, closing the bug.
If anyone reencounters the problem, please reopen this bug.
Cheers,
Moritz
--- End Message ---
