Kernel hang with Jaz

[Eric Towers]

-----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@xxxxxxxxxxx
-----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-----


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/