and I am at a loss to debug this problem at present. Does anyone know if
tripwire includes some kind of kernel module that it uses when it is running?
(see output below)
If indeed tripwire is what is "tripping up" this system, how would it be
able to do this? If tripwire doesn't somehow load kernel modules and use
them, then this may be a kernel bug (or a hardware problem)...
tnx, K
Red Hat Linux release 7.2 Enigma Kernel 2.4.7010 on an i686
Sage login: invalid operand: 0000 CPU: 0 EIP: 0010:[<c01363bc>] EFLAGS: 00010086 Eax: 0000001c ebx: c39de9c0 ecx: 0000001 edx: 00001dc1 Esi: c12ebdac edi: 0000002 ebp: c39dea08 esp: c42b7e20 ds: 0018 es: 0018 ss: 0018 Process tripwire (pid: 6782, stackpage=c42b7000) Stack: c022d46 00000361…. (3 lines) Call Trace: [<c022d346>] …..
Code: 0f 0b 59 …. <0> Kernel panic: Aiee, killing interrupt handler ! In interrupt handler – not syncing
(machine hangs)
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
