mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Melnikoff <temnota+news@kmv.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: Serial Console and Slow SCSI Disk Access?
Date: Thu, 22 Jun 2006 20:18:54 +0400	[thread overview]
Message-ID: <egsqm3-0tr.ln1@kenga.kmv.ru> (raw)
In-Reply-To: <Pine.LNX.4.63.0606211729360.6305@qynat.qvtvafvgr.pbz>

David Lang <dlang@digitalinsight.com> wrote:
> On Tue, 20 Jun 2006, Helge Hafting wrote:

> > Jeff Gold wrote:
> >> Helge Hafting wrote:
> >>> With nothing attached, any write to the serial device might go
> >>> through a lengthy timeout because of flow control.  [...] 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.
> >> 
> >> This makes sense to me.  When I attach a serial cable and use that to login 
> >> (I've got agetty running), hdparm produces no console messages that I can 
> >> see using minicom.  Still, the disk throughput is around 1.5 MB/sec for 
> >> some reason.  When I disable the serial console in grub.conf and reboot I 
> >> get over 70 MB/sec again.
> >> 
> >> A combination of out-of-tree patches (mainly network related but also one 
> >> to disable PM_TIMERS) seem to eliminate the issue even with the serial 
> >> console enabled, at least for the moment.  That means I no longer have a 
> >> problem, but the whole thing is mysterious to me.
> > I can see one possibility, that I didn't think of yesterday.
> > Do the scsi host adapter share its interrupt with the serial line?
> > (Boot a kernel that has the problem, and when scsi is slow, do a
> > cat /proc/interrupts
> > If the scsi and the serial driver share an interrupt, then that is the source
> > of the problem.

[skipp]

> I ran into a similar problem (extremely slow scsi performance), but hadn't 
> reported it as I made a lot of changes at the same time (moved from 2.6.7 to 
> 2.6.12.3 as well as enabling the serial console). but with this report I wanted 
> to chime in with a weak 'me-too'. I haven't rebooted without the serial console 
> yet to confirm this, but I will do so shortly, and try 2.6.17 to see if it has a 
> similar problem or not.

2.6.17.1 here, MB Intel SCB20, aic7899 onboard. aic7xxx compilled in, serial
core compilled in, serial console enabled.
With/without serial sonsole - speed 66.0 Mb/s.

Maybe problem related to MB chipset?



      reply	other threads:[~2006-06-22 16:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12 21:28 Jeff Gold
2006-06-12 21:39 ` Mark Lord
2006-06-12 22:04   ` Jeff Gold
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 [this message]

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=egsqm3-0tr.ln1@kenga.kmv.ru \
    --to=temnota+news@kmv.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome