From: Paul Flinders <paul@dawa.demon.co.uk>
To: linux-kernel@vger.kernel.org
Subject: IDE "lost interrupt" on SMP
Date: Thu, 26 Jul 2001 00:01:30 +0100 [thread overview]
Message-ID: <3B5F4FCA.EF860FF@dawa.demon.co.uk> (raw)
I decided to replace the Celerons on my Asus P2B-D with something
a little faster so I bought a new 1Ghz PIII** (it would have been two but
the local dealer only had one in stock).
However I can't boot any SMP configured kernel. It gets as far as
the partition check and then starts printing "hd<x>: lost interrupt"
after than it proceeds _very_ slowly to print the partitions and
then grinds to a halt as it tries to mount the root fs (I suspect that
it hasn't actually crashed but that disk I/O is proceeding extremely
slowly).
Configuring the kernel for single processor works and boots OK
- this is true for all the kernels (2.2.x and 2.4.x including 2.4.7)
that I've tried.
I thought that SMP kernels were OK with just one processor. Do
I need to add the second one or could there be something else
wrong.
** Actually underclocked at 750Mhz as the BX chipset only goes to
100 Mhz FSB
next reply other threads:[~2001-07-25 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 23:01 Paul Flinders [this message]
2001-07-26 12:10 ` IDE "lost interrupt" on SMP Zdenek Kabelac
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=3B5F4FCA.EF860FF@dawa.demon.co.uk \
--to=paul@dawa.demon.co.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