From: Jeff Gold <jgold@mazunetworks.com>
To: Mark Lord <lkml@rtr.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Serial Console and Slow SCSI Disk Access?
Date: Mon, 12 Jun 2006 18:04:33 -0400 [thread overview]
Message-ID: <448DE4F1.9000407@mazunetworks.com> (raw)
In-Reply-To: <448DDF1D.5020108@rtr.ca>
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.
Jeff
next prev parent reply other threads:[~2006-06-12 22:04 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 [this message]
2006-06-19 6:50 ` Helge Hafting
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=448DE4F1.9000407@mazunetworks.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox