All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Jeff Gold <jgold@mazunetworks.com>
Cc: Mark Lord <lkml@rtr.ca>, linux-kernel@vger.kernel.org
Subject: Re: Serial Console and Slow SCSI Disk Access?
Date: Mon, 19 Jun 2006 08:50:18 +0200	[thread overview]
Message-ID: <4496492A.1030907@aitel.hist.no> (raw)
In-Reply-To: <448DE4F1.9000407@mazunetworks.com>

Jeff Gold wrote:
> Mark Lord wrote:
>> This can happen if there are kernel messages being printed on the 
>> serial console.
>> If all is quiet, I would expect things to be as fast as normal 
>> elsewhere.
>
> Thank you for the suggestion.  I don't see much in /var/log/messages 
> (syslogd is running).  There are 3326 lines taking up about 256 kB 
> there, and when I run hdparm runs no further messages are generated.
>
> I don't have anything attached to the serial port at the moment.  
> Could that cause problems?  I'm going to attach something and see what 
> happens.  Other advice is still welcome. 
With nothing attached, any write to the serial device might go through
a lengthy timeout because of flow control.  I'd consider that a bug
in this case though, and there is usually no console printout
per scsi disk access either.


I would not be surprised if your serial console causes a longer boot time,
as all boot messages have to be transferred over the slow serial link
or in the worst case timed out one message at a time.

But I can't see why it'd make scsi disks slower. The scsi host adapter 
initialization
writes some messages of course, but there should be no more console accesses
during a hdparm test run.

Helge Hafting

  reply	other threads:[~2006-06-19  6:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12 21:28 Serial Console and Slow SCSI Disk Access? Jeff Gold
2006-06-12 21:39 ` Mark Lord
2006-06-12 22:04   ` Jeff Gold
2006-06-19  6:50     ` Helge Hafting [this message]
2006-06-19 15:14       ` Jeff Gold
2006-06-20  7:11         ` Helge Hafting
2006-06-20 16:20           ` Jeff Gold
2006-06-22  0:32           ` David Lang
2006-06-22 16:18             ` Andrey Melnikoff

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=4496492A.1030907@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=jgold@mazunetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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.