Date: Wed, 15 Nov 2006 21:19:43 -0700 From: Scott Long <scottl@samsco.org> To: mjacob@freebsd.org Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org, John Baldwin <jhb@freebsd.org> Subject: Re: cvs commit: src/sys/dev/mpt mpt_pci.c Message-ID: <455BE6DF.4090907@samsco.org> In-Reply-To: <20061115200109.U7495@ns1.feral.com> References: <200611152018.kAFKI9A3061678@repoman.freebsd.org> <200611151617.23125.jhb@freebsd.org> <20061115134949.T1700@ns1.feral.com> <20061115192354.D7197@ns1.feral.com> <455BDC68.2080603@samsco.org> <20061115194305.M7355@ns1.feral.com> <455BDFB7.9040303@samsco.org> <20061115200109.U7495@ns1.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
mjacob@freebsd.org wrote: > > see http://people.freebsd.org/~mjacob for 2 bootverbose files. > > Ah, it looks like the MPT chips support 8 messages. I think that John's patch assumes only 1 message for it. For some devices, requesting 1 message when N are available will work, but it really is undefined behaviour and is dependent on the device to DTRT. So in your case, some of the MPT chips handled it well, some did not. Just out of curiosity, do you have any MPT docs that describe its MSI capabilities? In any case, it should probably be disabled in the MPT driver until we have a better understanding of how it works there. For your if_em problem, I'm not seeing what the problem is. It looks like em0 was successful at getting an IP address over DHCP, so I would assume that interrupts are working on it. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?455BE6DF.4090907>