Thanks for the hints! I hope my report is complete now ;-)
DISTRIBUTION:
Based on an early SuSe-distribution (Nov.94) and extended
by hand. Directory tree based on Slackware manner. I followed
the hacker kernels and update the software in accordance
to linux/Documentation/Changes.txt -- hoping nothing to forget.
WHAT VERSION OF SAMBA:
(none)
SMP OR UNIPROCESSOR:
*one* processor -- NO SMP
WHAT PROCESSOR:
processor : 0
cpu : 586
model : Pentium 75+
vendor_id : GenuineIntel
stepping : 4
fdiv_bug : no
hlt_bug : no
fpu : yes
fpu_exception : yes
cpuid : yes
wp : yes
flags : fpu vme de pse tsc msr mce cx8
bogomips : 39.83
WHAT GCC:
gcc-2.7.2.1
WHAT BINUTILS:
ld -v says
"ld version 2.7 (with BFD 2.7.0.3)"
WHAT LIBC:
libc-5.4.17
WHAT HARDWARE:
motherboard: Intel Plato
processor : Intel Pentium
harddisc : CONNER Model: CFA540S Rev: 0EAD
CONNER Model: CFP1080S Rev: 4040
cdrom : SANYO Model: CRD-254S Rev: 1.05
others : SyQuest Model: EZ135S Rev: 6722
SCSI adapt.: ncr53c815
graphic : ELSA WINNER 1000Trio 2MB (_no_ TrioV, TrioV+ or Virge!!!)
monitor : iliyama vision master 17
mouse : ordinary serial one: MouseMan Sensa by Logitech
modem : ZOOM V34
RAM : 32MB PS2 -- NO EDO or other "tricky RAM"
SWAP : 20MB on harddisc CFA540S
***in addition:
I use iproute.c instead of the old route command. I have NOT
patched ifconfig (if this both is important...)
OUTPUT OF DMESG (ordinary boot, done _after_ the oops-session)
Console: 8 point font, 400 scans
Console: colour VGA+ 80x50, 1 virtual console (max 63)
pcibios_init : BIOS32 Service Directory structure at 0xc00f0120
pcibios_init : BIOS32 Service Directory entry at 0xf13ec
pcibios_init : PCI BIOS revision 2.10 entry at 0xf13d0
Probing PCI hardware.
Calibrating delay loop.. ok - 39.83 BogoMIPS
Memory: 31036k/32768k available (564k kernel code, 384k reserved, 784k data)
Swansea University Computer Society NET3.038 for Linux 2.1
NET3: Unix domain sockets 0.15 for Linux NET3.038.
Swansea University Computer Society TCP/IP for NET3.037
IP Protocols: IGMP, ICMP, UDP, TCP
Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Checking 'hlt' instruction... Ok.
Linux version 2.1.26 (root@solfire) (gcc version 2.7.2.1) #8 Sat Feb 22 20:32:01
1997
POSIX conformance testing by UNIFIX
Real Time Clock Driver v1.07
ncr53c8xx: at PCI bus 0, device 6, function 0
ncr53c8xx: unit=0 chip=815 rev=0x3 base=0xffbffc00, io_port=0xfc00, irq=9
ncr53c815-0: using memory mapped IO at virtual address 0xc2805c00
ncr53c815-0: requesting shared irq 9 (dev_id=0xc0008068)
ncr53c815-0: restart (scsi reset).
ncr53c815-0: final value of dmode/ctest4/ctest5 = 0xc0/0x00/0x00
scsi0 : ncr53c8xx - revision 1.16e
scsi : 1 host.
Started kswapd v 1.21
Vendor: CONNER Model: CFA540S Rev: 0EAD
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: SANYO Model: CRD-254S Rev: 1.05
Type: CD-ROM ANSI SCSI revision: 02
Vendor: CONNER Model: CFP1080S Rev: 4040
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 2, lun 0
Vendor: SyQuest Model: EZ135S Rev: 6722
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi removable disk sdc at scsi0, channel 0, id 3, lun 0
scsi : detected 3 SCSI disks total.
ncr53c815-0-<0,0>: FAST SCSI-2 10.0 MB/s (100 ns, offset 8)
SCSI device sda: hdwr sector= 512 bytes. Sectors= 1056708 [515 MB] [0.5 GB]
ncr53c815-0-<2,0>: FAST SCSI-2 10.0 MB/s (100 ns, offset 8)
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 2110812 [1030 MB] [1.0 GB]
ncr53c815-0-<3,0>: FAST SCSI-2 10.0 MB/s (100 ns, offset 8)
SCSI device sdc: hdwr sector= 512 bytes. Sectors= 262144 [128 MB] [0.1 GB]
sdc: Write Protect is off
Partition check:
sda: sda1 sda2 < sda5 sda6 sda7 >
sdb: sdb1 < sdb5 sdb6 sdb7 sdb8 sdb9 >
sdc: sdc1
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 21484k swap-space (priority -1)
Serial driver version 4.22 with no serial options enabled
tty00 at 0x03f8 (irq = 4) is a 16550A
tty01 at 0x02f8 (irq = 3) is a 16550A
lo UP fl=0000004b pa=0100007F/000000FF brd=FFFFFF7F dst=00000000 <<<----- ???
Serial driver version 4.22 with no serial options enabled
tty00 at 0x03f8 (irq = 4) is a 16550A
tty01 at 0x02f8 (irq = 3) is a 16550A
CSLIP: code copyright 1989 Regents of the University of California
PPP: version 2.2.0 (dynamic channel allocation)
PPP Dynamic channel allocation code copyright 1995 Caldera, Inc.
PPP line discipline registered.
registered device ppp0
ppp0 UP fl=00000051 pa=70DCC3C2/FFFFFFFF brd=00000000 dst=130440C2 <<<----- ???
pppd forgot to specify route netmask.
pppd forgot to specify route netmask.
PPP: ppp line discipline successfully unregistered
CSLIP: code copyright 1989 Regents of the University of California
PPP: version 2.2.0 (dynamic channel allocation)
PPP Dynamic channel allocation code copyright 1995 Caldera, Inc.
PPP line discipline registered.
registered device ppp0
ppp0 UP fl=00000051 pa=70DCC3C2/FFFFFFFF brd=00000000 dst=130440C2 <<<---- ???
pppd forgot to specify route netmask.
pppd forgot to specify route netmask.
PPP: ppp line discipline successfully unregistered
By the way: What does the "<<<---- ???" marked lines mean???
###################################################################
OUTPUT OF KSYMOOPS (first oops as input to ksymoops)
Using `/home/root/linux/System.map' to map addresses to symbols.
>>EIP: c01269d0 <get_hash_table+34/ac>
Trace: c015f12a <trunc_direct+8a/15c>
Trace: c015fd5e <ext2_truncate+46/160>
Trace: c015a80b <ext2_put_inode+3f/64>
Trace: c015a821 <ext2_put_inode+55/64>
Trace: c0125a0d <iput+cd/17c>
Trace: c015d075 <ext2_unlink+209/21c>
Trace: c012d5ff <do_unlink+ef/100>
Trace: c012d636 <sys_unlink+26/3c>
Trace: c010a388 <system_call+38/40>
Code: c01269d0 <get_hash_table+34/ac> cmpl %edi,(%eax)
Code: c01269d2 <get_hash_table+36/ac> jne c01269f8 <get_hash_table+5c/ac>
Code: c01269d4 <get_hash_table+38/ac> cmpw %bx,0x4(%eax)
Code: c01269d8 <get_hash_table+3c/ac> jne c01269f8 <get_hash_table+5c/ac>
Code: c01269da <get_hash_table+3e/ac> cmpl %ebp,0x20(%eax)
Code: c01269dd <get_hash_table+41/ac> je c0126a01 <get_hash_table+65/ac>
Code: c01269df <get_hash_table+43/ac> pushl %esi
Code: c01269e0 <get_hash_table+44/ac> call 00fffa34 <_EIP+fffa34>
Code: c01269e5 <get_hash_table+49/ac> nop
Code: c01269e6 <get_hash_table+4a/ac> nop
Code: c01269e7 <get_hash_table+4b/ac> nop
OUTPUT OF KSYMOOPS (second oops as input to ksymoops)
Using `/home/root/linux/System.map' to map addresses to symbols.
>>EIP: c01269d0 <get_hash_table+34/ac>
Trace: c0127d79 <brw_page+141/364>
Trace: c012819f <generic_readpage+73/80>
Trace: c011dbb9 <try_to_read_ahead+25/104>
Trace: c011dc88 <try_to_read_ahead+f4/104>
Trace: c011e01a <generic_file_read+2d2/61c>
Trace: c012493d <do_open+59/124>
Trace: c0124eab <sys_read+9b/c0>
Trace: c010a388 <system_call+38/40>
Code: c01269d0 <get_hash_table+34/ac> cmpl %edi,(%eax)
Code: c01269d2 <get_hash_table+36/ac> jne c01269f8 <get_hash_table+5c/ac>
Code: c01269d4 <get_hash_table+38/ac> cmpw %bx,0x4(%eax)
Code: c01269d8 <get_hash_table+3c/ac> jne c01269f8 <get_hash_table+5c/ac>
Code: c01269da <get_hash_table+3e/ac> cmpl %ebp,0x20(%eax)
Code: c01269dd <get_hash_table+41/ac> je c0126a01 <get_hash_table+65/ac>
Code: c01269df <get_hash_table+43/ac> pushl %esi
Code: c01269e0 <get_hash_table+44/ac> call 00fffa34 <_EIP+fffa34>
Code: c01269e5 <get_hash_table+49/ac> nop
Code: c01269e6 <get_hash_table+4a/ac> nop
Code: c01269e7 <get_hash_table+4b/ac> nop
(I used the System.map file in /usr/src/linux/ -- it has the same date
as my kernel)
###################################################
Would You please do me a favour???
If You will find something in the dmesg output (for example),
which in unecessary configured "badly" or "not so good" or ...
(my English is a personal OOPS, which I have to trace down
by time ;-), which eats up perfomance and/or system stability
please give me a hint, how to make it better. I only can learn
from all the gurus here :-)
Hope that all the outputs above would help...
KEEP HACKING!
meino
...who dances with modems...
On 22-Feb-97 Tomasz Motylewski wrote:
>
>On Sat, 22 Feb 1997, Meino Christian Cramer wrote:
>
>>
>> Please mail me, if more informations are required!
>>
>
>Best would be the result of running your log file through 'ksymoops' program.
>Make sure it uses proper System.map file - generated together with the kernel
>you were running when you got the OOPS.
>
>Alan Cox recommends also:
>
>
>>Ok small lesson for folks reporting bugs
>>1. What distribution
>>2. What version of samba #(non relevant here)
>>3. SMP or Uniprocessor
>>4. What processor
>>5. What gcc/binutils
>>6. What libc
>>7. What hardware.
>
(output of 'dmesg' would be appreciated).