This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
*** Bug 724925 has been marked as a duplicate of this bug. ***
Reproduced on RHEL6.1 with kernel-2.6.32-131.el6.
[root@hp-dl585g7-02 ~]# virsh list
Id Name State
4 test2 running
5 test running
[root@localhost ~]# ethtool -i eth0
Verify that the netdump server is installed.
Change the password for the "netdump" user: passwd netdump
Enable the netdump server: chkconfig netdump-server on
Start the netdump server: service netdump-server start
Verify that the netdump client is installed.
Edit /etc/sysconfig/netdump and add the following line:
Enter the following command and give the netdump password when prompted: service netdump propagate
Enable the netdump client: chkconfig netdump on
Start the netdump client: service netdump start.
Add "echo c > /proc/sysrq-trigger" to /etc/rc.local to make the guset "test" reboot in a loop.
Got 1 hang in 80 times and the vmcore is not collected as expected.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
A race condition between the e1000 irq handler and e1000 netpoll handler could lead to a deadlock while executing the netdump utility. The disable_irq_nosync() function is now called to eliminate the potential deadlock situation.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.