Date: Mon, 15 Apr 1996 20:04:26 -0700 From: asami@cs.berkeley.edu (Satoshi Asami) To: gibbs@freefall.freebsd.org Cc: scsi@freebsd.org Subject: Re: Changing ID of 2940UW Message-ID: <199604160304.UAA21623@forgery.CS.Berkeley.EDU> In-Reply-To: <199604152146.OAA07136@sunrise.cs.berkeley.edu> (asami@cs.berkeley.edu)
next in thread | previous in thread | raw e-mail | index | archive | help
* A couple of weeks ago. I'll upgrade it to the current -current and * let you know if it works. Well, it doesn't work very well, -current just supped from sup2. :( === sd13(ahc1:5:0): parity error during Message-In phase. 0MB (1 512 byte sectors) (ahc1:6:0): parity error during Message-In phase. (ahc1:6:0): parity error during Message-In phase. (ahc1:6:0): "unknown unknown ????" type 0 fixed SCSI 0 sd14(ahc1:6:0): Direct-Access sd14(ahc1:6:0): parity error during Message-In phase. sd14(ahc1:6:0): parity error during Message-In phase. 0MB (1 512 byte sectors) (ahc1:8:0): parity error during Message-In phase. (ahc1:8:0): parity error during Message-In phase. (ahc1:8:0): "unknown unknown ????" type 0 fixed SCSI 0 sd15(ahc1:8:0): Direct-Access sd15(ahc1:8:0): parity error during Message-In phase. sd15(ahc1:8:0): parity error during Message-In phase. 0MB (1 512 byte sectors) (ahc1:9:0): parity error during Message-In phase. (ahc1:9:0): parity error during Message-In phase. (ahc1:9:0): "unknown unknown ????" type 0 fixed SCSI 0 sd16(ahc1:9:0): Direct-Access sd16(ahc1:9:0): parity error during Message-In phase. sd16(ahc1:9:0): parity error during Message-In phase. 0MB (1 512 byte sectors) (ahc1:10:0): parity error during Message-In phase. (ahc1:10:0): parity error during Message-In phase. (ahc1:10:0): "unknown unknown ????" type 0 fixed SCSI 0 sd17(ahc1:10:0): Direct-Access sd17(ahc1:10:0): parity error during Message-In phase. sd17(ahc1:10:0): parity error during Message-In phase. 0MB (1 512 byte sectors) (ahc1:11:0): parity error during Message-In phase. (ahc1:11:0): parity error during Message-In phase. (ahc1:11:0): "unknown unknown ????" type 0 fixed SCSI 0 sd18(ahc1:11:0): Direct-Access sd18(ahc1:11:0): parity error during Message-In phase. sd18(ahc1:11:0): parity error during Message-In phase. 0MB (1 512 byte sectors) (ahc1:12:0): parity error during Message-In phase. (ahc1:12:0): parity error during Message-In phase. (ahc1:12:0): "unknown unknown ????" type 0 fixed SCSI 0 sd19(ahc1:12:0): Direct-Access sd19(ahc1:12:0): parity error during Message-In phase. sd19(ahc1:12:0): parity error during Message-In phase. 0MB (1 512 byte sectors) (ahc1:13:0): parity error during Message-In phase. (ahc1:13:0): parity error during Message-In phase. (ahc1:13:0): "unknown unknown ????" type 0 fixed SCSI 0 sd20(ahc1:13:0): Direct-Access sd20(ahc1:13:0): parity error during Message-In phase. sd20(ahc1:13:0): parity error during Message-In phase. 0MB (1 512 byte sectors) (ahc1:14:0): parity error during Message-In phase. (ahc1:14:0): parity error during Message-In phase. (ahc1:14:0): "unknown unknown ????" type 0 fixed SCSI 0 sd21(ahc1:14:0): Direct-Access sd21(ahc1:14:0): parity error during Message-In phase. sd21(ahc1:14:0): parity error during Message-In phase. 0MB (1 512 byte sectors) (ahc1:15:0): parity error during Message-In phase. (ahc1:15:0): parity error during Message-In phase. (ahc1:15:0): "unknown unknown ????" type 0 fixed SCSI 0 sd22(ahc1:15:0): Direct-Access sd22(ahc1:15:0): parity error during Message-In phase. sd22(ahc1:15:0): parity error during Message-In phase. 0MB (1 512 byte sectors) === The messages scrolled past too quickly to see what's going on, the configuration is as follows: ahc0: ID7, with 8 disks (ID 8-15) ahc1: ID15, with 8 disks (ID 0-7) Here's the lsdev output: === # This listing automatically generated by lsdev(1) 1: # CPU cpu0 2: controller scbus0 3: chip0 at pci0:0 4: chip1 at pci1792:0 5: piix0 at pci1792:1 6: ahc0 at pci3584:0 # int a irq 10 7: sd0 at SCSI bus 0:8:0 (ready) (open) 8: sd1 at SCSI bus 0:9:0 (ready) (open) 9: sd2 at SCSI bus 0:10:0 (ready) 10: sd3 at SCSI bus 0:11:0 (ready) 11: sd4 at SCSI bus 0:12:0 (ready) 12: sd5 at SCSI bus 0:13:0 (ready) 13: sd6 at SCSI bus 0:14:0 (ready) 14: sd7 at SCSI bus 0:15:0 (ready) 15: ahc1 at pci3840:0 # int a irq 11 16: sd8 at SCSI bus 1:0:0 (ready) (open) 17: sd9 at SCSI bus 1:1:0 (ready) 18: sd10 at SCSI bus 1:2:0 (ready) 19: sd11 at SCSI bus 1:3:0 (ready) 20: sd12 at SCSI bus 1:4:0 (ready) 21: sd13 at SCSI bus 1:5:0 (ready) 22: sd14 at SCSI bus 1:6:0 (ready) 23: sd15 at SCSI bus 1:8:0 (ready) 24: sd16 at SCSI bus 1:9:0 (ready) 25: sd17 at SCSI bus 1:10:0 (ready) 26: sd18 at SCSI bus 1:11:0 (ready) 27: sd19 at SCSI bus 1:12:0 (ready) 28: sd20 at SCSI bus 1:13:0 (ready) 29: sd21 at SCSI bus 1:14:0 (ready) 30: sd22 at SCSI bus 1:15:0 (ready) 31: de0 at pci4096:0 # int a irq 11 32: controller isa0 33: sc0 at isa? tty (id 5) port 0x60 irq 1 34: sio0 at isa? tty (id 6) port 0x3f8 irq 4 35: sio1 at isa? tty (id 7) port 0x2f8 irq 3 36: sio2 at isa? tty (id 8) port 0x3e8 irq 5 37: sio3 at isa? tty (id 9) port 0x2e8 irq 9 38: lpt0 at isa? tty (id 10) port 0x378 irq 7 39: lpt1 at isa? tty (id 11) port ? 40: lpt2 at isa? tty (id 12) port ? 41: fdc0 at isa? bio (id 2) port 0x3f0 irq 6 drq 2 42: fd0 at fdc0 drive 0 43: wdc0 at isa? (id 3) port 0x1f0 irq 14 44: wd0 at wdc0 drive 0 45: wdc1 at isa? (id 4) port 0x170 irq 15 46: npx0 at isa? (id 13) port 0xf0 === Note that sd15 to sd22 are totally bogus, we only have 16 disks! ;) All disks are found fine if I set the adapter's ID to 7 (well I need to pull out one of the disks but that's it). Since the "real" sd15 is not found (i.e., missing ID7 on scbus1) I suspect something in the ahc code still assumes the ID is 7. Satoshi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604160304.UAA21623>