From: "Howard The Duck" <h.t.d@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: "Disabling IRQ #18" when mounting cdrom with SATA on 2.6.0beta7/8?
Date: Sat, 18 Oct 2003 22:25:03 +0200 [thread overview]
Message-ID: <3F91BDBF.14789.17CDF8A@localhost> (raw)
Hi
I had troubles with the 2.6 series using devfs and my SATA drive, i got the "Disabling
irq #18" message on boot. I removed devfs support and the machine worked flawless,
until i mounted a cdrom. I very seldom need to access cdroms or dvds that's why i
never saw this happening within the last few month of kernel installing (starting with
2.5.74 in June because 2.4.21 and 2.4.22 wouldn't boot at all).
When i do not mount cdroms or enable devfs support in the kernel the system is
running very stable and fast. My troubles with devfs are described here
http://www.ussg.iu.edu/hypermail/linux/kernel/0310.1/0874.html
My current setup has no devfs support, but i get the "Disabling IRQ #18" message
right after the moment i mounted a cdrom/dvd with my dvd-drive or a cdrom with the
cd-writer. Accessing the PATA harddrives seems to have no negative effect, although i
can only test them by reading data because they are NTFS partitions and mounted
read-only. Even when i unmount the CDrom the "Disabling IRQ #18" message keeps
on appearing. It slows down my system to unusable speed (e.g.: it takes approx 4
minutes to shut the system down).
I think the devfs thingy triggers the "Disabling IRQ #18" problem when it tests for
"existing" optical media drives on boot. I think so because the same message appears
when i access cdroms manually.
I have no access to a second system with SATA support to verify or reproduce that
behaviour, can anybody else do that on another machine? Also i'd be interested in how
this problem could be tracked down to its root. I reproduced that with 2.6.0beta7 and
beta8, the only kernels currently left on my machine ;)
thanks in advance for any hints
HTD
p.s.: i'm not subscribed to lkml, please send me a CC when answering.
reply other threads:[~2003-10-18 20:24 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=3F91BDBF.14789.17CDF8A@localhost \
--to=h.t.d@gmx.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;
as well as URLs for NNTP newsgroup(s).