From: Hans Mueller <hans42mueller@googlemail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-ide <linux-ide@vger.kernel.org>
Subject: Re: [Bug 16142] r8169: Kernel Panic when a lot of data is transferred through network interface
Date: Sat, 3 Jul 2010 09:49:18 +0200 [thread overview]
Message-ID: <20100703094918.03007437@cbook.fritz.box> (raw)
In-Reply-To: <20100630183138.GA11036@liondog.tnic>
Hi,
On Wed, 30 Jun 2010 20:31:38 +0200
Borislav Petkov <bp@alien8.de> wrote:
> Alternatively, if you have a spare PCI NIC, you can insert it into one
> of the PCI slots after having disabled the onboard NIC in the BIOS. Just
> for testing purposes, to see whether "unsharing" the IRQ line fixes the
> issue.
I have currently no access to the computer, I will be able to test
things again on monday.
But as I wrote in my original bugreport, I tested with a PCI NIC. (But
the onboard NIC was not completely disabled, it was only disabled via
ifconfig ... down)
When using the PCI NIC, the whole problem (kernel panik) did not occure.
--
Regards Jonas
next prev parent reply other threads:[~2010-07-03 7:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 8:07 [Bug 16142] r8169: Kernel Panic when a lot of data is transferred through network interface Borislav Petkov
[not found] ` <20100617150008.16a5e653@cpc>
2010-06-18 7:45 ` Borislav Petkov
2010-06-18 13:08 ` Hans Mueller
2010-06-18 15:02 ` Borislav Petkov
2010-06-18 22:50 ` Hans Mueller
2010-06-19 10:05 ` Borislav Petkov
2010-06-19 11:27 ` Hans Mueller
2010-06-23 8:02 ` Borislav Petkov
2010-06-25 16:58 ` Hans Mueller
2010-06-30 6:54 ` Borislav Petkov
2010-06-30 18:02 ` Hans Mueller
2010-06-30 18:31 ` Borislav Petkov
2010-07-03 7:49 ` Hans Mueller [this message]
2010-07-03 8:23 ` Borislav Petkov
2010-07-03 11:01 ` [PATCH] ide-cd: Do not access completed requests in the irq handler Borislav Petkov
2010-07-06 4:24 ` David Miller
2010-07-03 11:41 ` [Bug 16142] r8169: Kernel Panic when a lot of data is transferred through network interface Hans Mueller
2010-07-03 11:53 ` Borislav Petkov
2010-07-05 11:44 ` Hans Mueller
2010-07-05 12:11 ` Borislav Petkov
[not found] <bug-16142-11633@https.bugzilla.kernel.org/>
2010-06-14 22:17 ` bugzilla-daemon
2010-06-15 6:39 ` bugzilla-daemon
2010-06-15 11:17 ` bugzilla-daemon
2010-06-15 11:50 ` bugzilla-daemon
2010-06-15 15:19 ` bugzilla-daemon
2010-06-15 15:20 ` bugzilla-daemon
2010-06-15 15:21 ` bugzilla-daemon
2010-06-15 15:21 ` bugzilla-daemon
2010-06-15 15:22 ` bugzilla-daemon
2010-06-15 15:22 ` bugzilla-daemon
2010-06-15 15:26 ` bugzilla-daemon
2010-06-15 19:12 ` bugzilla-daemon
2010-06-15 19:39 ` bugzilla-daemon
2010-07-03 8:26 ` bugzilla-daemon
2012-07-20 12:55 ` bugzilla-daemon
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=20100703094918.03007437@cbook.fritz.box \
--to=hans42mueller@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=linux-ide@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).