Date: Fri, 15 Jan 2021 16:46:11 +0000 (UTC) From: Filippo Moretti <filippomore@yahoo.com> To: Hans Petter Selasky <hps@selasky.org>, FreeBSD Current <current@freebsd.org> Subject: Re: Problem with drm Message-ID: <1458920202.313097.1610729171060@mail.yahoo.com> In-Reply-To: <4dcb7a9a-2c72-fc0a-fd5b-9386cb489185@selasky.org> References: <1030157071.192741.1610701909753.ref@mail.yahoo.com> <1030157071.192741.1610701909753@mail.yahoo.com> <4dcb7a9a-2c72-fc0a-fd5b-9386cb489185@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes the port is up to date and I did rebuild from ports drm-current-kmod gpu-firmware-kmod and drm-kmodFilippo
On Friday, January 15, 2021, 10:29:38 AM GMT+1, Hans Petter Selasky <hps@selasky.org> wrote:
On 1/15/21 10:11 AM, Filippo Moretti wrote:
> After upgrading my custom kernel I get the following error (that did not occur before hid):hidbus0: <HID bus> on usbhid0
> link_elf_obj: symbol linux_pci_get_class undefined
> Warning: memory type debugfsint leaked memory on destroy (2 allocations, 80 bytes leaked).
> linker_load_file: /boot/modules/radeonkms.ko - unsupported file type
>
> Also the generic kernel was working fine before I upgraded my kernel STING now it no longer works and Xorg start with scfb instead of radeon kms.After completing installworld I always rebuild from ports drm-current-kmod gpu-firmware-kmod drm-kmod.SincerelyFilippo
Is your ports updated to the latest?
Looks like radeonkms was not re-build after upgrading and installing the
sources.
--HPS
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
From owner-freebsd-current@freebsd.org Fri Jan 15 16:46:57 2021
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
by mailman.nyi.freebsd.org (Postfix) with ESMTP id 313484EB6F6
for <freebsd-current@mailman.nyi.freebsd.org>;
Fri, 15 Jan 2021 16:46:57 +0000 (UTC)
(envelope-from mikael@FreeBSD.org)
Received: from smtp.freebsd.org (smtp.freebsd.org
[IPv6:2610:1c1:1:606c::24b:4])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
client-signature RSA-PSS (4096 bits) client-digest SHA256)
(Client CN "smtp.freebsd.org", Issuer "R3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4DHRss0FmHz3FQY;
Fri, 15 Jan 2021 16:46:57 +0000 (UTC)
(envelope-from mikael@FreeBSD.org)
Received: from [192.168.1.2] (112.56.88.79.rev.sfr.net [79.88.56.112])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client did not present a certificate) (Authenticated sender: mikael)
by smtp.freebsd.org (Postfix) with ESMTPSA id A5E01200BA;
Fri, 15 Jan 2021 16:46:56 +0000 (UTC)
(envelope-from mikael@FreeBSD.org)
Subject: Re: Waiting for bufdaemon
To: Konstantin Belousov <kostikbel@gmail.com>
Cc: freebsd-current <freebsd-current@freebsd.org>
References: <7c4da243-52ff-c5ee-3d56-1ae651286e0e@alvermark.net>
<369b3d82-98c5-b31e-6168-4003a042f174@FreeBSD.org>
<YAGua8f8G57SbUMT@kib.kiev.ua>
<556d40b8-92d7-303e-7d87-ea496d0ca733@FreeBSD.org>
<YAG4g7dJbRWM7act@kib.kiev.ua>
<51df64cc-f01c-0030-a708-f4002be6411e@FreeBSD.org>
<YAHET2xB+nnc7IgZ@kib.kiev.ua>
From: =?UTF-8?Q?Mika=c3=abl_Urankar?= <mikael@FreeBSD.org>
Message-ID: <5bf89915-122d-b321-d85c-771bde02aed7@FreeBSD.org>
Date: Fri, 15 Jan 2021 17:46:55 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101
Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <YAHET2xB+nnc7IgZ@kib.kiev.ua>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>;
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2021 16:46:57 -0000
On 15/01/2021 17:35, Konstantin Belousov wrote:
> On Fri, Jan 15, 2021 at 05:18:56PM +0100, Mikaël Urankar wrote:
>> On 15/01/2021 16:45, Konstantin Belousov wrote:
>>> On Fri, Jan 15, 2021 at 04:30:19PM +0100, Mikaël Urankar wrote:
>>>> On 15/01/2021 16:02, Konstantin Belousov wrote:
>>>>> On Fri, Jan 15, 2021 at 03:56:01PM +0100, Mikaël Urankar wrote:
>>>>>> On 15/01/2021 11:26, Jakob Alvermark wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>> When rebooting my thinkpad the 'bufdaemon' times out:
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... timed
>>>>>>> out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-0' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-1' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-2' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-3' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-4' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>> Waiting (max 60 seconds) for system thread 'bufspacedaemon-5' to stop
>>>>>>> ... timed out
>>>>>>>
>>>>>>>
>>>>>>> This started happening recently (within the last week I think).
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I'm also affected. I have an AMD Ryzen 9 3900X cpu, running bare metal.
>>>>>>
>>>>>> 5844bd058aed6f3d0c8cbbddd6aa95993ece0189 (jobc: rework detection of orphaned
>>>>>> groups) "seems" ok
>>>>>>
>>>>>> cd240c9cf100bec3def38ceb4a320611b1d02693 (x86 vdso gettc: Add RDTSCP
>>>>>> support), affected by the timeout.
>>>>>>
>>>>>> I haven't tried the intermediate commit yet.
>>>>>>
>>>>>> My intel machine doesn't seem to be affected
>>>>>
>>>>> If you revert only 9e680e4005b7, is it fixed ?
>>>>>
>>>> Yes it seems to be fixed with 9e680e4005b7 reverted (I've only done 2 tests,
>>>> I can do more if you want)
>>> Please show me the output from sysctl
>>> kern.timecounter
>>> kern.eventtimer
>>> and first 100 lines of dmesg from the verbose boot (that contains the CPU
>>> ident lines).
>>>
>>
>> I put the /var/run/dmesg.boot file on freefall /home/mikael/dmesg.boot (it
>> seems to be truncated though, I don't know how to retrieve the full log)
>>
>> sysctl kern.timecounter
>> kern.timecounter.tsc_shift: 1
>> kern.timecounter.smp_tsc_adjust: 0
>> kern.timecounter.smp_tsc: 1
>> kern.timecounter.invariant_tsc: 1
>> kern.timecounter.fast_gettime: 1
>> kern.timecounter.tick: 1
>> kern.timecounter.choice: ACPI-fast(900) HPET(950) i8254(0) TSC-low(1000)
>> dummy(-1000000)
>> kern.timecounter.hardware: TSC-low
>> kern.timecounter.alloweddeviation: 5
>> kern.timecounter.timehands_count: 2
>> kern.timecounter.stepwarnings: 0
>> kern.timecounter.tc.ACPI-fast.quality: 900
>> kern.timecounter.tc.ACPI-fast.frequency: 3579545
>> kern.timecounter.tc.ACPI-fast.counter: 1470549582
>> kern.timecounter.tc.ACPI-fast.mask: 4294967295
>> kern.timecounter.tc.HPET.quality: 950
>> kern.timecounter.tc.HPET.frequency: 14318180
>> kern.timecounter.tc.HPET.counter: 378058131
>> kern.timecounter.tc.HPET.mask: 4294967295
>> kern.timecounter.tc.i8254.quality: 0
>> kern.timecounter.tc.i8254.frequency: 1193182
>> kern.timecounter.tc.i8254.counter: 20425
>> kern.timecounter.tc.i8254.mask: 65535
>> kern.timecounter.tc.TSC-low.quality: 1000
>> kern.timecounter.tc.TSC-low.frequency: 1900039387
>> kern.timecounter.tc.TSC-low.counter: 2386729797
>> kern.timecounter.tc.TSC-low.mask: 4294967295
>>
>> sysctl kern.eventtimer
>> kern.eventtimer.choice: LAPIC(600) HPET(350) HPET1(350) HPET2(350)
>> i8254(100) RTC(0)
>> kern.eventtimer.et.HPET2.quality: 350
>> kern.eventtimer.et.HPET2.frequency: 14318180
>> kern.eventtimer.et.HPET2.flags: 3
>> kern.eventtimer.et.HPET1.quality: 350
>> kern.eventtimer.et.HPET1.frequency: 14318180
>> kern.eventtimer.et.HPET1.flags: 3
>> kern.eventtimer.et.HPET.quality: 350
>> kern.eventtimer.et.HPET.frequency: 14318180
>> kern.eventtimer.et.HPET.flags: 3
>> kern.eventtimer.et.RTC.quality: 0
>> kern.eventtimer.et.RTC.frequency: 32768
>> kern.eventtimer.et.RTC.flags: 17
>> kern.eventtimer.et.i8254.quality: 100
>> kern.eventtimer.et.i8254.frequency: 1193182
>> kern.eventtimer.et.i8254.flags: 1
>> kern.eventtimer.et.LAPIC.quality: 600
>> kern.eventtimer.et.LAPIC.frequency: 50001034
>> kern.eventtimer.et.LAPIC.flags: 7
>> kern.eventtimer.periodic: 0
>> kern.eventtimer.timer: LAPIC
>> kern.eventtimer.idletick: 0
>> kern.eventtimer.singlemul: 2
>
> It is clipped at the start, and that was the information which I need.
> Add something like
> kern.msgbufsize=1048576
> to /boot/loader.conf and try again. I need to see the lines starting with
>
> CPU: Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (1992.08-MHz K8-class CPU)
> Origin="GenuineIntel" Id=0x806ea Family=0x6 Model=0x8e Stepping=10
> Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
> MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> ...
>
> (well, this is my w/s, your CPU would be different of course).
>
Thanks, I've updated the file on freefall
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1458920202.313097.1610729171060>