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:
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:
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
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
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
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
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 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,
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
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
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
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
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
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]
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.
>
>
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
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
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
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
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
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:
>
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:
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
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,
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
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
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
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
> >
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
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
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
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
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
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.
>
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
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
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
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
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
>
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
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.
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,
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.
---
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.
---
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
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
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
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.
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,
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
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
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
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
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
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
55 matches
Mail list logo