: Friday, March 04, 2005 1:37 AM
To: [email protected]
Cc: Bryan Althouse
Subject: Re: [linux-usb-devel] ohci_hcd problem when device removed
On Tuesday 01 March 2005 1:26 pm, Bryan Althouse wrote:
> I am observing this on a compulabs ARMCore (Intel PXA255) processor board
> r
On Tuesday 01 March 2005 1:26 pm, Bryan Althouse wrote:
> I am observing this on a compulabs ARMCore (Intel PXA255) processor board
> running a 2.6.7 kernel.
Try a more current kernel ...
---
SF email is sponsored by - The IT Product Guide
I have what I believe is a problem with ohci_hcd. If my thumb drive is
plugged in to the usb when I insmod ohci_hcd.ko , then my usb drive will
work properly. If the drive is not plugged into the usb when I insmod
ohci_hcd.ko, then it will never work. If I plug it in afterwards, the only
way tha
>> EIP is at releaseintf+0x5e/0x8c
DB> Looks like "usbfs problem" instead. Maybe your "coldsync" program
DB> can be modified to make usbfs less unhappy.
i don't know how do it
but after small changes (kernel upgrade to 2.6.3-rc2 and moving other
usb devices to additional pci usb controller) sys
[EMAIL PROTECTED] wrote:
today i found other problem: if i run pppd on acm modem (zyxel omni
uno 56k) kernel generate lots of messages (i attach some)
Blame it on the TTY layer. I understand the next 2.6.3-pre version
with USB changes will have the fix (to cdc-acm.c, not ohci) for this.
- Dave
>> EIP is at releaseintf+0x5e/0x8c
DB> Looks like "usbfs problem" instead. Maybe your "coldsync" program
DB> can be modified to make usbfs less unhappy.
i want find and correct error source.
can everyone help me with it?
today i found other problem: if i run pppd on acm modem (zyxel omni
uno 56
[EMAIL PROTECTED] wrote:
EIP is at releaseintf+0x5e/0x8c
Looks like "usbfs problem" instead. Maybe your "coldsync" program
can be modified to make usbfs less unhappy.
- Dave
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Confere
after several days uptime ohci on my linux box stop work.
if i run
# rmmod ohci_hcd; modprobe ohci_hcd
all work again.
i attach part of dmesg output to this message.
what information is necessary to detect problem source?
ps: i use 2.6.1 kernel with serverworks chipset
dmesg.
Description: Bina
