From: Ed Sweetman <safemode@comcast.net>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: 8139too PCI IRQ issues WAS Re: 2.6.12 breaks 8139cp
Date: Sun, 26 Jun 2005 10:59:02 -0400 [thread overview]
Message-ID: <42BEC2B6.6020905@comcast.net> (raw)
In-Reply-To: <200506261446.57802.nick@linicks.net>
What are you supposed to do though if you dont have that bios option.
And if the bios wasn't changed between kernel version upgrades, what is
the PCI irq subsystem doing now that requires such a change? And what
makes it possible to remove the problem with reverting just the 8139too
driver ... There is a quirk here, but the fix should be in the kernel,
since not all bios' allow you to make the fix yourself.
Nick Warne wrote:
>>It seems that whatever is causing the bug i'm seeing was a change that
>>involved the network driver/interrupt subsystem and not actually the
>>8139too driver, this was done at around 2.6.3-2.6.4. A NAPI patch that
>>was introduced at that time basically reverted the interrupt function
>>and removed the poll functions from the driver (via not enabling napi in
>>Kconfig).
>>
>>
>
>Ummm. I was involved in this. Here is the 'final' post after Mr Hirofumi
>found the cause of my issues:
>
>http://www.ussg.iu.edu/hypermail/linux/kernel/0402.3/1709.html
>
>But I looked at what he said and found the real problem on my system (after
>all that):
>
>http://www.ussg.iu.edu/hypermail/linux/kernel/0403.1/1537.html
>
>Nick
>
>
next prev parent reply other threads:[~2005-06-26 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 13:46 2.6.12 breaks 8139cp Nick Warne
2005-06-26 14:59 ` Ed Sweetman [this message]
2005-06-26 15:03 ` 8139too PCI IRQ issues WAS " Nick Warne
2005-06-27 13:27 ` OGAWA Hirofumi
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=42BEC2B6.6020905@comcast.net \
--to=safemode@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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