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

Bug#428895: marked as done (No way to use serial console with Xen kernel)

Your message dated Mon, 15 Feb 2010 20:18:14 +0100
with message-id <20100215191814.GN9624@baikonur.stro.at>
and subject line Re: Xen || vserver troubles
has caused the Debian Bug report #396169,
regarding No way to use serial console with Xen kernel
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.)


-- 
396169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396169
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.18-4-xen-amd64
Version: 2.6.18.dfsg.1-12etch2
It appears that the 2.6.18-4 kernel in Etch does not support 8250 serial devices. I see the following messages in dmesg when I boot up: 

Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
8250_pnp: Unknown symbol serial8250_unregister_port
8250_pnp: Unknown symbol serial8250_register_port
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
8250_pnp: Unknown symbol serial8250_unregister_port
8250_pnp: Unknown symbol serial8250_register_port
The devices are enabled in the BIOS and work correctly when running the stock 2.6.18-4 kernel. When booting with that version, the relevant dmesg lines look like: 

Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
This appears to be a Xen issue, since Xen steals the ttyS* devices for xencons. I found a reference to a possible fix here: 

http://www.nabble.com/xen-console-question-t690692.html
As the server is at a remote data center with RS232 console being the only available way to access it in the event of network problems, I'd like to see the 8250/16550 driver re-enabled in the Xen kernel.

--- End Message ---
--- Begin Message --- 
the 2.6.18 linux images from Etch are no longer supported, thus closing
this bug report.  As both Xen or vserver stayed out of tree it is very
unlikely that they improved a lot since.

With modern hardware kvm or lxc (linux containers) are recommended.
if you still haven't upgraded to Lenny please notice that Etch has
no security support any more as of today:
http://www.debian.org/News/2010/20100121


if you can reproduce said bugs with 2.6.32 linux images from
unstable please shout on said box and bug can be reopened:
reportbug -N <bugnr>

thank you for your report.

--- End Message ---
Reply to: