USB devices cause a crash at Lion login screen

Since I have installed MacOS X Lion I am experiencing regular crashes at the login screen at startup.
These crashes occur virtually always when
+ a USB device that was connected at the previous shutdown is missing at next launch
+ a USB device that was not connected at previous shutdown is connected at next launch
The type of the device does not make a difference.
I have had this with USB sticks, but also with my Wacom graphics tablet and a regular USB hard disk (connected via two USB ports).
This is extremely annoying and I had hoped this would be fixed with the latest Lion upgrade, but it is not.
Anyone out there has an idea for an easy fix?

Guys -
am I really the only person who sees this?
This is a serious issue and I also see it happening upon connecting certain USB devices (e.g. today a Garmin nüvi 1250) while running Lion. Non of the OS updates since I posted this helped.
I feel like I am running Windows here...

Similar Messages

Adjusting (ok... fiddling) the new Lion login screen

Is it possible to edit the new Lion Login screen beyond replacing the picture (/System/Library/Frameworks/AppKit.framework/Versions/C/Resources/NSTexturedFul lScreenBackgroundColor.png)? Specifically, can you change the contrast/brightness of the background picture and more importantly add the hostname/machine name as we had with the original login screen (handy when setting up computer labs). Does the machine administrator have access to an hidden program to handle this?

I guess I'll try turning off Vault
as per this thread its supposed to fix it.
https://discussions.apple.com/message/15794636#15794636

USB devices causing G5 meltdown

A friend purchased a used G5 Dual 2.5GHz running a fresh install of 10.4.x. The machine runs fine when no USB devices are attached, but consistently crashes when a USB device is connected. Both the Maxtor external HDD and Pro Tools external audio Interface (Mbox2) result in the same behavior. The computer attempts to go to sleep and never wakes up, with the fans humming at full strength. Without the USB devices attached the machine can go to sleep without problems.
This occurs with both the front USB ports and the rear (Althoug I assume these are connected to the same controller?) The keyboard and mouse can remain connected without issues. It would appear that the USB hardware is the original.
Thoughts, next troubleshooting steps?
Much appreciated,
Jon

Ah, the good ol' cinema display. We may have Yahtzee.
That would most likely be your problem. The hubs built into those monitors are prone to failure. It is especially bad if you chain a mouse of the keyboard ports.
Try leaving the hub connections from the monitor disconnected and plug the mouse and keyboard each into its own USB port on the Mac and try that. If it works and you still need a hub try a standalone powered USB hub.

Mac mini crashing into the login screen. Anyone else experiencing the same and know of a solution?

I have a Mac mini (mid-2010) with 5GB of RAM and running OS X Lion 10.7.2 and lately I've been noticing it crash and take me directly to the login screen. After I sign back in everything reboots to where I left off. I believe the problem is related to Safari. I normally have many instances of Safari browser windows open and I'm wondering if that might be the issue? Is anyone else experiencing this problem and have they found any remedies?

Note the time it freezes. That upon next successful start open the Console app in the Utilities folder and look for associated log entries at that time and post them here

Lion login screen problems on Mid 2009 MacBook Pro

After upgrading my wife's Mid 2009 MacBook Pro from Snow Leopard to Lion we are seeing weird behavior on the login screen after the computer wakes from sleep mode.
The screen is only partially drawn (usually the top left 1/4 of the screen), and the grey background is shown instead of her desktop background picture. When you move the mouse around on the screen, it repaints blocks on the screen where the pointer has been.
This only seems to happen when the machine sleeps for a long period of time, e.g., overnight. When it just sleeps for a little while we don't see the issue.
When searching the forums for anyone else with the problem, several folks said that there was an issue with the video drivers for the 9400M card and recommended switching to the 9600M GT, but her machine only has the 9400M in it.
All other aspects of the system work fine.
Anyone else seeing this? Any clues?

Surprised there hasn't been anyone else experiencing this issue.
I have seen this on 2 new MBP 2.3mhz i5's with the Intel HD 3000 384mb graphics, Lion 10.7.3 & 10.7.4.
Also with the latest Lion firmware for the late 2011 MBP's that addresses compatibility and stability issues.
Hopefully there is a fix soon because the painting on my locked screen to login is getting annoying

OS Lion login screen buttons

I recently upgraded to lion so far most things are ok. I have one issue though, the new buutons on the login screen to shut down and restart don't work. Is anyone else having this issue or know of a way to resolve it.

I guess I'll try turning off Vault
as per this thread its supposed to fix it.
https://discussions.apple.com/message/15794636#15794636

Why is the resolution of my Lion login screen so low?

I just turned on my MacBook Air, and I found that the login screen was enlarged, in which it seemed to me that the resolution of the login screen was very low. But after logging in, the resolution went back to normal. How can I fix this?

So the pictures hardly show a difference, but both my friend and I agree that there is a clear differene the picture quality of my laptop and the monitor.
Also, the photos are too large to be uploaded here.
Laptop:
http://i1131.photobucket.com/albums/m559/AaronAAA/laptop.jpg
Monitor:
http://i1131.photobucket.com/albums/m559/AaronAAA/original.jpg

New Lion Login Screen, Auto Sleep?

I set up two user accounts on my Mac Mini 1.83GHZ Core 2 Duo, and each account is set to auto-log off after 10 minutes of inactivity. This works as expected (phew!) so that when each user needs to use their account, the computer is ready for them at the new log in screen. Since this Mac is hooked up to a 40" TV, I want to make sure that I dont screenburn my TV if I leave it on at the new login screen. I waited for ten minutes and the mac didn't sleep at the new login screen, I know I have the option to Sleep it from there manually, but does anyone know if the new login screen was designed to autosleep?
Thanks,
Mr. Louis

I guess I'll try turning off Vault
as per this thread its supposed to fix it.
https://discussions.apple.com/message/15794636#15794636

USB Devices Cause Kernal Panic

Hi Everyone,
Ok, So on my White MacBook 2.2Ghz Core 2 Duo when I plug a device into either of the USB ports the computer goes into a kernal panic. It has the screen that says press the power button to turn off your computer. The funny thing, is that it only seems to be certain types of devices: Printers, and Jumpdrives. The mouse and keyboard don't do that, and neither does the iPhone. Any ideas?
Thanks!

Tue Mar 3 12:14:29 2009
panic(cpu 1 caller 0x003EB97C): "IOUSBDevice::_RESERVEDIOUSBDevice8 called\n"@/SourceCache/xnu/xnu-1228.9.59/libkern/c++/OSMetaClass.cpp:816
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x3bfb7a68 : 0x12b4f3 (0x45b13c 0x3bfb7a9c 0x1335e4 0x0)
0x3bfb7ab8 : 0x3eb97c (0x49c500 0x678280 0x678280 0x8)
0x3bfb7ad8 : 0x6694d4 (0x680118 0x8 0x3bfb7b08 0x3ece8f)
0x3bfb7af8 : 0x34696b66 (0xbafbe00 0x3bfb7b1c 0x3bfb7b28 0x3f0459)
0x3bfb7b28 : 0x346979ce (0xbeb0e00 0x3469cad4 0x3ebfe60 0x0)
0x3bfb7b78 : 0x412976 (0xbeb0e00 0xbaf6000 0x1 0x3ecd96)
0x3bfb7bd8 : 0x414219 (0xbaf6000 0xbeb0e00 0xbc6a6c0 0xbc72280)
0x3bfb7c58 : 0x413a7d (0xbaf6000 0x45e4d80 0x0 0x1)
0x3bfb7ca8 : 0x414786 (0xbaf6000 0x2 0x0 0x0)
0x3bfb7ce8 : 0x40e528 (0xbaf6000 0x2 0x0 0xbaf6000)
0x3bfb7d28 : 0x667c75 (0xbaf6000 0x2 0x4 0x0)
0x3bfb7da8 : 0x94ee3c (0xbafbe00 0xbae6500 0x1 0x1)
0x3bfb7dc8 : 0x94e886 (0xbae6500 0x1 0x1 0x0)
0x3bfb7e18 : 0x94e3f5 (0xbae6500 0x680118 0x3e91d80 0x10001)
0x3bfb7e48 : 0x412976 (0xbae6500 0xbafbe00 0x1 0x3ecd96)
0x3bfb7ea8 : 0x414219 (0xbafbe00 0xbae6500 0xbb2b1e0 0xbb2b180)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBMassStorageClass(2.0.4)@0x34695000->0x3469efff
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(2.0.5)@0x628000
dependency: com.apple.iokit.IOUSBFamily(3.1.5)@0x659000
dependency: com.apple.iokit.IOStorageFamily(1.5.5)@0x83f000
com.apple.driver.AppleUSBComposite(3.0.0)@0x94d000->0x950fff
dependency: com.apple.iokit.IOUSBFamily(3.1.5)@0x659000
com.apple.iokit.IOUSBFamily(3.1.5)@0x659000->0x680fff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9G55
Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
System model name: MacBook3,1 (Mac-F22788C8)

Lion login screen hangs

Hello, this is more of a FYI than a question.
Symptom: Upon entering your credentials in Mac OS X Lion Server, the login window will hang. However you can still move the mouse.
Since the Mac's background services were up and running at this point, I could SSH in and look around.
system.log revealed this:
Jan 19 18:55:01 Tesseract com.apple.authorizationhost.00000000-0000-0000-0000-0000000186AF[482]: buffer size: 1024 length: 592
Jan 19 18:55:01: --- last message repeated 1 time ---
Jan 19 18:55:01 Tesseract loginwindow[461]: Login Window - Returned from Security Agent
Jan 19 18:55:01 Tesseract loginwindow[461]: USER_PROCESS: 461 console
Jan 19 18:55:01 Tesseract applepushserviced[103]: Unable to bootstrap_lookup connection port for 'com.apple.iCalPush': unknown error code
Jan 19 18:55:01 Tesseract applepushserviced[103]: Unable to bootstrap_lookup connection port for 'com.apple.syncdefaultsd.push': unknown error code
Jan 19 18:55:01 Tesseract applepushserviced[103]: Unable to bootstrap_lookup connection port for 'com.apple.AddressBook.PushNotification': unknown error code
Jan 19 18:55:01 Tesseract applepushserviced[103]: Unable to bootstrap_lookup connection port for 'com.apple.safaridavclient.push': unknown error code
Jan 19 18:55:01 Tesseract airportd[499]: _doAutoJoin: Already associated to “Emerald”. Bailing on auto-join.
Jan 19 18:55:01 Tesseract com.apple.launchd.peruser.501[453] (com.apple.ReportCrash): Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
Jan 19 18:55:01 Tesseract com.apple.launchctl.Aqua[502]: com.apple.RemoteDesktop.agent: Already loaded
Jan 19 18:55:01: --- last message repeated 1 time ---
Jan 19 18:55:01 Tesseract com.apple.launchctl.Aqua[502]: load: option requires an argument -- D
Jan 19 18:55:01 Tesseract com.apple.launchctl.Aqua[502]: usage: launchctl load [-wF] [-D <user|local|network|system|all>] paths...
Jan 19 18:55:01 Tesseract loginwindow[461]: -[__NSCFConstantString count]: unrecognized selector sent to instance 0x10eeda8e0
Jan 19 18:55:01: --- last message repeated 1 time ---
Jan 19 18:55:01 Tesseract loginwindow[461]: (
                              0   CoreFoundation                      0x000000010ed87286 __exceptionPreprocess + 198
                              1   libobjc.A.dylib                     0x000000010ebf1d5e objc_exception_throw + 43
                              2   CoreFoundation                      0x000000010ee134ce -[NSObject doesNotRecognizeSelector:] + 190
                              3   CoreFoundation                      0x000000010ed74133 ___forwarding___ + 371
                              4   CoreFoundation                      0x000000010ed73f48 _CF_forwarding_prep_0 + 232
                              5   loginwindow                         0x000000010c5bf2c9 loginwindow + 74441
                              6   loginwindow                         0x000000010c5bf293 loginwindow + 74387
                              7   loginwindow                         0x000000010c5bc646 loginwindow + 63046
                              8   CoreFoundation                      0x000000010ed76a1d -[NSObject performSelector:withObject:] + 61
                              9   Foundation                          0x000000010e0a5e44 __NSThreadPerformPerform + 214
                              10 CoreFoundation                      0x000000010ecf5b51 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
                              11 CoreFoundation                      0x000000010ecf53bd __CFRunLoopDoSources0 + 253
                              12 CoreFoundation                      0x000000010ed1c1a9 __CFRunLoopRun + 905
                              13 CoreFoundation                      0x000000010ed1bae6 CFRunLoopRunSpecific + 230
                              14 HIToolbox                           0x00000001133a93d3 RunCurrentEventLoopInMode + 277
                              15 HIToolbox                           0x00000001133b063d ReceiveNextEventCommon + 355
                              16 HIToolbox                           0x00000001133b04ca BlockUntilNextEventMatchingListInMode + 62
                              17 AppKit                              0x000000010cd233f1 _DPSNextEvent + 659
                              18 AppKit                              0x000000010cd22cf5 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
                              19 AppKit                              0x000000010cd1f62d -[NSApplication run] + 470
                              20 loginwindow                         0x000000010c5b2142 loginwindow + 20802
                              21 loginwindow                         0x000000010c5b1bf0 loginwindow + 19440
                              22 ???                                 0x0000000000000002 0x0 + 2
Jan 19 18:55:01 Tesseract com.apple.launchd.peruser.501[453] (com.apple.launchctl.Aqua[502]): Exited with code: 1
Jan 19 18:55:01 Tesseract UserEventAgent[23]: CaptiveNetworkSupport:CNSServerRegisterUserAgent:187 new user agent port: 34987
Looks like the loginwindow was crashing out.
These are the steps I tried that didn't remedy the problem:
     repair Permissions
     repair Disk
     booted to safe mode (this caused a instant reboot at the login point)
     attempted to Log in as a different user
     repaired the volume with DiskWarrior
     reset pram/smc/smu
     emptied user and Library cache folders
     emptied /Library/Internet Plug-Ins
     emptied /Library/PreferencesPanes
note: to make things worse the boot volume was protected by FileVault 2.
I finally made progress when I renamed/replaced /Library/Preferences and rebooted. I could login without issue at this point.
Turns out /Library/Preferences/loginwindow.plist had a bad value.
Here is the contents of the "corrupted" plist that caused loginwindow to crash out. I verified this file was the culprit by placing it back in the Preferences folder. The symptom returned. I removed it once again, and was able to login fine.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
               <key>AutoLaunchedApplicationDictionary</key>
               <string></string>
</dict>
</plist>
and for comparison the new loginwindow.plist generated by the system:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
               <key>AutoLaunchedApplicationDictionary</key>
               <array/>
</dict>
</plist>
As you can see, somehow a empty string was passed to AutoLaunchApplicationDictionary in stead of a closed array.
Hopefully this post will help someone who was having the same issue I was.
lastly, you can "kick" the login window by logging in via ssh and running:
launchctl unload /System/Library/LaunchDaemons/com.apple.loginwindow.plist
launchctl load /System/Library/LaunchDaemons/com.apple.loginwindow.plist

I unfortunately can't add a solution along with my issue, but I'm hoping someone can comment.
When I replace the contents of com.apple.loginwindow.plist with the corrected version above, stop and restart the loginwindow process with launchctl, the loginwindow launches normally and seems ready to accept a login request.
After attempting to log in, however, the screen will flash white and return to the login window. The contents of com.apple.loginwindow.plist then reverts to:
bplist00?
_OptimizerLastRunForSystem\lastUserName_OptimizerLastRunForBuild_!AutoLaunchedAp plicationDictionaryXlastUser
Ulocalf?XloggedI/<W{?????
...which is odd, to say the least. The above behavior with the white flash then comes back and the admin user cannot log in.

Mountain Lion login screen background, how to change it?

I've upgraded today, and while all other customizations still work just fine with Lion Designer 3 (updated), the login background is the only one that just won't work, not even manually. I'm stuck (again, as it was after the last Lion update) with the Apple Linen image, duh. Anyone who's already figured out how to change it? I know Lion Designer will probably be updated about this, just wondering if I can avoid waiting! Thanks a lot!

Thats what the loginox app did to me. I did not do the manual way. If needed, I dont if I can, but it might be possible for me to insert a video showing that.
The loginox app failed to change my background.
applewarm wrote:
That's what the manual way did for me too. As said in my last comment, you need to use the Loginox app instead. You can download it here: http://www.loginox.branox.com

Issue with Lion login screen

Any idea why this might be happening when Lion gets woken up from sleep?

Have you got this box ticked:
Regards,
Colin R.

Why do I suddenly have to type my password twice at mountain lion login screen?

I am running 10.8.2 on my 2012 11" air 64GB / 4GB.
Suddenly I have to type my password in twice when logging in. It seems to accept it, then pauses, and I have to type in again, after which it logs in fine.
Interestingly this only happens with my main username. I have another user profile which has fewer apps and I wonder if there is some incompatibility.
It happens both when waking from sleep & from full restart.
I've reparied disk permissions using disk utility and onyx.
I'm not using firevault (it is off and I believe always has been).
I have no peripherals plugged in.
The password thing It's a minor inconvenience only but the system has been a bit unstable recently with a occasional sudden shutdowns. Also all my chrome "favicons" disappeared after the last crash. (the double password thing was happening before this). So I wonder if there is an underlying problem
Any ideas?

bump

Toshiba DVR20KB shows USB device not recognised

Hi,
We have a DVR20KB, which shows, when turning on USB Device not recognised error message on the screen, and there is no USB plugged in to the machine. We have already replace the DVD Drive and the board for the fault of not recognising disc but the problem of the USB error message coming up on the screen still remains, we tried disconnecting the USB board from the front but the message still comes up on the screen.
Any help would be much appreciated..
Thanks..

Originally Posted by Ranil.Wickramarachch
Hi,
We have a DVR20KB, which shows, when turning on USB Device not recognised error message on the screen, and there is no USB plugged in to the machine. We have already replace the DVD Drive and the board for the fault of not recognising disc but the problem of the USB error message coming up on the screen still remains, we tried disconnecting the USB board from the front but the message still comes up on the screen.
Any help would be much appreciated..
Thanks..
Same problem here, wondering if it has been caused by a recent OAD ?
Regards
Ken

Usb devices not working after 2.6.38 kernel upgrade

Hello everyone,
today I've upgraded my aur system to the latest packages version , kernel 2.6.38-2 .
After the reboot the usb keyboard doesn't work at all , as the usb mouse, leaving me struck at the login screen .
If I try to modify kernel boot parameters in grub or in a live distro (sysrescd) the keyboard works flawlessy .
Any clue ?
thanks in advance

I just updated to 2.6.38.7-1. The USB devices that I have plugged in before booting work (e.g USB headset). If I try to insert a new USB device, it isn't recognized. Flash-disks and USB mice that worked under the last kernel aren't working at all.
Is there a command that lets you "turn on" a USB device, or force the kernel to recognize it? I tried messing around in /sys/bus, but even in the root shell, I got "invalid write" errors.
Interesting snippet from dmesg;
[ 19.399041] uhci_hcd 0000:00:1a.0: PCI INT A disabled
[ 19.399447] uhci_hcd 0000:00:1a.1: PCI INT B disabled
[ 19.412940] uhci_hcd 0000:00:1d.1: PCI INT B disabled
[ 19.413381] uhci_hcd 0000:00:1d.2: PCI INT C disabled
[ 151.340126] uhci_hcd 0000:00:1d.0: PCI INT A disabled
Here's where it finds my webcam;
[ 9.626704] usb 2-5: new high speed USB device using ehci_hcd and address 3
[ 10.381678] input: HP Webcam as /devices/pci0000:00/0000:00:1d.7/usb2/2-5/2-5:1.0/input/input15
[ 10.381759] usbcore: registered new interface driver uvcvideo
.. and where it finds the mouse I had plugged in (you can see me disconnect it at entry 148);
[ 10.490045] usb 5-1: new low speed USB device using uhci_hcd and address 2
[ 11.201856] input: Dell Dell USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input16
[ 11.202001] generic-usb 0003:413C:3012.0001: input,hidraw0: USB HID v1.11 Mouse [Dell Dell USB Optical Mouse] on usb-0000:00:1d.0-1/input0
[ 11.202017] usbcore: registered new interface driver usbhid
[ 11.202019] usbhid: USB HID core driver
[ 148.846756] usb 5-1: USB disconnect, address 2
When I try to reconnect the mouse, nothing happens. You can see that the kernel has this error repeatedly;
ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
Edit: Found a temporary fix*.
# cd /sys/bus/usb/devices/
# for device in usb*; do echo "on" > $device/power/control; done
* I'm not responsible for what happens to your devices when you run this, but it worked for me. Check out: http://www.mjmwired.net/kernel/Document … gement.txt
Last edited by vkumar (2011-05-28 04:28:05)

USB devices cause a crash at Lion login screen

Similar Messages

Maybe you are looking for