From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, sanarin@nikiet.ru
Subject: Re: [Bugme-new] [Bug 9225] New: typhoon : "no descs for cmd, had (needed) 0 (1) cmd, 31 (7) resp"
Date: Thu, 25 Oct 2007 13:20:16 -0700 [thread overview]
Message-ID: <20071025132016.b6f8ce45.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9225-10286@http.bugzilla.kernel.org/>
On Thu, 25 Oct 2007 06:45:42 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9225
>
> Summary: typhoon : "no descs for cmd, had (needed) 0 (1) cmd, 31
> (7) resp"
> Product: Drivers
> Version: 2.5
> KernelVersion: 2.6.23.1 SMP PREEMPT
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Network
> AssignedTo: jgarzik@pobox.com
> ReportedBy: sanarin@nikiet.ru
>
>
> Most recent kernel where this bug did not occur: none
> Distribution: Fedora Core 4
> Hardware Environment: Intel 845 chipset, 3 x 3C990-FX-97 NICs
> Software Environment:
> Problem Description:
> Our dmesg buffer fill of these messages
>
> eth1: no descs for cmd, had (needed) 0 (1) cmd, 31 (7) resp
> eth1: error getting stats
> eth1: no descs for cmd, had (needed) 0 (1) cmd, 31 (7) resp
> eth1: error getting stats
> eth1: no descs for cmd, had (needed) 0 (1) cmd, 31 (7) resp
> eth1: error getting stats
>
> and so one.
>
> After for days of working we got kernel panic.
>
> Steps to reproduce:
(switching to email - please respond via reply-to-all, not via the bugzilla
web interface)
typhoon.c doesn't appear to have a maintainer.
It oopsed in typhoon_rx - there's a jpg attached to the bugzilla report.
parent reply other threads:[~2007-10-25 20:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-9225-10286@http.bugzilla.kernel.org/>]
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=20071025132016.b6f8ce45.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sanarin@nikiet.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.