From: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Linux-2.4.2-ac27 - read on /proc/bus/pci/devices never finishes after rmmod aic7xxx
Date: Wed, 28 Mar 2001 20:16:38 -0600 [thread overview]
Message-ID: <3AC29B06.16A7C987@mnsu.edu> (raw)
Hello,
I'm using Linux-2.4.2-ac27 SMP compiled with gcc version 2.95.2 20000220
(Debian GNU/Linux).
After an "insmod aic7xxx" "cat /proc/bus/pci/devices" works just fine.
After an "rmmod aic7xxx" "cat /proc/bus/pci/devices" fails to produce
any output and never finishes. Top show the process in R state taking
as much CPU as it can get.
Killing the process doesn't do anything, rebooting is the only way to
get rid of it. This problem does not happen with aic7xxx_old.
Strace shows a "read" on the fd of /proc/bus/pci/devices that never
finishes.
My aic7xxx devices as reported by "lspci -vvv":
00:12.0 SCSI storage controller: Adaptec AIC-7881U (rev 01)
Subsystem: Adaptec: Unknown device 7881
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 8 min, 8 max, 64 set, cache line size 08
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at e800 [size=256]
Region 1: Memory at febff000 (32-bit, non-prefetchable)
[size=4K]
Expansion ROM at febe0000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- AuxPwr- DSI+ D1- D2- PME-
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
--
jeffrey hundstad
minnesota state university, mankato
mankato, mn
usa
next reply other threads:[~2001-03-29 2:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 2:16 Jeffrey Hundstad [this message]
2001-03-29 3:20 ` Justin T. Gibbs
2001-03-29 3:39 ` Jeffrey Hundstad
2001-03-29 3:59 ` Justin T. Gibbs
2001-03-29 4:21 ` Alan Cox
2001-03-29 5:13 ` Justin T. Gibbs
2001-03-29 5:31 ` Jeffrey Hundstad
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=3AC29B06.16A7C987@mnsu.edu \
--to=jeffrey.hundstad@mnsu.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--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®