Re: kmemleak report on isp1763 and sierra MC8705

2012-11-25 Thread Ben Hutchings
On Tue, 2012-11-20 at 17:15 -0800, Greg Kroah-Hartman wrote: > On Wed, Nov 14, 2012 at 06:52:18PM +0100, Johan Hovold wrote: > > On Wed, Nov 14, 2012 at 12:12:01PM -0500, Richard Retanubun wrote: > > > On 10/11/12 09:30 AM, Johan Hovold wrote: > > > Hi Johan, > > > > > > > There was a

Re: kmemleak report on isp1763 and sierra MC8705

2012-11-25 Thread Ben Hutchings
On Tue, 2012-11-20 at 17:15 -0800, Greg Kroah-Hartman wrote: On Wed, Nov 14, 2012 at 06:52:18PM +0100, Johan Hovold wrote: On Wed, Nov 14, 2012 at 12:12:01PM -0500, Richard Retanubun wrote: On 10/11/12 09:30 AM, Johan Hovold wrote: Hi Johan, There was a reference-count fix for the

Re: kmemleak report on isp1763 and sierra MC8705

2012-11-20 Thread Greg Kroah-Hartman
On Wed, Nov 14, 2012 at 06:52:18PM +0100, Johan Hovold wrote: > On Wed, Nov 14, 2012 at 12:12:01PM -0500, Richard Retanubun wrote: > > On 10/11/12 09:30 AM, Johan Hovold wrote: > > Hi Johan, > > > > > There was a reference-count fix for the probe error path that went in to > > > v3.5. Haven't

Re: kmemleak report on isp1763 and sierra MC8705

2012-11-20 Thread Greg Kroah-Hartman
On Wed, Nov 14, 2012 at 06:52:18PM +0100, Johan Hovold wrote: On Wed, Nov 14, 2012 at 12:12:01PM -0500, Richard Retanubun wrote: On 10/11/12 09:30 AM, Johan Hovold wrote: Hi Johan, There was a reference-count fix for the probe error path that went in to v3.5. Haven't read all the

Re: kmemleak report on isp1763 and sierra MC8705

2012-11-14 Thread Johan Hovold
On Wed, Nov 14, 2012 at 12:12:01PM -0500, Richard Retanubun wrote: > On 10/11/12 09:30 AM, Johan Hovold wrote: > Hi Johan, > > > There was a reference-count fix for the probe error path that went in to > > v3.5. Haven't read all the details on how you trigger your leak, but at > > the face of it,

Re: kmemleak report on isp1763 and sierra MC8705

2012-11-14 Thread Richard Retanubun
On 10/11/12 09:30 AM, Johan Hovold wrote: Hi Johan, There was a reference-count fix for the probe error path that went in to v3.5. Haven't read all the details on how you trigger your leak, but at the face of it, it could be related. Have a look at 0658a3366db7e27fa ("usb: use usb_serial_put

Re: kmemleak report on isp1763 and sierra MC8705

2012-11-14 Thread Richard Retanubun
On 10/11/12 09:30 AM, Johan Hovold wrote: Hi Johan, There was a reference-count fix for the probe error path that went in to v3.5. Haven't read all the details on how you trigger your leak, but at the face of it, it could be related. Have a look at 0658a3366db7e27fa (usb: use usb_serial_put in

Re: kmemleak report on isp1763 and sierra MC8705

2012-11-14 Thread Johan Hovold
On Wed, Nov 14, 2012 at 12:12:01PM -0500, Richard Retanubun wrote: On 10/11/12 09:30 AM, Johan Hovold wrote: Hi Johan, There was a reference-count fix for the probe error path that went in to v3.5. Haven't read all the details on how you trigger your leak, but at the face of it, it could

Re: kmemleak report on isp1763 and sierra MC8705

2012-11-10 Thread Johan Hovold
On Fri, Nov 9, 2012 at 11:14 PM, Richard Retanubun wrote: > On 29/10/12 06:14 PM, Alan Stern wrote: >> >> On Mon, 29 Oct 2012, Richard Retanubun wrote: >>> >>> Focusing down on one of the dumps: >>> >>> unreferenced object 0xd3849740 (size 8): >>> comm "khubd", pid 1026, jiffies 232553037

Re: kmemleak report on isp1763 and sierra MC8705

2012-11-10 Thread Johan Hovold
On Fri, Nov 9, 2012 at 11:14 PM, Richard Retanubun richardretanu...@ruggedcom.com wrote: On 29/10/12 06:14 PM, Alan Stern wrote: On Mon, 29 Oct 2012, Richard Retanubun wrote: Focusing down on one of the dumps: unreferenced object 0xd3849740 (size 8): comm khubd, pid 1026, jiffies

Re: kmemleak report on isp1763 and sierra MC8705

2012-11-09 Thread Richard Retanubun
On 29/10/12 06:14 PM, Alan Stern wrote: On Mon, 29 Oct 2012, Richard Retanubun wrote: Focusing down on one of the dumps: unreferenced object 0xd3849740 (size 8): comm "khubd", pid 1026, jiffies 232553037 (age 506.597s) hex dump (first 8 bytes): 4d 43 38 37 30 35 00 00

Re: kmemleak report on isp1763 and sierra MC8705

2012-11-09 Thread Richard Retanubun
On 29/10/12 06:14 PM, Alan Stern wrote: On Mon, 29 Oct 2012, Richard Retanubun wrote: Focusing down on one of the dumps: unreferenced object 0xd3849740 (size 8): comm khubd, pid 1026, jiffies 232553037 (age 506.597s) hex dump (first 8 bytes): 4d 43 38 37 30 35 00 00

Re: kmemleak report on isp1763 and sierra MC8705

2012-10-29 Thread Alan Stern
On Mon, 29 Oct 2012, Richard Retanubun wrote: > do the disconnect without actually removing the power to the device. > I tried "echo 1 > /sys/bus/usb/drivers/usb/2-1.2/remove" and then take down > the power > but this produced the same leak signature even before I take down the power. > >

Re: kmemleak report on isp1763 and sierra MC8705

2012-10-29 Thread Greg KH
On Mon, Oct 29, 2012 at 04:47:04PM -0400, Richard Retanubun wrote: > On 26/10/12 07:35 PM, Greg KH wrote: > >On Fri, Oct 26, 2012 at 05:57:23PM -0400, Richard Retanubun wrote: > >>Hi Guys, > >> > >>I am debugging a reported kmemleak involving a sierra wireless MC8705 > >>connected > >>through

Re: kmemleak report on isp1763 and sierra MC8705

2012-10-29 Thread Richard Retanubun
On 26/10/12 07:35 PM, Greg KH wrote: On Fri, Oct 26, 2012 at 05:57:23PM -0400, Richard Retanubun wrote: Hi Guys, I am debugging a reported kmemleak involving a sierra wireless MC8705 connected through isp1763 on powerpc linux-3.0.22 Does this also happen on 3.6.3? thanks, greg k-h Hi

Re: kmemleak report on isp1763 and sierra MC8705

2012-10-29 Thread Richard Retanubun
On 26/10/12 07:35 PM, Greg KH wrote: On Fri, Oct 26, 2012 at 05:57:23PM -0400, Richard Retanubun wrote: Hi Guys, I am debugging a reported kmemleak involving a sierra wireless MC8705 connected through isp1763 on powerpc linux-3.0.22 Does this also happen on 3.6.3? thanks, greg k-h Hi

Re: kmemleak report on isp1763 and sierra MC8705

2012-10-29 Thread Greg KH
On Mon, Oct 29, 2012 at 04:47:04PM -0400, Richard Retanubun wrote: On 26/10/12 07:35 PM, Greg KH wrote: On Fri, Oct 26, 2012 at 05:57:23PM -0400, Richard Retanubun wrote: Hi Guys, I am debugging a reported kmemleak involving a sierra wireless MC8705 connected through isp1763 on powerpc

Re: kmemleak report on isp1763 and sierra MC8705

2012-10-29 Thread Alan Stern
On Mon, 29 Oct 2012, Richard Retanubun wrote: do the disconnect without actually removing the power to the device. I tried echo 1 /sys/bus/usb/drivers/usb/2-1.2/remove and then take down the power but this produced the same leak signature even before I take down the power. Update on

Re: kmemleak report on isp1763 and sierra MC8705

2012-10-26 Thread Greg KH
On Fri, Oct 26, 2012 at 05:57:23PM -0400, Richard Retanubun wrote: > Hi Guys, > > I am debugging a reported kmemleak involving a sierra wireless MC8705 > connected > through isp1763 on powerpc linux-3.0.22 Does this also happen on 3.6.3? thanks, greg k-h -- To unsubscribe from this list: send

kmemleak report on isp1763 and sierra MC8705

2012-10-26 Thread Richard Retanubun
Hi Guys, I am debugging a reported kmemleak involving a sierra wireless MC8705 connected through isp1763 on powerpc linux-3.0.22 We are still isolating the exact trigger, but this is a pretty good one so far send "at!reset" to the modem control tty, wait until it finishes rebooting then try to

kmemleak report on isp1763 and sierra MC8705

2012-10-26 Thread Richard Retanubun
Hi Guys, I am debugging a reported kmemleak involving a sierra wireless MC8705 connected through isp1763 on powerpc linux-3.0.22 We are still isolating the exact trigger, but this is a pretty good one so far send at!reset to the modem control tty, wait until it finishes rebooting then try to

Re: kmemleak report on isp1763 and sierra MC8705

2012-10-26 Thread Greg KH
On Fri, Oct 26, 2012 at 05:57:23PM -0400, Richard Retanubun wrote: Hi Guys, I am debugging a reported kmemleak involving a sierra wireless MC8705 connected through isp1763 on powerpc linux-3.0.22 Does this also happen on 3.6.3? thanks, greg k-h -- To unsubscribe from this list: send the