Description of problem:
I'm having a problem with 2.6.17-1.2139 freezing hard on my ThinkPad T42p.
In trying to debug it I wanted to use netconsole, however it no longer works
with the netdump RPM and the /etc/init.d/netdump script.
The error is "netlog unknown parameter" when trying to start the script (which
modprobes the kernel module).
Here is modinfo -p from 2.6.16-1.2133:
modinfo -p 2.6.16-1.2133_FC5/kernel/drivers/net/netconsole.ko
Here is modinfo -p from 2.6.17-1.2139:
modinfo -p 2.6.17-1.2139_FC5/kernel/drivers/net/netconsole.ko
Also, the netdump module appears to no longer be shipping. Is this intentional?
The situation did not changed for 1,5 month. Anybody cares? Netdump feature
would be nice to trace actual VMware-server problems. My output here:
[root@gsxt7 ~]# service netdump start
netdump: cannot arp on eth0
initializing netdump FATAL: Module netdump not found.
initializing netconsole FATAL: Error inserting netconsole
symbol in module, or unknown parameter (see dmesg)
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
netdump is no longer supported in FC6 because the kernel dumping
mechanism has been replaced by kexec/kdump.
for how to use kdump to gather core dumps for the kernel.
Hmm. Backporting the FC6 kernel to FC5 caused quite a bit of damage here.
As Linda pointed out, we dropped the netdump patches from the kernel in favour
of what was upstream (in part as they were unmaintained and tended to bitrot
We also previously had some netconsole changes that for reasons I was never able
to figure out deviated from upstream for no good reason.
This has broken the FC5 netdump script quite horribly.
The easiest fix for FC5 is probably to
a) Drop netdump support from the script [rather than backport all the kdump stuff]
b) Make the scripts use netconsole= instead of netlog=
seems reasonable. I'll get to it as soon as I'm able.
Created attachment 142324 [details]
patch to fix up netdump on FC-5
Haven't got an FC-5 box handy to test it on, but this should make the netlog
setup use the netconsole module option instead and fails if any NETDUMP
parameters are configured on systems not having the netdump.ko module for the
running version. Please test this and confirm that it functions as expected.
I don't have easy access to a FC5 box anymore (it now runs FC6). I doubt I'll be
able to dig one up soon.
Asside from a minor typo on the netdump.ko logic, I've managed to test and get
the results I wanted. I'll check the corrected patch in
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
since we don't support netdump anymore, I'm closing this as wontfix