On Sun 2018-10-21 09:36:28, Sitsofe Wheeler wrote: > Looking at an old AMD Athlon(tm) II Neo N36L system booting > 4.15.0-36-generic #39-Ubuntu on Ubuntu 18.04 shows the following: > > [ 3.381871] calling intel_pstate_init+0x0/0xa4 @ 1 > [ 3.381875] initcall intel_pstate_init+0x0/0xa4 returned -19 after 0 usecs > [ 3.381877] calling ledtrig_disk_init+0x0/0x33 @ 1 > [ 3.381881] initcall ledtrig_disk_init+0x0/0x33 returned 0 after 1 usecs > [ 3.381884] calling ledtrig_mtd_init+0x0/0x33 @ 1 > [ 3.381887] initcall ledtrig_mtd_init+0x0/0x33 returned 0 after 0 usecs > [ 3.381890] calling ledtrig_cpu_init+0x0/0xde @ 1 > [ 6.862005] ledtrig-cpu: registered to indicate activity on CPUs > [ 6.901263] initcall ledtrig_cpu_init+0x0/0xde returned 0 after 3436879 usecs > [ 6.901267] calling ledtrig_panic_init+0x0/0x3e @ 1 > [ 6.901286] clocksource: Switched to clocksource tsc > [ 6.901291] initcall ledtrig_panic_init+0x0/0x3e returned 0 after 19 usecs > > So more than 3 seconds were spent in/around ledtrig_cpu_init . A very > old Debian install seemed too boot faster but I notice that > CONFIG_LEDS_TRIGGER_CPU was enabled in Debian back in 2014 (see > https://salsa.debian.org/kernel-team/linux/commit/8e2b47b9d2961757ee300e9e9eb5de5817f6e649 > ). Is this long delay normal? You may want to investigate, 3 seconds is too much. Also CPU led trigger did not work on x86 last time I checked... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
