From: Tejun Heo <htejun@gmail.com>
To: Rob Whitton <rwhitton@bluearc.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: "SCR access via SIDPR is available but doesn't work"
Date: Thu, 09 Oct 2008 06:48:38 +0900 [thread overview]
Message-ID: <48ED2AB6.4010905@gmail.com> (raw)
In-Reply-To: <3D76E016F4A2A749A1EB1A3FD83E22BC01E0D723@uk-email.terastack.bluearc.com>
Rob Whitton wrote:
> I have run this test and I can confirm that NumLock does still work,
> although unreliably. What I mean by this is that once we get to this
> point often it takes a number of presses of numlock to get the state of
> the LED to change. Before we get to this point it seems to behave fine.
> Ctrl-alt-sysrq-t doesn't appear to dump anything to the console. After
> doing ctrl-alt-sysrq-t numlock no longer functions at all.
>
> Something I forgot to mention in my original email is that using
> "noapic" at boot is also a work around for the problem. It isn't an
> option for us as we are going to be using advanced features such as MSI
> that are only available via the APIC route.
I don't think MSI has anything to do with noapic. Can you please post
the result of "lspci -nn"? Also, what kind of motherboard is it?
Thanks.
--
tejun
next prev parent reply other threads:[~2008-10-08 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D76E016F4A2A749A1EB1A3FD83E22BC01D6E466@uk-email.terastack.bluearc.com>
[not found] ` <48E6D8F4.2080207@gmail.com>
2008-10-08 10:37 ` "SCR access via SIDPR is available but doesn't work" Rob Whitton
2008-10-08 21:48 ` Tejun Heo [this message]
2008-10-08 21:50 ` Tejun Heo
2008-10-09 11:14 ` Rob Whitton
2008-10-13 7:28 ` Tejun Heo
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=48ED2AB6.4010905@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=rwhitton@bluearc.com \
/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).