Date: Mon, 11 Sep 1995 21:12:37 -0700 From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org> To: Joe Greco <jgreco@brasil.moneng.mei.com> Cc: gibbs@freefall.freebsd.org (Justin T. Gibbs), hackers@freebsd.org Subject: Re: Help! :-( (fwd) Message-ID: <199509120412.VAA03607@aslan.cdrom.com> In-Reply-To: Your message of "Mon, 11 Sep 1995 21:49:46 CDT." <199509120249.VAA18581@brasil.moneng.mei.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>This is looking like it may well be a configuration problem, but I don't >really have a clue. I did some minimal debugging and tracing but it's not >clear to me how it's all supposed to work together. It is a configuration problem. You have the de1 device not getting properly attached and on the same IRQ as one of your 3940s, so I think it is getting really confused. The errors you show bellow look like stray ints. Stephan, what does the PCI code do, if anything, to handle stray ints like this with shared interrupts? >It appears that getintdescbytag is getting called with the same values for >ahc0/ahc2 and ahc1/ahc3. I couldn't really make a lot of sense quickly out >of what was causing that, however, and I believe it is only a symptom of >something else that hasn't happened for that second controller. This is also interresting. I would have expected all devices behind the Dec bridge chip to be sequentially before other PCI devices. It looks like ahc0 is Channel A on controller 1, ahc2 is Channel B on controller 1, etc. Is this in fact your setup? >chip0 <CPU-PCI bridge> rev 1 on pci0:0 >chip1 <PCI-ISA bridge> rev 2 on pci0:7 >de0 <Digital DC21040 Ethernet> rev 35 int a irq 10 on pci0:9 > reg20: virtual=0xf6639000 physical=0xfbdff000 size=0x80 >de0: DC21040 [10Mb/s] pass 2.3 Ethernet address 00:80:48:e8:1f:ec >de0: enabling Thinwire/AUI port >bpf: de0 attached >PCI.C: getintdescbytag(10, -2147465216) not found, this is ok! >de1 <Digital DC21040 Ethernet> rev 35 int a irq 11 on pci0:10 >de1: not configured; kernel is built for only 1 device. Stray int source. >chip2 <DEC 21050 PCI-PCI bridge> rev 2 on pci0:11 > bridge from pci0 to pci1 through 1. > mapping regs: io:2280d0d0 mem:fbc0fbc0 pmem:fbf0fbf0chip3 <DEC 21050 PC There should be two of these... one for each 3940. Hmmmm. >I-PCI bridge> rev 2 on pci0:12 > bridge from pci0 to pci1 through 1. > mapping regs: io:3280c0c0 mem:fbb0fbb0 pmem:fbe0fbe0pci0: uses 256 byte >s of memory from fbb00000 upto fbffffff. >pci0: uses 256 bytes of I/O space from c000 upto e47f. >pci0: subordinate busses from 1 upto 1. >Probing for devices on the pci1 bus: >ahc0 <Adaptec 3940 SCSI host adapter> rev 0 int a irq 15 on pci1:4 > [pci1 uses memory from fbc00000 to fbcfffff] >ahc0: reading board settings >ahc0: Reading SEEPROM...done. >ahc0: 3940 Single Channel, SCSI Id=7, aic7870, 16 SCBs >ahc0: Downloading Sequencer Program...Done >... Joe Can you try this with -current's driver files? There are quite a few things cleaned up with respect to the 3940. You'll need i386/scsi/*, i386/isa/aic7770.c, and pci/aic7870.c. >------------------------------------------------------------------------------ >- >Joe Greco - Systems Administrator jgreco@ns.sol.net >Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509120412.VAA03607>