From: David Ford <david@blue-labs.org>
To: linux-kernel@vger.kernel.org
Subject: 2.4.5+ hangs on boot
Date: Sat, 14 Jul 2001 16:39:41 -0400 [thread overview]
Message-ID: <3B50AE0D.80002@blue-labs.org> (raw)
Ok, aic7xxx hang solved on one machine with APIC solution
Ok, sched.c hang solved on another machine with patch.
However that patch doesn't solve everything and there are a few other
places where things hang.
*) I20 hangs in the middle of I20 init on -every- system I have from 586
to pIII in recent kernels
*) something hangs just after floppy init, last line is FDC0...
The FDC is immediately prior to where I2O inits so possibly the hang is
actually just following FDC/I2O? Normal boot messages should be like this:
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Loading I2O Core - (c) Copyright 1999 Red Hat Software
Linux I2O PCI support (c) 1999 Red Hat Software.
i2o: Checking for PCI I2O controllers...
I2O configuration manager v 0.04.
(C) Copyright 1999 Red Hat Software
I2O Block Storage OSM v0.9
(c) Copyright 1999-2001 Red Hat Software.
i2o_block: Checking for Boot device...
i2o_block: Checking for I2O Block devices...
I2O LAN OSM (C) 1999 University of Helsinki.
early initialization of device teql0 is deferred
loop: loaded (max 8 devices)
Linux Tulip driver version 0.9.15-pre3 (June 1, 2001)
PCI: Found IRQ 5 for device 00:10.0
Any comments or suggestions? 2.4.5-ac19 is the last kernel I have that
works.
David
next reply other threads:[~2001-07-14 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-14 20:39 David Ford [this message]
2001-07-14 22:11 ` [found-not fixed] Re: 2.4.5+ hangs on boot David Ford
2001-07-15 0:56 ` [PATCH] " David Ford
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=3B50AE0D.80002@blue-labs.org \
--to=david@blue-labs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.