From: Greg from Systems <chandler@d2.com>
To: John Jasen <jjasen1@umbc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bummer...
Date: Wed, 31 Jan 2001 20:51:37 -0800 [thread overview]
Message-ID: <Pine.SGI.4.10.10101311933320.29904-100000@hell.d2.com> (raw)
In-Reply-To: <Pine.SGI.4.31L.02.0101312218130.32454-100000@irix2.gl.umbc.edu>
This is the kind of problem I have been experiancing.
It either hangs on boot, or in a compile...
However I am using an NCR 810 and a scsi disk..
My board is the Compaq PC164 {some nasty partnumber}
The Servers all have the Qlogic ISP controller for the main disk.
both setups have only the boot disk on the boot controller, no other
devices....
On Wed, 31 Jan 2001, John Jasen wrote:
> On Wed, 31 Jan 2001, Greg from Systems wrote:
>
> > I've been playing with the 2.4.0 kernel scince you gave me the patch for
> > the alphas...
> >
> > What I have found is that it tends to randomly hang...
> > No Panic, no OOPs, no nothing...
> > The machine is a PC164, Which falls under the EB164 class.
> > It exhibits this behaviour on both the "generic" and "eb164" cpu types
> > {compile option} It doesn't even boot compiled as pc164..
> > I'm also seeing this problem on my A/S 4100, "Rawhide"..
>
> I've been having IDE problems under alpha (API UP1100 motherboard) with
> the ALI M1535D pci-isa bridge/ide controller and the AIC7xxx drivers.
> Under 2.4.0, any heavy disk access "dd if=/dev/hda of=/dev/null" will
> immediately lock the system, and under 2.4.1, it won't finish booting ...
>
> --
> -- John E. Jasen (jjasen1@umbc.edu)
> -- In theory, theory and practise are the same. In practise, they aren't.
>
----------------------------------------------------------------------------
IGNOTUM PER IGNOTIUS
"Grasshopper always wrong in argument with chicken"
The "socratic approach" is what you call starting an argument by
asking questions.
The human race will begin solving it's problems on the day that it
ceases taking itself so seriously.
PRINCIPIA DISCORDIA
Published by POEE Head Temple - San Francisco
" On The Future Site of Beautiful
San Andreas Canyon"
Please do not use this
document as toilet tissue
Fnord
-
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:[~2001-02-01 4:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 21:22 Big Bada Boom Greg from Systems
2001-01-24 13:23 ` Peter Rival
2001-01-24 18:21 ` Ivan Kokshaysky
2001-01-25 3:02 ` Greg from Systems
2001-01-25 3:12 ` Greg from Systems
2001-01-25 4:34 ` Las message I promise Greg from Systems
2001-01-25 11:07 ` Ivan Kokshaysky
2001-01-31 23:15 ` Bummer Greg from Systems
2001-02-01 3:20 ` Bummer John Jasen
2001-02-01 4:51 ` Greg from Systems [this message]
2001-02-01 0:07 ` Grr Greg from Systems
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=Pine.SGI.4.10.10101311933320.29904-100000@hell.d2.com \
--to=chandler@d2.com \
--cc=jjasen1@umbc.edu \
--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®