From: Vasily Averin <vvs@sw.ru>
To: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
linux-ide@vger.kernel.org
Cc: devel@openvz.org
Subject: Re: [Q] ide cdrom in native mode leads to irq storm?
Date: Fri, 27 Oct 2006 17:17:34 +0400 [thread overview]
Message-ID: <454206EE.9080206@sw.ru> (raw)
In-Reply-To: <453DC65C.8000408@sw.ru>
Vasily Averin wrote:
> Vasily Averin wrote:
>> there is node with Intel 7520-based motherboard (MSI-9136), IDE cdrom (hda) and
>> SATA disc and 2.6.19-rc3 linux kernel.
>>
>> When I set IDE controller into the native mode, I get irq storm on the node and
>> this interrupt is disabled. If this interrupt is shared, the other subsystems
>> are stop working too.
>>
>> When I switch the IDE controller into legacy mode, all works correctly.
I have reproduced the same issue on the another node:
ASUSTeK P5GD1-VM,
Intel 915G chipset,
ICH6 IDE controller,
IDE dvdrom: SONY DVD-ROM DDU1615 (hda),
sata disk: WDC WD1600JS-00M
when I switch IDE controller to the native mode, I see "Disabling IRQ" message,
then kernel generates an oops in create_empty_buffers(), like I've reported earlier.
Could somebody please help me to troubleshoot this issue? I've seen this issue
on the customer nodes and would like to know how I can work-around this issue
without any changes inside motherboard BIOS.
thank you,
Vasily Averin
next prev parent reply other threads:[~2006-10-27 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 7:37 [Q] ide cdrom in native mode leads to irq storm? Vasily Averin
2006-10-24 7:53 ` Vasily Averin
2006-10-27 13:17 ` Vasily Averin [this message]
2006-10-27 14:21 ` Alan Cox
2006-11-14 9:08 ` [Q] PCI Express and ide (native) " Vasily Averin
2006-11-15 10:46 ` Tejun Heo
2006-11-15 18:49 ` Jeff Garzik
2006-11-16 8:45 ` Vasily Averin
2006-11-17 12:54 ` [Q] workaround for " Vasily Averin
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=454206EE.9080206@sw.ru \
--to=vvs@sw.ru \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=axboe@kernel.dk \
--cc=devel@openvz.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).