Date: Sun, 27 Oct 1996 07:26:45 -0500 (EST) From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: AHA2940UW differences with 2.1.5-STABLE. Message-ID: <199610271226.HAA00233@lakes.water.net>
next in thread | raw e-mail | index | archive | help
I've just installed 2.1.5-STABLE (by grabbing the sys directory from freefall.cdrom.com and rebuilding a kernel) on a machine with an AHA 2940UW. I noticed a lit of changes to the aic7xxx code since 2.1.5R. I've also noticed a difference in how the two operate. I don't know if this is good, or bad, just different. 2.1.5R reports my SCSI devices as (from an older /var/log/messages, this is going to be "wide" - so expand your window :-) ): Oct 20 21:33:40 lakes /kernel: FreeBSD 2.1.5-RELEASE #3: Sat Sep 28 20:32:19 EDT 1996 Oct 20 21:33:40 lakes /kernel: rivers@lakes.water.net:/usr/src/sys/compile/LAKES Oct 20 21:33:40 lakes /kernel: CPU: 133-MHz Pentium 735\90 or 815\100 (Pentium-class CPU) Oct 20 21:33:40 lakes /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Oct 20 21:33:40 lakes /kernel: Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8> Oct 20 21:33:40 lakes /kernel: real memory = 33554432 (32768K bytes) Oct 20 21:33:40 lakes /kernel: avail memory = 30617600 (29900K bytes) Oct 20 21:33:40 lakes /kernel: Probing for devices on PCI bus 0: Oct 20 21:33:40 lakes /kernel: chip0 <generic PCI bridge (vendor=8086 device=7030 subclass=0)> rev 1 on pci0: 0 Oct 20 21:33:40 lakes /kernel: chip1 <Intel 82371 PCI-ISA bridge> rev 1 on pci0:7:0 Oct 20 21:33:41 lakes /kernel: chip2 <Intel 82371 Bus-Master IDE controller> rev 0 on pci0:7:1 Oct 20 21:33:41 lakes /kernel: ahc0 <Adaptec 2940 Ultra SCSI host adapter> rev 0 int a irq 15 on pci0:17 Oct 20 21:33:41 lakes /kernel: ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs Oct 20 21:33:41 lakes /kernel: ahc0 waiting for scsi devices to settle Oct 20 21:33:41 lakes /kernel: (ahc0:0:0): "HP C3323-300 4242" type 0 fixed SCSI 2 Oct 20 21:33:41 lakes /kernel: sd0(ahc0:0:0): Direct-Access 1003MB (2056008 512 byte sectors) Oct 20 21:33:41 lakes /kernel: (ahc0:1:0): "MICROP 1548-15MZ1077802 HZ2P" type 0 fixed SCSI 1 Oct 20 21:33:41 lakes /kernel: sd1(ahc0:1:0): Direct-Access 1635MB (3349512 512 byte sectors) Oct 20 21:33:41 lakes /kernel: ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers Oct 20 21:33:42 lakes /kernel: ahc0:A:2: refuses syncronous negotiation. Using asyncronous transfers Oct 20 21:33:42 lakes /kernel: (ahc0:2:0): "WANGTEK 5150ES SCSI FA23 08" type 1 removable SCSI 1 Oct 20 21:33:42 lakes /kernel: st0(ahc0:2:0): Sequential-Access drive offline Oct 20 21:33:42 lakes /kernel: (ahc0:3:0): "NEC CD-ROM DRIVE:400 1.0" type 5 removable SCSI 2 Oct 20 21:33:42 lakes /kernel: cd0(ahc0:3:0): CD-ROM cd present.[268501 x 2048 byte records] You'll notice that the "MICROP 1548-15MZ1077802 HZ2P" successfully negotiates WIDE data paths. However, with 2.1.5-STABLE, I get: Oct 26 07:03:14 lakes /kernel: ahc0 waiting for scsi devices to settle Oct 26 07:03:14 lakes /kernel: (ahc0:0:0): "HP C3323-300 4242" type 0 fixed SCSI 2 Oct 26 07:03:14 lakes /kernel: sd0(ahc0:0:0): Direct-Access 1003MB (2056008 512 byte sectors) Oct 26 07:03:14 lakes /kernel: ahc0:A:1: refuses WIDE negotiation. Using 8bit transfers Oct 26 07:03:15 lakes /kernel: (ahc0:1:0): "MICROP 1548-15MZ1077802 HZ2P" type 0 fixed SCSI 1 Oct 26 07:03:15 lakes /kernel: sd1(ahc0:1:0): Direct-Access 1635MB (3349512 512 byte sectors) Oct 26 07:03:15 lakes /kernel: ahc0:A:2: refuses WIDE negotiation. Using 8bit transfers Oct 26 07:03:15 lakes /kernel: ahc0:A:2: refuses syncronous negotiation. Using asyncronous transfers Oct 26 07:03:15 lakes /kernel: (ahc0:2:0): "WANGTEK 5150ES SCSI FA23 08" type 1 removable SCSI 1 Oct 26 07:03:15 lakes /kernel: st0(ahc0:2:0): Sequential-Access drive offline Oct 26 07:03:15 lakes /kernel: (ahc0:3:0): "NEC CD-ROM DRIVE:400 1.0" type 5 removable SCSI 2 Oct 26 07:03:16 lakes /kernel: cd0(ahc0:3:0): CD-ROM cd present.[320520 x 2048 byte records] You'll notice here that the "MICROP 1548-15MZ1077802 HZ2P" does not negotiate WIDE data paths. This is correct, as this is an ancient SCSI I drive (from about 1989.) My question is - is this part of the improvements in 2.1.5-STABLE? Understand that I believe the 2.1.5-STABLE behaviour is correct - just wondering if it's expected.... - Dave Rivers -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610271226.HAA00233>