Hi all,
I am trying to replace 2 of my current Dachstein firewalls with a Bering version. Each of these use 3c509 NICs which have been working fine for a couple of years under Dachstein but as soon as I boot the machines in Bering I get the following Kernel Panic:
skput: over: c2837d85:0 put:60 dev;eth0 kernel BUG at skbuff.c:92! invalid operand:0000 CPU:0 EIP: 0010:[<c01df749>] Not tainted EFLAGS: 000010286 eax:000000026 ebx:c10e8490 ecx:c1996000 edx:c1fb2890 esi:c10f8d60 edi:0000063c ebp:00000012 esp:c19a7b38 ds:0018 es:0018 ss:0018 Process iptables (pid:3092, stackpage ........... .. ............. Kernel panic:Aiee, killing interupt handler!
At this point the machine is locked up with the keyboard lights flashing and can only be accessed by rebooting. The module I am using was downloaded from the LEAF site under the Bering section.
Unfortunately I have no facility to compile modules so any help would be appreciated.
First, we probably need a bit more detail on what versions of things you are using. Am I right in surmising that you downloaded an image of Bering-1.2 and the associated modules file from the Bering download area, that is, these packages:
Bering_1.2_img_bering-1680.bin [or .exe]
Bering_1.2_modules_2.4.20.tar.gzIf not, be specific about what you are using. The LEAF site is a bit like Zork, with "twisty little passages" that sometimes lead you to obsolete or incorrect files, and the first thing to check is that you are using current and matching versions of things.
Second, these kernel panics can be the result of hardware problems, not only of module problems. In your case, this is less likely (since the system runs OK with Dachstein), but you do want to check two possibilities:
1. A bad floppy disk. If you have not tried several different floppies, please do.
2. A RAM problem. 2.4.x kernels do use a bit more RAM than 2.2.x kernels, typically, so you want to make sure there is enough RAM on the system to handle Bering. (The "invalid operand" part of the panic message makes this a particularly tempting guess, BTW.)
Finally, I know that it is hard to transcribe panic messages exactly, but the fragmentary nature of yours leaves me wondering where in boot/init this panic happens. "As soon as I boot" isn't really an answer to this, since it surely does not happen before the 3c509 module is loaded, and a lot happens before that (like actual booting; module installation doesn't happen until later, after init is running). The closing reference to "iptables" makes me think it is well after the NIC module is installed, perhaps when Shorewall is setting up its rules. You might want to clarify that part (for example, does the module think it finds and configures the NICs, earlier in the boot/init process)?
If none of these suggestions leads tyou to a solution, please post a follow-up with additional information about your setup and exactly what Bering files you downloaded. (Unless, of course, someone else regognizes the problem from the description you posted and gives you a succinct answer.)
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
