netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ganesh Venkatesan <ganesh.venkatesan@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@oss.sgi.com, hejianj@cn.ibm.com,
	linuxppc64-dev@lists.linuxppc.org.sgi.com,
	Anton Blanchard <anton@samba.org>
Subject: Re: Fw: [Bugme-new] [Bug 4628] New: Test server hang while running rhr (network) test on RHEL4 with kernel 2.6.12-rc1-mm4
Date: Tue, 24 May 2005 11:36:49 -0700	[thread overview]
Message-ID: <5fc59ff305052411366b9b058c@mail.gmail.com> (raw)
In-Reply-To: <20050516025901.4b26ccf3.akpm@osdl.org>

Could you tell me what the rhr test is? Is this an IBM internal test tool?


On 5/16/05, Andrew Morton <akpm@osdl.org> wrote:
> 
> Might be a bug in the e100 driver, might not be.
> 
> I assume this is the
> 
>         BUG_ON(skb->list != NULL);
> 
> in __kfree_skb(), although the line number is off-by-one, and the
> .__kfree_skb+0x188/0x240 would tend to contradict that.  Anton, can you
> help work out where we went splat please?
> 
> tx timeouts are fairly rare events, so this might not be a recently-added
> bug.
> 
> Do we know if it is repeatable?
> 
> 
> 
> Begin forwarded message:
> 
> Date: Mon, 16 May 2005 02:44:04 -0700
> From: bugme-daemon@osdl.org
> To: bugme-new@lists.osdl.org
> Subject: [Bugme-new] [Bug 4628] New: Test server hang while running rhr (network) test on RHEL4 with kernel 2.6.12-rc1-mm4
> 
> 
> http://bugme.osdl.org/show_bug.cgi?id=4628
> 
>            Summary: Test server hang while running rhr (network) test on
>                     RHEL4 with kernel 2.6.12-rc1-mm4
>     Kernel Version: 2.6.12-rc1 with mm4 patch
>             Status: NEW
>           Severity: normal
>              Owner: anton@samba.org
>          Submitter: hejianj@cn.ibm.com
>                 CC: hanwenb@cn.ibm.com,mridge@us.ibm.com,rende@cn.ibm.com,wa
>                     ngjs@cn.ibm.com
> 
> 
> Distribution:
> RHEL4 with kernel 2.6.12-rc1-mm4
> 
> Hardware Environment:
> IBM OpenPower( CHRP IBM,9124-720 )
> 
> Software Environment:
> RHEL4
> RHR: rhr2-rhel4-1.0-14a.noarch.rpm
> 
> Problem Description:
> The test server hang while running rhr (network) test on RHEL4 with kernel
> 2.6.12-rc1-mm4.
> 
> Steps to reproduce:
> 1. Download kernel 2.6.12-rc1 and 2.6.12-rc1-mm4 patch from kernel.org, then
> build the kernel on OpenPower 720
> 2. Download rhr2-rhel4-1.0-14a.noarch.rpm from rhn.redhat.com and install it on
> the test machine.
> 3. Configure and run the rhr test via invoking redhat-ready.
> 
> Additional information:
> Here is the backtrace from xmon.
> 
> 3:mon> e
> cpu 0x3: Vector: 700 (Program Check) at [c00000000ffe7920]
>     pc: c00000000029632c: .__kfree_skb+0x188/0x240
>     lr: c000000000296328: .__kfree_skb+0x184/0x240
>     sp: c00000000ffe7ba0
>    msr: 8000000000029032
>   current = 0xc000000107f94040
>   paca    = 0xc000000000431c00
>     pid   = 0, comm = swapper
> kernel BUG in __kfree_skb at net/core/skbuff.c:282!
> 
> 3:mon> t
> [c00000000ffe7c40] d0000000000ebac4 .e100_rx_clean_list+0xa0/0x144 [e100]
> [c00000000ffe7ce0] d0000000000ed6dc .e100_tx_timeout+0x7c/0xb0 [e100]
> [c00000000ffe7d70] c0000000002b87bc .dev_watchdog+0xc8/0x154
> [c00000000ffe7e00] c00000000006d6b4 .run_timer_softirq+0x180/0x298
> [c00000000ffe7ed0] c0000000000667d8 .__do_softirq+0xdc/0x1b8
> [c00000000ffe7f90] c000000000014bf0 .call_do_softirq+0x14/0x24
> [c000000086b43860] c0000000000102c4 .do_softirq+0x98/0xac
> [c000000086b438f0] c0000000000669cc .irq_exit+0x70/0x8c
> [c000000086b43970] c000000000011fb8 .timer_interrupt+0x398/0x47c
> [c000000086b43a90] c00000000000a2b4 decrementer_common+0xb4/0x100
> --- Exception: 901 (Decrementer) at c000000000010554 .dedicated_idle+0x114/0x280
> [c000000086b43e80] c0000000000108c8 .cpu_idle+0x3c/0x54
> [c000000086b43f00] c00000000003cc8c .start_secondary+0x108/0x148
> [c000000086b43f90] c00000000000bd84 .enable_64b_mode+0x0/0x28
> 
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
> 
>

  parent reply	other threads:[~2005-05-24 18:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16  9:59 Fw: [Bugme-new] [Bug 4628] New: Test server hang while running rhr (network) test on RHEL4 with kernel 2.6.12-rc1-mm4 Andrew Morton
2005-05-16 10:41 ` Jian Jun He
2005-05-16 11:00 ` Herbert Xu
2005-05-16 17:43   ` Ganesh Venkatesan
2005-05-16 21:29     ` Herbert Xu
2005-05-16 21:58       ` Jeff Garzik
     [not found]     ` <OFB1F7DBFD.6A6514AD-ON48257004.0038A154-48257004.0038E08A@cn.ibm.com>
2005-05-26  7:38       ` Andrew Morton
2005-05-26  7:53         ` Jeff Garzik
2005-05-24 18:36 ` Ganesh Venkatesan [this message]
2005-05-25  3:21   ` Jian Jun He
  -- strict thread matches above, loose matches on Subject: below --
2005-05-26 13:00 Venkatesan, Ganesh
2005-05-26 16:09 ` Jian Jun He
2005-05-26 20:31   ` Andrew Morton
2005-05-27  6:18     ` Jian Jun He
2005-05-27  8:21       ` Andrew Morton
2005-05-27 10:12         ` Jian Jun He
2005-05-26 20:41 Venkatesan, Ganesh
2005-05-26 21:34 ` Herbert Xu
2005-05-26 23:08   ` Ganesh Venkatesan
2005-05-27  0:11     ` Herbert Xu
2005-05-27  0:20       ` Herbert Xu
2005-05-27  0:28 Venkatesan, Ganesh
2005-05-27  1:26 ` Herbert Xu
2005-05-27  1:44   ` Andrew Morton

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=5fc59ff305052411366b9b058c@mail.gmail.com \
    --to=ganesh.venkatesan@gmail.com \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=hejianj@cn.ibm.com \
    --cc=linuxppc64-dev@lists.linuxppc.org.sgi.com \
    --cc=netdev@oss.sgi.com \
    /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).