From: Alexander Huemer <alexander.huemer@sbg•ac.at>
To: Jarek Poplawski <jarkao2@gmail•com>
Cc: David Miller <davem@davemloft•net>,
linux-net@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: kernel panics with net_rx_action on kernels >2.6.26
Date: Mon, 15 Dec 2008 21:11:09 +0100 [thread overview]
Message-ID: <4946B9DD.9010105@sbg.ac.at> (raw)
In-Reply-To: <20081215133521.GA6697@ff.dom.local>
Jarek Poplawski wrote:
> On 15-12-2008 07:48, David Miller wrote:
>
>> From: Alexander Huemer <alexander.huemer@sbg•ac.at>
>> Date: Sun, 14 Dec 2008 15:17:32 +0100
>>
>> Networking developers generally don't read the linux-net list, it is
>> for user configuration and basic questions only, not bug reports or
>> technical discussions.
>>
>> netdev is the place to report such things, and I've added that to the
>> CC:
>>
>>
>>> one of my machines (x86) crashes under heavy network load with kernels
>>>
>>>> 2.6.26, i tried quite everything possible between 2.6.27 and 2.6.28-rc8.
>>>>
>>> lspci -vv: http://xx.vu/~ahuemer/lspci_vv.txt <http://xx.vu/%7Eahuemer/lspci_vv.txt>
>>> of the quad nic 2 ports are used, the machine is acting as a iptables
>>> firewall/router.
>>>
>>> kernel config (2.6.26) http://xx.vu/~ahuemer/config <http://xx.vu/%7Eahuemer/config>
>>> screenshot of the panic:
>>> http://xx.vu/~ahuemer/kernel_panic_net_rx_action.jpg <http://xx.vu/%7Eahuemer/kernel_panic_net_rx_action.jpg>
>>>
>>> as i do not have any problems with kernels <=2.6.26, i doubt that this
>>> is a hardware problem.
>>> in case of the panic, nothing is written to the system log.
>>>
>>> any hints welcome.
>>> please CC me on replies, i am not subscribed to the mailing list.
>>>
>
> Could you try this patch, please?
>
> Jarek P.
> ---
>
> drivers/net/starfire.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/net/starfire.c b/drivers/net/starfire.c
> index 0358809..f86d6bb 100644
> --- a/drivers/net/starfire.c
> +++ b/drivers/net/starfire.c
> @@ -1503,6 +1503,11 @@ static int __netdev_rx(struct net_device *dev, int *quota)
> desc->status = 0;
> np->rx_done = (np->rx_done + 1) % DONE_Q_SIZE;
> }
> +
> + if (*quota == 0) { /* out of rx quota */
> + retcode = 1;
> + goto out;
> + }
> writew(np->rx_done, np->base + CompletionQConsumerIdx);
>
> out:
>
thanks for the patch, jarek.
i applied it to 2.6.28-rc8.
the machine is already running under heavy network load, as before, when
the panics occur.
heavy load means high packets/second values, not high byte/second values.
if you find that necessary for testing i will find a way to pump some
gigs through the machine.
let's see what happens.
i will get back to you after a new panic or 2 days without panic.
--
kind regards
alex.
next prev parent reply other threads:[~2008-12-15 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4945157C.9000305@sbg.ac.at>
2008-12-15 6:48 ` kernel panics with net_rx_action on kernels >2.6.26 David Miller
2008-12-15 13:35 ` Jarek Poplawski
2008-12-15 20:11 ` Alexander Huemer [this message]
2008-12-16 6:59 ` Jarek Poplawski
2008-12-16 9:22 ` David Miller
2008-12-16 14:06 ` [PATCH] " Jarek Poplawski
2008-12-16 23:42 ` David Miller
[not found] <4944026B.40301@sbg.ac.at>
2008-12-20 23:00 ` Rafael J. Wysocki
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=4946B9DD.9010105@sbg.ac.at \
--to=alexander.huemer@sbg$(echo .)ac.at \
--cc=davem@davemloft$(echo .)net \
--cc=jarkao2@gmail$(echo .)com \
--cc=linux-net@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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