User profile for user: Tex-Twil
Tex-Twil Author
User level: Level 1
6 points

DSMOS has arrived - long boot

Hello,
I have SL on a 2010 uMBP with a 5400 drive and my boot time has become kind of long (more that a minute till the Desktop).

When I boot in the verbose mode I see that the boots stops for around *25 seconds* on the following message (kernel.log):

Jul 8 08:28:13 localhost kernel[0]: DSMOS has arrived
Jul 8 08:28:38 localhost kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).


If I open the kernel.log and search from DSMOS, I see older logs where it didn't wait so long:

Jun 8 07:41:13 mbp kernel[0]: DSMOS has arrived
Jun 8 07:41:13 mbp kernel[0]: BCM5701Enet: Ethernet address 58:b0:35:fb:XX:XX
Jun 8 07:41:13 mbp kernel[0]: AirPort_Brcm43224: Ethernet address 58:b0:35:78:XX:XX



any ideas ?

Thanks,
Tex

2010 Unibody MBP 15", Mac OS X (10.6)

Posted on Jul 8, 2010 12:36 AM

Reply
8 replies
User profile for user: William-Boyd-Jr
William-Boyd-Jr
User level: Level 6
10,587 points

Jul 8, 2010 12:37 PM in response to Tex-Twil

Tex-Twil wrote:
When I boot in the verbose mode I see that the boots stops for around *25 seconds* on the following message (kernel.log):

Jul 8 08:28:13 localhost kernel[0]: DSMOS has arrived
Jul 8 08:28:38 localhost kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).


I won't claim to be an expert on this subject, but I believe that the "DSMOS has arrived" message marks the end of a boot process, not the beginning. In my kernel.log I see a message "Waiting for DSMOS" a couple of seconds before that message, suggesting to me that those two form a pair. Instead, I would explore the possibility that there's something wrong with the AirPort function. Try booting your MBP with AirPort turned off and see what happens.

Also in my kernel.log, I sometimes see the "Waiting" message immediately followed by the AirPort message, followed by the "arrived" message a second later.
Reply
User profile for user: William-Boyd-Jr
William-Boyd-Jr
User level: Level 6
10,587 points

Jul 8, 2010 1:42 PM in response to Tex-Twil

Tex-Twil wrote:
Could you please check your logs and see how much time there is between the DSMOS message and the next one ?


Is this what you wanted, or did you want to see the message after the one for "DMSOS has arrived"?

Jul 2 10:12:40 localhost kernel[0]: Waiting for DSMOS...
Jul 2 10:12:40 localhost kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Jul 2 10:12:41 localhost kernel[0]: Warning - kext com.apple.iokit.CHUDProf has i
mmediate dependencies on both com.apple.kernel* and com.apple.kpi.* components; us
e only one style.
Jul 2 10:12:42 localhost kernel[0]: NVDANV50HAL loaded and registered.
Jul 2 10:12:42 localhost kernel[0]: Previous Shutdown Cause: 5
Jul 2 10:12:42 localhost kernel[0]: DSMOS has arrived


Jul 3 11:56:40 localhost kernel[0]: Waiting for DSMOS...
Jul 3 11:56:40 localhost kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Jul 3 11:56:41 localhost kernel[0]: Warning - kext com.apple.iokit.CHUDProf has immediate dependencies on both com.apple.kernel* and com.apple.kpi.* components; use only one style.
Jul 3 11:56:41 localhost kernel[0]: Previous Shutdown Cause: 5
Jul 3 11:56:41 localhost kernel[0]: NVDANV50HAL loaded and registered.
Jul 3 11:56:41 localhost kernel[0]: DSMOS has arrived


Jul 3 12:09:15 localhost kernel[0]: Waiting for DSMOS...
Jul 3 12:09:21 MacBook kernel[0]: NVDANV50HAL loaded and registered.
Jul 3 12:09:25 MacBook kernel[0]: Previous Shutdown Cause: 5
Jul 3 12:09:26 MacBook kernel[0]: wl0: Broadcom BCM432b 802.11 Wireless Controller
Jul 3 12:09:26 MacBook kernel[0]: 5.10.91.27
Jul 3 12:09:28 MacBook kernel[0]: Warning - kext com.apple.iokit.CHUDProf has immediate dependencies on both com.apple.kernel* and com.apple.kpi.* components; use only one style.
Jul 3 12:09:29 MacBook kernel[0]: DSMOS has arrived

Interestingly, for these messages I only see the "has arrived" message, not the "Waiting for" message:

Jul 4 10:18:47 MacBook kernel[0]: DSMOS has arrived
Jul 6 07:47:21 localhost kernel[0]: DSMOS has arrived
Jul 6 10:20:47 localhost kernel[0]: DSMOS has arrived
Jul 7 08:53:03 localhost kernel[0]: DSMOS has arrived
Jul 8 10:24:49 localhost kernel[0]: DSMOS has arrived
Reply
User profile for user: Tex-Twil
Tex-Twil Author
User level: Level 1
6 points

Jul 8, 2010 11:31 PM in response to William-Boyd-Jr

hmm I don't know what to think. Maybe I am chasing a ghost but I find it strange that it"s stuck during 25 seconds.

I repaired permissions and clean caches using Onyx and today the "Airport" message disappeared. Though, it takes still 20 seconds:

/var/log//kernel.log:Jul 9 08:02:06 localhost kernel[0]: DSMOS has arrived
/var/log//kernel.log:Jul 9 08:02:26 mbp kernel[0]: IOBluetoothBNEPDriver: Ethernet address 58:b0:35:78:14:50
/var/log//kernel.log:Jul 9 08:02:27 mbp kernel[0]: en1: 802.11d country code set to 'DE'.
/var/log//kernel.log:Jul 9 08:02:27 mbp kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
/var/log//kernel.log:Jul 9 08:02:27 mbp kernel[0]: Auth result for: 00:23:12:fc:f1:XX MAC AUTH succeeded
/var/log//kernel.log:Jul 9 08:02:27 mbp kernel[0]: AirPort: Link Up on en1
/var/log//kernel.log:Jul 9 08:02:28 mbp kernel[0]: AirPort: RSN handshake complete on en1



I also tried to look for eventual log messages which have time stamp between the "has arrived" (08:02:06) and the next message (08:02:26) and found this in system log:

/var/log//system.log:Jul 9 08:02:25 localhost configd[14]: bootp sessiontransmit: bpf_write(en1) failed: Network is down (50)
/var/log//system.log:Jul 9 08:02:25 localhost configd[14]: DHCP en1: INIT-REBOOT transmit failed
/var/log//system.log:Jul 9 08:02:25 localhost configd[14]: network configuration changed.
/var/log//system.log:Jul 9 08:02:25 mbp configd[14]: setting hostname to "mbp.local"
/var/log//system.log:Jul 9 08:02:25 mbp configd[14]: bootp sessiontransmit: bpf_write(en3) failed: Operation not permitted (1)
/var/log//system.log:Jul 9 08:02:25 mbp configd[14]: DHCP en3: INIT transmit failed


So I set a fixed IP to my mac and it seems to be a bit better
Jul 9 08:28:30 localhost kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
Jul 9 08:28:32 localhost kernel[0]: DSMOS has arrived
Jul 9 08:28:42 mbp kernel[0]: IOBluetoothBNEPDriver: Ethernet address 58:b0:35:78:14:50
Jul 9 08:28:48 mbp kernel[0]: en1: 802.11d country code set to 'US'.


Message was edited by: Tex-Twil
Reply
User profile for user: Tex-Twil
Tex-Twil Author
User level: Level 1
6 points

Jul 9, 2010 9:29 AM in response to plcn

plcn wrote:
Try to boot your Mac in safe mode, holding the shift key after the startup sound chimes, and releasing it after the Apple logo appears.

In safe mode, the system will check the disk, clean caches and rebuild some internal databases. After login, reboot your Mac normally to see if it helped

Hi,
this solved the "DSMOS arrived" problem:

Jul 9 18:21:16 mbp kernel[0]: DSMOS has arrived
Jul 9 18:21:16 mbp kernel[0]: BCM5701Enet: Ethernet address 58:b0:35:fb:c7:7a


But now the boot sequence waits on another point almost 30 seconds ( I did try several times)
Jul 9 18:22:37 localhost kernel[0]: systemShutdown false
Jul 9 18:23:04 mbp kernel[0]: AppleUSBMultitouchDriver::_deviceSetReport - DeviceRequest for reportID 0xac returned with result 0xe000404f - retryingWaiting for DSMOS...


I think I just give up 🙂

Thanks for your help

Tex

Message was edited by: Tex-Twil
Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

DSMOS has arrived - long boot

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up