Date: Mon, 23 Mar 2009 11:58:27 -0400 From: John Baldwin <jhb@freebsd.org> To: Mars G Miro <spry@anarchy.in.the.ph> Cc: pyunyh@gmail.com, freebsd-current@freebsd.org Subject: Re: sk/msk no more Message-ID: <200903231158.28121.jhb@freebsd.org> In-Reply-To: <f12f408a0903202008h7fa41c56o8b8f804c03d063f8@mail.gmail.com> References: <f12f408a0903151922p22475836s1d840e8e2cf203a2@mail.gmail.com> <200903201242.09167.jhb@freebsd.org> <f12f408a0903202008h7fa41c56o8b8f804c03d063f8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 20 March 2009 11:08:35 pm Mars G Miro wrote: > On Sat, Mar 21, 2009 at 12:42 AM, John Baldwin <jhb@freebsd.org> wrote: > > On Thursday 19 March 2009 11:24:24 pm Mars G Miro wrote: > >> On Thu, Mar 19, 2009 at 11:26 PM, John Baldwin <jhb@freebsd.org> wrote: > >> > On Monday 16 March 2009 12:10:21 am Mars G Miro wrote: > >> >> On Mon, Mar 16, 2009 at 11:31 AM, Pyun YongHyeon <pyunyh@gmail.com> > > wrote: > >> >> > On Mon, Mar 16, 2009 at 10:22:40AM +0800, Mars G Miro wrote: > >> >> >> Hi guys, > >> >> >> > >> >> >> =A0 =A0I upgraded a box w/ sk and msk NICs running 7.1-RELEASE t= o=20 latest > >> >> >> -CURRENT =A0to try out the new USB2 stuff but my sk/msk NICs don= 't=20 work > >> >> >> anymore: > >> >> >> > >> >> >> =A0 =A0http://pastebin.com/m28a41b14 > >> >> >> > >> >> >> =A0 =A0Saw this first last Friday, March 13, and re-csup'd a few= hours=20 ago > >> >> >> and the problem is still there. > >> >> >> > >> >> >> =A0 =A0Any thoughts? Thanks. > >> >> >> > >> >> > > >> >> > I don't see sk(4)/msk(4) hardwares in your dmesg output. > >> >> > Does "pciconf -lcv" show your controller? > >> >> > >> >> That's the problem, the hardware disappears: > >> > > >> > What if you set 'hw.pci.mcfg=3D0' in loader? > >> > > >> > >> That did it! Even w/ ACPI enabled in the BIOS, the sk/msk NICs don't > >> get lost anymore. > >> > >> pciconf and verbose dmesg: http://pastebin.com/f31621191 > >> > >> btw, what does this knob actually do ? > > > > mcfg is a mechanism for doing faster PCI config access using a memory=20 mapped > > window. =A0Can you grab the output of 'acpidump -t'? > > >=20 > /* > MCFG: Length=3D60, Revision=3D1, Checksum=3D46, > OEMID=3DIntelR, OEM Table ID=3DAWRDACPI, OEM Revision=3D0x42302e3= 1, > Creator ID=3DAWRD, Creator Revision=3D0x0 >=20 > Base Address=3D 0x00000000e0000000 > Segment Group=3D 0x0000 > Start Bus=3D 0 > End Bus=3D 0 > */ Hmm, your BIOS is rather buggy and claims to only support MCFG for bus 0. = I=20 will work on a fix. I think I will make the code fall back to the old conf= ig=20 mechanism when an MCFG region doesn't include the requested bus. =2D-=20 John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903231158.28121.jhb>