On Mon, 28 Jan 2008 08:46:25 +0100
Christof Schmitt [EMAIL PROTECTED] wrote:
On Sun, Jan 27, 2008 at 12:41:50PM +0900, FUJITA Tomonori wrote:
The commit de25deb18016f66dcdede165d07654559bb332bc changed
scsi_cmnd.sense_buffer from a static array to a dynamically allocated
buffer. We can't
On Mon, Jan 28, 2008 at 06:29:12PM +0900, FUJITA Tomonori wrote:
ACK for fixing the access to the sense buffer.
We are working internally on cleaning up the zfcp messages. With this
change, the 'trace' and 'hex dump' messages will disappear. So, could
you simply remove the ZFCP_HEX_DUMP
On Mon, 2008-01-28 at 11:04 +0100, Christof Schmitt wrote:
On Mon, Jan 28, 2008 at 06:29:12PM +0900, FUJITA Tomonori wrote:
ACK for fixing the access to the sense buffer.
We are working internally on cleaning up the zfcp messages. With this
change, the 'trace' and 'hex dump'
drivers/scsi/aic7xxx_old/sequencer.h:130:#define AIC_OP_JZ 0xf
--
Test opcode, not definition
Signed-off-by: Roel Kluin [EMAIL PROTECTED]
---
diff --git a/drivers/scsi/aic7xxx/aicasm/aicasm_gram.y
b/drivers/scsi/aic7xxx/aicasm/aicasm_gram.y
index 6066998..702e2db 100644
---
Hi,
This is my first message on this list.
The problem I'm facing are several messages of the form
Jan 28 06:49:17 [kernel] (scsi0:A:0:0): Unexpected busfree in Data-out phase
Jan 28 06:49:17 [kernel] SEQADDR == 0x86
generated by the aic7xxx driver running my Adaptec 29160.
I get a lot of
Merde, this patch caused a problem with a system lockup. Please revert it.
Sincerely -- Mark Salyzyn
-Original Message-
From: James Bottomley [mailto:[EMAIL PROTECTED]
Sent: Friday, January 25, 2008 12:05 PM
To: [EMAIL PROTECTED]; Salyzyn, Mark; James Bottomley; AACRAID
Subject:
On Mon, Jan 28, 2008 at 09:49:35PM +0100, Jens Axboe wrote:
Hi,
Running latest -git (head 91525300baf162e83e923b09ca286f9205e21522) and
connecting my cf usb storage device yields and endless stream of:
Initializing USB Mass Storage driver...
scsi6 : SCSI emulation for USB Mass Storage
__iscsi_complete_pdu() can now become static.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
drivers/scsi/libiscsi.c |5 ++---
include/scsi/libiscsi.h |2 --
2 files changed, 2 insertions(+), 5 deletions(-)
4d4f211556f92590bfc32a243f562853c499b314
diff --git
James,
I am facing issues with device removal being done when there
are commands outstanding in the LLD. As explained in my original post,
its resulting in effects ranging from the duplicate kobject warnings to
the inability of the scsi subsystem to find a valid device (all symptoms
are
The first patch was a bit too aggressive and nested the locks (!) unit testing
was in error.
Signed-off-by: Mark Salyzyn [EMAIL PROTECTED]
drivers/scsi/aacraid/commctrl.c | 26 ++
1 file changed, 14 insertions(+), 12 deletions(-)
Sincerely -- Mark Salyzyn
We've got a bit of a problem with the sata_nv driver that I'm trying to
figure out a decent solution to (hence all the lists CCed). This is the
situation:
The nForce4 ADMA hardware has 2 modes: legacy mode, where it acts like a
normal ATA controller with 32-bit DMA limits, and ADMA mode where
On Jan 29, 2008 11:08 AM, Robert Hancock [EMAIL PROTECTED] wrote:
...
The last solution I tried was to set the DMA mask on both ports to
32-bit on slave_configure when an ATAPI device is connected. However,
this runs into complications as well. This is run on initialization and
when trying to
The ideal solution would be to do mapping against a different struct
device for each port, so that we could maintain the proper DMA mask for
each of them at all times. However I'm not sure if that's possible.
I cannot imagine why it should be that difficult. The PCI subsystem
could over a
On Mon, Jan 28 2008, Greg KH wrote:
On Mon, Jan 28, 2008 at 09:49:35PM +0100, Jens Axboe wrote:
Hi,
Running latest -git (head 91525300baf162e83e923b09ca286f9205e21522) and
connecting my cf usb storage device yields and endless stream of:
Initializing USB Mass Storage driver...
14 matches
Mail list logo
