3ware 9500S problem in newly updated 4.x box.

Jason Thomson jason.thomson at mintel.com
Thu Jan 27 01:52:38 PST 2005


That worked.  Thank you.

Vinod Kashyap wrote:

> See if this fixes your problem.
> 
> Index: twa_cam.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/dev/twa/twa_cam.c,v
> retrieving revision 1.1.2.4
> diff -u -r1.1.2.4 twa_cam.c
> --- twa_cam.c	7 Jan 2005 01:00:45 -0000	1.1.2.4
> +++ twa_cam.c	26 Jan 2005 18:53:54 -0000
> @@ -424,9 +424,9 @@
>  		twa_dbg_dprint(3, sc, "XPT_PATH_INQ request");
>  
>  		path_inq->version_num = 1;
> -		path_inq->hba_inquiry = PI_WIDE_16;
> +		path_inq->hba_inquiry = 0;
>  		path_inq->target_sprt = 0;
> -		path_inq->hba_misc |= PIM_NOBUSRESET;
> +		path_inq->hba_misc = 0;
>  		path_inq->hba_eng_cnt = 0;
>  		path_inq->max_target = TWA_MAX_UNITS;
>  		path_inq->max_lun = 0;
> 
> 
> 
>>-----Original Message-----
>>From: owner-freebsd-stable at freebsd.org
>>[mailto:owner-freebsd-stable at freebsd.org]On Behalf Of Jason Thomson
>>Sent: Wednesday, January 26, 2005 7:52 AM
>>To: freebsd-stable at freebsd.org
>>Cc: Vinod Kashyap
>>Subject: 3ware 9500S problem in newly updated 4.x box.
>>
>>
>>Recently CVSupped and rebuilt a releng4 box.
>>
>>This box has a 9500S in RAID10 configuration.
>>
>>On reboot,  it failed to find da0,  so it couldn't mount root.
>>
>>If you wait a few seconds,  and then type to specify the root 
>>filesystem
>>again,  then the da0 device is found (the message is printed as you
>>type),  and on hitting return,  the machine continues booting.
>>
>>(See dmesg below).
>>
>>
>>The twa driver and firmware are up to date.
>>
>>This is a DELL 1600SC SMP.  HyperThreading is enabled (but it's not a
>>big deal to us one way or the other,  so if it's a good idea 
>>to turn it
>>off,  we could).
>>
>>If you don't type on the keyboard,  then the message doesn't 
>>appear.  I
>>haven't tried this without SMP.  It's a production box I just 
>>upgraded,
>>and can only mess around with it early in the morning.
>>
>>Before today,  it was running FreeBSD 4-STABLE from September 24th.
>>
>>Has anyone else seen this?  Does anyone have any ideas? Is there
>>anything I can try to debug this?
>>
>>
>>
>>
>>
>>
>>
>>Copyright (c) 1992-2005 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 4.11-STABLE #3: Wed Jan 26 14:03:18 GMT 2005
>>     jason at baldrick.mintel.co.uk:/usr/obj/usr/src/sys/BALDRICK
>>Timecounter "i8254"  frequency 1193182 Hz
>>CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2790.72-MHz 686-class CPU)
>>   Origin = "GenuineIntel"  Id = 0xf29  Stepping = 9
>>
>>Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SE
> 
> P,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> 
>>   Hyperthreading: 2 logical CPUs
>>real memory  = 3757965312 (3669888K bytes)
>>avail memory = 3659362304 (3573596K bytes)
>>Changing APIC ID for IO APIC #0 from 0 to 8 on chip
>>Changing APIC ID for IO APIC #1 from 0 to 9 on chip
>>Changing APIC ID for IO APIC #2 from 0 to 10 on chip
>>Programming 16 pins in IOAPIC #0
>>IOAPIC #0 intpin 2 -> irq 0
>>Programming 16 pins in IOAPIC #1
>>Programming 16 pins in IOAPIC #2
>>FreeBSD/SMP: Multiprocessor motherboard: 4 CPUs
>>  cpu0 (BSP): apic id:  0, version: 0x00050014, at 0xfee00000
>>  cpu1 (AP):  apic id:  1, version: 0x00050014, at 0xfee00000
>>  cpu2 (AP):  apic id:  6, version: 0x00050014, at 0xfee00000
>>  cpu3 (AP):  apic id:  7, version: 0x00050014, at 0xfee00000
>>  io0 (APIC): apic id:  8, version: 0x000f0011, at 0xfec00000
>>  io1 (APIC): apic id:  9, version: 0x000f0011, at 0xfec01000
>>  io2 (APIC): apic id: 10, version: 0x000f0011, at 0xfec02000
>>pnpbios: Bad PnP BIOS data checksum
>>Preloaded elf kernel "kernel" at 0xa03f0000.
>>Warning: Pentium 4 CPU: PSE disabled
>>Pentium Pro MTRR support enabled
>>md0: Malloc disk
>>Using $PIR table, 9 entries at 0xa00fc200
>>npx0: <math processor> on motherboard
>>npx0: INT 16 interface
>>pcib0: <ServerWorks host to PCI bridge(unknown chipset)> on 
>>motherboard
>>IOAPIC #1 intpin 0 -> irq 2
>>IOAPIC #1 intpin 9 -> irq 3
>>pci0: <PCI bus> on pcib0
>>em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.35> port
>>0xecc0-0xecff mem 0xfe100000-0xfe11ffff irq 2 at device 2.0 on pci0
>>em0:  Speed:N/A  Duplex:N/A
>>sis0: <NatSemi DP83815 10/100BaseTX> port 0xe800-0xe8ff mem
>>0xfe122000-0xfe122fff irq 3 at device 4.0 on pci0
>>sis0: Ethernet address: 00:02:e3:02:6e:10
>>miibus0: <MII bus> on sis0
>>ukphy0: <Generic IEEE 802.3u media interface> on miibus0
>>ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>>pci0: <ATI Mach64-GR graphics accelerator> at 14.0
>>atapci0: <ServerWorks CSB5 ATA100 controller> port
>>0x8b0-0x8bf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device
>>15.1 on pci0
>>ata0: at 0x1f0 irq 14 on atapci0
>>ata1: at 0x170 irq 15 on atapci0
>>pci0: <OHCI USB controller> at 15.2 irq 5
>>isab0: <PCI to ISA bridge (vendor=1166 device=0225)> at 
>>device 15.3 on pci0
>>isa0: <ISA bus> on isab0
>>pcib1: <ServerWorks host to PCI bridge(unknown chipset)> on 
>>motherboard
>>IOAPIC #1 intpin 4 -> irq 10
>>pci1: <PCI bus> on pcib1
>>3ware device driver for 9000 series storage controllers, version:
>>2.40.02.011
>>twa0: <3ware 9000 series Storage Controller> port 0xdc00-0xdcff mem
>>0xfc000000-0xfc7fffff,0xfcf00000-0xfcf000ff irq 10 at device 
>>6.0 on pci1
>>twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047
>>pcib2: <Host to PCI bridge> on motherboard
>>pci2: <PCI bus> on pcib2
>>pcib3: <ServerWorks host to PCI bridge(unknown chipset)> on 
>>motherboard
>>pci3: <PCI bus> on pcib3
>>pcib4: <ServerWorks host to PCI bridge(unknown chipset)> on 
>>motherboard
>>pci4: <PCI bus> on pcib4
>>orm0: <Option ROMs> at iomem
>>0xc0000-0xc7fff,0xc8000-0xc97ff,0xe3000-0xea7ff,0xec000-0xefff
>>f on isa0
>>pmtimer0 on isa0
>>fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 
>>drq 2 on isa0
>>fdc0: FIFO enabled, 8 bytes threshold
>>fd0: <1440-KB 3.5" drive> on fdc0 drive 0
>>atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
>>atkbd0: <AT Keyboard> irq 1 on atkbdc0
>>kbd0 at atkbd0
>>vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 
>>0xa0000-0xbffff on isa0
>>sc0: <System console> at flags 0x100 on isa0
>>sc0: VGA <16 virtual consoles, flags=0x300>
>>sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
>>sio0: type 16550A
>>sio1: configured irq 3 not in bitmap of probed irqs 0
>>ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
>>ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
>>ppc0: FIFO with 16/16/8 bytes threshold
>>lpt0: <Printer> on ppbus0
>>lpt0: Interrupt-driven port
>>APIC_IO: Testing 8254 interrupt delivery
>>APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0
>>intpin 2
>>APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0
>>IP packet filtering initialized, divert enabled, rule-based forwarding
>>enabled, default to deny, logging limited to 1000 
>>packets/entry by default
>>IPsec: Initialized Security Association Processing.
>>SMP: AP CPU #2 Launched!
>>SMP: AP CPU #1 Launched!
>>SMP: AP CPU #3 Launched!
>>acd0: CDROM <SAMSUNG CD-ROM SC-148A> at ata1-master PIO4
>>Mounting root from ufs:/dev/da0s1a
>>no such device 'da'
>>setrootbyname failed
>>ffs_mountroot: can't find rootvp
>>Root mount failed: 6
>>
>>Manual root filesystem specification:
>>   <fstype>:<device>  Mount <device> using filesystem <fstype>
>>                        eg. ufs:/dev/da0s1a
>>   ?                  List valid disk boot devices
>>   <empty line>       Abort manual input
>>
>>mountroot> ufs\^[[}\^[[}:/dev/da0s1a
>>Mounting root from ufs\^[[}\^[[}:/dev/da0s1a
>>ffs_mountroot: can't find rootvp
>>Root mount failed: 6
>>
>>Manual root filesystem specification:
>>   <fstype>:<device>  Mount <device> using filesystem <fstype>
>>                        eg. ufs:/dev/da0s1a
>>   ?                  List valid disk boot devices
>>   <empty line>       Abort manual input
>>
>>mountroot> da0 at twa0 bus 0 target 0 lun 0
>>da0: <3ware Logical Disk 00 1.00> Fixed Direct Access SCSI-0 device
>>da0: 100.000MB/s transfers
>>da0: 381448MB (781205504 512 byte sectors: 255H 63S/T 48627C)
>>ufs:/dev/da0s1a
>>Mounting root from ufs:/dev/da0s1a
>>ohci0: <OHCI (generic) USB controller> mem 0xfe120000-0xfe120fff irq 5
>>at device 15.2 on pci0
>>usb0: OHCI version 1.0, legacy support
>>usb0: SMM does not respond, resetting
>>usb0: <OHCI (generic) USB controller> on ohci0
>>usb0: USB revision 1.0
>>uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
>>uhub0: 2 ports with 2 removable, self powered
>>em0: Link is up 100 Mbps Full Duplex
>>
>>
>>
>>_______________________________________________
>>freebsd-stable at freebsd.org mailing list
>>http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>To unsubscribe, send any mail to 
>>"freebsd-stable-unsubscribe at freebsd.org"
>>
> 
> 
> 
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
> 
> 
> 


More information about the freebsd-stable mailing list