Bug#384955: Nokia E70 as "PC suite" destabilises kernel
Now using Lenovo V200.
Connected as "pc suite" and got:
[1385043.445612] usb 4-1: new full speed USB device using uhci_hcd and
address 10
[1385043.631492] usb 4-1: configuration #1 chosen from 1 choice
[1385043.649517] usb 4-1: New USB device found, idVendor=0421,
idProduct=0418
[1385043.649525] usb 4-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[1385043.649528] usb 4-1: Product: Nokia E70
[1385043.649531] usb 4-1: Manufacturer: Nokia
[1385044.245041] cdc_acm 4-1:1.12: ttyACM0: USB ACM device
[1385044.246762] usbcore: registered new interface driver cdc_acm
[1385044.246762] cdc_acm: v0.26:USB Abstract Control Model driver for
USB modems and ISDN adapters
[1385044.279844] usbcore: registered new interface driver cdc_ether
[1385044.285053] usb 4-1: bad CDC descriptors
[1385044.285053] usbcore: registered new interface driver rndis_host
[1385044.325052] usb 4-1: bad CDC descriptors
[1385044.325052] usbcore: registered new interface driver rndis_wlan
It does not destabilize the Kernel (so far...) but is does complain
about "bad CDC descriptors" - so I guess it is not a non-bug yet.
Sam.
Moritz Muehlenhoff wrote:
reassign 384955 linux-2.6
thanks
On Mon, Aug 28, 2006 at 11:26:38AM +0300, Sam Freed wrote:
Package: kernel
Version: linux-image-2.6.17-2-686 2.6.17-7 x debian unstable
Severity: normal
Hardware Environment: Toshiba Portege R100, Nokia E70
When connecting Nokia E70 as "PC suite", kernel
destabilises to the point of crashing randomly. When connecting the USB
cable, the E70 gives you a menu of 3 options: "PC Suite","Data
Transfer", and "IP passthrouh". The "Data transfer" mode makes the
(mini-SD) mem card in the phone look like a USB_storage - that works
99%. But if you ask for "PC suite", which AFAIK will establish some sort
of serial channell to speak to the phone for syncing etc, All hell
breaks loose. Never tried the "IP passthrough" option.
I attach the kernel log. The Oops occured in the "Gnome-ternimal"
process, so probably is just an effect, but what do I know, never
debugged kernels.
Does this error still occur with more recent kernel versions?
Cheers,
Moritz
Reply to: