HELP! FreeBSD 2.2.8 system regularly gets corrupted, AHA2940UW ?

HELP! FreeBSD 2.2.8 system regularly gets corrupted, AHA2940UW ?

Post by Daniel T » Wed, 01 Sep 1999 04:00:00

        A newly set up 2.2.8 FreeBSD system used for moderate
amounts of email, file service etc, is regularly getting
corrupted at a frequency of about one every 3-5 days.
        The system is a Pentium Pro 200Mhz with 64Mb ECC RAM
and a Tyan 1668? mobo, with an Adaptec 2940UW and a pair of
Seagate 2Gb UW SCSI disks.
        The symptoms are a crash with the root, /var and /usr
filesystems scrambled (usually root and /var are totally
scrambled, fsck reports Partially allocated inode 3, 4, 5
etc, or Bad magic number in superblock), while /usr is lightly
damaged, and /tmp and /home are generally fine.

        I have run this exact same configuration of 2.2.8 on
many other systems doing essentially the same tasks, and it
has been rock solid, using IDE or other SCSI controllers.

        However I have not yet run this setup with an Adaptec
AHA2940UW controller. Are there any outstanding issues wrt
the 2940 driver in 2.2.8 ?

        With a problem like this, I suspect an issue in the
SCSI subsystem, either hardware, in the drives, controller,
or in the SCSI driver. However, I have replaced the controller
and the drives and the problem still exists, which is why I
question the FreeBSD 2940 driver. Would it help to throttle
the SCSI bus from 20Mhz down to 10Mhz ? Other 2940 options
I should use ?

        It seems less likely that it is a CPU, mobo or memory
problem. I suppose it could be a PCI problem... but the
symptoms, particularly the nature of the disk corruption, is
very consistent, over about ten crashes.

        Thanks for any help...

Dan Ts'o, 212-327-7671, FAX: 212-327-7671
The Rockefeller University, 1230 York Ave.  Box 138
New York, NY  10021


1. FreeBSD 5.0-p6 recently started crashing regularly (panic: kmem_malloc(4096): kmem_map too small:)


I've been running a box 5.0-RELEASE system since january and have updated
the patches to -p6.  I just recently started having problems with the system

It started this past saturday...

The server has crashed at the following times:

Nothing seemed to be capturing anything in the logs, so on June 11th, I
stayed up and watched the server carefully... and sure enough it crashed at
3:06 am... I managed to catch this on the console before the system went

panic: kmem_malloc(4096): kmem_map too small: 275378176 total allocated
cpuid = 3; = 07000000
boot() called on cpu#3
syncing disks, buffers remaining... panic: bwrite: buffer is not busy???
cpuid = 3; = 07000000
boot() called on cpu#3
Uptime: 23h41m49s
Terminate ACPI
Automatic reboot in 15 seconds - press a key on the console to abort
cpu_reset called on cpu#3
cpu_reset: Stopping other CPUs
cpu_reset: Restarting BSP
cpu_reset_proxy: Stopped CPU 3

I haven't seen the above before... and don't have the slightest idea why it
just started... the system at the time was running "periodic daily" and
processing some mail in the queue (sendmail).  It was also serving a couple
http requests that were accessing the mysql database which is local and a
mysql slave server was slaving that data.... this setup has been running
since january and the tasks running at the time of the latest crash are
normal for this time of night.

Here are the hardware specs:
dual 2.2Ghz Xeon w/ 4Gigs of RAM

Let me know if I can provide any further data to help resolve this
problem... I suspect the system will "crash" again in 24 hours.


2. Linux from a Windows perspective

3. Kernel 2.0.30 crashes regularly and destroys file systems

4. List files older than x weeks and do something

5. corrupted tar in freebsd how do i replace it TIA [newbie to freebsd]

6. CUPS printing....................

7. Route Table - Getting Corrupted - Please Help

8. Mail reader needed for Wyse60 emulation!

9. getting system load on freebsd

10. aha2940uw: system hangs

11. Help! Corrupted EXT2 File System

12. Re : mmap corrupting system -- help!

13. Corrupted / incomplete system microcode update. Help?