From: Jarek Poplawski <jarkao2@o2.pl>
To: Thibaut VARENE <T-Bone@parisc-linux.org>
Cc: netdev@vger.kernel.org
Subject: Re: kernel BUG in eth_alloc_tx_desc_index at drivers/net/mv643xx_eth.c:1069!
Date: Tue, 9 Jan 2007 10:26:02 +0100 [thread overview]
Message-ID: <20070109092602.GC1703@ff.dom.local> (raw)
In-Reply-To: <7d01f9f00701051103q3ee6ed35q9fd0f778a18061b8@mail.gmail.com>
On 05-01-2007 20:03, Thibaut VARENE wrote:
> Hi,
>
> I've been experiencing this bug on my Pegasos II (PPC G4 1GHz, 512M
...
> [C7F6FA60] [C0012498] ret_from_except+0x0/0x14
> --- Exception: 501 at __kmalloc+0x30/0xc0
> LR = rpc_malloc+0x48/0xac [sunrpc]
> [C7F6FB20] [C3D72508] 0xc3d72508 (unreliable)
> [C7F6FB30] [E2A88E18] rpc_malloc+0x48/0xac [sunrpc]
> [C7F6FB40] [E2A835F8] call_allocate+0x88/0x108 [sunrpc]
> [C7F6FB60] [E2A89554] __rpc_execute+0x94/0x248 [sunrpc]
Aren't there any other warnings displayed before?
No problems with memory or disk?
Regards,
Jarek P.
next prev parent reply other threads:[~2007-01-09 9:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 19:03 kernel BUG in eth_alloc_tx_desc_index at drivers/net/mv643xx_eth.c:1069! Thibaut VARENE
2007-01-09 9:26 ` Jarek Poplawski [this message]
2007-01-09 10:27 ` Thibaut VARENE
2007-01-09 10:52 ` Jarek Poplawski
2007-01-09 10:56 ` Thibaut VARENE
2007-01-09 11:48 ` Jarek Poplawski
2007-01-09 10:57 ` Jarek Poplawski
2007-01-09 13:02 ` Jarek Poplawski
2007-01-09 17:44 ` Thibaut VARENE
2007-01-09 20:05 ` Dale Farnsworth
2007-01-09 21:05 ` Thibaut VARENE
2007-01-10 17:12 ` Thibaut VARENE
2007-01-11 10:42 ` [PATCH] " Jarek Poplawski
2007-01-21 12:18 ` Thibaut VARENE
2007-01-21 13:02 ` Thibaut VARENE
2007-01-22 10:02 ` Jarek Poplawski
2007-01-22 17:06 ` Dale Farnsworth
2007-01-23 8:17 ` Jarek Poplawski
2007-01-23 11:52 ` Thibaut VARENE
2007-01-23 12:42 ` Thibaut VARENE
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=20070109092602.GC1703@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=T-Bone@parisc-linux.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).