Hi Marko,
On Thu, Jan 9, 2025 at 1:49 PM Marko Hoyer <Marko.Hoyer@xxxxxxxxxx> wrote:
> Take a look into the kmesg logs. Looks like there is a 8s delay at a
> certain point:
>
> [ 5.897018] input: C-Media Electronics Inc. USB Audio Device as
> /devices/platform/soc/20980000.usb/usb1/1-1/1-1:1.3/0003:0D8C:0014.0001/input/input1
> [ 6.016086] hid-generic 0003:0D8C:0014.0001: input,hidraw0: USB HID
> v1.00 Device [C-Media Electronics Inc. USB Audio Device] on
> usb-20980000.usb-1/input3[ 14.012174] printk: console [ttyS0] enabled
> [ 14.064965] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
> [ 14.142795] bcm2835-power bcm2835-power: Broadcom BCM2835 power
> domains driver
> [ 14.232013] mmc-bcm2835 20300000.mmcnr: mmc_debug:0 mmc_debug2:0
Those eight seconds are the time needed for printing all
previously-collected and time-stamped kernel log lines to the serial
console.
BTW, only slightly related, but I have no better place to vent ;-)
On OrangeCrab running a 64 MHz VexRiscv softcore, I noticed another
big delay. With initcall_debug:
initcall pty_init+0x0/0x3c8 returned 0 after 185427581 usecs
Apparently this is due to:
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
So yes, almost one one second to set up one legacy pty, ugh...
Disabling CONFIG_LEGACY_PTYS fixed the issue.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
