On 16/06/05, David Liontooth <[EMAIL PROTECTED]> wrote: > Package: ipkungfu > Severity: normal > > On an amd64 (dual opteron) that has been running 2.6.9 stably for > months, I got my first kernel panic. There is unfortunately nothing in
Hmmm, I may have to consider getting ipkungfu builds for amd64's stopped if there is an issue with this. > the logs, and I didn't copy the screen, so this won't be useful, just a > vague data point. The crash said something like "Aiee -- not sync'ing" > and the text above showed that my tg3 NIC was involved, plus a series > of fireware-related errors. ipkungfu is prime suspect, as it was > recently installed and fit the crash profile. I agree with this. > > I don't need ipkungfu and removed it: > > Stopping ipkungfu: FATAL: Module ip_tables not found. > iptables v1.2.11: can't initialize iptables table `mangle': Table does not > exist (do you need to insmod?) > Perhaps iptables or your kernel needs to be upgraded. > iptables: No chain/target/match by that name I'm not certain about errors like this, but it could even possibly relate to the fact that iptables may have a fault? I really depends on what happened regrading iptables, ipkungfu, and possible interference... There are a few reasons why this may have happened: 1) ipkungfu did not load correct at start 2) someone (maybe you) cleared all the iptables chains 3) there is a problem with iptables on amd64 which means that it never loaded the chains correctly 4) there is another firewall installed on your system, which loads after ipkungfu which has cleared the "chains" and replaced it with its own that ipkungfu does not know about, and tries to clear non-existant chains. > > Please close this report; I'm unable to provide the necessary Not going to close the report, because: 1) I'd love to know if you get the same problem with shorewall - a similar iptables firewall (thats if you are comfortable with doing this 2) I suspect that it may be related to iptables or maybe even the kernel in amd64, in which case, we can notify these maintainers and sort it all out for maybe less knowledgable users. 3) If it is a problem with ipkungfu we can consider (from what I believe) taking it out of the amd64 package lists. > information to prosecute. If my machine ever crashes again I'll post a > retraction of these unsubstantiated accusations and a public apology. I think if such a thing was to happen, it'd make history! > > - T. Sneddon > > -- System Information: > Debian Release: testing/unstable > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.9-ac6 > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) > > Versions of packages ipkungfu is related to: > ii reportbug 3.13 reports bugs in the Debian > distrib > pn totem-gstreamer <none> (no description available) Last thing, the above worries me, ipkungfu is NOT related to either of the two! > > Thanks for reporting this, -- N Jones Blogging @ http://nigelj.blogspot.com Proud Debian & FOSS User Debian Maintainer of: html2ps & ipkungfu
