Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Feb 2018 13:49:17 -0500
From:      Mike Tancsa <mike@sentex.net>
To:        Ed Maste <emaste@freebsd.org>
Cc:        Nimrod Levy <nimrodl@gmail.com>, Don Lewis <truckman@freebsd.org>, freebsd-stable stable <freebsd-stable@freebsd.org>, Andriy Gapon <avg@freebsd.org>, Peter Moody <freebsd@hda3.com>, Pete French <petefrench@ingresso.co.uk>
Subject:   Re: Ryzen issues on FreeBSD ? (with sort of workaround)
Message-ID:  <38a14576-2dbd-a1ba-791c-197351d091c0@sentex.net>
In-Reply-To: <CAPyFy2C33S8-=HR2Vv-hSVU5ewknskH7G0MxQ%2Bmvq_FNMfJgqA@mail.gmail.com>
References:  <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <CAMgUhpop54hJ%2Biq_VYYqrEHgSapmMu_GmOPaOsmhA=QbjPEZ5A@mail.gmail.com> <CADbMJxk=HDoMsPghDrkTNqsC_XZo28nYPNGC%2BD9fddENPiiFng@mail.gmail.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <tkrat.8fa97919286143d7@FreeBSD.org> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <CADbMJxkRR8s1=WWXP%2BH9eOHv_UWMQrUR=_E4aFw91VCeep82pw@mail.gmail.com> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <tkrat.975666e9f483a6a0@FreeBSD.org> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> <tkrat.ada77e0420783bed@FreeBSD.org> <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net> <tkrat.e541d1b83f4f6c75@FreeBSD.org> <5e48bbc2-e872-46bd-eece-25acbb180f77@sentex.net> <c0319297-d47d-449d-a6f1-2529d1d38541@sentex.net> <CAMgUhppdkcqYTpZEZJ1ScTevPOEK6WRXpg_WP-L-R6rKNhpYAA@mail.gmail.com> <ed1dd16e-0121-a578-23f0-1b3503d6475d@sentex.net> <CAPyFy2C33S8-=HR2Vv-hSVU5ewknskH7G0MxQ%2Bmvq_FNMfJgqA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2/1/2018 1:40 PM, Ed Maste wrote:
>> root@amdtestr12:/home/mdtancsa # procstat -kk 6067
>>   PID    TID COMM                TDNAME              KSTACK
>>
>>  6067 100865 python2.7           -                   ??+0 ??+0 ??+0 ??+0
>> ??+0 ??+0 ??+0 ??+0 ??+0 ??+0
> 
> I think this part is due to the broken loader change in r328536.
> Kernel symbol loading is broken, and this in particular isn't related
> to Ryzen issues.

Just for the archives, after a buildworld to a newer rev of the source
tree, all was good :)

	---Mike


-- 
-------------------
Mike Tancsa, tel +1 519 651 3400 x203
Sentex Communications, mike@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38a14576-2dbd-a1ba-791c-197351d091c0>