From: Matthias Urlichs <smurf@smurf.noris.de>
To: linux-kernel@vger.kernel.org
Subject: Kernel hangs on PCI config register access ???
Date: Fri, 18 Feb 2005 08:49:58 +0100 [thread overview]
Message-ID: <pan.2005.02.18.07.49.57.620452@smurf.noris.de> (raw)
Hi,
we have a bunch of systems which semi-reproducibly (chance of 1:1000) hang
when a PCMCIA card is removed from its PCI->PCMCIA interface via "cardctl
eject". Right *here*, in fact:
static int pci_conf1_read (int seg, int bus, int devfn, int reg, int
len, + u32 *value) {
[...]
case 2:
debug("you see me \n");
*value = inw(0xCFC + (reg & 2));
debug("but you don't get here \n");
break;
[...]
Does anybody have *any* idea what could possibly be the cause of this?
Using pci=bios still hangs; pci=conf2 doesn't work.
FWIW, the call sequence is:
shutdown_socket
yenta_sock_init
yenta_clear_maps
yenta_set_socket
pci_bus_read_config_word
pci_conf1_read
The systems in question are wildly different (VIA vs. Intel CPUs, standard
mainboard vs. PCI backplane, Ricoh vs. ENE cardbus bridges), so I'm
inclined to rule out hardware problems. The NMI monitor doesn't trigger
(yes I tested it), kgdb is unresponsive -- the system hangs hard at that
point, as far as I can determine.
Kernel: tested with various 2.6.1? plus -rc* and/or -mm*, no change.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
next reply other threads:[~2005-02-18 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 7:49 Matthias Urlichs [this message]
2005-03-07 21:26 ` Adam Belay
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=pan.2005.02.18.07.49.57.620452@smurf.noris.de \
--to=smurf@smurf.noris.de \
--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
all inboxes | Powered by JetHome®