From: Miles Lane <miles@megapathdsl.net>
To: linux-hotplug@vger.kernel.org
Subject: Can't hotplug two cardbus devices -- a 3c575 ethernet adapter and a USB host-controller.
Date: Mon, 22 Jan 2001 10:51:00 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98016069100543@msgid-missing> (raw)
First off, I have successfully hotplugged my USB mouse on
this machine, so I don't think my configuration is wrong.
My config:
kernel 2.4.0-pre9
modutils 2.4.0 + David Brownell's depmod patch.
The latest hotplug package from the linux-hotplug site.
usbutils is not installed.
I just tested and got this:
Jan 22 02:20:35 agate kernel: cs: socket c4ffa000 timed out during
reset. Try increasing setup_delay.
Jan 22 02:20:36 agate kernel: cs: cb_alloc(bus 5): vendor 0x1045, device
0xc861
Jan 22 02:20:36 agate kernel: got res[11000000:11000fff] for resource
0 of PCI device 1045:c861
Jan 22 02:20:36 agate kernel: PCI: Enabling device 05:00.0 (0000 -> 0002)
Jan 22 02:20:36 agate kernel: PCI: No IRQ known for interrupt pin A of
device 05:00.0.
Jan 22 02:20:36 agate cardmgr[437]: initializing socket 1
Jan 22 02:20:36 agate cardmgr[437]: unsupported card in socket 1
Jan 22 02:20:36 agate /sbin/hotplug: arguments (pci) env
(PCI_CLASSÀ310 PCI_ID\x1045:C861 ACTIONd TERM=dumb HOSTTYPE=i386
PATH=/bin:/sbin:/usr/sbin:/usr/bin HOME=/ SHELL=/bin/bash DEBUG=yes
PCI_SUBSYS_ID\x1045:C861 OSTYPE=Linux PCI_SLOT_NAME\x05:00.0 SHLVL=1
_=/usr/bin/env)
Jan 22 02:20:36 agate cardmgr[437]: no product info available
# pci module vendor device subvendor subdevice class
class_mask driver_data
ohci1394 0xffffffff 0xffffffff 0xffffffff 0xffffffff
0x000c0010 0x00ffffff 0x00000000
It looks to me like something is hosed in creating this entry.
We don't want the vendor/device IDs to be "0xffffffff 0xffffffff",
do we? How are those values getting into the modules.pcimap file?
Also interesting is the fact that during the boot process,
my 3c575 cardbus ethernet PC Card was noticed, but no hotplug
events happened for it:
Jan 22 02:12:50 agate kernel: Yenta IRQ list 0698, PCI irq11
Jan 22 02:12:51 agate kernel: Socket status: 30000068
Jan 22 02:12:51 agate kernel: Yenta IRQ list 0698, PCI irq11
Jan 22 02:12:51 agate kernel: Socket status: 30000006
Jan 22 02:12:51 agate kernel: devfs: v0.102 (20000622) Richard Gooch
(rgooch@atnf.csiro.au)
Jan 22 02:12:51 agate kernel: devfs: devfs_debug: 0x0
Jan 22 02:12:51 agate kernel: devfs: boot_options: 0x2
Jan 22 02:12:51 agate kernel: cs: cb_alloc(bus 1): vendor 0x10b7, device
0x5157
Jan 22 02:12:52 agate kernel: got res[1000:107f] for resource 0 of PCI
device 10b7:5157
Jan 22 02:12:52 agate kernel: got res[10800000:1080007f] for resource
1 of PCI device 10b7:5157
Jan 22 02:12:52 agate kernel: got res[10800080:108000ff] for resource
2 of PCI device 10b7:5157
Jan 22 02:12:52 agate kernel: got res[10400000:1041ffff] for resource
6 of PCI device 10b7:5157
Jan 22 02:12:52 agate kernel: PCI: Enabling device 01:00.0 (0000 -> 0003)
Jan 22 02:12:52 agate kernel: PCI: No IRQ known for interrupt pin A of
device 01:00.0.
Instead, when I loaded the driver by hand, the hotplug event got
triggered:
Jan 22 02:22:23 agate kernel: 3c59x.c:LK1.1.12 06 Jan 2000 Donald
Becker and others. http://www.scyld.com/network/vortex.html $Revision:
1.102.2.46 $
Jan 22 02:22:23 agate kernel: See Documentation/networking/vortex.txt
Jan 22 02:22:23 agate kernel: eth0: 3Com PCI 3CCFE575BT Cyclone CardBus
at 0x1000, PCI: Setting latency timer of device 01:00.0 to 64
Jan 22 02:22:23 agate kernel: 00:10:4b:7c:9d:9d, IRQ 11
Jan 22 02:22:23 agate kernel: product code 'NV' rev 07.1 date 06-09-98
Jan 22 02:22:23 agate kernel: eth0: CardBus functions mapped
10800080->c5a53080
Jan 22 02:22:23 agate kernel: 8K byte-wide RAM 5:3 Rx:Tx split, MII
interface.
Jan 22 02:22:23 agate kernel: MII transceiver found at address 0,
status 782d.
Jan 22 02:22:23 agate kernel: Enabling bus-master transmits and
whole-frame receives.
Jan 22 02:22:23 agate /sbin/hotplug: arguments (net) env
(ACTION=register TERM=dumb HOSTTYPE=i386
PATH=/bin:/sbin:/usr/sbin:/usr/bin HOME=/ SHELL=/bin/bash DEBUG=yes
INTERFACE=eth0 OSTYPE=Linux SHLVL=1 _=/usr/bin/env)
Jan 22 02:22:23 agate kernel: eth0: using default media MII
Here is the modules.pcimap line that shows that there should have been a
match:
3c59x 0x000010b7 0x00005157 0xffffffff 0xffffffff
0x00000000 0x00000000 0x0000001a
Lastly, I am getting a SCSI hotplug error early in the boot cycle.
Jan 22 02:12:47 agate kernel: request_module[scsi_hostadapter]: Root
fs not mounted
I thought this was fixed?
Miles
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2001-01-22 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-22 10:51 Miles Lane [this message]
2001-01-22 11:11 ` Can't hotplug two cardbus devices -- a 3c575 ethernet adapter and a Andrew Morton
2001-01-22 18:50 ` Miles Lane
2001-01-22 23:26 ` Can't hotplug two cardbus devices -- a 3c575 ethernet adapter David Brownell
2001-01-23 0:10 ` Miles Lane
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=marc-linux-hotplug-98016069100543@msgid-missing \
--to=miles@megapathdsl.net \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).