Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The console log didn't reveal anything from that exact time because I don't know what time it happened exactly, although I will check immediately after the next time it crashes. What I did see was this line, repeated several hundred times a day with nothing in between instances:

Looking for devices matching vendor ID=1193 and product ID=8717

This was in my user log file. Any clue what that means or if it's a problem?

JW
 
skywalker said:
The console log didn't reveal anything from that exact time because I don't know what time it happened exactly, although I will check immediately after the next time it crashes. What I did see was this line, repeated several hundred times a day with nothing in between instances:



This was in my user log file. Any clue what that means or if it's a problem?

JW
Don't just check console.log; look in the other log files too - you might find an application that was generating errors that were being logged. That's a good indicator of which application/background process is causing the problem. Make sure you check system.log - this is where errors are usually recorded. As for that log line, my gut feeling is that your system is scanning the hardware for a particular device which it cannot find. This is another clue as to why the system is freezing. Maybe try a PRAM reset?
 
I do have a piece of hardware on here that is not working correctly, but it is not contributing to the crashes, because they started before I had the device. That is almost definitely causing those messages, thanks for reminding me. I checked the other logs, but as I said, I don't have the exact time marked, so I can't check this time. I will check on the system log and others next time I have a problem.

Thanks,
JW
 
wrldwzrd89 said:
Sounds to me like some process on your crashing computer is encountering errors and hogging CPU time and memory, preventing any SSH connections or most other activity. If I were you, I'd open the Console utility and look at the logs to see if you can find any hints as to what's causing the problem.
Here's another suggestion: try generating some logs with the top command-line utility. I know that top has a logging mode and can be run in the background. The logs will tell you what application/background process, if any, is hogging the CPU and causing the freezes.
 
skywalker--every time I've seen a freeze problem with mouse movement like that, it's been as a result of a "stuck" disk of some sort--either a problem with a connected network volume, or a flaky Firewire hard drive that's gone to sleep and refuses to wake (or something like that).

Do you have any disks connected when this happens? If you've got a firewire drive attached, try just yanking the firewire cord out of it--in my case, I'd suddenly get a "disk has been unmounted improperly" error, but the system would spring back to life. Very, VERY annoying.

Network errors along the same lines have no easy fix other than a restart, unfortunately.

I haven't personally seen any of these freezes under 10.3, though--seems to have helped a lot.

skywalker said:
Looking for devices matching vendor ID=1193 and product ID=8717
Sounds like skywalker figured out what this was from, but for reference, that's the error that the Canon CanoScan scanner driver throws up when it can't find a scanner (actually, in my experience, it sometimes seems to say that even when it can, and in the logs you can see it frequently "re acquiring" the scanner for no apparent reason.

These can be alieviated by either plugging in a scanner, or removing the button manager part of the driver. As skywalker said, though, they don't cause anything but a bloated log file--I've never heard of a crash related to Canon's driver.

When it's not cluttering up your logfile, I've got to admit they work pretty well--the scanner buttons function perfectly even under 10.3, including pass-through-to-printer copying.
 
Felix_the_Mac said:
Yeah, that happened to me yesterday. I have never experienced it before.
Any suggestions as to how to recover? I had to do a power-off.

No... didn't find a fix for that so far. Power-Off and Restart is the only thing that works so far... :(

Very annoying...

groovebuster
 
This seems to fix it

I too was getting the annoying "Looking for devices matching vendor" messages in my log. I fixed it using HexEdit.

Download HexEdit from:
http://sourceforge.net/project/showfiles.php?group_id=9366

Edit the following file:
/Users/Shared/N067U/N067U_Driver.bundle/Contents/MacOS/N067U_Driver

Do a search for "Looking for devices" within the file and replace the beginning of the string - the L - with a hex zero.

The whole process is a bit more complicated because the file is open by default, so you have to make a copy, edit that, and replace the original file. Plus the file is inside the bundle so you have to choose "Show Package Contents" to actually get there.

If I have some time off, I can write a small app or shell script to do this, but that's not likely anytime in the immediate future.

Good luck.
 
EASY FIX FOUND AFTER 2 DAYS!

In your finder search for "_ButtonManager"
You will come up with some files (probably 3 files) like "NO67U_ButtonManager" delete these files. NOTE: my cannon scanner still works, but I use it through Photoshop.
 
DDi John said:
In your finder search for "_ButtonManager"
You will come up with some files (probably 3 files) like "NO67U_ButtonManager" delete these files. NOTE: my cannon scanner still works, but I use it through Photoshop.

What the huh? :confused:
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.