;
+
+ /*
+ * Should probably precede any commands to change power mode with
+ * CHECK POWER MODE to see what the current state of the device is.
+ * The patch author does not know how to do this.
+ * D. Gilbert 20050731
+ */
+ tf-flags |= ATA_TFLAG_DEVICE | ATA_TFLAG_ISADDR;
+ tf-protocol = ATA_PROT_NODATA
From: Marcelo Feitoza Parisi [EMAIL PROTECTED]
Use of the time_after() macro, defined at linux/jiffies.h, which deal
with wrapping correctly and are nicer to read.
Signed-off-by: Marcelo Feitoza Parisi [EMAIL PROTECTED]
Signed-off-by: Domen Puncer [EMAIL PROTECTED]
---
qlogicfc.c |3 ++-
On Sat, Jun 11, 2005 at 12:11:03AM +0100, Christoph Hellwig wrote:
is there a technical reason the PCI_DEVICE_ID_AMI_MEGARAID and
PCI_DEVICE_ID_AMI_MEGARAID2 cards are supported in the old
megraid driver, but not in megaraid_mbox? It would be a real
pain to keep the old driver around just for
On Sun, 24 Oct 2004, Olaf Hering wrote:
On Sun, Oct 24, James Bottomley wrote:
The trace doesn't show any error handler activity at all. Are there no
messages in the log about offlining the device? If not, it sounds like
there's a problem somewhere in the firewire system.
How should
On Sun, Jul 31, 2005 at 07:54:59PM +0200, Stefan Richter wrote:
Well, the LLD can _try_ it, but it may go horribly wrong.
It seems to work nicely for everyone but sbp2..
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More
Christoph Hellwig wrote:
On Sun, Jul 31, 2005 at 07:54:59PM +0200, Stefan Richter wrote:
Well, the LLD can _try_ it, but it may go horribly wrong.
It seems to work nicely for everyone but sbp2..
Sure. There is be probably something in sbp2 or nodemgr that leads
to a deadlock, although the
Patrick Mansfield wrote:
Do you have slab poisoning on (CONFIG_DEBUG_SLAB)?
No, not yet...
I reported the following problem, it looks like nodemgr had a similar
patch to change list_for_each_safe to device_for_each_child, but
device_for_each_child is not safe, see this thread:
On Sun, Jul 31, Dan Hollis wrote:
On Sun, 24 Oct 2004, Olaf Hering wrote:
On Sun, Oct 24, James Bottomley wrote:
The trace doesn't show any error handler activity at all. Are there no
messages in the log about offlining the device? If not, it sounds like
there's a problem
The SCSI qlogicisp driver is both marked BROKEN and superseded by the
qla1280 driver.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
This patch was already sent on:
- 22 Jul 2005
Due to it's size, the patch is attached compressed.
Documentation/scsi/00-INDEX |2
Patrick Mansfield wrote:
device_for_each_child is not safe, see this thread:
http://marc.theaimsgroup.com/?t=11193154112r=1w=2
...
I think DEBUG_SLAB will catch any use after frees there.
...
I tested with CONFIG_DEBUG_SLAB now. Nothing showed up.
--
Stefan Richter
-=-=-=-= -===
When a FireWire CD-ROM or RBC harddisk was detached, the ieee1394
subsystem and probably the scsi subsystem was locked up. The fix
unblocks the sbp2 host before attempting to remove scsi devices.
Commands from scsi highlevel are no longer blocked, but rather
completed with DID_NO_CONNECT when the
On 31 Jul, Olaf Hering wrote:
On Sun, Jul 31, Dan Hollis wrote:
On Sun, 24 Oct 2004, Olaf Hering wrote:
On Sun, Oct 24, James Bottomley wrote:
The trace doesn't show any error handler activity at all. Are there no
messages in the log about offlining the device? If not, it sounds like
Document a pitfall of scsi_block_requests() and hot-unplugging.
Signed-off-by: Stefan Richter [EMAIL PROTECTED]
diff -rU 5 linux-2.6.13-rc4.orig/Documentation/scsi/scsi_mid_low_api.txt
linux-2.6.13-rc4/Documentation/scsi/scsi_mid_low_api.txt
---
I wrote on 2005-07-23:
Problem 1) Hot unplugging of SBP-2 hangs ieee1394's nodemgr when *sd_mod*
was attached to the SBP-2 device. I have seen this problem since RBC
handling was moved from sbp2 to sd_mod.
Problem 2) Hot unplugging of SBP-2 hangs ieee1394's nodemgr when *sr_mod*
was attached to
14 matches
Mail list logo
