Date: Tue, 27 Dec 2005 15:41:20 -0800 From: Nate Lawson <nate@root.org> To: Scott Long <scottl@samsco.org> Cc: cvs-src@FreeBSD.org, Gleb Smirnoff <glebius@FreeBSD.org>, cvs-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/em if_em.c Message-ID: <43B1D120.9080604@root.org> In-Reply-To: <43B1D121.1080309@samsco.org> References: <20051222090955.E621416A4D5@hub.freebsd.org> <43B1CE9E.1060602@root.org> <43B1D121.1080309@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote: > Nate Lawson wrote: >> This probably means that the PCI memory space isn't fully initialized >> but an interrupt has been triggered. If you then go and try to poke >> the hardware, then you can hang the system. >> > > I can believe your first statement, but not your second. Hanging the > system on an aborted memory read cycle (as opposed to just throwing a > #SERR) would indicate a highly highly broken chipset. In any case, if > we ever implement PCI hotplug then we'll have to deal with the effects > of aborted PCI transfers anyways. > > Scott It's not the PCI write that hangs the system, it's the behavior of the device written to. It may never release the interrupt. Using an NMI to debug would be good. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43B1D120.9080604>