Re: [Bluez-devel] [BUG] rfcomm

2008-02-20 Thread Stefan Seyfried
Dave Young schrieb: >> Feb 16 23:41:33 alon1 BUG: unable to handle kernel NULL pointer dereference >> at virtual address 0008 >> Feb 16 23:41:33 alon1 printing eip: c01b2db6 *pde = >> Feb 16 23:41:33 alon1 Oops: [#1] PREEMPT >> Feb 16 23:41:33 alon1 Modules linked in:

Re: [BUG] rfcomm

2008-02-20 Thread Dave Young
On Sat, Feb 16, 2008 at 11:49:58PM +0200, Alon Bar-Lev wrote: > On Saturday 16 February 2008, Dave Young wrote: > > Hi, alon > > > > Please try the attached patch, hope it fixes your problem. > > > > Regards > > dave > > Does not work... :( > > Alon. > > Feb 16 23:41:33 alon1 usb 3-1:

Re: [BUG] rfcomm

2008-02-20 Thread Dave Young
On Sat, Feb 16, 2008 at 11:49:58PM +0200, Alon Bar-Lev wrote: On Saturday 16 February 2008, Dave Young wrote: Hi, alon Please try the attached patch, hope it fixes your problem. Regards dave Does not work... :( Alon. Feb 16 23:41:33 alon1 usb 3-1: configuration #1 chosen

Re: [Bluez-devel] [BUG] rfcomm

2008-02-20 Thread Stefan Seyfried
Dave Young schrieb: Feb 16 23:41:33 alon1 BUG: unable to handle kernel NULL pointer dereference at virtual address 0008 Feb 16 23:41:33 alon1 printing eip: c01b2db6 *pde = Feb 16 23:41:33 alon1 Oops: [#1] PREEMPT Feb 16 23:41:33 alon1 Modules linked in: ppp_deflate

Re: [BUG] rfcomm

2008-02-16 Thread Alon Bar-Lev
On Saturday 16 February 2008, Dave Young wrote: > Hi, alon > > Please try the attached patch, hope it fixes your problem. > > Regards > dave Does not work... :( Alon. Feb 16 23:41:33 alon1 usb 3-1: configuration #1 chosen from 1 choice Feb 16 23:41:33 alon1 BUG: unable to handle kernel NULL

Re: [BUG] rfcomm

2008-02-16 Thread Alon Bar-Lev
On Saturday 16 February 2008, Dave Young wrote: Hi, alon Please try the attached patch, hope it fixes your problem. Regards dave Does not work... :( Alon. Feb 16 23:41:33 alon1 usb 3-1: configuration #1 chosen from 1 choice Feb 16 23:41:33 alon1 BUG: unable to handle kernel NULL pointer

Re: [BUG] rfcomm

2008-02-15 Thread Dave Young
On Fri, Feb 15, 2008 at 11:28 AM, Dave Young <[EMAIL PROTECTED]> wrote: > > On Wed, Feb 13, 2008 at 3:58 PM, Andrew Morton > <[EMAIL PROTECTED]> wrote: > > On Mon, 11 Feb 2008 17:57:54 +0200 Alon Bar-Lev <[EMAIL PROTECTED]> wrote: > > > > > On Tuesday 06 November 2007, Alon Bar-Lev wrote: >

Re: [BUG] rfcomm

2008-02-15 Thread Dave Young
On Fri, Feb 15, 2008 at 11:28 AM, Dave Young [EMAIL PROTECTED] wrote: On Wed, Feb 13, 2008 at 3:58 PM, Andrew Morton [EMAIL PROTECTED] wrote: On Mon, 11 Feb 2008 17:57:54 +0200 Alon Bar-Lev [EMAIL PROTECTED] wrote: On Tuesday 06 November 2007, Alon Bar-Lev wrote: On 11/6/07,

Re: [BUG] rfcomm

2008-02-14 Thread Dave Young
On Wed, Feb 13, 2008 at 3:58 PM, Andrew Morton <[EMAIL PROTECTED]> wrote: > On Mon, 11 Feb 2008 17:57:54 +0200 Alon Bar-Lev <[EMAIL PROTECTED]> wrote: > > > On Tuesday 06 November 2007, Alon Bar-Lev wrote: > > > On 11/6/07, Dave Young <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > sorry for

Re: [BUG] rfcomm

2008-02-14 Thread Dave Young
On Wed, Feb 13, 2008 at 3:58 PM, Andrew Morton [EMAIL PROTECTED] wrote: On Mon, 11 Feb 2008 17:57:54 +0200 Alon Bar-Lev [EMAIL PROTECTED] wrote: On Tuesday 06 November 2007, Alon Bar-Lev wrote: On 11/6/07, Dave Young [EMAIL PROTECTED] wrote: Hi, sorry for reply again, this seems

Re: [BUG] rfcomm

2008-02-13 Thread Mark Lord
Andrew Morton wrote: On Mon, 11 Feb 2008 17:57:54 +0200 Alon Bar-Lev <[EMAIL PROTECTED]> wrote: On Tuesday 06 November 2007, Alon Bar-Lev wrote: On 11/6/07, Dave Young <[EMAIL PROTECTED]> wrote: Hi, sorry for reply again, this seems a diffrent issue ... All that I do is running pppd over

Re: [BUG] rfcomm

2008-02-13 Thread Andrew Morton
On Mon, 11 Feb 2008 17:57:54 +0200 Alon Bar-Lev <[EMAIL PROTECTED]> wrote: > On Tuesday 06 November 2007, Alon Bar-Lev wrote: > > On 11/6/07, Dave Young <[EMAIL PROTECTED]> wrote: > > > Hi, > > > sorry for reply again, this seems a diffrent issue ... > > > > All that I do is running pppd over

Re: [BUG] rfcomm

2008-02-13 Thread Mark Lord
Andrew Morton wrote: On Mon, 11 Feb 2008 17:57:54 +0200 Alon Bar-Lev [EMAIL PROTECTED] wrote: On Tuesday 06 November 2007, Alon Bar-Lev wrote: On 11/6/07, Dave Young [EMAIL PROTECTED] wrote: Hi, sorry for reply again, this seems a diffrent issue ... All that I do is running pppd over the

Re: [BUG] rfcomm

2008-02-11 Thread Frederik Deweerdt
Hello Alon, On Mon, Feb 11, 2008 at 05:57:54PM +0200, Alon Bar-Lev wrote: [...] > Feb 11 17:46:05 alon1 BUG: unable to handle kernel NULL pointer dereference > at virtual address 0008 > Feb 11 17:46:05 alon1 printing eip: c01b2da6 *pde = > Feb 11 17:46:05 alon1 Oops: [#1]

[BUG] rfcomm

2008-02-11 Thread Alon Bar-Lev
On Tuesday 06 November 2007, Alon Bar-Lev wrote: > On 11/6/07, Dave Young <[EMAIL PROTECTED]> wrote: > > Hi, > > sorry for reply again, this seems a diffrent issue ... > > All that I do is running pppd over the rfcomm, suspending the system and > resume. > I don't load any binary module. > >

Re: [BUG] rfcomm

2008-02-11 Thread Frederik Deweerdt
Hello Alon, On Mon, Feb 11, 2008 at 05:57:54PM +0200, Alon Bar-Lev wrote: [...] Feb 11 17:46:05 alon1 BUG: unable to handle kernel NULL pointer dereference at virtual address 0008 Feb 11 17:46:05 alon1 printing eip: c01b2da6 *pde = Feb 11 17:46:05 alon1 Oops: [#1] PREEMPT

[BUG] rfcomm

2008-02-11 Thread Alon Bar-Lev
On Tuesday 06 November 2007, Alon Bar-Lev wrote: On 11/6/07, Dave Young [EMAIL PROTECTED] wrote: Hi, sorry for reply again, this seems a diffrent issue ... All that I do is running pppd over the rfcomm, suspending the system and resume. I don't load any binary module. Alon. Tried

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Alon Bar-Lev
On 11/6/07, Dave Young <[EMAIL PROTECTED]> wrote: > Hi, > sorry for reply again, this seems a diffrent issue ... All that I do is running pppd over the rfcomm, suspending the system and resume. I don't load any binary module. Alon. - To unsubscribe from this list: send the line "unsubscribe

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Dave Young
On 11/6/07, Dave Young <[EMAIL PROTECTED]> wrote: > On 11/5/07, Alon Bar-Lev <[EMAIL PROTECTED]> wrote: > > On 11/5/07, Dave Young <[EMAIL PROTECTED]> wrote: > > > Hi, > > > I managed to produce this bug last weekend. I debugged it and found a > > > rfcomm_dev refcnt BUG. > > > please try the

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Dave Young
On 11/5/07, Alon Bar-Lev <[EMAIL PROTECTED]> wrote: > On 11/5/07, Dave Young <[EMAIL PROTECTED]> wrote: > > Hi, > > I managed to produce this bug last weekend. I debugged it and found a > > rfcomm_dev refcnt BUG. > > please try the patch of attachment, sorry for attachement because of > > my

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Alon Bar-Lev
On 11/5/07, Dave Young <[EMAIL PROTECTED]> wrote: > Hi, > I managed to produce this bug last weekend. I debugged it and found a > rfcomm_dev refcnt BUG. > please try the patch of attachment, sorry for attachement because of > my gmail/mutt configuration problem. > > I post it in below thread: >

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Alon Bar-Lev
On 11/5/07, Dave Young [EMAIL PROTECTED] wrote: Hi, I managed to produce this bug last weekend. I debugged it and found a rfcomm_dev refcnt BUG. please try the patch of attachment, sorry for attachement because of my gmail/mutt configuration problem. I post it in below thread:

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Dave Young
On 11/5/07, Alon Bar-Lev [EMAIL PROTECTED] wrote: On 11/5/07, Dave Young [EMAIL PROTECTED] wrote: Hi, I managed to produce this bug last weekend. I debugged it and found a rfcomm_dev refcnt BUG. please try the patch of attachment, sorry for attachement because of my gmail/mutt

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Dave Young
On 11/6/07, Dave Young [EMAIL PROTECTED] wrote: On 11/5/07, Alon Bar-Lev [EMAIL PROTECTED] wrote: On 11/5/07, Dave Young [EMAIL PROTECTED] wrote: Hi, I managed to produce this bug last weekend. I debugged it and found a rfcomm_dev refcnt BUG. please try the patch of attachment,

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-05 Thread Alon Bar-Lev
On 11/6/07, Dave Young [EMAIL PROTECTED] wrote: Hi, sorry for reply again, this seems a diffrent issue ... All that I do is running pppd over the rfcomm, suspending the system and resume. I don't load any binary module. Alon. - To unsubscribe from this list: send the line unsubscribe

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-04 Thread Dave Young
On 10/24/07, Alon Bar-Lev <[EMAIL PROTECTED]> wrote: > > Hello, > > I have this issue for long time (At least from linux-2.6.18). > I think it is about time I report this... :) > > When coming out of suspend (uswsusp or suspend2) if rfcomm was > active it creates this dump. > > If you need any

Re: [Bluez-devel] [BUG] rfcomm]

2007-11-04 Thread Dave Young
On 10/24/07, Alon Bar-Lev [EMAIL PROTECTED] wrote: Hello, I have this issue for long time (At least from linux-2.6.18). I think it is about time I report this... :) When coming out of suspend (uswsusp or suspend2) if rfcomm was active it creates this dump. If you need any more info I

Re: [BUG] rfcomm]

2007-10-24 Thread Pavel Machek
On Tue 2007-10-23 20:28:04, Jiri Kosina wrote: > On Tue, 23 Oct 2007, Marcel Holtmann wrote: > > > > actually uswsusp has been upstream for quite some time already. See > > > Documentation/power/userland-swsusp.txt > > nice. I've never used it. Currently I am using what comes with Ubuntu > >

Re: [BUG] rfcomm]

2007-10-24 Thread Cornelia Huck
On Tue, 23 Oct 2007 20:55:54 +0200, "Alon Bar-Lev" <[EMAIL PROTECTED]> wrote: > On 10/23/07, Marcel Holtmann <[EMAIL PROTECTED]> wrote: > > the code in net/bluetooth/rfcomm/tty.c contains two calls to > > device_move(). Please comment these out and try again. At least then we > > know that it is

Re: [BUG] rfcomm]

2007-10-24 Thread Cornelia Huck
On Tue, 23 Oct 2007 20:55:54 +0200, Alon Bar-Lev [EMAIL PROTECTED] wrote: On 10/23/07, Marcel Holtmann [EMAIL PROTECTED] wrote: the code in net/bluetooth/rfcomm/tty.c contains two calls to device_move(). Please comment these out and try again. At least then we know that it is in issue on

Re: [BUG] rfcomm]

2007-10-24 Thread Pavel Machek
On Tue 2007-10-23 20:28:04, Jiri Kosina wrote: On Tue, 23 Oct 2007, Marcel Holtmann wrote: actually uswsusp has been upstream for quite some time already. See Documentation/power/userland-swsusp.txt nice. I've never used it. Currently I am using what comes with Ubuntu 7.10 and that

Re: [BUG] rfcomm]

2007-10-23 Thread Rafael J. Wysocki
On Tuesday, 23 October 2007 19:57, Alon Bar-Lev wrote: > On 10/23/07, Marcel Holtmann <[EMAIL PROTECTED]> wrote: > > first of all, please check if this still happens with 2.6.23, because we > > had some patches in the area of the RFCOMM TTY code that might have > > fixed this. > > These messages

Re: [BUG] rfcomm]

2007-10-23 Thread Alon Bar-Lev
On 10/23/07, Marcel Holtmann <[EMAIL PROTECTED]> wrote: > the code in net/bluetooth/rfcomm/tty.c contains two calls to > device_move(). Please comment these out and try again. At least then we > know that it is in issue on how we use the driver model. No bugs... Looks OK, although I don't know

Re: [BUG] rfcomm]

2007-10-23 Thread Alon Bar-Lev
On 10/23/07, Marcel Holtmann <[EMAIL PROTECTED]> wrote: > still another one to go :( Anyway since you have experience and you have > a way to reproduce it, please test the latest kernel from Linus' Git > tree. I can reproduce this. But I cannot use git snapshot as I have too much dependencies. >

Re: [BUG] rfcomm]

2007-10-23 Thread Marcel Holtmann
Hi Alon, > > nice. I've never used it. Currently I am using what comes with Ubuntu > > 7.10 and that seems to work. > > Have you tried to suspend while pppd is using rfcomm? > > The fact that it happens with suspend2 and uswsusp means that the > issue is suspend blind. > Do you need any more

Re: [BUG] rfcomm]

2007-10-23 Thread Alon Bar-Lev
On 10/23/07, Marcel Holtmann <[EMAIL PROTECTED]> wrote: > nice. I've never used it. Currently I am using what comes with Ubuntu > 7.10 and that seems to work. Have you tried to suspend while pppd is using rfcomm? The fact that it happens with suspend2 and uswsusp means that the issue is suspend

Re: [BUG] rfcomm]

2007-10-23 Thread Jiri Kosina
On Tue, 23 Oct 2007, Marcel Holtmann wrote: > > actually uswsusp has been upstream for quite some time already. See > > Documentation/power/userland-swsusp.txt > nice. I've never used it. Currently I am using what comes with Ubuntu > 7.10 and that seems to work. Never used ubuntu, so I have no

Re: [BUG] rfcomm]

2007-10-23 Thread Marcel Holtmann
Hi Alon, > > first of all, please check if this still happens with 2.6.23, because we > > had some patches in the area of the RFCOMM TTY code that might have > > fixed this. > > These messages are of 2.6.23. still another one to go :( Anyway since you have experience and you have a way to

Re: [BUG] rfcomm]

2007-10-23 Thread Marcel Holtmann
Hi Jiri, > > Second, can you try without uswsusp or suspend2. Both of them are not > > upstream and I can't tell how much these would effect this kind of > > behavior. > > Hi Marcel, > > actually uswsusp has been upstream for quite some time already. See >

Re: [BUG] rfcomm]

2007-10-23 Thread Jiri Kosina
On Tue, 23 Oct 2007, Marcel Holtmann wrote: > Second, can you try without uswsusp or suspend2. Both of them are not > upstream and I can't tell how much these would effect this kind of > behavior. Hi Marcel, actually uswsusp has been upstream for quite some time already. See

Re: [BUG] rfcomm]

2007-10-23 Thread Alon Bar-Lev
On 10/23/07, Marcel Holtmann <[EMAIL PROTECTED]> wrote: > first of all, please check if this still happens with 2.6.23, because we > had some patches in the area of the RFCOMM TTY code that might have > fixed this. These messages are of 2.6.23. > Second, can you try without uswsusp or suspend2.

Re: [BUG] rfcomm]

2007-10-23 Thread Marcel Holtmann
Hi Alon, > I have this issue for long time (At least from linux-2.6.18). > I think it is about time I report this... :) > > When coming out of suspend (uswsusp or suspend2) if rfcomm was > active it creates this dump. > > If you need any more info I will be glad to provide. first of all,

[BUG] rfcomm]

2007-10-23 Thread Alon Bar-Lev
Hello, I have this issue for long time (At least from linux-2.6.18). I think it is about time I report this... :) When coming out of suspend (uswsusp or suspend2) if rfcomm was active it creates this dump. If you need any more info I will be glad to provide. Best Regards, Alon Bar-Lev. ---

[BUG] rfcomm]

2007-10-23 Thread Alon Bar-Lev
Hello, I have this issue for long time (At least from linux-2.6.18). I think it is about time I report this... :) When coming out of suspend (uswsusp or suspend2) if rfcomm was active it creates this dump. If you need any more info I will be glad to provide. Best Regards, Alon Bar-Lev. ---

Re: [BUG] rfcomm]

2007-10-23 Thread Marcel Holtmann
Hi Alon, I have this issue for long time (At least from linux-2.6.18). I think it is about time I report this... :) When coming out of suspend (uswsusp or suspend2) if rfcomm was active it creates this dump. If you need any more info I will be glad to provide. first of all, please check

Re: [BUG] rfcomm]

2007-10-23 Thread Alon Bar-Lev
On 10/23/07, Marcel Holtmann [EMAIL PROTECTED] wrote: first of all, please check if this still happens with 2.6.23, because we had some patches in the area of the RFCOMM TTY code that might have fixed this. These messages are of 2.6.23. Second, can you try without uswsusp or suspend2. Both

Re: [BUG] rfcomm]

2007-10-23 Thread Jiri Kosina
On Tue, 23 Oct 2007, Marcel Holtmann wrote: Second, can you try without uswsusp or suspend2. Both of them are not upstream and I can't tell how much these would effect this kind of behavior. Hi Marcel, actually uswsusp has been upstream for quite some time already. See

Re: [BUG] rfcomm]

2007-10-23 Thread Marcel Holtmann
Hi Jiri, Second, can you try without uswsusp or suspend2. Both of them are not upstream and I can't tell how much these would effect this kind of behavior. Hi Marcel, actually uswsusp has been upstream for quite some time already. See Documentation/power/userland-swsusp.txt nice.

Re: [BUG] rfcomm]

2007-10-23 Thread Marcel Holtmann
Hi Alon, first of all, please check if this still happens with 2.6.23, because we had some patches in the area of the RFCOMM TTY code that might have fixed this. These messages are of 2.6.23. still another one to go :( Anyway since you have experience and you have a way to reproduce it,

Re: [BUG] rfcomm]

2007-10-23 Thread Alon Bar-Lev
On 10/23/07, Marcel Holtmann [EMAIL PROTECTED] wrote: nice. I've never used it. Currently I am using what comes with Ubuntu 7.10 and that seems to work. Have you tried to suspend while pppd is using rfcomm? The fact that it happens with suspend2 and uswsusp means that the issue is suspend

Re: [BUG] rfcomm]

2007-10-23 Thread Jiri Kosina
On Tue, 23 Oct 2007, Marcel Holtmann wrote: actually uswsusp has been upstream for quite some time already. See Documentation/power/userland-swsusp.txt nice. I've never used it. Currently I am using what comes with Ubuntu 7.10 and that seems to work. Never used ubuntu, so I have no idea

Re: [BUG] rfcomm]

2007-10-23 Thread Alon Bar-Lev
On 10/23/07, Marcel Holtmann [EMAIL PROTECTED] wrote: still another one to go :( Anyway since you have experience and you have a way to reproduce it, please test the latest kernel from Linus' Git tree. I can reproduce this. But I cannot use git snapshot as I have too much dependencies. I can

Re: [BUG] rfcomm]

2007-10-23 Thread Marcel Holtmann
Hi Alon, nice. I've never used it. Currently I am using what comes with Ubuntu 7.10 and that seems to work. Have you tried to suspend while pppd is using rfcomm? The fact that it happens with suspend2 and uswsusp means that the issue is suspend blind. Do you need any more information

Re: [BUG] rfcomm]

2007-10-23 Thread Alon Bar-Lev
On 10/23/07, Marcel Holtmann [EMAIL PROTECTED] wrote: the code in net/bluetooth/rfcomm/tty.c contains two calls to device_move(). Please comment these out and try again. At least then we know that it is in issue on how we use the driver model. No bugs... Looks OK, although I don't know what

Re: [BUG] rfcomm]

2007-10-23 Thread Rafael J. Wysocki
On Tuesday, 23 October 2007 19:57, Alon Bar-Lev wrote: On 10/23/07, Marcel Holtmann [EMAIL PROTECTED] wrote: first of all, please check if this still happens with 2.6.23, because we had some patches in the area of the RFCOMM TTY code that might have fixed this. These messages are of