From: Eric Towers <etowers@nomadics.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel hang with Jaz
Date: Wed, 17 Dec 2003 21:16:55 -0600 [thread overview]
Message-ID: <3FE11C27.8000107@nomadics.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have (re-)discovered a problem with vectoring from LILO to the Linux
kernel (2.4.x). When there is no cartridge in my Jaz drive, LILO will
load and uncompress the kernel, then hang. Cartridge in Jaz: LILO
successfully vectors to the kernel.
This does not appear to be a well documented problem. I found
references on a Linux PPC page. Then (finally) section 6.6 of
http://packetstormsecurity.nl/linux/admin/Mini-HOWTOs-FAQs/Jaz-Drive
(The Mini-HOWTOs appear to have generally vanished from the obvious
sources.) This reference states
<quote>
6.6. What happens if there is no disk inserted when I boot ?
The kernel will try to read the partition table, but the operation
will (eventually) time out.
When you change disks, it is a good idea always to use fsck to
check the partition structure on the new disk.
The BIOS on some SCSI host adapters will attempt to read the partition
table on your disk during the system boot. If you cannot disable this
check, you may be forced always to boot with a disk in the drive.
</quote>
I have not observed a timeout. I have left this machine idle for a
week. (I was going on vacation, so this wasn't a significant burden.)
Turning the Jaz drive off to ensure that I can't use it under Linux is
also a workaround (of no utility).
The reference describes a workaround that will accelerate the death of
the inserted cartridge. How can I help fix this (not a programmer)? or
help champion fixing it?
- --
~ -- Eric Towers ! fuzzyeric@bigfoot.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/4RwnEJrYj/1UkJARAuPDAJ0XAbu6LsopNGUBCw+ZpAUAR4yIBACggZgv
C5U1RkFj3zQippngOjtu63A=
=/pr7
-----END PGP SIGNATURE-----
reply other threads:[~2003-12-18 3:17 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=3FE11C27.8000107@nomadics.com \
--to=etowers@nomadics.com \
--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