From: Andreas Dilger <adilger@turbolinux.com>
To: "Mike A. Harris" <mharris@opensourceadvocate.org>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.2.18 dies on my 486..
Date: Wed, 27 Dec 2000 18:13:30 -0700 (MST) [thread overview]
Message-ID: <200012280113.eBS1DUD00873@webber.adilger.net> (raw)
In-Reply-To: <Pine.LNX.4.31.0012220359540.666-100000@asdf.capslock.lan> "from Mike A. Harris at Dec 27, 2000 08:05:25 pm"
Mike Harris writes:
> I just upgraded my 486 firewall's kernel to pure 2.2.18 from
> 2.2.17, with no other changes, and now it dies with all sorts
> of hard disk failures.
>
> I get:
>
> hdb: lost interrupt
>
> And stuff about DRQ lost...
Is it possible you compiled the kernel with gcc 2.95.2? I've been having
a similar problem, but I'm having trouble tracking it down. Because I
normally use a very heavily modified 2.2.18 kernel, I'm trying to isolate
just where the problem is - I have no problems with a stock 2.2.18 kernel.
If I compile with gcc 2.7.2.3 it works fine.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-28 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-28 1:05 2.2.18 dies on my 486 Mike A. Harris
2000-12-28 1:13 ` Andreas Dilger [this message]
2000-12-28 2:15 ` Mike A. Harris
2000-12-28 2:35 ` Alan Cox
2000-12-29 0:09 ` Mike A. Harris
2000-12-29 8:14 ` Vid Strpic
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=200012280113.eBS1DUD00873@webber.adilger.net \
--to=adilger@turbolinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mharris@opensourceadvocate.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