From: Andreas Happe <andreashappe@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: various problems with usb2.0 pcmcia adaptor
Date: Mon, 22 Sep 2003 15:37:11 +0200 [thread overview]
Message-ID: <slrnbmtuo7.1ab.andreashappe@flatline.ath.cx> (raw)
Kernel Version: 2.6.0-test5-bk8
I've got some problems with the D-Link DUB-C2 2Port USB2.0 PCMCIA
adaptor. If present at boot up time, the kernel hangs after initiating a
second Yenta Socket (log below).
When inserted into a running system ohci-hcd generates multiple error
messages.
Bootup - Log (hand copied):
| Yenta: CardBus Bridge fount at 0000:02:05.0 [103c:001a]
| Yenta: Enabling burst memory read transactions
| Yenta: Using INTVAL to route CSC interrupts to PCI
| Yenta: Routing CardBus interrupts to PCI
| Yenta: ISA IRQ list 0a98, PCI irq 10
| Socket status: 300000006
[..]
| Yenta: CardBus Bridge fount at 0000:02:05.1 [103c:001a]
| Yenta: Enabling burst memory read transactions
| Yenta: Using INTVAL to route CSC interrupts to PCI
| Yenta: Routing CardBus interrupts to PCI
| Yenta: ISA IRQ list 0a98, PCI irq 10
| Socket status: 300000020
[computer hangs]
Tried to disable the onboard usb controller, but the system BIOS won't
allow it (POS in question is a HP Omnibook 6100).
The error messages which could be gained by inserting the PCMCIA card
after booting are:
| cs: IO port probe 0x0c00-0x0cff: clean.
| cs: IO port probe 0x0800-0x08ff: clean.
| cs: IO port probe 0x0100-0x04ff: excluding 0x200-0x207 0x3c0-0x3df 0x4d0-0x4d7
| cs: IO port probe 0x0a00-0x0aff: clean.
| ohci-hcd: 2003 Feb 24 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
| ohci-hcd: block sizes: ed 64 td 64
| PCI: Enabling device 0000:07:00.0 (0000 -> 0002)
| ohci-hcd 0000:07:00.0: OHCI Host Controller
| PCI: Setting latency timer of device 0000:07:00.0 to 64
| ohci-hcd 0000:07:00.0: irq 10, pci mem d2c7d000
| ohci-hcd 0000:07:00.0: new USB bus registered, assigned bus number 2
| ohci-hcd 0000:07:00.0: HC died; cleaning up
| usb usb2: device not accepting address 1, error -22
| ohci-hcd 0000:07:00.0: can't register root hub for usb2, -22
| ohci-hcd 0000:07:00.0: can't start
| ohci-hcd 0000:07:00.0: remove, state 0
| ohci-hcd 0000:07:00.0: USB bus 2 deregistered
| ohci-hcd: probe of 0000:07:00.0 failed with error -16
| ohci-hcd 0000:07:00.1: OHCI Host Controller
and:
| ohci-hcd: 2003 Feb 24 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
| ohci-hcd: block sizes: ed 64 td 64
| PCI: Enabling device 0000:07:00.0 (0000 -> 0002)
| ohci-hcd 0000:07:00.0: OHCI Host Controller
| PCI: Setting latency timer of device 0000:07:00.0 to 64
| ohci-hcd 0000:07:00.0: irq 10, pci mem d18ae000
| ohci-hcd 0000:07:00.0: new USB bus registered, assigned bus number 2
| hub 2-0:0: USB hub found
| hub 2-0:0: 3 ports detected
| PCI: Enabling device 0000:07:00.1 (0000 -> 0002)
| ohci-hcd 0000:07:00.1: OHCI Host Controller
| PCI: Setting latency timer of device 0000:07:00.1 to 64
| ohci-hcd 0000:07:00.1: irq 10, pci mem d18b8000
| ohci-hcd 0000:07:00.1: new USB bus registered, assigned bus number 3
| hub 3-0:0: USB hub found
| hub 3-0:0: config failed, hub has too many ports! (err -19)
[true, it has only 2 ports.]
| ehci_hcd 0000:07:00.2: EHCI Host Controller
--Andreas
next reply other threads:[~2003-09-22 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 13:37 Andreas Happe [this message]
2003-09-22 12:02 ` various problems with usb2.0 pcmcia adaptor Russell King
2003-09-23 11:16 ` Andreas Happe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnbmtuo7.1ab.andreashappe@flatline.ath.cx \
--to=andreashappe@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox