Home
 
Previous | Memories | Tell a Friend | Next
 
kernelslacker
kernelslacker
08 May 2008 @ 09:21 am
OSX fail.  
For an OS that apparently "just works", I seem to encounter a remarkable amount of fail.
Some investigation reveals all manner of disasters in syslog..

kernel[0]: IOAudioStream[0x4634100]::clipIfNecessary() - adjusting clipped position to (d0b9d,3fd9)
kernel[0]: IOAudioStream[0x4634100]::clipIfNecessary() - Error: attempting to clip to a position more than one buffer ahead of last clip position (d0b2f,3ff9)->(d0b9f,4b).
The best part about this fail is that it does it even when no audio is playing. I just need an app that plays audio to be open.
Result: A gazillion of these in the logs.

usbmuxd[104]: MuxTCPSendRST StartWrite failed: 0xffffffff
usbmuxd[104]: MuxInterfacev1Receive Dropping packet. Received 26036, expected -769822944 bytes
lol whut?

kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
Good job. Please try n+1 times.

This is just from todays log, and just the kernel messages. The spew from userspace freaking out about this that and everything is even worse.

But at least it looks pretty whilst it's failing.
Tags:
 
7 comments | Leave a comment
 
( Post a new comment )
redline6561[info]redline6561 on May 8th, 2008 03:46 pm (UTC)
Dave,

This post makes me unreasonably happy. I'm glad someone dug out the dirt.

Regards,
Brit
(Reply) (Thread) (Link)
[info]jamezm on May 8th, 2008 04:10 pm (UTC)
Hmm, studlyCaps.
(Reply) (Thread) (Link)
evilidler[info]evilidler on May 8th, 2008 11:49 pm (UTC)
The Steve's reality warping field works through every Apple device. Just code enough on them, and you'll be writing in studlyCaps everyWhereYouGo.
(Reply) (Parent) (Thread) (Link)
new now know how[info]strangestone on May 8th, 2008 09:23 pm (UTC)
This makes OS*X reasonably better if you don't stick with *stable* kernels out of distros -- just dont get out of mainline fruity tree.

Though, it makes a problem once you need something out of the box, of course.
(Reply) (Thread) (Link)
evilidler[info]evilidler on May 8th, 2008 11:48 pm (UTC)
Opening the syslog is like xmas every day! I only run a browser. music and XCode, but the damn logs fill up with junk.

XCode leaks memory, and knows it. At least that's what I guess from the console messages I get at work.

SMART status checking fails when a harddrive isn't HFS/+ formatted (big ext2/3 drive with portable music). What the hell? This is a different layer from the actual content! The other external drive is fine, and HFS+ with journal.

Whether it's kernel or userland, there are Problems in OS X. Just like everything else.
(Reply) (Thread) (Link)
[info]mvpittman on May 9th, 2008 01:54 am (UTC)
That's the point. It hides stuff you can't actually fix.
"But at least it looks pretty whilst it's failing."

That might actually be the point behind "just works" (other than dictating to users the way in which things work, and only presenting them with those options).

If I can't fix it, don't bother showing me, and just record it somewhere. Keep pretending like it works.

On Linux, we'd expect that to be completely visibly broken, and then want someone to file a bug report and fix it.
(Reply) (Thread) (Link)
Jon Dowland[info]jmtd on May 12th, 2008 08:43 am (UTC)
The thing is, as my smug mac-loving friends would point out, the average mac user won't see these errors and won't notice anything going wrong.

By contrast, my syslog output might be cleaner (It's by no means spotless, and my .xsession-errors is a disaster), but my GTK user space is sluggish, my network-manager unreliable, and various other ui aspects pale too.
(Reply) (Thread) (Link)