public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11: iostat values broken, or IDE siimage driver ?
Date: Fri, 4 Mar 2005 00:24:07 +0000 (UTC)	[thread overview]
Message-ID: <d089r7$iuq$1@news.cistron.nl> (raw)
In-Reply-To: d05513$8fr$1@news.cistron.nl

In article <d05513$8fr$1@news.cistron.nl>,
Miquel van Smoorenburg <miquels@cistron.nl> wrote:
>In article <d053g8$6et$1@news.cistron.nl>,
>Miquel van Smoorenburg <miquels@cistron.nl> wrote:
>>I just upgrades one of our newsservers from 2.6.9 to 2.6.11. I
>>use "iostat -k -x 2" to see live how busy the disks are. But
>>I don't believe that Linux optimizes things so much that a disk
>>can be 1849.55% busy :)
>
>Perhaps this is the cause:
>
>Mar  2 19:55:25 hdg: sata_error = 0x00000000, watchdog = 0,
>siimage_mmio_ide_dma_test_irq
>Mar  2 19:55:26 quantum last message repeated 12 times
>hdg: sata_error = 0x00000000, watchdog = 0, siimage_mmio_ide_dma_test_irq

I just recompiled and reconfigured with libata sata_sil.c instead
of ide siimage.c, and now everything just works fine.

I just noticed this in dmesg:

** PCI interrupts are no longer routed automatically.  If this
** causes a device to stop working, it is probably because the
** driver failed to call pci_enable_device().  As a temporary
** workaround, the "pci=routeirq" argument restores the old
** behavior.  If this argument makes the device work again,
** please email the output of "lspci" to bjorn.helgaas@hp.com
** so I can fix the driver.

.. so perhaps that might causing siimage.c to break, but this
being a production server now catching up with a backlog I can't
try it right away.

Mike.


  parent reply	other threads:[~2005-03-04  0:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02 19:17 2.6.11: iostat values broken ? Miquel van Smoorenburg
2005-03-02 19:43 ` 2.6.11: iostat values broken, or IDE siimage driver ? Miquel van Smoorenburg
2005-03-02 22:02   ` Rick Lindsley
2005-03-03  0:43     ` Miquel van Smoorenburg
2005-03-04  0:24   ` Miquel van Smoorenburg [this message]
2005-03-21 22:09 ` 2.6.11: iostat values broken ? Andrew Morton
2005-03-22  0:12   ` Miquel van Smoorenburg

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='d089r7$iuq$1@news.cistron.nl' \
    --to=miquels@cistron.nl \
    --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