on 06/09/2010 20:12 Olivier Smedts said the following: > Here is mine : no difference before and after the patch :
Thanks! [snip] > The only thing I noticed is this, after the patch : > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > ada1: <SAMSUNG HD161HJ JF100-19> ATA-7 SATA 2.x device > ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 152627MB (312581808 512 byte sectors: 16H 63S/T 16383C) > SMP: AP CPU #1 Launched!cd0 at ahcich2 bus 0 scbus2 target 0 lun 0 > > cd0: <LITE-ON DVDRW LH-20A1S 9L08> Removable CD-ROM SCSI-0 device > cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes) > cd0: Attempt to query device size failed: NOT READY, Medium not present > SMP: AP CPU #3 Launched! > SMP: AP CPU #2 Launched! > Trying to mount root from zfs:tank/freebsd > > > Before the patch, all the "SMP: AP CPU #X Launched!" were correctly > displayed, with carriage returns. Yes, I use "options > PRINTF_BUFR_SIZE=128". And I don't know if that's related to the > patch. No, it's not related, it's a probabilistic thing. Those "Launched!" messages are printed from threads running on freshly started APs and thus are executed truly parallel to BSP. BTW, is the above snippet from /var/log/messages or from actual console (e.g. ttyv0)? If it's from message, then could you please check how it looks on the console? -- Andriy Gapon _______________________________________________ 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"
