Hi all again,
I must have been totally blind with the last try on ksymoops. I hope the
one in the attachment is better now.
the substantial part of my first email:
I get an oops when doing isdnctrl dial ipppX.
Somewhere along the pre7-3 or -4 this behaviour started.
It could be connected with a crash I had around that time that forced me
to fsck. That fsck had to repair lots of errors on the fs.
But then again I replaced all necessary libs to the best of my knowledge
and it still happened.
Now I am up to pre9-2 and still no go. Here is the oops:
My Hardware is as follows:
Biostar M6VBE motherboard, P-III 450, 256MB, Teledat PCI (AVM Fritz PCI),
Matrox G400 single head, creative dxr3 dvd (no module loaded at that
stage), Hauppauge wintv based on bt878.
silverado:/home/rolf# sh /usr/src/linux/scripts/ver_linux
-- Versions installed: (if some fields are empty or look
-- unusual then possibly you have very old versions)
Linux silverado 2.2.14 #2 Wed May 10 21:00:11 CEST 2000 i686 unknown
Kernel modules 2.3.11
Gnu C 2.95.2
Binutils 2.9.5.0.31
Linux C Library 2.1.3
Dynamic linker ldd: version 1.9.11
Procps .
Mount 2.10f
Net-tools 2.05
Kbd 0.99
Sh-utils 2.0g
Modules Loaded hisax isdn msp3400 tuner bttv i2c videodev
snd-pcm-oss snd-pcm-plugin snd-mixer-oss snd-card-es1938 snd-es1938
snd-pcm snd-timer snd-mixer snd soundcore
The module list doesnt represent the modules loaded when it oopses
At that point the modules loaded are hisax isdn msp3400 tuner bttv i2c
videov in version from stock pre2.3.
the lspci -vvv output is included as attachment.
What's left to say is that all is well with 2.2.14 and with pre8-final it
dialled 3 times before oopsing without being able to connect tho.
Bis bald, Rolf
lspci.silverado
Description: Text document
oops
Description: Text document
|