Strange issue after early AP startup

Cy Schubert Cy.Schubert at komquats.com
Tue Jan 17 20:53:41 UTC 2017


In message <b9c53237-4b1a-a140-f692-bf5837060b18 at selasky.org>, Hans Petter 
Sela
sky writes:
> Hi,
> 
> When booting I observe an additional 30-second delay after this print:
> 
> > Timecounters tick every 1.000 msec
> 
> ~30 second delay and boot continues like normal.
> 
> Checking "vmstat -i" reveals that some timers have been running loose.
> 
> > cpu0:timer                         44300        442
> > cpu1:timer                         40561        404
> > cpu3:timer                      48462822     483058
> > cpu2:timer                      48477898     483209
> 
> Trying to add delays and/or prints around the Timecounters printout 
> makes the issue go away. Any ideas for debugging?
> 
> Looks like a startup race to me.

just picking a random email to reply to, I'm seeing a different issue with 
early AP startup. It affects one of my four machines, my laptop. My three 
server systems downstairs have no problem however my laptop will reboot 
repeatedly at:

Jan 17 11:55:16 slippy kernel: cd0: Attempt to query device size failed: 
NOT READY, Medium not present - tray closed

Then finally boot after a number of reboots (0-N), it finally boots. 
Disabling early AP start allows it to boot past that point first time.


-- 
Cheers,
Cy Schubert <Cy.Schubert at cschubert.com>
FreeBSD UNIX:  <cy at FreeBSD.org>   Web:  http://www.FreeBSD.org

	The need of the many outweighs the greed of the few.




More information about the freebsd-current mailing list