freebsd-current@freebsd.org

On Tue, Feb 22, 2022 at 06:23:17PM -0500, Alexander Motin wrote: > On 22.02.2022 17:46, Konstantin Belousov wrote: > > Ok, the next step is to get the CPU feature reports from P- vs. E- cores. > > Patch below should work, with verbose boot. > > Not much difference on that level: > > --- zzzp

freebsd-current@freebsd.org

On 22.02.2022 17:46, Konstantin Belousov wrote: Ok, the next step is to get the CPU feature reports from P- vs. E- cores. Patch below should work, with verbose boot. Not much difference on that level: --- zzzp2022-02-22 18:18:24.531704000 -0500 +++ zzze2022-02-22 18:18:18.63123

freebsd-current@freebsd.org

On Sat, Feb 19, 2022 at 07:26:24PM -0500, Alexander Motin wrote: > On 19.02.2022 13:23, Konstantin Belousov wrote: > > On Sat, Feb 19, 2022 at 12:14:16PM -0500, Alexander Motin wrote: > > > On 19.02.2022 12:02, Mike Karels wrote: > > > > On 18 Feb 2022, at 20:55, Tomoaki AOKI wrote: > > > > > Just

Re: "linker_load_file ... unsupported file type" after upgrade attempts on -CURRENT

to respond to myself: I bit the bullet and installed one of the latest memstick images of -CURRENT , and am back up and running - with amdgpu and drm-current, and KDE (which had stopped working for me on the previous setup a while ago). Sorry if anyone's gone to any lengths here, though I didn't ge

Re: New panic in main-n253273-a52d8d4a6c6:

Hey Mike, Should be fixed in commit 0a2f498234023008d9a3b13ad7fc8fd81d384bab Thanks for the report -Rob On Mon, Feb 21, 2022 at 7:48 PM Rob Wing wrote: > Think that's it...thanks for testing for the patch. > >