Since last week (today) current on my Ryzen box is unstable

[Andrew Reilly]

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 at 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

The output above suggests that there isn't a driver attached to that device anyway, though.

Cheers,

Andrew Reilly



> On 18 Feb 2018, at 00:06 , Hans Petter Selasky <hps at selasky.org> wrote:
> 
> On 02/17/18 13:42, Hans Petter Selasky wrote:
>> On 02/17/18 13:16, Andrew Reilly wrote:
>>> On a side-note, the new devmatch workings are giving me 43 boot warnings about "Malformed NOMATCH string: ''?'', and devmatch_enable="NO" in /etc/rc.conf doesn't seem to help, and the new matching is very very keen to load cc_vegas.ko, a lot.  Here's the output of devmatch -v, in case that helps:
>> Hi,
>> Does the attached patch solve the devmatch issue? Just apply it directly on /etc and reboot.
>> --HPS
> 
> Please find updated patch attached.
> 
> --HPS
> 
> <devmatch.diff>