ahd driver on 4.9 has problem with more than 3 drives (update)

2004-07-20 Thread Pranav
I have an update on the problem.

When I boot the machine with the -v option it boots up
completely. It does dump card state and give a few
other messages, but it boots up completely unlike
before wherei t used to just dump card state
repeatedly. I can provide you with the dmesg if
needed.

What do you think could be reason for that? is it
stable enough to run like this (with the -v option and
with those error messages) as a production server.

-Pranav






__
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
http://advision.webevents.yahoo.com/yahoo/votelifeengine/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: ahd driver on 4.9 has problem with more than 3 drives (update)

2004-07-20 Thread Pranav Desai
When I boot the machine with the -v option it boots up completely. I
can provide you with the dmesg if needed. So, what do you think could
be reason for that? is it stable enough to run as a production server.

-Pranav

On Tue, 20 Jul 2004 06:28:23 -0700 (PDT), Pranav <[EMAIL PROTECTED]> wrote:
> Hello All,
> 
>  I am trying to run FreeBSD 4.9 on a server that has
> 4x146GB ultra
> 320 SCSI drives. The motherboard is a Tyan S2720 with
> an Adaptec 7902
> Ultra 320 onboard. (Also tried it with 4x73GB drives).
> 
> The systems works fine when there are 3 drives in the
> system. As, soon
> as I plug in the 4th drive and boot the system in
> starts to 'dump card
> state' after the
> 'waiting for 15 secs for scsi devices to settle' line
> and never boots
> up completely. It just repeats dumps card state.
> 
> I then loaded FreeBSD 5.2.1-REL and even that dumps
> card state, but it
> boots up fine.
> I have included the dmesg in the mail. (Sorry for
> including
> everything. I didnt know what might be important).
> 
> I havent changed anything in the kernel, its a
> standard install.
> 
> Does anyone have any clue as to why this could be
> happening on 4.9. Am
> I missing some parameter or something here.
> 
> Or, is it possible to load the 5.2.1 ahd driver on
> 4.9. If so can
> somebody give some instructions on how to do that.
> 
> I would appreciate any kind of help. Please let me
> know if you want me
> to do anything else or provide any other information.
> 
> Thanks
> -Pranav
> 
> dmesg output on 5.2.1
> 
> Copyright (c) 1992-2004 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989,
> 1991, 1992, 1993, 1994
>The Regents of the University of California.
> All rights reserved.
> FreeBSD 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004
> 
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
> Preloaded elf kernel "/boot/kernel/kernel" at
> 0xc0a35000.
> Preloaded elf module "/boot/kernel/acpi.ko" at
> 0xc0a3526c.
> ACPI APIC Table: 
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2799.22-MHz
> 686-class CPU)
>  Origin = "GenuineIntel"  Id = 0xf25  Stepping = 5
> 
> Features=0xbfebfbff
>  Hyperthreading: 2 logical CPUs
> real memory  = 4160684032 (3967 MB)
> avail memory = 4044111872 (3856 MB)
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
> cpu0 (BSP): APIC ID:  0
> cpu1 (AP): APIC ID:  1
> ioapic0  irqs 0-23 on motherboard
> ioapic1  irqs 24-47 on motherboard
> ioapic2  irqs 48-71 on motherboard
> Pentium Pro MTRR support enabled
> npx0: [FAST]
> npx0:  on motherboard
> npx0: INT 16 interface
> acpi0:  on motherboard
> pcibios: BIOS version 2.10
> Using $PIR table, 14 entries at 0xc00f2fb0
> acpi0: Power Button (fixed)
> Timecounter "ACPI-fast" frequency 3579545 Hz quality
> 1000
> acpi_timer0: <24-bit timer at 3.579545MHz> port
> 0x408-0x40b on acpi0
> acpi_cpu0:  on acpi0
> acpi_cpu1:  on acpi0
> acpi_cpu2:  on acpi0
> device_probe_and_attach: acpi_cpu2 attach returned 6
> acpi_cpu2:  on acpi0
> device_probe_and_attach: acpi_cpu2 attach returned 6
> pcib0:  port 0xcf8-0xcff on
> acpi0
> pci0:  on pcib0
> pcib1:  at device 2.0 on pci0
> pcib1: could not get PCI interrupt routing table for
> \\_SB_.PCI0.P0P2
> - AE_NOT_FOUND
> pci2:  on pcib1
> pci2:  at
> device 28.0 (no
> driver attached)
> pcib2:  at device 29.0 on pci2
> pci4:  on pcib2
> em0:  1.7.19> port
> 0xc000-0xc03f mem 0xfe98-0xfe99 irq
> 48 at device 1.0 on pci4
> em0:  Speed:N/A  Duplex:N/A
> em1:  1.7.19> port
> 0xc400-0xc43f mem 0xfe9c-0xfe9d irq
> 53 at device 1.1 on pci4
> em1:  Speed:N/A  Duplex:N/A
> ahd0:  port
> 0xc800-0xc8ff,0xd000-0xd0ff mem 0xfe9fc000-0xfe9fdfff
> irq 50 at device
> 4.0 on pci4
> aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or
> 66Mhz, 512 SCBs
> ahd1:  port
> 0xd400-0xd4ff,0xd800-0xd8ff mem 0xfe9fe000-0xfe9f
> irq 51 at device
> 4.1 on pci4
> aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI 33 or
> 66Mhz, 512 SCBs
> pci2:  at
> device 30.0 (no
> driver attached)
> pcib3:  at device 31.0 on pci2
> pci3:  on pcib3
> uhci0: 
> port
> 0xe800-0xe81f irq 16 at device 29.0 on pci0
> usb0: 
> on uhci0
> usb0: USB revision 1.0
> uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00,
> addr 1
> uhub0: 2 ports with 2 removable, self powered
> pcib4:  at device 30.0 on pci0
> pci1:  on pcib4
> pci1:  at device 2.0 (no driver
> attached)
> fxp0:  port
> 0xa400-0xa43f mem
> 0xfe4a-0xfe4b,0xfe4fe000-0xfe4fefff irq 17
> at device 3.0 on pci1
> fxp0: Ethernet address 00:e0:81:27:ce:99
> miibus0:  on fxp0
> inphy0:  on miibus0
> inphy0:  10baseT, 10baseT-FDX, 100baseTX,
> 100baseTX-FDX, auto
> isab0:  at device 31.0 on pci0
> isa0:  on isab0
> atapci0:  port
> 0xffa0-0xffaf,0-0x3,0-0x7,0-0x3,0-0x7 at device 31.1
> on pci0
> ata0: at 0x1f0 irq 14 on atapci0
> ata0: [MPSAFE]
> ata1: at 0x170 irq 15 on atapci0
> ata1: [MPSAFE]
> pci0:  at device 31.3 (no driver
> attached)
> acpi_button0:  on acpi0
> acpi