Re: 2.2.0pre7ac7/pre8ac1, writing to /dev/sg? from XCDRoast

Alex Butche (linkern@cocoa.demon.co.uk)
Thu, 21 Jan 1999 20:05:42 +0000 (GMT)


On Tue, 19 Jan 1999, I wrote:

> Hi -
>
> When I start XCDroast 0.96e under kernel versions 2.2.0pre7ac7 or pre8ac1, it
> hangs when it writes to /dev/sg1 after opening it O_RDWR:
>
> open("/dev/sg0", O_RDWR) = 4
> write(4, "*\0\0\0\204\0\0\0\0\0\0\0\0\0\0\0"..., 42) = 42
> read(4, "\204\0\0\0\204\0\0\0\0\0\0\0\0\0"..., 132) = 132
> close(4) = 0
> open("/dev/sg1", O_RDWR) = 4
> write(4, "*\0\0\0\204\0\0\0\0\0\0\0\0\0\0\0"..., 42

I have now discovered the cause of the problem - compiling MULTI_LUN (why?
because Red Hat do it to make their kernels nice and generic and I use that
as a base mark) and IDESCSI emulation into the same kernel. Bad plan.

Sorry if I've wasted anyone's time. Alan. :)

May I suggest (against pre8ac1):

======================================================================
--- Configure.help.orig Thu Jan 21 19:52:15 1999
+++ Configure.help Thu Jan 21 19:57:52 1999
@@ -416,6 +416,10 @@

People with SCSI-only systems can say N here. If unsure, say N.

+ This option MUST NOT be used with CONFIG_SCSI_MULTI_LUN (which
+ forces the kernel to probe all LUNs on each SCSI device) as it
+ will cause many operations to fail.
+
CMD640 chipset bugfix/support
CONFIG_BLK_DEV_CMD640
The CMD-Technologies CMD640 IDE chip is used on many common 486 and
@@ -3555,6 +3559,10 @@
devices. The vast majority of SCSI devices have only one LUN, and
so most people can say N here and should in fact do so, because it
is safer.
+
+ This option MUST NOT be used with CONFIG_BLK_DEV_IDESCSI (which
+ provides SCSI emulation for ATAPI drives) as it will cause
+ many operations to fail.

Verbose SCSI error reporting (kernel size +=12K)
CONFIG_SCSI_CONSTANTS
======================================================================

Best Regards,
Alex.

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