Bug 6285
| Summary: | Writing to Novatel v620 causes kernel hang | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Chris Worley (chris.worley) |
| Component: | USB | Assignee: | Greg Kroah-Hartman (greg) |
| Status: | REJECTED INSUFFICIENT_DATA | ||
| Severity: | normal | CC: | bunk |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.16 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 5089 | ||
| Attachments: |
lspci -vv
Bootup serial console capture /proc/config |
||
|
Description
Chris Worley
2006-03-26 09:18:29 UTC
Created attachment 7678 [details]
lspci -vv
Created attachment 7679 [details]
Bootup serial console capture
Created attachment 7680 [details]
/proc/config
ACPI is turned on, but appears to not exist on the embedded board.
All PHY are turned on, since I'm not sure which driver works.
bugme-daemon@bugzilla.kernel.org wrote: > > http://bugzilla.kernel.org/show_bug.cgi?id=6285 > > Summary: Writing to Novatel v620 causes kernel hang > Kernel Version: 2.6.16 > Status: NEW > Severity: normal > Owner: linux-pcmcia@lists.infradead.org > Submitter: chris.worley@sbcglobal.net > > > Most recent kernel where this bug did not occur: Unknown > Distribution: Linux From Scratch 01/23/06 > Hardware Environment: Geode GX1 SC1100, TI 1410, DP83815 > Software Environment: 2.6.16 with minimal toolset and pccardctl > Problem Description: Any attempt to write to usb-serial port causes > kernel to hang until card is removed. > > Steps to reproduce: boot kernel with card inserted, login as root, > execute /bin/cat AT > /dev/ttyUSB0 > Guys, is this likely to be a USB problem or a PCMCIA one? Thanks. Can you do: echo 1 > /sys/module/usbserial/parameters/debug echo 1 > /sys/module/airprime/paramaters/debug and then do the "echo AT > /dev/ttyUSB0" thing and attach the kernel log from that? And as for it being a USB or PCMCIA issue, this is a very wierd device with an embedded usb controller and a fake usb-serial device all rigged together to try to get it to work properly together. I've had numerous reports of this device working just fine, and numerous ones of it not working at all. The joys of working with undocumented hardware... Traced down to a completely messed up airprime driver file. Although it looks correct, none of the usbserial functions are being called. After I did the modprobe vendor product hack, everything worked. So something is seriously wrong in the airprime.c file. Ok, perhaps the airprime driver just is not the proper driver for this device? Why did you think that this driver would work for this device? What is the output of /proc/bus/usb/devices with the device plugged in? Please reopen this bug if: - it is still present in kernel 2.6.17 and - you can provide the requested information. |