From: Florian Lohoff <flo@rfc822.org>
To: linux-kernel@vger.kernel.org
Subject: pcmcia ide (CF adapter) and exit resource munging
Date: Mon, 27 Aug 2001 17:28:36 +0200 [thread overview]
Message-ID: <20010827172836.A7779@paradigm.rfc822.org> (raw)
Hi,
with 2.4.8 + pcmcia-cs modules 3.1.27 i see the problem that i put a
CF Card with the pcmcia adapter into the pcmcia slot - It gets detected
corrent and i mount the drive/vfat partition. Then i eject the card
(without unmounting) and the "virtual ide controller" does not get freed.
All processes still accessing the drive get killed which is completely ok
Means - the next time i insert a CF Card/Microdrive with the adapter
it does not get hde it gets hdg and so forth. It seems the driver
never realizes the controller has been gone.
[ ... dmesg output ... ]
hde: CFA, ATA DISK drive
ide2 at 0x100-0x107,0x10e on irq 5
hde: 128128 sectors (66 MB) w/4KiB Cache, CHS=1001/4/32
hde: hde1
ide_cs: hde: Vcc = 3.3, Vpp = 0.0
VFS: Disk change detected on device ide2(33,1)
hde: hde1
VFS: Disk change detected on device ide2(33,1)
hde: hde1
VFS: Disk change detected on device ide2(33,1)
hde: hde1
VFS: Disk change detected on device ide2(33,1)
hde: hde1
ide2: unexpected interrupt, status=0xff, count=2
Trying to free nonexistent resource <00000100-0000010f>
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,1)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
hdg: IBM-DSCM-11000, ATA DISK drive
ide3 at 0x110-0x117,0x11e on irq 10
hdg: 2104704 sectors (1078 MB) w/60KiB Cache, CHS=2088/16/63
hdg: [PTBL] [522/64/63] hdg1
ide_cs: hdg: Vcc = 3.3, Vpp = 0.0
VFS: Disk change detected on device ide3(34,1)
hdg: hdg1
VFS: Disk change detected on device ide3(34,1)
hdg: hdg1
VFS: Disk change detected on device ide3(34,1)
hdg: hdg1
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
VFS: Disk change detected on device ide2(33,0)
hde:hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
hde: drive not ready for command
ide2: reset timed-out, status=0xff
hde: status timeout: status=0xff { Busy }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
unable to read partition table
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
reply other threads:[~2001-08-27 15:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010827172836.A7779@paradigm.rfc822.org \
--to=flo@rfc822.org \
--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®