1 2 Previous Next 20 Replies Latest reply: Apr 7, 2013 10:03 AM by SwankPeRFection Go to original post
  • 15. Re: Damsel in Distress Again.
    SwankPeRFection Level 4 Level 4 (1,435 points)

    What kind of smartboard?  Plugging/unplugging serial or other type of connectors into devices can cause a crash in the IO driver for that connector and show up like this.

     

    For example, I have a USB to Serial converter that I use for admin work on router, switches, etc.  I wrote my own simple scripted command program which loads up the necessary OSX command to console into these devices.  If I am not careful and remember to close the connections and exit the program properly and I just unplug the cable, I'll get a crash of OSX as well.  In this case, it's not a hardware problem... it's a software issue where OSX craps out on itself because it cannot properly release control of the serial connection/port.  Could be a driver issue or it could be an OS issue, either way, the easy fix is for me to either exit out everything properly or just use a Terminal app that handles it better.

     

    So, I guess what I'm saying is, please tell us what this 15 pin connector is going to or who made it?  Could be the cable, could be that OSX expect something to be on the end of that cable and when it doesn't see a device, it just crashes because of an OS bug.  Could be anything... and yes, it could be a hardware issue, but I don't think it's a hardware issue if you can load OSX on it and let it sit there working away and there's no problems with a base load.  Your problems seem to only happen when you're messing with connectivity stuff you have.

     

    Here's another idea... load up a copy of Windows in Bootcamp and run that for a while testing.  If you have issues there too, then it's hardware.  If that's clean, then it's bs OSX bugs ringing your bell.  If that's the case, all you can do is backload your OS back to a 10.8.2 or whatever your OS version was before you updated to 10.8.3 and stay at that version while you report the issues to Apple via the Apple - Feedback pages for your model laptop.  Let their developers deal with it, but you'll need to provide very clear step by step narrowed findings/results of exactly what causes this... something that you're not being very methodical about with us to some point.

  • 16. Re: Damsel in Distress Again.
    missrossbach Level 1 Level 1 (0 points)

    Well, certainly I do apologize for not being methodical enough but as I stated before, I know enough just to be dangerous.  Translation:  I am not a tech guru, nor can I read the system log and know what it says.  My methods trying to fix this blasted thing because partially it was my lifeblood as an art teacher in a high school. I've transferred my files, but regardless...enough said.

     

    The smartboard is an older model (I'm guessing 9-10 years) made by Smart Technologies.  I don't have the connector in front of me (not at work) but it is a USB to 15 pin made by apple.  I couldn't read the numbers on the connector and I will try and update that later. I may have a second one I can replace.  I do move the machine from one room to another room which means disconnecting the machine from the smartboard to a freestanding projector.  I leave the USB connection in the machine generally speaking and connect/disconnect the 15 pin end. 

     

    I don't have a copy of Windows to load in Bootcamp and at this point, it's either time for it to go to the Apple boys or let my tech guy deal with it. 

     

    I will try replacing the connector and if that doesn't do it, it's beyond my knowledge base then. 

     

    I thank everyone who has contributed to helping me solve the problem. 

  • 17. Re: Damsel in Distress Again.
    Grant Bennet-Alder Level 8 Level 8 (49,250 points)

    I disagree with the interpretation that this is related to SMB issues.

     

    The backtrace show that the panic occurred deep in the system -- but in routines called by graphics extensions.

     

     

    Backtrace (CPU 0), Frame : Return Address

    0xffffff807d59b5b0 : 0xffffff8004c1d626

    0xffffff807d59b620 : 0xffffff8004cb7e95

    0xffffff807d59b7f0 : 0xffffff8004ccd4dd

    0xffffff807d59b810 : 0xffffff7f855abe49

    0xffffff807d59b9b0 : 0xffffff7f855a07f7

    0xffffff807d59bbf0 : 0xffffff7f8534a387

    0xffffff807d59bc60 : 0xffffff7f8533657b

    0xffffff807d59bcd0 : 0xffffff7f853391b8

    0xffffff807d59bd40 : 0xffffff7f85339343

    0xffffff807d59bdb0 : 0xffffff7f85338db4

    0xffffff807d59be10 : 0xffffff7f852ffc78

    0xffffff807d59be50 : 0xffffff7f852fef63

    0xffffff807d59be80 : 0xffffff7f852fe31e

    0xffffff807d59bef0 : 0xffffff80050467a8

    0xffffff807d59bf30 : 0xffffff80050452aa

    0xffffff807d59bf80 : 0xffffff80050453d9

    0xffffff807d59bfb0 : 0xffffff8004cb2977

          Kernel Extensions in backtrace:

             com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f852f1000->0xffffff7f85328fff

                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f852a3000

             com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7f85334000->0xffffff7f85345fff

                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f852f1000

                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f852a3000

             com.apple.NVDAResman(8.1)[A26D2A3D-C06F-3A0F-BCFF-901A98C93C3D]@0xffffff7f85348 000->0xffffff7f85655fff

                dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f852a3000

                dependency: com.apple.iokit.IONDRVSupport(2.3.7)[38C214C0-83C8-3594-8A4C-DC6AC3FEC163]@0xff ffff7f85334000

                dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[74E3E50F-E50A-3073-8C96-06F854292A91]@0 xffffff7f852f1000

     

     

    BSD process name corresponding to current thread: kernel_task

     

     

    The order of listing of loaded/unloaded extensions generally does not correlate with the cause of the problem.

     

    I agree with Linc Davis that this is likely to be a Hardware (specifically a graphics Hardware) issue.

     

    You should take your MacBook in for service, and if it no longer under warranty, the bill will be large.

  • 18. Re: Damsel in Distress Again.
    SwankPeRFection Level 4 Level 4 (1,435 points)

    missrossbach wrote:

     

    Well, certainly I do apologize for not being methodical enough but as I stated before, I know enough just to be dangerous.  Translation:  I am not a tech guru, nor can I read the system log and know what it says.  My methods trying to fix this blasted thing because partially it was my lifeblood as an art teacher in a high school. I've transferred my files, but regardless...enough said.

     

    The smartboard is an older model (I'm guessing 9-10 years) made by Smart Technologies.  I don't have the connector in front of me (not at work) but it is a USB to 15 pin made by apple.  I couldn't read the numbers on the connector and I will try and update that later. I may have a second one I can replace.  I do move the machine from one room to another room which means disconnecting the machine from the smartboard to a freestanding projector.  I leave the USB connection in the machine generally speaking and connect/disconnect the 15 pin end. 

     

    I don't have a copy of Windows to load in Bootcamp and at this point, it's either time for it to go to the Apple boys or let my tech guy deal with it. 

     

    I will try replacing the connector and if that doesn't do it, it's beyond my knowledge base then. 

     

    I thank everyone who has contributed to helping me solve the problem. 

    There's no such thing as USB to 15 pin.  Are you sure your cable isn't a MiniDisplay one?  Even so, if this smartboard is used for showing what's on the screen of your laptop, then make it a habit of turning off that display selection within OSX and then unplugging the adapter from your laptop.  OSX does not do well (they've improved it, but it still doesn't handle stuff well enough) when you unplug in-use hardware from it.  It doesn't know how to properly handle the safe unloading of the module while also transfering all the work back to whatever else natively replaces that.  Since it's a display type setup, it shouldn't be causing you this issue, but the fact that it only started to happen after you updated to 10.8.3 makes me think it IS NOT a hardware issue.  This is software stuff and no different than what happens to me when I unplug my serial connection without first closing out of the programs using it.

     

    Yes, you might not have had to do it in the past, but if Apple overlooked something in 10.8.3 and this is an OS bug (which you'll probably need to report on the Feedback pages), you may have to change your process of connecting/disconnecting the smartboard.  If that is now truly the only thing that's causing this crash, then you have your answer.  The system is on or was last on (maybe it's sleeping when you disconnect it) pushing data to this smartboard and when you just yank the connection out, it doesn't know how to handle the change.  When that happens, the OS crashes.  It's pretty simple and there's nothing magical about what's going on.  Figure out another way to disconnect from that board.  Perhaps something along the lines of set you display back to just your LCD screen on the laptop effectively turning off the mirroing on the smartboard and then unplug cables.  Start by making that display change and then unplug the 15 pin from the dongle on your laptop (like you have been all this time).  See if this is doesn't cause a crash.  If it does, then change it to unplugging the dongle from your laptop first and then that from the 15 pin cable.  The trick is figuring out a way to SAFELY unplug that external display from your system without causing this crash.

     

    As a side note, if and that's a big IF, you ever had to load any drivers or anything for this smartboard to work properly, then you need to go and try and get the newest drivers for it.  I looked on SmartTech's website and they definitely do have drivers and software for their stuff, but I don't know if they had this 9-10 years ago for the model you specifically have or if it can be treated as a simple external display.  Either way, check into that as well.  But, and most importantly, if there is software on your Mac that somehow controls this board, QUIT that app(s) before you unplug the device.  That can also be added to your list of things to try.

     

    Good luck and let us know what happens please.

  • 19. Re: Damsel in Distress Again.
    missrossbach Level 1 Level 1 (0 points)

    You're correct on the dongle (truth be told, I thought that was a slang)...it is not a USB connection.  I was incorrect. 

     

     

    And I have been sending the reports in every time.  I'll attempt some of this later in the week. 

  • 20. Re: Damsel in Distress Again.
    SwankPeRFection Level 4 Level 4 (1,435 points)

    No, you missed what I meant by reporting it.  The crash reports won't tell Apple much and they'll probably write it off as a normal crash with some kind of graphics hardware glitch like others on here have done.

     

    You need to work on finding out a way to keep the crash from happening now that we know it's somehow related to the smartboard connection.  Maybe try a normal external monitor hooked up to your dongle and see if disconnecting it the same way you do the smartboard causes the same crash.  If it does, then you know it's just a glitch with external display connections... heck, maybe it's specific to that model dongle you have, who knows.  If it ends up being specific to the smartboard then, you need to figure out if there is a safe way to disconnect it and once you have all your findings put together, go to Apple - Feedback and report it there under the MacBook Pro section.  Be specific with model numbers of the smartboard, the model number of the dongle you're using, OSX version, procedure you're doing to disconnect and cause the crash as well as the other procedure you come up with disconnecting without causing a crash and the full crash report (copy/paste it).  That is what Apple will need to do their job and correct the issue.  You gotta spoon feed those folks quite a bit.

1 2 Previous Next