netdump netpoll bug?

Every time my system panics and  my client is dumping the
vmcore to
the netdump-server, I get error
"netpoll_start_netdump: called
recursively. rebooting". and my client reboots. And I
get a
vmcore-incomplete file. I did a fresh install of Linux
RHEL4-WS and
still get the same problem. Any ideas how to proceed?

google search for "netpoll_start_netdump" ..
"netdump bug recursively"
etc dint return any perceivable results.. any leads would be
appreciated..

also if this is the wrong place to post, I would appreciate
it if i
could know the right place to post this message?


Thanks a lot,
Rohan Mutagi

--
Crash-utility mailing list
Crash-utilityredhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

==> Regarding [Crash-utility] netdump netpoll bug?;
"Rohan Mutagi" <rohan208gmail.com> adds:

rohan208> Every time my system panics and my client is
dumping the vmcore
rohan208> to the netdump-server, I get error
"netpoll_start_netdump: called
rohan208> recursively. rebooting". and my client
reboots. And I get a
rohan208> vmcore-incomplete file. I did a fresh install
of Linux RHEL4-WS
rohan208> and still get the same problem. Any ideas how
to proceed?

rohan208> google search for
"netpoll_start_netdump" .. "netdump bug
rohan208> recursively" etc dint return any
perceivable results.. any leads
rohan208> would be appreciated..

rohan208> also if this is the wrong place to post, I
would appreciate it if
rohan208> i could know the right place to post this
message?

That message is likely accompanied by a stack trace.  The
contents of that
stack trace will be necessary to diagnose the problem.  Also
useful would
be the exact kernel version, and the type of network card
you are using.

The best place for this type of request would be Red Hat
support.  If you
don't have a support account, then file a bugzilla:
  http://bugzilla.redhat.co
m/

My first suggestion to you is to ensure that you are running
the latest
kernel available, which would be 2.6.9-34.EL for RHEL 4.

Thanks!

Jeff

--
Crash-utility mailing list
Crash-utilityredhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

My kernel version is 2.6.9-34.EL (my system is "up to
date" from
RHN)... I am running this inside VMWare and the eth0 is seen
as
"PCnet/PCI II 79C97OA"

I am wondering how do I provide the stack trace? As its on
the screen
of my laptop. This trace doesnt apper in the
"log" file generated by
the netdump-server.

Any leads would be appricaited.

Thanks,
Rohan Mutagi


On 5/15/06, Jeff Moyer <jmoyerredhat.com> wrote:
> ==> Regarding [Crash-utility] netdump netpoll bug?;
"Rohan Mutagi" <rohan208gmail.com> adds:
>
> rohan208> Every time my system panics and my client
is dumping the vmcore
> rohan208> to the netdump-server, I get error
"netpoll_start_netdump: called
> rohan208> recursively. rebooting". and my
client reboots. And I get a
> rohan208> vmcore-incomplete file. I did a fresh
install of Linux RHEL4-WS
> rohan208> and still get the same problem. Any ideas
how to proceed?
>
> rohan208> google search for
"netpoll_start_netdump" .. "netdump bug
> rohan208> recursively" etc dint return any
perceivable results.. any leads
> rohan208> would be appreciated..
>
> rohan208> also if this is the wrong place to post, I
would appreciate it if
> rohan208> i could know the right place to post this
message?
>
> That message is likely accompanied by a stack trace. 
The contents of that
> stack trace will be necessary to diagnose the problem. 
Also useful would
> be the exact kernel version, and the type of network
card you are using.
>
> The best place for this type of request would be Red
Hat support.  If you
> don't have a support account, then file a bugzilla:
>   http://bugzilla.redhat.co
m/
>
> My first suggestion to you is to ensure that you are
running the latest
> kernel available, which would be 2.6.9-34.EL for RHEL
4.
>
> Thanks!
>
> Jeff
>
> --
> Crash-utility mailing list
> Crash-utilityredhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility
>

--
Crash-utility mailing list
Crash-utilityredhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

==> Regarding Re: [Crash-utility] netdump netpoll bug?;
"Rohan Mutagi" <rohan208gmail.com> adds:

rohan208> My kernel version is 2.6.9-34.EL (my system is
"up to date" from
rohan208> RHN)... I am running this inside VMWare and the
eth0 is seen as
rohan208> "PCnet/PCI II 79C97OA"

rohan208> I am wondering how do I provide the stack
trace? As its on the
rohan208> screen of my laptop. This trace doesnt apper in
the "log" file
rohan208> generated by the netdump-server.

Typically, I would recommend a serial console.  I guess
that's not possible
with VMWare, though.  ;)

rohan208> Any leads would be appricaited.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=
142269

That bug seems to be private... *sigh*  Here is the stack
trace that you
are likely getting:

Call Trace:
 [<f882604d>] pcnet32_start_xmit+0x23/0xf8 [pcnet32]
 [<c0274c78>] netpoll_send_skb+0x6a/0x98
 [<c02751d6>] arp_reply+0x2f7/0x2ff
 [<c027521f>] netpoll_rx+0x41/0x2e4
 [<c026a5c0>] netif_rx+0x1c/0x1b2
 [<f88267e8>] pcnet32_rx+0x2c8/0x325 [pcnet32]
 [<f88261ed>] pcnet32_interrupt+0xcb/0x3fe [pcnet32]
 [<f8824132>] pcnet32_poll_controller+0x16/0x1f
[pcnet32]
 [<c0274aa2>] netpoll_poll+0x32/0x8f
 [<f89ef69d>] netpoll_netdump+0xa3/0x478 [netdump]
 [<c01f9a96>] sysrq_handle_crash+0x0/0x8
 [<c01f9a96>] sysrq_handle_crash+0x0/0x8
 [<f89ef5fa>] netpoll_netdump+0x0/0x478 [netdump]
 [<f89ef5f1>] netpoll_start_netdump+0xf1/0xfa
[netdump]
 =======================
 ...

Basically, the network transmit queue is busy, and so we
call the
poll_controller routine to free up some TX descriptors.  If,
in the
process, we end up with ARP requests, we need to service
them.  This ends
up in a call to the hard_start_xmit routine inside the
pcnet32 driver, and
deadlocks.

Is there possibly another driver that VMWare will mimic?  If
not, you can
circumvent this problem by adding an ARP entry for the
crashing system to
the netdump server.

-Jeff

--
Crash-utility mailing list
Crash-utilityredhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

Excellent Jeff!! You are a life saver!
I couldn't find a quick way to make Vmware change it
drivers, however,
adding arp entry to my server worked! Now I need to figure
out a way
to make this working on a more permanent basis.
thanks once again.
Rohan Mutagi

On 5/15/06, Jeff Moyer <jmoyerredhat.com> wrote:
> ==> Regarding Re: [Crash-utility] netdump netpoll
bug?; "Rohan Mutagi" <rohan208gmail.com> adds:
>
> rohan208> My kernel version is 2.6.9-34.EL (my
system is "up to date" from
> rohan208> RHN)... I am running this inside VMWare
and the eth0 is seen as
> rohan208> "PCnet/PCI II 79C97OA"
>
> rohan208> I am wondering how do I provide the stack
trace? As its on the
> rohan208> screen of my laptop. This trace doesnt
apper in the "log" file
> rohan208> generated by the netdump-server.
>
> Typically, I would recommend a serial console.  I guess
that's not possible
> with VMWare, though.  ;)
>
> rohan208> Any leads would be appricaited.
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=
142269
>
> That bug seems to be private... *sigh*  Here is the
stack trace that you
> are likely getting:
>
> Call Trace:
>  [<f882604d>] pcnet32_start_xmit+0x23/0xf8
[pcnet32]
>  [<c0274c78>] netpoll_send_skb+0x6a/0x98
>  [<c02751d6>] arp_reply+0x2f7/0x2ff
>  [<c027521f>] netpoll_rx+0x41/0x2e4
>  [<c026a5c0>] netif_rx+0x1c/0x1b2
>  [<f88267e8>] pcnet32_rx+0x2c8/0x325 [pcnet32]
>  [<f88261ed>] pcnet32_interrupt+0xcb/0x3fe
[pcnet32]
>  [<f8824132>] pcnet32_poll_controller+0x16/0x1f
[pcnet32]
>  [<c0274aa2>] netpoll_poll+0x32/0x8f
>  [<f89ef69d>] netpoll_netdump+0xa3/0x478
[netdump]
>  [<c01f9a96>] sysrq_handle_crash+0x0/0x8
>  [<c01f9a96>] sysrq_handle_crash+0x0/0x8
>  [<f89ef5fa>] netpoll_netdump+0x0/0x478 [netdump]
>  [<f89ef5f1>] netpoll_start_netdump+0xf1/0xfa
[netdump]
>  =======================
>  ...
>
> Basically, the network transmit queue is busy, and so
we call the
> poll_controller routine to free up some TX descriptors.
 If, in the
> process, we end up with ARP requests, we need to
service them.  This ends
> up in a call to the hard_start_xmit routine inside the
pcnet32 driver, and
> deadlocks.
>
> Is there possibly another driver that VMWare will
mimic?  If not, you can
> circumvent this problem by adding an ARP entry for the
crashing system to
> the netdump server.
>
> -Jeff
>
> --
> Crash-utility mailing list
> Crash-utilityredhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility
>

--
Crash-utility mailing list
Crash-utilityredhat.com
https://www.redhat.com/mailman/listinfo/crash-utility