From: Alexey Dobriyan <adobriyan@gmail.com>
To: David Lang <david.lang@digitalinsight.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Fwd: [Bug 4774] e1000 driver works on UP, but not SMP x86_64
Date: Sat, 25 Jun 2005 01:57:13 +0400 [thread overview]
Message-ID: <200506250157.14499.adobriyan@gmail.com> (raw)
David, please try this debugging patch.
You can also register at http://bugme.osdl.org/createaccount.cgi and add
yourself to CC list.
---------- Forwarded Message ----------
Subject: [Bug 4774] e1000 driver works on UP, but not SMP x86_64
Date: Saturday 25 June 2005 01:27
From: bugme-daemon@kernel-bugs.osdl.org
To: adobriyan@gmail.com
http://bugzilla.kernel.org/show_bug.cgi?id=4774
------- Additional Comments From nacc@us.ibm.com 2005-06-24 14:27 -------
Created an attachment (id=5211)
--> (http://bugzilla.kernel.org/attachment.cgi?id=5211&action=view)
Debugging patch
That e1000 error message indicates an EINVAL error code, which is from this
code:
if ((irqflags & SA_SHIRQ) && !dev_id)
return -EINVAL;
if (irq >= NR_IRQS)
return -EINVAL;
if (!handler)
return -EINVAL;
I don't think it's the last one, because e1000_intr (which is sent in to
request_irq() from e1000) is prototyped/defined. I spun up a patch to spit out
some debugging here which simply inserts some printks (if the only driver which
gets this warning is e1000, then it shouldn't flood your logs) -- basically
narrowing down which error condition is causing the failure. I'm guessing it's
probably the first case, but let's be sure.
next reply other threads:[~2005-06-24 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 21:57 Alexey Dobriyan [this message]
2005-06-24 22:15 ` Fwd: [Bug 4774] e1000 driver works on UP, but not SMP x86_64 David Lang
-- strict thread matches above, loose matches on Subject: below --
2005-06-25 18:22 Alexey Dobriyan
2005-06-27 0:52 ` David Lang
[not found] ` <D53BF43BC70DD511A22500508BB3C0071AA66A3A@wlvexc00.diginsite.com>
2005-06-29 7:32 ` David Lang
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=200506250157.14499.adobriyan@gmail.com \
--to=adobriyan@gmail.com \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).