Blank console on recent current

Is there an estimate on when the blank console on booting may be fixed? If the answer is someday, can whoever is responsible for break console output please revert their changes? There is a much worse problem at the moment on my laptop where heavy disk IO leads to a complete lock-up of the

Re: Waiting for bufdaemon

On 1/15/21 3:26 AM, Jakob Alvermark wrote: > > When rebooting my thinkpad the 'bufdaemon' times out: > > Waiting (max 60 seconds) for system thread 'bufdaemon' to stop ... > timed out I'm glad other people are seeing this: I was about to report it to the list! I'm running an AMD Threadripper

Re: WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 13.0.

Warner Losh imp at bsdimp.com wrote on Sat Jan 16 00:22:51 UTC 2021 : > On Fri, Jan 15, 2021 at 1:03 PM Hartmann, O. > wrote: > > > Running FreeBSD CURRENT on a USB only platform with a customised kernel, I > > see this > > message all the time I reboot or log console messages: > > > > [...] >

Invoking -v for clang during buildworld

While playing with -current on armv7 using a raspberry pi 2 v1.1 an error crops up with recent kernels while building world: ++: error: linker command failed with exit code 1 (use -v to see invocation) *** [clang.full] Error code 1 make[5]: stopped in /usr/freebsd-src/usr.bin/clang/clang How

Re: WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 13.0.

From: Mark Millard Subject: Re: WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 13.0. Date: Fri, 15 Jan 2021 16:54:26 -0800 > Other examples for the general type of question . . . > > > For example, various aarch64, armv7, and powerpc*: > > WARNING: Device "openfirm"

Re: WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 13.0.

On Fri, Jan 15, 2021 at 1:03 PM Hartmann, O. wrote: > Running FreeBSD CURRENT on a USB only platform with a customised kernel, I > see this > message all the time I reboot or log console messages: > > [...] > WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD > 13.0. > >

Re: Waiting for bufdaemon

In the interest of documenting some variability . . . While not readily reproducible, on a ThreadRipper 1950X that I have access to, a recent reboot had one "system thread" time out: bufspacedaemon-3 . The rest of the "system thread" list behaved normally. === Mark Millard marklmi at yahoo.com

Re: Problem with drm

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 wrote: On 1/15/21 10:11 AM, Filippo Moretti wrote: > After upgrading my custom kernel I get the following

Re: boot loader blank screen

___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 13.0.

Running FreeBSD CURRENT on a USB only platform with a customised kernel, I see this message all the time I reboot or log console messages: [...] WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD 13.0. Where does this message come from and what is causing the warning? I

Re: boot loader blank screen

On 15/01/2021 14:51, Toomas Soome wrote: Could you please check latest current now?:) Thanks, Toomas On 13. Jan 2021, at 20:13, Santiago Martinez wrote: Hi, +1 on this, i still have issue on a supermicro. Santi On 1/8/21 8:11 PM, John Kennedy wrote: On Wed, Jan 06, 2021 at 02:19:12PM

Re: Waiting for bufdaemon

From: Yasuhiro Kimura Subject: Re: Waiting for bufdaemon Date: Fri, 15 Jan 2021 20:10:30 +0900 (JST) > I have been experiencing same problem with my 13-CURRENT amd64 > VirtualBox VM for about a month. The conditions that the problem > happens are unclear and all what I can say is > > * It

Re: Waiting for bufdaemon

Am 15.01.21 um 16:45 schrieb Konstantin Belousov: > 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,

Re: Waiting for bufdaemon

On Fri., Jan. 15, 2021, 9:41 a.m. Juraj Lutter, wrote: > > On 15 Jan 2021, at 18:26, Freddie Cash wrote: > > > > /var/run/dmesg.boot includes all output from dmesg for the current boot. > No > > need to manually redirect dmesg output to a file or play with buffer > sizes. > > :) Just upload

Re: boot loader blank screen

Could you please check latest current now?:) Thanks, Toomas > On 13. Jan 2021, at 20:13, Santiago Martinez wrote: > > Hi, +1 on this, i still have issue on a supermicro. > > Santi > >> On 1/8/21 8:11 PM, John Kennedy wrote: >>> On Wed, Jan 06, 2021 at 02:19:12PM -0800, John Kennedy wrote:

Re: Waiting for bufdaemon

> On 15 Jan 2021, at 18:26, Freddie Cash wrote: > > > /var/run/dmesg.boot includes all output from dmesg for the current boot. No > need to manually redirect dmesg output to a file or play with buffer sizes. > :) Just upload that file. On boot, dmesg is saved to dmesg.boot quite lately

Re: Waiting for bufdaemon

On Fri., Jan. 15, 2021, 8:47 a.m. Mikaël Urankar, wrote: > On 15/01/2021 17:35, Konstantin Belousov wrote: > > 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

Re: Waiting for bufdaemon

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

Re: Waiting for bufdaemon

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

Re: Waiting for bufdaemon

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

Re: Waiting for bufdaemon

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

Re: Waiting for bufdaemon

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

Re: Waiting for bufdaemon

On 1/15/21 3:56 PM, 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

Re: Waiting for bufdaemon

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

Re: Waiting for bufdaemon

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)

Re: Current kernel build broken with linuxkpi?

Yesterday I typod: > So, yes as I believe I said buildkernel ran successfully. Please make that: So, yes as I believe I said buildworld ran successfully. [Whack! Whack! Whack!] Respectfully,

Problem with drm

After upgrading my custom kernel I get the following error (that did not occur before hid):hidbus0: 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:

Re: Waiting for bufdaemon

Hi, there, im having the same issue here ( AMD Ryzen7). i do not use mrsas but in my case even if i try to reboot immediately after a fresh reboot i get the timeouts. Regards Santiago Original message From: Juraj Lutter Date: 15/01/2021 12:17 (GMT+01:00) To:

Re: Waiting for bufdaemon

> On 15 Jan 2021, at 12:10, Yasuhiro Kimura wrote: > > From: Jakob Alvermark > Subject: Waiting for bufdaemon > Date: Fri, 15 Jan 2021 11:26:47 +0100 > >> When rebooting my thinkpad the 'bufdaemon' times out: >> >> Waiting (max 60 seconds) for system thread 'bufdaemon' to stop >> ... timed

Re: Waiting for bufdaemon

On 1/15/21 11:53 AM, Konstantin Belousov wrote: On Fri, Jan 15, 2021 at 11:26:47AM +0100, 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

Re: Waiting for bufdaemon

From: Jakob Alvermark Subject: Waiting for bufdaemon Date: Fri, 15 Jan 2021 11:26:47 +0100 > 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

Re: Waiting for bufdaemon

On Fri, Jan 15, 2021 at 11:26:47AM +0100, 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 ... >

Waiting for bufdaemon

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

Re: Problem with drm

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: on usbhid0 link_elf_obj: symbol linux_pci_get_class undefined Warning: memory type debugfsint leaked memory on destroy (2 allocations, 80 bytes

buildworld, installworld, world: etymology

On 14/01/2021 05:15, Warner Losh wrote: > Re: How does /usr/bin/uname work in plain english? On Wed, Jan 13, 2021, 10:13 PM Graham Perrin > wrote: … the installworld part of a FreeBSD-CURRENT system update routine? (Am I confused?) He has a newer