Mailing List Archive: ooops on debian with 2.2.17

ooops on debian with 2.2.17

Nov 27, 2000, 5:26 AM

Post #1 of 5 (1233 views)

Hello folks,

I just subscribed to this list and checked the last three months in the
archieves, but I couldn't find anything, so here's my problem.
I installed 4 computers with debian potato with current 2.2.17 and
patched one of them with the lvs patch (both, 1.0 and 1.1). Everytime I
booted the patched machine it crashed. As far as I have seen there were
two kinds of crashes, both related to the lvs patch, tho. I attached the
debugged oops messages (bzip2'd, I think you mind getting a 200kb
mail:-)) maybe some of you can help me. I also tried this on the other
machines, with the same results. Even older kernel version (2.2.15 and
2.2.16 tested) crashed with the aproperiate patches. However, one of
those machines didn't crash on boot but instantly after typing one of
two commands into it - not any better.
The machines are standard PIII 400 with 128megs and, yes, the kernel
compiled fine, there are no interrupt conflicts nor badblocks on disc.

thanks alot,

--
Wiktor Wodecki

Unix-Administration
Wodecki@wapme-systems.de

Re: ooops on debian with 2.2.17 [ In reply to ]

wodecki at wapme-systems

Nov 27, 2000, 5:27 AM

Post #2 of 5 (1184 views)

Permalink

yay, that's typicall...forgot to attach the files. Here we go now

--
Wiktor Wodecki
Unix-Administration
Wodecki@wapme-systems.de

Re: ooops on debian with 2.2.17 [ In reply to ]

ratz at tac

Nov 27, 2000, 6:30 AM

Post #3 of 5 (1171 views)

Permalink

Hi Wiktor,

> debugged oops messages (bzip2'd, I think you mind getting a 200kb
> mail:-)) maybe some of you can help me. I also tried this on the other

You bzip2'd it, so it isn't that big.

> machines, with the same results. Even older kernel version (2.2.15 and
> 2.2.16 tested) crashed with the aproperiate patches. However, one of
> those machines didn't crash on boot but instantly after typing one of
> two commands into it - not any better.

Indeed, I've never seen such a funny trace but I don't read
traces that often. Could you please give us more information
about the used modutils and binutils? How did you invoke ksymoops?
Could you also provide your .config?

Regards,
Roberto Nibali, ratz

BTW: Looking at the trace I don't think lvs is the only problem you
have. You have by far more fundamental problems ;)

--
mailto: `echo NrOatSz@tPacA.cMh | sed 's/[NOSPAM]//g'`

Re: ooops on debian with 2.2.17 [ In reply to ]

wodecki at wapme-systems

Nov 27, 2000, 8:11 AM

Post #4 of 5 (1185 views)

Permalink

ratz wrote:
> Indeed, I've never seen such a funny trace but I don't read
> traces that often. Could you please give us more information
> about the used modutils and binutils? How did you invoke ksymoops?
> Could you also provide your .config?

I use binutils standard debian package version 2.9.5.0.37-1 and modutils
2.3.11-10. I also patched the kernel with the kmsgdump patch to save the
oops output on a floppy. Afterwards I ran it through ksymoops with the
approperiate parameters for vmlinux and the modules. I know ksymoops
gives error about them, but these were the files I used to boot (I can't
run ksymoops with the kernel running, since it wont boot).

> BTW: Looking at the trace I don't think lvs is the only problem you
> have. You have by far more fundamental problems ;)

uhm, everything works okay if I disable lvs in kernel...but I also
looked at the trace and understand what you mean :-))

Regards,

--
Wiktor Wodecki
Unix-Administration
Wodecki@wapme-systems.de

Re: ooops on debian with 2.2.17 [ In reply to ]

ja at ssi

Nov 27, 2000, 3:59 PM

Post #5 of 5 (1188 views)

Permalink

Hello,

On Mon, 27 Nov 2000, Wiktor Wodecki wrote:

> CONFIG_IP_MASQUERADE_VS_TAB_BITS=4096

This is an invalid value. Use 14 bits for example. 4096 bits
kills the kernel.

Regards

--
Julian Anastasov <ja@ssi.bg>

Mailing List Archive

Attached Files:

Attached Files: