** Changed in: linux
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/138583
Title:
[Gutsy] Kernel Oops after calling synce-serial-start
--
ubuntu-bugs mailing list
The Gutsty Gibbon 7.10 release has reached it's end of life. As a
result I'm closing the linux-source-2.6.22 task as well as it's Gutsy
nomination. Thanks.
http://www.ubuntu.com/news/ubuntu-7.10-eol
** Changed in: linux-source-2.6.22 (Ubuntu Gutsy)
Status: In Progress = Won't Fix
**
** Changed in: linux
Status: Confirmed = Fix Released
--
[Gutsy] Kernel Oops after calling synce-serial-start
https://bugs.launchpad.net/bugs/138583
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi, I suspect this bug will end up in the Won't Fix state if it's not
tested. Any volunteers to test this?
Colin
--
[Gutsy] Kernel Oops after calling synce-serial-start
https://bugs.launchpad.net/bugs/138583
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi,
If anyone would like to test this, please do, as I can then see if the
patch resolves the issue. I do not have the specific hardware, so this
bug is not going to be resolved without some testing. Thanks
Colin
--
[Gutsy] Kernel Oops after calling synce-serial-start
Hi jcd,
I have pack ported commit 063a2da8f01806906f7d7b1a1424b9afddebc443 and I
have build a set of kernels with this patch in. Can you download the
appropriate deb from:
http://people.ubuntu.com/~cking/sru-138583/
and try it out to see if this fixed the bug.
Thanks, Colin
--
[Gutsy] Kernel
** Changed in: linux-source-2.6.22 (Ubuntu Gutsy)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Colin King
(colin-king)
Status: Triaged = In Progress
--
[Gutsy] Kernel Oops after calling synce-serial-start
https://bugs.launchpad.net/bugs/138583
You received this bug
Just closing invalid Gutsy nomination against the Hardy kernel. Gutsy
nomination remains open against the appropriate 2.6.22 Gutsy kernel.
** Changed in: linux (Ubuntu Gutsy)
Status: Triaged = Invalid
--
[Gutsy] Kernel Oops after calling synce-serial-start
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Won't Fix = Triaged
--
[Gutsy] Kernel Oops after calling synce-serial-start
https://bugs.launchpad.net/bugs/138583
You received this
Hi jcd,
Thanks for opening up the bug report for the RNDIS problem. That was
the correct thing to do. I'll go ahead and open the Gutsy nomination
for the kernel team to take into consideration. I'm also including the
hardy git commit id for the patch that you are proposing to be
backported to
Hello Leann,
Just a small update to make things clear. The OOPS by itself doesn't
happen anymore on 2.6.24 (Hardy) because the following patch is applied
to the standard 2.6.24 kernel.
http://bugzilla.kernel.org/attachment.cgi?id=12918action=view
This patch could be applied right now to 2.6.22
So Leann, I guess this report should be split in 2 independent bugs (as
I should have done from the beginning).
One (the original) with the kernel OOPS problem should be nominated for
Gusty release following the SRU policy by applying
http://bugzilla.kernel.org/attachment.cgi?id=12918action=view
I created bug 192411 for the RNDIS part. I will therefore nominate this
bug for release with the appropriate required information.
1) A statement explaining the impact: with the Gusty 2.6.22 kernel 2
ttyUSB serial lines are created when you plug in the smartphone into the
USB. Unfortunately the
Hi jcd,
Thank you for your concern. I'll elaborate a little more - according to
the SRU policy, the fix should already be deployed and tested in the
current development version before an update to the stable releases will
be considered. With Gutsy 7.10 now released and Hardy 8.04 under
It is a bit desapointing to consider that people using Gusty are doomed
if they try to connect their smartphone as this will never get fixed
(according to your decision). After all this bug triggers an OOPS which
should be considered critical.
Also as things go the fix will not be in the kernel
** Changed in: linux
Status: Unknown = Confirmed
--
[Gutsy] Kernel Oops after calling synce-serial-start
https://bugs.launchpad.net/bugs/138583
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Also just adding a note that this report will remain open against the
actively developed kernel, but will be closed against linux-
source-2.6.22. Thanks!
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New = Won't Fix
--
[Gutsy] Kernel Oops after calling synce-serial-start
Hi jcd,
Your efforts to get the necessary patch into the upstream mainline
kernel is the correct approach. It is a lot of extra work for the
Ubuntu kernel team to maintain out of tree patches. As such they require
evidence of upstream submission and acceptance before considering to
maintain
Just adding a note that I'm reassigning the Ubuntu Hardy kernel source
package from 'linux-source-2.6.24' to just 'linux'. Beginning with the
Hardy release the package naming convention changed from linux-
source-2.6.x to just linux. Sorry for any confusion.
** Changed in: linux (Ubuntu)
The kernel guys don't seem to like the WM5 patch. Therefore I tried to
propose a new patch.
See my proposal at: http://bugzilla.kernel.org/show_bug.cgi?id=8094#c37
Any feedback is appreciated.
--
[Gutsy] Kernel Oops after calling synce-serial-start
https://bugs.launchpad.net/bugs/138583
You
Just to confirm that once the synce patch is applied to the current
2.6.24 linux kernel of Hardy the RNDIS feature is then working properly.
--
[Gutsy] Kernel Oops after calling synce-serial-start
https://bugs.launchpad.net/bugs/138583
You received this bug notification because you are a member
So considering that:
a) the problem seems to be understood
b) there are available patches for linux 2.6.22 and 2.6.24
Is it reasonable to expect:
1) an updated kernel for Gusty with the appropriate patches
2) the integration of the required patch in Hardy to get thing working out of
the box
In order to prevent the ipaq driver to be enabled for the wrong USB
endpoint we also need to integrate this patch to the kernel (as proposed
in http://bugzilla.kernel.org/show_bug.cgi?id=8094):
http://bugzilla.kernel.org/attachment.cgi?id=12918action=view
--
[Gutsy] Kernel Oops after calling
while patch
http://bugzilla.kernel.org/attachment.cgi?id=12918action=view is
applied to the latest 2.6.24 ubuntu kernel (Hardy), the other patch
(http://synce.svn.sourceforge.net/svnroot/synce/trunk/patches/linux-2.6.22
-rndis_host-wm5.patch) is still not integrated making it impossible to
connect
hum ... It doesn't seem to be fixed even in Linus latest GIT tree ...
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=drivers/net/usb/rndis_host.c;h=a61324757b179b04d67673d26c2484580d5a8676;hb=HEAD
--
[Gutsy] Kernel Oops after calling synce-serial-start
So it seems my device (qtek 9100 under windows mobile 5) is not supposed to be
handled by usbserial/ipaq with the help of synce-serial-start. Instead it is
supposed to be managed as an RNDIS device (rndis_host,cdc_ether,usbnet).
Indeed I got connected using RNDIS after applying the following
** Tags added: kernel-oops
--
[Gutsy] Kernel Oops after calling synce-serial-start
https://bugs.launchpad.net/bugs/138583
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
[Gutsy] Kernel Oops after calling synce-serial-start
https://bugs.launchpad.net/bugs/138583
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
A bit more analysis on this:
When the smartphone is connected, 2 USB serial lines are created
(ttyUSB0 and ttyUSB1). But the first line (ttyUSB0) has no bulk in/out,
only an interupt in support. Therefore no read_urb/write_urb are
associated to this line. On the opposite the second line (ttyUSB1)
Same for me when trying to synchronize with a Qtek 9100 running Windows
Mobile 5:
[291275.346347] BUG: unable to handle kernel NULL pointer dereference at
virtual address 002c
[291275.346359] printing eip:
[291275.346361] f8b6bba4
[291275.346363] *pde =
[291275.346368] Oops: 0002
This bug seems to be quite similar to bug 98701 except it is still
present in Gusty while 98701 was applied to Fiesty. so it was present in
2.6.20 and is still present in 2.6.22.
--
[Gutsy] Kernel Oops after calling synce-serial-start
https://bugs.launchpad.net/bugs/138583
You received this bug
I get exactly the same error when trying to synchronise with my Windows
Mobile 5 Device
--
[Gutsy] Kernel Oops after calling synce-serial-start
https://bugs.launchpad.net/bugs/138583
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
32 matches
Mail list logo
