All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brice Figureau <brice+lkml@daysofwonder.com>
To: linux-kernel@vger.kernel.org
Subject: Serial console not working after device detection.
Date: Sat, 27 Sep 2008 19:20:46 +0200	[thread overview]
Message-ID: <48DE6B6E.4050306@daysofwonder.com> (raw)

Hi,

On two of my servers (some Dell poweredge 1850 and 2850), booting a 
2.6.26 debian kernel while at the same time looking at the serial 
console, nothing is printed after the following snippet:
...
Linux agpgart interface v0.103
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

The serial port of these servers is configured as 115200n8 and connected 
to an Opengear serial console server for remote administration through ssh.

This is not an issue per-se, but for an unknown reason 2.6.25 and 2.6.26 
debian kernels don't boot succesfully, and I'm trying to understand why, 
which is a complex task when you don't see anything :-)
The latest known debian kernel that boots fine is a 2.6.22 (I didn't try 
2.6.23 or 2.6.24).

On this kernel that boots, the first lines that the serial console 
displays are those from the initrd.

After the boot the dmesg contains the following lines which are just 
after the last line displayed (ie the serial8250: ttyS0 is at... line):

pnp: the driver 'serial' has been registered
pnp: match found with the PnP device '00:06' and the driver 'serial'
00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A
pnp: the driver 'parport_pc' has been registered
FDC 0 is a National Semiconductor PC87306
RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
...

Is there anything I can do to display something after the device 
detection, in order to understand why those kernels are not booting?

Many thanks for any answer,
Please CC: me on replies, as I'm not subscribed to the list.
--
Brice Figureau

             reply	other threads:[~2008-09-27 17:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-27 17:20 Brice Figureau [this message]
2008-09-27 21:33 ` Serial console not working after device detection Alan Cox
2008-09-28 11:18   ` Brice Figureau
2008-09-28 14:03     ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48DE6B6E.4050306@daysofwonder.com \
    --to=brice+lkml@daysofwonder.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.