Re: "it just works the way you want it to"

In article <trollkiller-AF8E57.08061909012008@xxxxxxxxxxxxxxxxxxxxxxxx>,
Steve Carroll <trollkiller@xxxxxx> wrote:

In article <C3AA2E8A.A0BC5%CSMA@xxxxxxxxxxxxxxxxxxxxx>,
Snit <CSMA@xxxxxxxxxxxxxxxxxxxxx> wrote:


While I appreciate your faith in me, Steve, I do *not* believe Apple should
state what you claim to believe about me...

Why not? Apparently you and John are right, unless one is prepared to
trouble shoot issues and is "technically competent" enough to "get"
Leopard to run it doesn't "just work" as their site claims.

but I take full blame for believing what I read on the Apple site that
obviously wasn't true. You shouldn't believe everything you read...
especially where advertising is concerned. I admit it... I was duped by
Apple's hype.

http://www.apple.com/getamac/

Until now you really did not get the fact that Macs, too, can have problems.
OK. I accept you are sincere about your ignorance.

Do you also accept the "fact" that the Apple site contains
misinformation with no appropriate disclaimer?

Steve, I ran across the following this morning and thought you might like to see
it.
"MacBook Pro Trackpad wake from sleep issue

Listener Fred noticed he had the issue when Remote Buddy was installed.

Contacted the developer and they uncovered a bug in the Leopard 10.5.1 IOKit and
the IOUSB*UserClient.

On "Santa Rosa" Macbooks all the USB devices internal and external share same
bus and the bug causes the controller to become deadlocked.

Explanation from IOSpirit

1) after a (deep) sleep, the USB devices all have to be re-enumerated, which
means that IOKit will look for available drivers and user space apps that have
registered for notifications (including Remote Buddy) will try to connect to the
device through the respective IOUSB*UserClient.

2) Apple's HID drivers (IOUSBHIDDriver and subclasses) schedule an async read on
all HID devices (including the IR Receiver, which, too, is just a HID device)

3) Right after, Remote Buddy receives notice from IOKit in userspace that a
matching device (here: the built-in IR receiver) is available

4) To start from a clean basis, Remote Buddy's current release will make a
ResetDevice() call via the user client for the respective IOUSBDevice.

5) In Kernel space, Apple's HID drivers still have their async reads scheduled.
As the device is reset, they receive an error (errorcode kIOReturnUnderrun).
Their standard reaction is to make a synchronous call to reset the interrupt
pipe they are listening on.

6) The IOUSBController instance responsible for the device deadlocks.

7) As the IOUSBController instance has deadlocked, but is responsible for
handling the communication for all other devices connected to the same port, all
other devices connected to the same port will no longer appear to work, as data
is neither handed to them nor polled from them.

8) As Santa Rosa MacBook Pros internally connect keyboard, trackpad and built-in
IR receiver to the same USB port, unfortunate timing can lead to the
ResetDevice() (in user space) and ClearStall() (on IOUSBPipe, in kernel space)
calls to deadlock the IOUSBController instance handling all three devices.
That's also, why all other USB ports will continue to work.

Said simply, any application that uses the quite common and widely used approach
of accessing a USB device from user space and that makes a call to ResetDevice()
on the IOUSBDevice can potentially deadlock the IOUSBController handling the
port of the USB device - consequently disabling all I/O handling for all other
devices connected to the same USB port.

So this bug can occur with almost any 3rd part app that interfaces with the USB
and takes this common programming approach

The workaround of now is to disable sleep mode or remove the 3rd party apps
until Apple issues and update."

Obviously this 'proves' john right that your problems in an 'operator error' LOL

 
 

--
regarding Snit "You are not flamed because you speak the truth,
you are flamed because you are a hideous troll and keep disrupting
the newsgroup." Andrew J. Brehm
.

Relevant Pages

  • Re: Cannot Capture Video from JVC DV Camcorder
    ... Belkin Videobus II into the USB port in my Dell 3.0 GHz ... I am trying to capture to a 7200RPM drive with no ... I was thinking that I may have too many USB devices, ...
    (microsoft.public.windowsxp.moviemaker)
  • Re: USB ports?
    ... through a single USB port? ... Cable impedence would be a nightmare. ... for the days of hardware manuals! ... you can have up to 127 usb devices through cascading hubs. ...
    (alt.sys.pc-clone.dell)
  • Re: Which USB port do I use and can I switch?
    ... There is no 'wrong' usb port ... Showing safely remove icon is correct if you have any usb devices, ... Hardware" icon is in my system tray. ... new "Removeable Disk" drive in my drive locations and nothing is plugged ...
    (microsoft.public.windowsxp.general)
  • Re: USB ports dont work w/XP SP1
    ... >manager to remove the USB port and hubs and to unplug the ... >and install the port and hubs with the latest drivers. ... >install the USB devices one at a time so they get ... >|> Meriah, check here ...
    (microsoft.public.windowsxp.hardware)