Date: Fri, 10 Jun 2011 18:17:53 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, John <jwd@slowblink.com> Subject: Re: NEW_PCIB? pcib1: failed to allocate initial I/O port window: 0x4000-0x4fff Message-ID: <4DF235A1.3000308@FreeBSD.org> In-Reply-To: <201106090857.33479.jhb@freebsd.org> References: <20110606002353.GA2518@slowblink.com> <20110608223037.GA83941@FreeBSD.org> <4DF06404.8090909@FreeBSD.org> <201106090857.33479.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 09/06/2011 15:57 John Baldwin said the following: > On Thursday, June 09, 2011 2:11:16 am Andriy Gapon wrote: >> on 09/06/2011 01:30 John said the following: >>> Sorry John, here's the verbose dmesg output with your patch applied. >>> >>> This is at the tail of the console: >>> >>> pcib1: allocated memory range (0xf6000000-0xf6ffffff) for rid 10 of pci0:1:3:0 >>> map[14]: type I/O Port, range 32, base 0x4400, size 8, enabled >>> pcib1: failed to allocate initial I/O port window (0x4000-0x4fff,0x1000) >>> map[18]: type Memory, range 32, base 0xf5ff0000, size 12, enabled >>> >>> >>> Output ends with a single 'M', not MCA as earlier. >> >> >> Just a wild guess - what happens if you revert r222537 (you might need to revert >> r222804 first)? > > I think he's getting a MCA due to writing to a bad address and getting a > PCI-e target abort equivalent and that the screen output is broken > because the VGA device is what is probably getting hosed by the pcib driver. > > Given that, I doubt the printf changes are related. Right. I was mostly curious if printf has become broken with respect to things like reporting MCEs. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DF235A1.3000308>