This is a rather long report on Linux-2.1.110.
This is written in outline format so that it is easier to read.
I. Hardware
a. Motherboard - FICA PT-2003 - Intel Chipset
b. CPU - AMD K5
c. Memory - 64 MB
d. Cards
i. Two 3Com 3c509B ISA NIC's
ii. BusLogic Flashpoint DL BT-932 (PCI)
iii. Soundblaster 32 PnP
iv. Diamond S3Virge video card (PCI)
e. Hard Drives
i. Two Quantum ST6.5S 6.4GB - SCSI Channel 0
ii. Four Seagate ST11200N 1.0GB - SCSI Channel 1
iii. One Fujitsu M1606S-512 1.0GB - SCSI Channel 1
iv. One Maxtor MXT-540SL 521MB - SCSI Channel 1
vi. One Quantum LPS525S 525MB - SCSI Channel 1
vii. One Plextor PX-12TS - SCSI Channel 0
viii. Two HP C4324/C4325 CD-R - SCSI Channel 0
II. Hard Drives Configuration
a. Four Seagates are configured as RAID linear on /dev/md0
The ext2 filesystem wsa created with the following command
mke2fs -c -g 7228 /dev/md0
It should be noted that the Seagates if used as separate
ext2 filesystems work fine no problems.
b. Quantum LPS525SL, Maxtor are not currently used,
i.e. installed no filesystems
c. Fujitsu is ext2 filesystem -- /usr/src
d. One Quantum is Linux-2.1.110.
Originally a Linux Universe Distribution
installation, everything upgraded over the years by me.
e. One Quantum, is RedHat-5.1 running Linux-2.0.34
III. Software Configuration
a. gcc-2.7.2.1
b. isapnptools-1.15
Kernel level PnP is not enabled.
c. e2fsprogs-1.12
e. 3c509 driver version - 1.16 ported to Linux-2.1.x by me.
The network cards work fine.
f. BusLogic driver version - 2.1.13 of 17 April 1998
IV. Problems
a. Sound
i. Building Soundblaster driver as a module leads to
drivers/sound/sound_firmware.o not being included in
the building of sb.o. This leads to an unresolved symbol
of sound_firmware_load, which is only needed when the
driver is built as a module. See sb_common.c as to where
the IFDEF code is
located.
I have fixed this temporary by building the sb.o module
by a shell script which includes sound_firmware.o. I was
able to get the Soundblaster card to work after fixing
this error.
I also used mm/vmalloc.c from Linux-2.1.109 instead of
the vmalloc.c from Linux-2.1.110.
b. MD linear /dev/md0
i. Consistent filesystem corruption when copying large files
from one of the Quantum drives to /mnt1 (/dev/md0).
The file sizes range from 25MB to 131MB. When /dev/md0
reaches approximately 27% capacity the BusLogic driver
continues to given screen after screen of errors, then
the machine reboots.
Running fsck -f /dev/md0 by hand fsck complains of
illegal blocks in inode 52, which is an inode use
by the 131MB file.
It would seem that the problem occurs when the copy needs
to span disks.
Below are the latest entries from syslog:
Jul 23 18:04:36 johann linux: scsi : aborting command due to timeout :
pid 102511,
scsi1, channel 0, id 1, lun 0 Write (6) 03 41 74 f4 00
Jul 23 18:04:36 johann linux: scsi1: Aborting CCB #102513 to Target 1
Jul 23 18:04:36 johann linux: scsi : aborting command due to timeout :
pid 102512,
scsi1, channel 0, id 1, lun 0 Write (6) 03 42 68 10
00
Jul 23 18:04:36 johann linux: scsi1: Aborting CCB #102514 to Target 1
Jul 23 18:04:36 johann linux: scsi : aborting command due to timeout :
pid 102523,
scsi1, channel 0, id 0, lun 0 Write (6) 00 00 22 02 00
Jul 23 18:04:36 johann linux: scsi1: Aborting CCB #102525 to Target 0
Jul 23 18:04:36 johann linux: scsi1: CCB #102525 to Target 0 Aborted
Jul 23 18:04:36 johann linux: scsi : aborting command due to timeout :
pid 102524,
scsi1, channel 0, id 0, lun 0 Write (6) 00 00 2c 02
00
Jul 23 18:04:36 johann linux: scsi1: Aborting CCB #102526 to Target
0
Jul 23 18:04:36 johann linux: scsi1: CCB #102526 to Target 0
Aborted
Jul 23 18:04:36 johann linux: scsi : aborting command due to timeout :
pid 102525,
scsi1, channel 0, id 0, lun 0 Write (6) 00 00 48 02 00
<snip several dozen of same type of message as above>
Jul 23 18:04:37 johann linux: scsi1: Sending Bus Device Reset CCB
#102628 to Target 1
Jul 23 18:04:37 johann linux: SCSI host 1 abort (pid 102511) timed out -
resetting
Jul 23 18:04:37 johann linux: SCSI bus is being reset for host 1 channel
0.
Jul 24 00:01:45 johann linux: scsi : aborting command due to timeout :
pid 209093,
scsi1, channel 0, id 1, lun 0 Write (6) 08 08 3c f4 00
Jul 24 00:01:45 johann linux: scsi1: Aborting CCB #209095 to Target 1
Jul 24 00:01:45 johann linux: scsi : aborting command due to timeout :
pid 209094,
scsi1, channel 0, id 1, lun 0 Write (6) 08 09 30 18 00
Jul 24 00:01:45 johann linux: scsi1: Aborting CCB #209096 to Target 1
Jul 24 00:01:45 johann linux: scsi : aborting command due to timeout :
pid 209106,
scsi1, channel 0, id 1, lun 0 Write (6) 08 09 48 f4 00
Jul 24 00:01:45 johann linux: scsi1: Aborting CCB #209108 to Target 1
Jul 24 00:01:45 johann linux: scsi : aborting command due to timeout :
pid 209107,
scsi1, channel 0, id 1, lun 0 Write (6) 08 0a 3c f4 00
Jul 24 00:01:45 johann linux: scsi1: Aborting CCB #209109 to Target 1
-- Terry L. Ridder Blue Danube Software (Blaue Donau Software) "We do not write software, we compose it."When the toast is burnt and all the milk has turned and Captain Crunch is waving farewell when the Big One finds you may this song remind you that they don't serve breakfast in hell ==Breakfast==Newsboys
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html