Nigel Jones wrote: >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. > > Hi Nigel,
The problem may well have arisen from an underlying iptables problem -- I never configured the package, just installed it to remind me it exists, with a plan to get around to it at some point. I generally assume packages will do no harm, though they may not do any good until I give them some attention. Even if a package fails badly, it obviously shouldn't crash the system. Unfortunately we won't know now if ifkongfu was the culprit, as I'm not in a position to experiment with this machine for the next four months. I think it's extremely unlikely the problem applies to all amd64 installations, but it will no doubt take some work to narrow it down. If we assume ipkungfu was at fault, we have this scenario: -- it runs (even if ineffectually) for a week with no incident -- out of the blue it crashes the whole system There wasn't a trace in the logs, and I wasn't doing anything unusual. This could be very hard to track down, so I really don't think it's worth considering this a serious bugreport unless someone else runs into a similar behavior. Appreciate your friendly reply though! I may be able to return to this in the fall. Dave > > >>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, > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
