netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: Dmitry Mishin <dim@openvz.org>
Cc: Auke Kok <auke-jan.h.kok@intel.com>,
	john.ronciak@intel.com, jesse.brandeburg@intel.com,
	akpm@osdl.org, netdev@vger.kernel.org, devel@openvz.org,
	xemul@openvz.org
Subject: Re: [PATCH 2.6.18] e1000: fix initialization irqs
Date: Wed, 22 Nov 2006 12:51:19 -0800	[thread overview]
Message-ID: <4564B847.80908@intel.com> (raw)
In-Reply-To: <200611221943.53963.dim@openvz.org>

Dmitry Mishin wrote:
> On Wednesday 22 November 2006 19:19, Auke Kok wrote:
>> Now you're telling the NIC to send interrupts before we routed them I think.
>>
>> If we _up() before we even have an interrupt, even more bad things could happen.
>>
>> What is the reason you wrote this workaround?
> The reason is simple, we've got this oops due to misrouted interrupts, 
> misrouted_irq() function. This workaround helps us, please, advice how to  fix
> it or fix it yourself.

without knowing all the parameters that are involved, I cannot make an informed fix at 
all. I need to see the oops, a full dmesg dump, lspci -vv, and possibly more (preferably 
both before and after the OOPS).

If you can provide those then that would really help a lot, especially since the "fix" 
you provide introduces a great number of trap doors and other undetermined behaviour.

Cheers,

Auke

      reply	other threads:[~2006-11-22 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 12:49 [PATCH 2.6.18] e1000: fix initialization irqs Dmitry Mishin
2006-11-22 16:19 ` Auke Kok
2006-11-22 16:43   ` Dmitry Mishin
2006-11-22 20:51     ` Auke Kok [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=4564B847.80908@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=akpm@osdl.org \
    --cc=devel@openvz.org \
    --cc=dim@openvz.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=xemul@openvz.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).