Andre Hedrick writes:
> That is not the case Joanne is pointing out.
> The SCSI low-level format glue performed by the HOST gets destroyed
> If you write to LBA Zero. ATA only suffers the lose of the partition
> table and that can be recovered, but SCSI needs that information to know
> where eve
Well, this doesn't help you much, but it's working here, and I also
have the adaptec driver loaded.
On Wed, Mar 07, 2001 at 12:32:27PM +0100, [EMAIL PROTECTED] wrote:
>
>
> Hi,
>
> is there somebody looking after the qlogicfc driver?
> It seems to be broken in kernel version 2.4.2 and
> later
Oliver Neukum wrote:
>
> Hi,
>
> I think there's a small window during which a low level driver can be
> unloaded while sg_open() is executing.
> The attached patch should fix it by incrementing the usage counter before
> sg_open() might sleep.
Oliver,
Yes that should be done. I intend to make
Oliver Neukum wrote:
>
> Hi,
>
> I was thinking about power management and the sg driver.
> Shouldn't the sg driver block any request for putting the system to sleep
> while and sg devices are open ?
Oliver,
Have you any idea how the sg driver could stop that?
That seems a little outside the re
Rogier Wolff wrote:
>
> Kurt Garloff wrote:
> > > A simple test shows that the module count is working for
> > > the sg driver. So it seems as if open() calls to char
> > > devices do an auto module count increment. However I
> > > was unable to find the code that does this (e.g. no sign
> > > of
its being set in the detect routine.I missed that.
Sorry for the inconvenience.
Thanks
--- rakesh rakesh <[EMAIL PROTECTED]> wrote:
> Hi List,
>
> To my knowledge to convert a low level driver to use
> the new error handling code one needs to define the
> new
> error handling points(at least on
>> When I try to load it, I get the following messages:
>> /lib/modules/2.4.3-pre2/kernel/drivers/scsi/qlogicfc.o: init_module: No
>> such device
>> Hint: insmod errors can be caused by incorrect module parameters,
including
>> invalid IO or IRQ parameters
>> /lib/modules/2.4.3-pre2/kernel/driv
> When I try to load it, I get the following messages:
> /lib/modules/2.4.3-pre2/kernel/drivers/scsi/qlogicfc.o: init_module: No
> such device
> Hint: insmod errors can be caused by incorrect module parameters, including
> invalid IO or IRQ parameters
> /lib/modules/2.4.3-pre2/kernel/drivers/scsi
Kurt Garloff wrote:
> > A simple test shows that the module count is working for
> > the sg driver. So it seems as if open() calls to char
> > devices do an auto module count increment. However I
> > was unable to find the code that does this (e.g. no sign
> > of it in fs/devices.c).
> >
> > Perh
On Tue, Mar 06, 2001 at 12:30:08PM -0500, Douglas Gilbert wrote:
> Oliver Neukum wrote:
> > where is the usage count of the sg module increased ?
> > I looked at sg_open , but only the count of the low level driver
> > is increased.
>
> Good question. The code to do that was stripped out of
> sg_
Hi,
is there somebody looking after the qlogicfc driver?
It seems to be broken in kernel version 2.4.2 and
later (2.4.3-pre2).
When I try to load it, I get the following messages:
/lib/modules/2.4.3-pre2/kernel/drivers/scsi/qlogicfc.o: init_module: No
such device
Hint: insmod errors can be ca
Hi, anybody
Currently I'm again frustrated about the fact, that
scsi_ioctl_send_command() only returns 16 Bytes of sense information.
I know this interface is deprecated, but I cannot use sg instead.
I want to poll a SCSI drive busy formatting a medium with TEST_UNIT_READY
from a kernel thread w
12 matches
Mail list logo
