John Baldwin wrote:
On Tuesday 20 April 2010 7:35:46 pm Matthew Jacob wrote:
On 04/20/2010 03:44 PM, Maxim Sobolev wrote:
Maxim Sobolev wrote:
Maybe try adding
hint.atkbdc.0.disabled="1"
hint.atkbd.0.disabled="1"
to /boot/device.hints? That has reportedly removed minute-long boot
delays on some Nehalem machines.
No, that have not helped at all. I measured the delay - it's about 6
minutes from boot command to the first "smap" message. Do you or
anybody else have other ideas?
Actually it helped, thank you very much! The problem was that I have
had my hints compiled into the kernel itself.
Me too!
I can't reproduce this currently, but it would be good to debug this further.
My suggestions on how to do this would be to create an array of uint64_t and
save TSC values (rdtsc()) into it at specific points in the atkbd/syscons
console init. You can then print out the deltas between array entries once
the console is fully initialized. Moving the rdtsc() calls around should
allow one to determine where in the atkbd/syscons init the long pause is
happening.
There is already a code to detect non-existing AT keyboard and avoid
attaching atkbd to it. The code is i386-only at the moment, I am trying
to figure out how to modify it so that it works on amd64 as well.
-Maxim
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
