Re: Problem charging blackberry 8700c with berry_charge (2.6.22.6)

2007-09-11 Thread Matt LaPlante 
On Mon, 10 Sep 2007 23:35:02 -0700
Greg KH <[EMAIL PROTECTED]> wrote:

> 
> > Sep  9 13:49:01 prizm kernel: [  584.407498] drivers/usb/core/inode.c: 
> > creating file '003'
> > Sep  9 13:49:01 prizm kernel: [  584.407509] hub 5-0:1.0: state 7 ports 8 
> > chg  evt 0004
> > Sep  9 13:49:01 prizm kernel: [  584.407520] hub 1-0:1.0: state 7 ports 2 
> > chg  evt 0004
> > Sep  9 13:49:03 prizm kernel: [  586.405512] usb 1-2: usb auto-suspend
> > Sep  9 13:49:03 prizm kernel: [  586.421471] hub 5-0:1.0: hub_suspend
> > Sep  9 13:49:03 prizm kernel: [  586.421481] ehci_hcd :00:10.4: suspend 
> > root hub
> > Sep  9 13:49:03 prizm kernel: [  586.421496] usb usb5: usb auto-suspend
> > Sep  9 13:49:05 prizm kernel: [  588.421351] hub 1-0:1.0: hub_suspend
> > Sep  9 13:49:05 prizm kernel: [  588.421361] usb usb1: suspend_rh
> > Sep  9 13:49:05 prizm kernel: [  588.421481] usb usb1: usb auto-suspend
> 
> Ah, oh wait, now we just turned the power off.
> 
> Try disabling CONFIG_USB_SUSPEND and see if that fixes this issue.  Or
> you can manually turn the power back on to your blackberry by writing to
> the autosuspend file for the usb device in sysfs, but that can be a
> pain.
> 
> Let me know if just changing that config option works for you.
> 

And now for the dramatic conclusion...

To begin, I have no access to the original machine at the moment, as I'm now 
out of that area for a couple weeks.  I built a similar kernel (same version) 
on another box that I have at my current location.  The new machine is 
different hardware, so some kernel re-configuring was required, but I kept with 
the same USB settings (and similar overall design).  Interestingly, this 
machine didn't reproduce the "magic command failed" error, but it did fail very 
similarly to the original at charging the device.  I disabled 
CONFIG_USB_SUSPEND as suggested, and lo and behold, it now charges the berry.  
Looks like an excellent diagnosis to me, doctor.  

Thanks! :)

> thanks,
> 
> greg k-h

-- 
Matt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Problem charging blackberry 8700c with berry_charge (2.6.22.6)

2007-09-10 Thread Greg KH 
On Sun, Sep 09, 2007 at 02:43:56PM -0400, Matt LaPlante wrote:
> On Sun, 9 Sep 2007 03:52:12 -0700
> Greg KH <[EMAIL PROTECTED]> wrote:
> 
> > On Sat, Sep 08, 2007 at 10:02:29PM -0400, Matt LaPlante wrote:
> > > I'm running the 2.6.22.6 kernel with the berry_charge module loaded.
> > > I connect my 8700c via USB, but the blackberry does not appear to
> > > charge. The power icon does not change, and even after staying
> > > connected for an extended period, the device does not appear to be
> > > gaining any power.  The cable is good, as I can plug it into my
> > > Windows machine and it begins charging immediately.  I see the
> > > following in dmesg:
> > > 
> > > [ 6638.606493] usb 1-2: new full speed USB device using uhci_hcd and 
> > > address 2
> > > [ 6638.776524] usb 1-2: configuration #1 chosen from 1 choice
> > > [ 6639.639611] usbcore: registered new interface driver berry_charge
> > > [ 6639.837097] usb 1-2: Second magic command failed: -71.
> > 
> > 
> > Ick, that's not nice.  Can you enable CONFIG_USB_DEBUG and debugging for
> > the berry_charge driver:
> > modprobe berry_charge debug=1
> > 
> > and let us know what happens?
> 
> Here you go...

This looks really odd:

> Sep  9 13:49:00 prizm kernel: [  583.455679] berry_charge 1-2:1.0: 
> usb_probe_interface
> Sep  9 13:49:00 prizm kernel: [  583.455681] berry_charge 1-2:1.0: 
> usb_probe_interface - got id
> Sep  9 13:49:00 prizm kernel: [  583.455685] usb 1-2: Power is set to 100mA
> Sep  9 13:49:00 prizm kernel: [  583.455687] usb 1-2: Sending first magic 
> command
> Sep  9 13:49:00 prizm kernel: [  583.457577] usb 1-2: Sending second magic 
> command
> Sep  9 13:49:00 prizm kernel: [  583.458578] usb 1-2: Calling 
> set_configuration
> Sep  9 13:49:00 prizm kernel: [  583.458727] drivers/usb/core/inode.c: 
> creating file '002'
> Sep  9 13:49:00 prizm kernel: [  583.458741] usb 1-2: usb_disable_device 
> nuking non-ep0 URBs
> Sep  9 13:49:00 prizm kernel: [  583.458744] usb 1-2: unregistering interface 
> 1-2:1.0

Ok, we send everything properly but then things get wierd:

> Sep  9 13:49:00 prizm kernel: [  583.461732] berry_charge 1-2:1.0: 
> usb_probe_interface
> Sep  9 13:49:00 prizm kernel: [  583.461734] berry_charge 1-2:1.0: 
> usb_probe_interface - got id
> Sep  9 13:49:00 prizm kernel: [  583.461738] usb 1-2: Power is set to 100mA
> Sep  9 13:49:00 prizm kernel: [  583.461740] usb 1-2: Sending first magic 
> command
> Sep  9 13:49:00 prizm kernel: [  583.462615] usb 1-2: Sending second magic 
> command
> Sep  9 13:49:00 prizm kernel: [  583.463568] usb 1-2: Calling 
> set_configuration
> Sep  9 13:49:00 prizm kernel: [  583.463679] usb 1-2: usb_disable_device 
> nuking non-ep0 URBs
> Sep  9 13:49:00 prizm kernel: [  583.463683] usb 1-2: unregistering interface 
> 1-2:1.0

We do it again.

> Sep  9 13:49:00 prizm kernel: [  583.465623] berry_charge 1-2:1.0: 
> usb_probe_interface
> Sep  9 13:49:00 prizm kernel: [  583.465625] berry_charge 1-2:1.0: 
> usb_probe_interface - got id
> Sep  9 13:49:00 prizm kernel: [  583.465642] usb 1-2: Power is set to 100mA
> Sep  9 13:49:00 prizm kernel: [  583.465644] usb 1-2: Sending first magic 
> command
> Sep  9 13:49:00 prizm kernel: [  583.466570] usb 1-2: Sending second magic 
> command
> Sep  9 13:49:00 prizm kernel: [  583.467566] usb 1-2: Calling 
> set_configuration
> Sep  9 13:49:00 prizm kernel: [  583.467675] usb 1-2: usb_disable_device 
> nuking non-ep0 URBs
> Sep  9 13:49:00 prizm kernel: [  583.467679] usb 1-2: unregistering interface 
> 1-2:1.0

And again.

> Sep  9 13:49:00 prizm kernel: [  583.469613] berry_charge 1-2:1.0: 
> usb_probe_interface
> Sep  9 13:49:00 prizm kernel: [  583.469616] berry_charge 1-2:1.0: 
> usb_probe_interface - got id
> Sep  9 13:49:00 prizm kernel: [  583.469619] usb 1-2: Power is set to 100mA
> Sep  9 13:49:00 prizm kernel: [  583.469621] usb 1-2: Sending first magic 
> command
> Sep  9 13:49:00 prizm kernel: [  583.470568] usb 1-2: Sending second magic 
> command
> Sep  9 13:49:00 prizm kernel: [  583.471565] usb 1-2: Calling 
> set_configuration
> Sep  9 13:49:00 prizm kernel: [  583.471671] usb 1-2: usb_disable_device 
> nuking non-ep0 URBs
> Sep  9 13:49:00 prizm kernel: [  583.471674] usb 1-2: unregistering interface 
> 1-2:1.0

And so on, numerous times.

This continues for a long time, until finally:

> Sep  9 13:49:01 prizm kernel: [  583.659570] berry_charge 1-2:1.0: 
> usb_probe_interface
> Sep  9 13:49:01 prizm kernel: [  583.659572] berry_charge 1-2:1.0: 
> usb_probe_interface - got id
> Sep  9 13:49:01 prizm kernel: [  583.659575] usb 1-2: Power is set to 100mA
> Sep  9 13:49:01 prizm kernel: [  583.659577] usb 1-2: Sending first magic 
> command
> Sep  9 13:49:01 prizm kernel: [  583.660516] usb 1-2: Sending second magic 
> command
> Sep  9 13:49:01 prizm kernel: [  583.661506] usb 1-2: uhci_result_common: 
> failed with status 44
> Sep  9 13:49:01 prizm kernel: [  583.661518] usb 1-2: Second magic command 
> failed: -71.

The c

Re: Problem charging blackberry 8700c with berry_charge (2.6.22.6)

2007-09-09 Thread Greg KH 
On Sat, Sep 08, 2007 at 10:02:29PM -0400, Matt LaPlante wrote:
> I'm running the 2.6.22.6 kernel with the berry_charge module loaded.
> I connect my 8700c via USB, but the blackberry does not appear to
> charge. The power icon does not change, and even after staying
> connected for an extended period, the device does not appear to be
> gaining any power.  The cable is good, as I can plug it into my
> Windows machine and it begins charging immediately.  I see the
> following in dmesg:
> 
> [ 6638.606493] usb 1-2: new full speed USB device using uhci_hcd and address 2
> [ 6638.776524] usb 1-2: configuration #1 chosen from 1 choice
> [ 6639.639611] usbcore: registered new interface driver berry_charge
> [ 6639.837097] usb 1-2: Second magic command failed: -71.


Ick, that's not nice.  Can you enable CONFIG_USB_DEBUG and debugging for
the berry_charge driver:
modprobe berry_charge debug=1

and let us know what happens?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Problem charging blackberry 8700c with berry_charge (2.6.22.6)

2007-09-08 Thread Matt LaPlante 
I'm running the 2.6.22.6 kernel with the berry_charge module loaded.  I connect 
my 8700c via USB, but the blackberry does not appear to charge. The power icon 
does not change, and even after staying connected for an extended period, the 
device does not appear to be gaining any power.  The cable is good, as I can 
plug it into my Windows machine and it begins charging immediately.  I see the 
following in dmesg:

[ 6638.606493] usb 1-2: new full speed USB device using uhci_hcd and address 2
[ 6638.776524] usb 1-2: configuration #1 chosen from 1 choice
[ 6639.639611] usbcore: registered new interface driver berry_charge
[ 6639.837097] usb 1-2: Second magic command failed: -71.
[ 6639.866430] usb 1-2: USB disconnect, address 2
[ 6640.610385] usb 1-2: new full speed USB device using uhci_hcd and address 3
[ 6640.775947] usb 1-2: configuration #1 chosen from 1 choice

I'd be glad to provide more information if needed.

-- 
Matt LaPlante
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/