Date: Sat, 17 Feb 2018 16:04:36 -0800 From: Conrad Meyer <cem@freebsd.org> To: Andrew Reilly <areilly@bigpond.net.au> Cc: current <current@freebsd.org> Subject: Re: Since last week (today) current on my Ryzen box is unstable Message-ID: <CAG6CVpUNCq2kG1j7joPpVhQxsX0B144kF7GQddRS5aP8WLU4Ug@mail.gmail.com> In-Reply-To: <CE34800E-346F-4221-BAA7-E250446DC9F3@bigpond.net.au> References: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> <e320afc1-a9fa-10ae-7d50-f6a756aea599@selasky.org> <e3ea22cd-ba73-a9d3-e1f1-fe530bf55e30@selasky.org> <CE34800E-346F-4221-BAA7-E250446DC9F3@bigpond.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 17, 2018 at 12:52 PM, Andrew Reilly <areilly@bigpond.net.au> wrote: > I've applied the patch, and the boot process is quiet now, but it's still loading cc_vegas.ko, seemingly in response to seeing this device: (from pciconf -l -v) > > none4@pci0:17:0:2: class=0x108000 card=0x14561022 chip=0x14561022 rev=0x00 hdr=0x00 > vendor = 'Advanced Micro Devices, Inc. [AMD]' > device = 'Family 17h (Models 00h-0fh) Platform Security Processor' > class = encrypt/decrypt > > (from devmatch -v) > Searching pci bus at slot=0 function=2 dbsf=pci0:17:0:2 handle=\_SB_.PCI0.GP17.APSP for pnpinfo vendor=0x1022 device=0x1456 subvendor=0x1022 subdevice=0x1456 class=0x108000 > cc_vegas.ko That's kind of interesting. That device should match ccp.ko, not cc_vegas.ko. As far as I can tell, cc_vegas has no PNP data at all. Maybe this is a bug in kldxref or devmatch. Best, Conrad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpUNCq2kG1j7joPpVhQxsX0B144kF7GQddRS5aP8WLU4Ug>