* [PATCH] fix sym2 negotiation
@ 2004-08-21 18:37 James Bottomley
2004-08-22 17:32 ` Matthias Andree
` (2 more replies)
0 siblings, 3 replies; 20+ messages in thread
From: James Bottomley @ 2004-08-21 18:37 UTC (permalink / raw)
To: willy; +Cc: SCSI Mailing List
The problems with domain validation were just the tip of the iceberg in
the sym2 driver. Most of its problems seem to come from an overly
complex set of negotiating rules, which I've swept away with this patch.
I also removed the ability to set parameters in the on-board bios and
have the driver respect them. (this hasn't worked for a while in 2.6
because after the driver sets them, Domain Validation resets them
again).
Finally, there was a really nasty bug where the driver negotiates
improperly when turning off DT clocking. If you simply turn it off, the
driver originally fell back to using the old WDTR/SDTR method of
negotiation. However, since it thought the bus was already wide, it
only emitted a SDTR, which causes the device to reset from wide to
narrow. Hence the driver thinks the device is wide and the device
thinks it is narrow => boom.
I redid the negotiation to predicate PPR messages on whether the device
claims support for them or not.
Finally, all this is dependent on the new inquiry getting macros of a
previous patch.
James
sym_glue.c | 119 ++++++----------------------------------------------------
sym_glue.h | 8 +++
sym_hipd.c | 122 ++++++++++++++++++++++++++++++++----------------------------
sym_hipd.h | 40 -------------------
sym_misc.c | 118 ----------------------------------------------------------
sym_nvram.c | 16 -------
6 files changed, 88 insertions(+), 335 deletions(-)
===== drivers/scsi/sym53c8xx_2/sym_hipd.c 1.20 vs edited =====
--- 1.20/drivers/scsi/sym53c8xx_2/sym_hipd.c 2004-08-21 09:27:03 -07:00
+++ edited/drivers/scsi/sym53c8xx_2/sym_hipd.c 2004-08-21 11:17:09 -07:00
@@ -1038,28 +1038,11 @@
for (i = 0 ; i < SYM_CONF_MAX_TARGET ; i++) {
tcb_p tp = &np->target[i];
- tp->tinfo.user.scsi_version = tp->tinfo.curr.scsi_version= 2;
- tp->tinfo.user.spi_version = tp->tinfo.curr.spi_version = 2;
- tp->tinfo.user.period = np->minsync;
- tp->tinfo.user.offset = np->maxoffs;
- tp->tinfo.user.width = np->maxwide ? BUS_16_BIT : BUS_8_BIT;
tp->usrflags |= (SYM_DISC_ENABLED | SYM_TAGS_ENABLED);
tp->usrtags = SYM_SETUP_MAX_TAG;
sym_nvram_setup_target (np, i, nvram);
- /*
- * Some single-ended devices may crash on receiving a
- * PPR negotiation attempt. Only try PPR if we're in
- * LVD mode.
- */
- if (np->features & FE_ULTRA3) {
- tp->tinfo.user.options |= PPR_OPT_DT;
- tp->tinfo.user.period = np->minsync_dt;
- tp->tinfo.user.offset = np->maxoffs_dt;
- tp->tinfo.user.spi_version = 3;
- }
-
if (!tp->usrtags)
tp->usrflags &= ~SYM_TAGS_ENABLED;
}
@@ -1493,6 +1476,55 @@
}
#endif
+static void sym_check_goals(struct scsi_device *sdev)
+{
+ struct sym_hcb *np = ((struct host_data *)sdev->host->hostdata)->ncb;
+ struct sym_trans *st = &np->target[sdev->id].tinfo.goal;
+
+ /* here we enforce all the fiddly SPI rules */
+
+ if (!scsi_device_wide(sdev))
+ st->width = 0;
+
+ if (!scsi_device_sync(sdev)) {
+ st->options = 0;
+ st->period = 0;
+ st->offset = 0;
+ return;
+ }
+
+ if (scsi_device_dt(sdev)) {
+ if (scsi_device_dt_only(sdev))
+ st->options |= PPR_OPT_DT;
+
+ if (st->offset == 0)
+ st->options &= ~PPR_OPT_DT;
+ } else {
+ st->options &= ~PPR_OPT_DT;
+ }
+
+ if (!(np->features & FE_ULTRA3))
+ st->options &= ~PPR_OPT_DT;
+
+ if (st->options & PPR_OPT_DT) {
+ /* all DT transfers must be wide */
+ st->width = 1;
+ if (st->offset > np->maxoffs_dt)
+ st->offset = np->maxoffs_dt;
+ if (st->period < np->minsync_dt)
+ st->period = np->minsync_dt;
+ if (st->period > np->maxsync_dt)
+ st->period = np->maxsync_dt;
+ } else {
+ if (st->offset > np->maxoffs)
+ st->offset = np->maxoffs;
+ if (st->period < np->minsync)
+ st->period = np->minsync;
+ if (st->period > np->maxsync)
+ st->period = np->maxsync;
+ }
+}
+
/*
* Prepare the next negotiation message if needed.
*
@@ -1504,6 +1536,10 @@
{
tcb_p tp = &np->target[cp->target];
int msglen = 0;
+ struct scsi_device *sdev = tp->sdev;
+
+ if (likely(sdev))
+ sym_check_goals(sdev);
/*
* Early C1010 chips need a work-around for DT
@@ -1514,19 +1550,21 @@
/*
* negotiate using PPR ?
*/
- if (tp->tinfo.goal.options & PPR_OPT_MASK)
+ if (scsi_device_dt(sdev)) {
nego = NS_PPR;
- /*
- * negotiate wide transfers ?
- */
- else if (tp->tinfo.curr.width != tp->tinfo.goal.width)
- nego = NS_WIDE;
- /*
- * negotiate synchronous transfers?
- */
- else if (tp->tinfo.curr.period != tp->tinfo.goal.period ||
- tp->tinfo.curr.offset != tp->tinfo.goal.offset)
- nego = NS_SYNC;
+ } else {
+ /*
+ * negotiate wide transfers ?
+ */
+ if (tp->tinfo.curr.width != tp->tinfo.goal.width)
+ nego = NS_WIDE;
+ /*
+ * negotiate synchronous transfers?
+ */
+ else if (tp->tinfo.curr.period != tp->tinfo.goal.period ||
+ tp->tinfo.curr.offset != tp->tinfo.goal.offset)
+ nego = NS_SYNC;
+ }
switch (nego) {
case NS_SYNC:
@@ -3995,7 +4033,6 @@
static int
sym_sync_nego_check(hcb_p np, int req, int target)
{
- tcb_p tp = &np->target[target];
u_char chg, ofs, per, fak, div;
if (DEBUG_FLAGS & DEBUG_NEGO) {
@@ -4015,19 +4052,11 @@
if (ofs) {
if (ofs > np->maxoffs)
{chg = 1; ofs = np->maxoffs;}
- if (req) {
- if (ofs > tp->tinfo.user.offset)
- {chg = 1; ofs = tp->tinfo.user.offset;}
- }
}
if (ofs) {
if (per < np->minsync)
{chg = 1; per = np->minsync;}
- if (req) {
- if (per < tp->tinfo.user.period)
- {chg = 1; per = tp->tinfo.user.period;}
- }
}
/*
@@ -4147,10 +4176,6 @@
}
if (!wide || !(np->features & FE_ULTRA3))
dt &= ~PPR_OPT_DT;
- if (req) {
- if (wide > tp->tinfo.user.width)
- {chg = 1; wide = tp->tinfo.user.width;}
- }
if (!(np->features & FE_U3EN)) /* Broken U3EN bit not supported */
dt &= ~PPR_OPT_DT;
@@ -4164,10 +4189,6 @@
}
else if (ofs > np->maxoffs)
{chg = 1; ofs = np->maxoffs;}
- if (req) {
- if (ofs > tp->tinfo.user.offset)
- {chg = 1; ofs = tp->tinfo.user.offset;}
- }
}
if (ofs) {
@@ -4177,10 +4198,6 @@
}
else if (per < np->minsync)
{chg = 1; per = np->minsync;}
- if (req) {
- if (per < tp->tinfo.user.period)
- {chg = 1; per = tp->tinfo.user.period;}
- }
}
/*
@@ -4282,7 +4299,6 @@
static int
sym_wide_nego_check(hcb_p np, int req, int target)
{
- tcb_p tp = &np->target[target];
u_char chg, wide;
if (DEBUG_FLAGS & DEBUG_NEGO) {
@@ -4301,10 +4317,6 @@
if (wide > np->maxwide) {
chg = 1;
wide = np->maxwide;
- }
- if (req) {
- if (wide > tp->tinfo.user.width)
- {chg = 1; wide = tp->tinfo.user.width;}
}
if (DEBUG_FLAGS & DEBUG_NEGO) {
===== drivers/scsi/sym53c8xx_2/sym_misc.c 1.4 vs edited =====
--- 1.4/drivers/scsi/sym53c8xx_2/sym_misc.c 2004-03-11 01:06:02 -08:00
+++ edited/drivers/scsi/sym53c8xx_2/sym_misc.c 2004-08-21 09:31:51 -07:00
@@ -216,121 +216,3 @@
#undef __tprev
#undef __tcurr
#endif /* SYM_OPT_ANNOUNCE_TRANSFER_RATE */
-
-
-#ifdef SYM_OPT_SNIFF_INQUIRY
-/*
- * Update transfer settings according to user settings
- * and bits sniffed out from INQUIRY response.
- */
-void sym_update_trans_settings(hcb_p np, tcb_p tp)
-{
- memcpy(&tp->tinfo.goal, &tp->tinfo.user, sizeof(tp->tinfo.goal));
-
- if (tp->inq_version >= 4) {
- switch(tp->inq_byte56 & INQ56_CLOCKING) {
- case INQ56_ST_ONLY:
- tp->tinfo.goal.options = 0;
- break;
- case INQ56_DT_ONLY:
- case INQ56_ST_DT:
- default:
- break;
- }
- }
-
- if (!((tp->inq_byte7 & tp->inq_byte7_valid) & INQ7_WIDE16)) {
- tp->tinfo.goal.width = 0;
- tp->tinfo.goal.options = 0;
- }
-
- if (!((tp->inq_byte7 & tp->inq_byte7_valid) & INQ7_SYNC)) {
- tp->tinfo.goal.offset = 0;
- tp->tinfo.goal.options = 0;
- }
-
- if (tp->tinfo.goal.options & PPR_OPT_DT) {
- if (tp->tinfo.goal.offset > np->maxoffs_dt)
- tp->tinfo.goal.offset = np->maxoffs_dt;
- }
- else {
- if (tp->tinfo.goal.offset > np->maxoffs)
- tp->tinfo.goal.offset = np->maxoffs;
- }
-}
-
-/*
- * Snoop target capabilities from INQUIRY response.
- * We only believe device versions >= SCSI-2 that use
- * appropriate response data format (2). But it seems
- * that some CCS devices also support SYNC (?).
- */
-int
-__sym_sniff_inquiry(hcb_p np, u_char tn, u_char ln,
- u_char *inq_data, int inq_len)
-{
- tcb_p tp = &np->target[tn];
- u_char inq_version;
- u_char inq_byte7;
- u_char inq_byte56;
-
- if (!inq_data || inq_len < 2)
- return -1;
-
- /*
- * Check device type and qualifier.
- */
- if ((inq_data[0] & 0xe0) == 0x60)
- return -1;
-
- /*
- * Get SPC version.
- */
- if (inq_len <= 2)
- return -1;
- inq_version = inq_data[2] & 0x7;
-
- /*
- * Get SYNC/WIDE16 capabilities.
- */
- inq_byte7 = tp->inq_byte7;
- if (inq_version >= 2 && (inq_data[3] & 0xf) == 2) {
- if (inq_len > 7)
- inq_byte7 = inq_data[7];
- }
- else if (inq_version == 1 && (inq_data[3] & 0xf) == 1)
- inq_byte7 = INQ7_SYNC;
-
- /*
- * Get Tagged Command Queuing capability.
- */
- if (inq_byte7 & INQ7_CMDQ)
- sym_set_bit(tp->cmdq_map, ln);
- else
- sym_clr_bit(tp->cmdq_map, ln);
- inq_byte7 &= ~INQ7_CMDQ;
-
- /*
- * Get CLOCKING capability.
- */
- inq_byte56 = tp->inq_byte56;
- if (inq_version >= 4 && inq_len > 56)
- inq_byte56 = inq_data[56];
-#if 0
-printf("XXXXXX [%d] inq_version=%x inq_byte7=%x inq_byte56=%x XXXXX\n",
- inq_len, inq_version, inq_byte7, inq_byte56);
-#endif
- /*
- * Trigger a negotiation if needed.
- */
- if (tp->inq_version != inq_version ||
- tp->inq_byte7 != inq_byte7 ||
- tp->inq_byte56 != inq_byte56) {
- tp->inq_version = inq_version;
- tp->inq_byte7 = inq_byte7;
- tp->inq_byte56 = inq_byte56;
- return 1;
- }
- return 0;
-}
-#endif /* SYM_OPT_SNIFF_INQUIRY */
===== drivers/scsi/sym53c8xx_2/sym_hipd.h 1.7 vs edited =====
--- 1.7/drivers/scsi/sym53c8xx_2/sym_hipd.h 2004-08-14 07:08:22 -07:00
+++ edited/drivers/scsi/sym53c8xx_2/sym_hipd.h 2004-08-21 11:14:46 -07:00
@@ -69,11 +69,6 @@
* When this option is set, the driver will use a queue per
* device and handle QUEUE FULL status requeuing internally.
*
- * SYM_OPT_SNIFF_INQUIRY
- * When this option is set, the driver sniff out successful
- * INQUIRY response and performs negotiations accordingly.
- * (set for Linux)
- *
* SYM_OPT_LIMIT_COMMAND_REORDERING
* When this option is set, the driver tries to limit tagged
* command reordering to some reasonnable value.
@@ -82,7 +77,6 @@
#if 0
#define SYM_OPT_HANDLE_DIR_UNKNOWN
#define SYM_OPT_HANDLE_DEVICE_QUEUEING
-#define SYM_OPT_SNIFF_INQUIRY
#define SYM_OPT_LIMIT_COMMAND_REORDERING
#endif
@@ -364,7 +358,6 @@
struct sym_tinfo {
struct sym_trans curr;
struct sym_trans goal;
- struct sym_trans user;
#ifdef SYM_OPT_ANNOUNCE_TRANSFER_RATE
struct sym_trans prev;
#endif
@@ -465,18 +458,7 @@
*/
u_char usrflags;
u_short usrtags;
-
-#ifdef SYM_OPT_SNIFF_INQUIRY
- /*
- * Some minimal information from INQUIRY response.
- */
- u32 cmdq_map[(SYM_CONF_MAX_LUN+31)/32];
- u_char inq_version;
- u_char inq_byte7;
- u_char inq_byte56;
- u_char inq_byte7_valid;
-#endif
-
+ struct scsi_device *sdev;
};
/*
@@ -1162,26 +1144,6 @@
#ifdef SYM_OPT_ANNOUNCE_TRANSFER_RATE
void sym_announce_transfer_rate(hcb_p np, int target);
#endif
-
-/*
- * Optionnaly, the driver may sniff inquiry data.
- */
-#ifdef SYM_OPT_SNIFF_INQUIRY
-#define INQ7_CMDQ (0x02)
-#define INQ7_SYNC (0x10)
-#define INQ7_WIDE16 (0x20)
-
-#define INQ56_CLOCKING (3<<2)
-#define INQ56_ST_ONLY (0<<2)
-#define INQ56_DT_ONLY (1<<2)
-#define INQ56_ST_DT (3<<2)
-
-void sym_update_trans_settings(hcb_p np, tcb_p tp);
-int
-__sym_sniff_inquiry(hcb_p np, u_char tn, u_char ln,
- u_char *inq_data, int inq_len);
-#endif
-
/*
* Build a scatter/gather entry.
===== drivers/scsi/sym53c8xx_2/sym_nvram.c 1.5 vs edited =====
--- 1.5/drivers/scsi/sym53c8xx_2/sym_nvram.c 2004-07-26 14:24:36 -07:00
+++ edited/drivers/scsi/sym53c8xx_2/sym_nvram.c 2004-08-21 09:31:52 -07:00
@@ -53,11 +53,6 @@
#include "sym_glue.h"
#include "sym_nvram.h"
-/*
- * Some poor and bogus sync table that refers to Tekram NVRAM layout.
- */
-static u_char Tekram_sync[16] =
- {25,31,37,43, 50,62,75,125, 12,15,18,21, 6,7,9,10};
#ifdef SYM_CONF_DEBUG_NVRAM
static u_char Tekram_boot_delay[7] = {3, 5, 10, 20, 30, 60, 120};
#endif
@@ -100,8 +95,6 @@
struct sym_tcb *tp = &np->target[target];
Symbios_target *tn = &nvram->target[target];
- tp->tinfo.user.period = tn->sync_period ? (tn->sync_period + 3) / 4 : 0;
- tp->tinfo.user.width = tn->bus_width == 0x10 ? BUS_16_BIT : BUS_8_BIT;
tp->usrtags =
(tn->flags & SYMBIOS_QUEUE_TAGS_ENABLED)? SYM_SETUP_MAX_TAG : 0;
@@ -121,15 +114,6 @@
{
struct sym_tcb *tp = &np->target[target];
struct Tekram_target *tn = &nvram->target[target];
- int i;
-
- if (tn->flags & TEKRAM_SYNC_NEGO) {
- i = tn->sync_index & 0xf;
- tp->tinfo.user.period = Tekram_sync[i];
- }
-
- tp->tinfo.user.width = (tn->flags & TEKRAM_WIDE_NEGO) ?
- BUS_16_BIT : BUS_8_BIT;
if (tn->flags & TEKRAM_TAGGED_COMMANDS) {
tp->usrtags = 2 << nvram->max_tags_index;
===== drivers/scsi/sym53c8xx_2/sym_glue.c 1.46 vs edited =====
--- 1.46/drivers/scsi/sym53c8xx_2/sym_glue.c 2004-08-21 09:27:03 -07:00
+++ edited/drivers/scsi/sym53c8xx_2/sym_glue.c 2004-08-21 09:31:49 -07:00
@@ -143,13 +143,6 @@
}
/*
- * Driver host data structure.
- */
-struct host_data {
- struct sym_hcb *ncb;
-};
-
-/*
* Used by the eh thread to wait for command completion.
* It is allocated on the eh thread stack.
*/
@@ -220,47 +213,12 @@
return use_sg;
}
-static void __sync_scsi_data_for_cpu(struct pci_dev *pdev, struct scsi_cmnd *cmd)
-{
- int dma_dir = cmd->sc_data_direction;
-
- switch(SYM_UCMD_PTR(cmd)->data_mapped) {
- case 2:
- pci_dma_sync_sg_for_cpu(pdev, cmd->buffer, cmd->use_sg, dma_dir);
- break;
- case 1:
- pci_dma_sync_single_for_cpu(pdev, SYM_UCMD_PTR(cmd)->data_mapping,
- cmd->request_bufflen, dma_dir);
- break;
- }
-}
-
-static void __sync_scsi_data_for_device(struct pci_dev *pdev, struct scsi_cmnd *cmd)
-{
- int dma_dir = cmd->sc_data_direction;
-
- switch(SYM_UCMD_PTR(cmd)->data_mapped) {
- case 2:
- pci_dma_sync_sg_for_device(pdev, cmd->buffer, cmd->use_sg, dma_dir);
- break;
- case 1:
- pci_dma_sync_single_for_device(pdev, SYM_UCMD_PTR(cmd)->data_mapping,
- cmd->request_bufflen, dma_dir);
- break;
- }
-}
-
#define unmap_scsi_data(np, cmd) \
__unmap_scsi_data(np->s.device, cmd)
#define map_scsi_single_data(np, cmd) \
__map_scsi_single_data(np->s.device, cmd)
#define map_scsi_sg_data(np, cmd) \
__map_scsi_sg_data(np->s.device, cmd)
-#define sync_scsi_data_for_cpu(np, cmd) \
- __sync_scsi_data_for_cpu(np->s.device, cmd)
-#define sync_scsi_data_for_device(np, cmd) \
- __sync_scsi_data_for_device(np->s.device, cmd)
-
/*
* Complete a pending CAM CCB.
*/
@@ -417,27 +375,6 @@
/*
- * Called on successfull INQUIRY response.
- */
-void sym_sniff_inquiry(struct sym_hcb *np, struct scsi_cmnd *cmd, int resid)
-{
- int retv;
-
- if (!cmd || cmd->use_sg)
- return;
-
- sync_scsi_data_for_cpu(np, cmd);
- retv = __sym_sniff_inquiry(np, cmd->device->id, cmd->device->lun,
- (u_char *) cmd->request_buffer,
- cmd->request_bufflen - resid);
- sync_scsi_data_for_device(np, cmd);
- if (retv < 0)
- return;
- else if (retv)
- sym_update_trans_settings(np, &np->target[cmd->device->id]);
-}
-
-/*
* Build the scatter/gather array for an I/O.
*/
@@ -1118,12 +1055,7 @@
np = ((struct host_data *) host->hostdata)->ncb;
tp = &np->target[device->id];
-
- /*
- * Get user settings for transfer parameters.
- */
- tp->inq_byte7_valid = (INQ7_SYNC|INQ7_WIDE16);
- sym_update_trans_settings(np, tp);
+ tp->sdev = device;
/*
* Allocate the LCB if not yet.
@@ -2384,16 +2316,6 @@
struct sym_hcb *np = ((struct host_data *)sdev->host->hostdata)->ncb;
struct sym_tcb *tp = &np->target[sdev->id];
- if (offset == 0)
- tp->tinfo.goal.options = 0;
-
- if (tp->tinfo.curr.options & PPR_OPT_DT) {
- if (offset > np->maxoffs_dt)
- offset = np->maxoffs_dt;
- } else {
- if (offset > np->maxoffs)
- offset = np->maxoffs;
- }
tp->tinfo.goal.offset = offset;
}
@@ -2411,23 +2333,11 @@
struct sym_hcb *np = ((struct host_data *)sdev->host->hostdata)->ncb;
struct sym_tcb *tp = &np->target[sdev->id];
- if (period <= 9 && np->minsync_dt) {
- if (period < np->minsync_dt)
- period = np->minsync_dt;
- tp->tinfo.goal.options = PPR_OPT_DT;
- tp->tinfo.goal.period = period;
- if (!tp->tinfo.curr.offset ||
- tp->tinfo.curr.offset > np->maxoffs_dt)
- tp->tinfo.goal.offset = np->maxoffs_dt;
- } else {
- if (period < np->minsync)
- period = np->minsync;
- tp->tinfo.goal.options = 0;
- tp->tinfo.goal.period = period;
- if (!tp->tinfo.curr.offset ||
- tp->tinfo.curr.offset > np->maxoffs)
- tp->tinfo.goal.offset = np->maxoffs;
- }
+ /* have to have DT for these transfers */
+ if (period <= np->minsync)
+ tp->tinfo.goal.options |= PPR_OPT_DT;
+
+ tp->tinfo.goal.period = period;
}
static void sym2_get_width(struct scsi_device *sdev)
@@ -2443,6 +2353,10 @@
struct sym_hcb *np = ((struct host_data *)sdev->host->hostdata)->ncb;
struct sym_tcb *tp = &np->target[sdev->id];
+ /* It is illegal to have DT set on narrow transfers */
+ if (width == 0)
+ tp->tinfo.goal.options &= ~PPR_OPT_DT;
+
tp->tinfo.goal.width = width;
}
@@ -2459,17 +2373,10 @@
struct sym_hcb *np = ((struct host_data *)sdev->host->hostdata)->ncb;
struct sym_tcb *tp = &np->target[sdev->id];
- if (!dt) {
- /* if clearing DT, then we may need to reduce the
- * period and the offset */
- if (tp->tinfo.curr.period < np->minsync)
- tp->tinfo.goal.period = np->minsync;
- if (tp->tinfo.curr.offset > np->maxoffs)
- tp->tinfo.goal.offset = np->maxoffs;
- tp->tinfo.goal.options &= ~PPR_OPT_DT;
- } else {
+ if (dt)
tp->tinfo.goal.options |= PPR_OPT_DT;
- }
+ else
+ tp->tinfo.goal.options &= ~PPR_OPT_DT;
}
===== drivers/scsi/sym53c8xx_2/sym_glue.h 1.20 vs edited =====
--- 1.20/drivers/scsi/sym53c8xx_2/sym_glue.h 2004-08-14 07:08:20 -07:00
+++ edited/drivers/scsi/sym53c8xx_2/sym_glue.h 2004-08-21 09:31:49 -07:00
@@ -89,7 +89,6 @@
#define SYM_OPT_HANDLE_DIR_UNKNOWN
#define SYM_OPT_HANDLE_DEVICE_QUEUEING
-#define SYM_OPT_SNIFF_INQUIRY
#define SYM_OPT_LIMIT_COMMAND_REORDERING
#define SYM_OPT_ANNOUNCE_TRANSFER_RATE
@@ -436,6 +435,13 @@
struct sym_nvram *nvram;
u_short device_id;
u_char host_id;
+};
+
+/*
+ * Driver host data structure.
+ */
+struct host_data {
+ struct sym_hcb *ncb;
};
/*
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-21 18:37 [PATCH] fix sym2 negotiation James Bottomley
@ 2004-08-22 17:32 ` Matthias Andree
2004-08-22 18:03 ` James Bottomley
2004-08-24 13:29 ` Olaf Hering
2004-08-27 16:54 ` Kai Makisara
2 siblings, 1 reply; 20+ messages in thread
From: Matthias Andree @ 2004-08-22 17:32 UTC (permalink / raw)
To: James Bottomley; +Cc: willy, SCSI Mailing List
James Bottomley <James.Bottomley@SteelEye.com> writes:
> The problems with domain validation were just the tip of the iceberg in
> the sym2 driver. Most of its problems seem to come from an overly
> complex set of negotiating rules, which I've swept away with this patch.
> ===== drivers/scsi/sym53c8xx_2/sym_hipd.c 1.20 vs edited =====
> --- 1.20/drivers/scsi/sym53c8xx_2/sym_hipd.c 2004-08-21 09:27:03 -07:00
> +++ edited/drivers/scsi/sym53c8xx_2/sym_hipd.c 2004-08-21 11:17:09 -07:00
James,
is the patch available in a BK tree that the public can pull from?
I can't seem to get it to apply even with either or both of the patches
Matt mentioned in another thread.
Thanks in advance,
--
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95 (PGP/MIME preferred)
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-22 17:32 ` Matthias Andree
@ 2004-08-22 18:03 ` James Bottomley
0 siblings, 0 replies; 20+ messages in thread
From: James Bottomley @ 2004-08-22 18:03 UTC (permalink / raw)
To: Matthias Andree; +Cc: willy, SCSI Mailing List
On Sun, 2004-08-22 at 13:32, Matthias Andree wrote:
> is the patch available in a BK tree that the public can pull from?
>
> I can't seem to get it to apply even with either or both of the patches
> Matt mentioned in another thread.
Yes, they're all in the SCSI BK tree:
bk://linux-scsi.bkbits.net/scsi-misc-2.6
But if you're just looking for a quick fix for the atlas problem, it's
here (and should apply to the vanilla kernel).
http://marc.theaimsgroup.com/?l=linux-scsi&m=109297058118127
James
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-21 18:37 [PATCH] fix sym2 negotiation James Bottomley
2004-08-22 17:32 ` Matthias Andree
@ 2004-08-24 13:29 ` Olaf Hering
2004-08-24 20:39 ` Mike Anderson
2004-08-27 16:54 ` Kai Makisara
2 siblings, 1 reply; 20+ messages in thread
From: Olaf Hering @ 2004-08-24 13:29 UTC (permalink / raw)
To: James Bottomley; +Cc: willy, SCSI Mailing List
On Sat, Aug 21, James Bottomley wrote:
> The problems with domain validation were just the tip of the iceberg in
> the sym2 driver. Most of its problems seem to come from an overly
> complex set of negotiating rules, which I've swept away with this patch.
I see timeouts on the CDROM during boot with 2.6.8, they do not happen
with our 2.6.5 based SLES9 kernel. This patch doesnt fix it, no idea if
it was supposed to fix this sort of error.
PCI: Enabling device: (0003:61:01.0), cmd 143
sym1: <875> rev 0x3 at pci 0003:61:01.0 irq 86
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: SCSI BUS has been reset.
scsi1 : sym-2.1.18j
sym1:5:0: ABORT operation started.
sym1:5:0: ABORT operation timed-out.
sym1:5:0: DEVICE RESET operation started.
sym1:5:0: DEVICE RESET operation complete.
sym1:5:control msgout: c.
sym1: TARGET 5 has been reset.
sym1:5:0: ABORT operation started.
sym1:5:0: ABORT operation complete.
sym1:5:0: BUS RESET operation started.
sym1:5:0: BUS RESET operation complete.
sym1: SCSI BUS reset detected.
sym1: SCSI BUS has been reset.
Vendor: IBM Model: DROM00203 Rev: 7R41
Type: CD-ROM ANSI SCSI revision: 02
scsi(1:0:5:0): Beginning Domain Validation
sym1:5: wide asynchronous.
sym1:5: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 14)
scsi(1:0:5:0): Domain Validation skipping write tests
scsi(1:0:5:0): Ending Domain Validation
sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
Attached scsi CD-ROM sr0 at scsi1, channel 0, id 5, lun 0
sym1:6: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 16)
Vendor: HP Model: IBM-C568303030!D Rev: C209
Type: Sequential-Access ANSI SCSI revision: 02
scsi(1:0:6:0): Beginning Domain Validation
sym1:6: FAST-20 SCSI 20.0 MB/s ST (50.0 ns, offset 16)
sym1:6: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 16)
scsi(1:0:6:0): Domain Validation skipping write tests
scsi(1:0:6:0): Ending Domain Validation
...
firmware_features = 0xd7f
Starting Linux PPC64 2.6.9-rc1-tst-timer4
-----------------------------------------------------
naca = 0xc000000000004000
naca->pftSize = 0x1c
naca->debug_switch = 0x0
naca->interrupt_controller = 0x2
systemcfg = 0xc000000000005000
systemcfg->processorCount = 0xc
systemcfg->physicalMemorySize = 0x210000000
systemcfg->dCacheL1LineSize = 0x80
systemcfg->iCacheL1LineSize = 0x80
htab_data.htab = 0x0000000000000000
htab_data.num_ptegs = 0x200000
-----------------------------------------------------
[boot]0100 MM Init
[boot]0100 MM Init Done
idle = default_idle
Linux version 2.6.9-rc1-tst-timer4 (olaf@pomegranate) (gcc version 3.3.3 (SuSE Linux)) #1 SMP Tue Aug 24 14:09:52 CEST 2004
[boot]0012 Setup Arch
WARNING: could not find NUMA associativity reference point
NUMA associativity depth for CPU/Memory: -1
Top of RAM: 0x210000000, Total RAM: 0x210000000
Memory hole size: 0MB
cpu 0 maps to domain 0
cpu 1 maps to domain 0
cpu 2 maps to domain 0
cpu 3 maps to domain 0
cpu 4 maps to domain 0
cpu 5 maps to domain 0
cpu 6 maps to domain 0
cpu 7 maps to domain 0
cpu 8 maps to domain 0
cpu 9 maps to domain 0
cpu 10 maps to domain 0
cpu 11 maps to domain 0
cpu 12 maps to domain 0
cpu 13 maps to domain 0
cpu 14 maps to domain 0
cpu 15 maps to domain 0
cpu 16 maps to domain 0
cpu 17 maps to domain 0
cpu 18 maps to domain 0
cpu 19 maps to domain 0
cpu 20 maps to domain 0
cpu 21 maps to domain 0
cpu 22 maps to domain 0
cpu 23 maps to domain 0
cpu 24 maps to domain 0
cpu 25 maps to domain 0
cpu 26 maps to domain 0
cpu 27 maps to domain 0
cpu 28 maps to domain 0
cpu 29 maps to domain 0
cpu 30 maps to domain 0
cpu 31 maps to domain 0
cpu 32 maps to domain 0
cpu 33 maps to domain 0
cpu 34 maps to domain 0
cpu 35 maps to domain 0
cpu 36 maps to domain 0
cpu 37 maps to domain 0
cpu 38 maps to domain 0
cpu 39 maps to domain 0
cpu 40 maps to domain 0
cpu 41 maps to domain 0
cpu 42 maps to domain 0
cpu 43 maps to domain 0
cpu 44 maps to domain 0
cpu 45 maps to domain 0
cpu 46 maps to domain 0
cpu 47 maps to domain 0
cpu 48 maps to domain 0
cpu 49 maps to domain 0
cpu 50 maps to domain 0
cpu 51 maps to domain 0
cpu 52 maps to domain 0
cpu 53 maps to domain 0
cpu 54 maps to domain 0
cpu 55 maps to domain 0
cpu 56 maps to domain 0
cpu 57 maps to domain 0
cpu 58 maps to domain 0
cpu 59 maps to domain 0
cpu 60 maps to domain 0
cpu 61 maps to domain 0
cpu 62 maps to domain 0
cpu 63 maps to domain 0
cpu 64 maps to domain 0
cpu 65 maps to domain 0
cpu 66 maps to domain 0
cpu 67 maps to domain 0
cpu 68 maps to domain 0
cpu 69 maps to domain 0
cpu 70 maps to domain 0
cpu 71 maps to domain 0
cpu 72 maps to domain 0
cpu 73 maps to domain 0
cpu 74 maps to domain 0
cpu 75 maps to domain 0
cpu 76 maps to domain 0
cpu 77 maps to domain 0
cpu 78 maps to domain 0
cpu 79 maps to domain 0
cpu 80 maps to domain 0
cpu 81 maps to domain 0
cpu 82 maps to domain 0
cpu 83 maps to domain 0
cpu 84 maps to domain 0
cpu 85 maps to domain 0
cpu 86 maps to domain 0
cpu 87 maps to domain 0
cpu 88 maps to domain 0
cpu 89 maps to domain 0
cpu 90 maps to domain 0
cpu 91 maps to domain 0
cpu 92 maps to domain 0
cpu 93 maps to domain 0
cpu 94 maps to domain 0
cpu 95 maps to domain 0
cpu 96 maps to domain 0
cpu 97 maps to domain 0
cpu 98 maps to domain 0
cpu 99 maps to domain 0
cpu 100 maps to domain 0
cpu 101 maps to domain 0
cpu 102 maps to domain 0
cpu 103 maps to domain 0
cpu 104 maps to domain 0
cpu 105 maps to domain 0
cpu 106 maps to domain 0
cpu 107 maps to domain 0
cpu 108 maps to domain 0
cpu 109 maps to domain 0
cpu 110 maps to domain 0
cpu 111 maps to domain 0
cpu 112 maps to domain 0
cpu 113 maps to domain 0
cpu 114 maps to domain 0
cpu 115 maps to domain 0
cpu 116 maps to domain 0
cpu 117 maps to domain 0
cpu 118 maps to domain 0
cpu 119 maps to domain 0
cpu 120 maps to domain 0
cpu 121 maps to domain 0
cpu 122 maps to domain 0
cpu 123 maps to domain 0
cpu 124 maps to domain 0
cpu 125 maps to domain 0
cpu 126 maps to domain 0
cpu 127 maps to domain 0
node 0
start_paddr = 0
end_paddr = 210000000
bootmap_pages = 42
bootmap_paddr = 20ffbc000
free_bootmem 0 210000000
reserve_bootmem 0 879b60
reserve_bootmem 4400000 154000
reserve_bootmem f92c000 6d4000
reserve_bootmem 20ffbc000 42000
reserve_bootmem 20fffef08 10f8
Boot arguments: root=/dev/sdb3 desktop selinux=0 elevator=cfq splash=silent
RTAS: event: 1, Type: Internal Device Failure, Severity: 5
RTAS: event: 2, Type: Internal Device Failure, Severity: 5
RTAS: event: 3, Type: Internal Device Failure, Severity: 5
RTAS: event: 4, Type: Internal Device Failure, Severity: 5
RTAS: event: 5, Type: Internal Device Failure, Severity: 5
EEH: PCI Enhanced I/O Error Handling Enabled
PPC64 nvram contains 22528 bytes
free_area_init node 0 210000 0 (hole: 0)
On node 0 totalpages: 2162688
DMA zone: 2162688 pages, LIFO batch:16
Normal zone: 0 pages, LIFO batch:1
HighMem zone: 0 pages, LIFO batch:1
[boot]0015 Setup Done
Built 1 zonelists
Kernel command line: root=/dev/sdb3 desktop selinux=0 elevator=cfq splash=silent
[boot]0020 XICS Init
[boot]0021 XICS Done
PID hash table entries: 4096 (order 12: 65536 bytes)
time_init: decrementer frequency = 137.495999 MHz
time_init: processor frequency = 1099.967992 MHz
Console: colour dummy device 80x25
Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
freeing bootmem node 0
Memory: 8485760k available (0k kernel code, 0k data, 0k init) [c000000000000000,c000000210000000]
Calibrating delay loop... 274.43 BogoMIPS
Security Scaffold v1.0.0 initialized
SELinux: Disabled at boot.
Mount-cache hash table entries: 256 (order: 0, 4096 bytes)
Partition configured for 16 cpus.
Processor 1 found.
Processor 2 found.
Processor 3 found.
Processor 4 found.
Processor 5 found.
Processor 6 found.
Processor 7 found.
Processor 8 found.
Processor 9 found.
Processor 10 found.
Processor 11 found.
Brought up 12 CPUs
CPU0: online
domain 0: span 00000000,00000000,00000000,00000001
groups: 00000000,00000000,00000000,00000001
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU1: online
domain 0: span 00000000,00000000,00000000,00000002
groups: 00000000,00000000,00000000,00000002
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU2: online
domain 0: span 00000000,00000000,00000000,00000004
groups: 00000000,00000000,00000000,00000004
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU3: online
domain 0: span 00000000,00000000,00000000,00000008
groups: 00000000,00000000,00000000,00000008
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU4: online
domain 0: span 00000000,00000000,00000000,00000010
groups: 00000000,00000000,00000000,00000010
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU5: online
domain 0: span 00000000,00000000,00000000,00000020
groups: 00000000,00000000,00000000,00000020
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU6: online
domain 0: span 00000000,00000000,00000000,00000040
groups: 00000000,00000000,00000000,00000040
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU7: online
domain 0: span 00000000,00000000,00000000,00000080
groups: 00000000,00000000,00000000,00000080
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU8: online
domain 0: span 00000000,00000000,00000000,00000100
groups: 00000000,00000000,00000000,00000100
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU9: online
domain 0: span 00000000,00000000,00000000,00000200
groups: 00000000,00000000,00000000,00000200
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU10: online
domain 0: span 00000000,00000000,00000000,00000400
groups: 00000000,00000000,00000000,00000400
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU11: online
domain 0: span 00000000,00000000,00000000,00000800
groups: 00000000,00000000,00000000,00000800
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU12: offline
domain 0: span 00000000,00000000,00000000,00001000
groups: 00000000,00000000,00000000,00001000
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU13: offline
domain 0: span 00000000,00000000,00000000,00002000
groups: 00000000,00000000,00000000,00002000
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU14: offline
domain 0: span 00000000,00000000,00000000,00004000
groups: 00000000,00000000,00000000,00004000
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00004000 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
CPU15: offline
domain 0: span 00000000,00000000,00000000,00008000
groups: 00000000,00000000,00000000,00008000
domain 1: span ffffffff,ffffffff,ffffffff,ffffffff
groups: 00000000,00000000,00000000,00008000 00000000,00000000,00000000,00000001 00000000,00000000,00000000,00000002 00000000,00000000,00000000,00000004 00000000,00000000,00000000,00000008 00000000,00000000,00000000,00000010 00000000,00000000,00000000,00000020 00000000,00000000,00000000,00000040 00000000,00000000,00000000,00000080 00000000,00000000,00000000,00000100 00000000,00000000,00000000,00000200 00000000,00000000,00000000,00000400 00000000,00000000,00000000,00000800 00000000,00000000,00000000,00001000 00000000,00000000,00000000,00002000 00000000,00000000,00000000,00004000
ERROR groups don't span domain->span
domain 2: span 00000000,00000000,00000000,0000ffff
groups: 00000000,00000000,00000000,0000ffff
checking if image is initramfs... it is
Freeing initrd memory: 1360k freed
NET: Registered protocol family 16
PCI: Probing PCI hardware
RTAS: event: 6, Type: Internal Device Failure, Severity: 5
RTAS: event: 7, Type: Internal Device Failure, Severity: 5
RTAS: event: 8, Type: Internal Device Failure, Severity: 5
RTAS: event: 9, Type: Internal Device Failure, Severity: 5
RTAS: event: 10, Type: Internal Device Failure, Severity: 5
RTAS: event: 11, Type: Internal Device Failure, Severity: 5
RTAS: event: 12, Type: Internal Device Failure, Severity: 5
RTAS: event: 13, Type: Internal Device Failure, Severity: 5
RTAS: event: 14, Type: Internal Device Failure, Severity: 5
RTAS: event: 15, Type: Internal Device Failure, Severity: 5
RTAS: event: 16, Type: Internal Device Failure, Severity: 5
RTAS: event: 17, Type: Internal Device Failure, Severity: 5
RTAS: event: 18, Type: Internal Device Failure, Severity: 5
RTAS: event: 19, Type: Internal Device Failure, Severity: 5
RTAS: event: 20, Type: Internal Device Failure, Severity: 5
RTAS: event: 21, Type: Internal Device Failure, Severity: 5
RTAS: event: 22, Type: Internal Device Failure, Severity: 5
RTAS: event: 23, Type: Internal Device Failure, Severity: 5
RTAS: event: 24, Type: Internal Device Failure, Severity: 5
RTAS: event: 25, Type: Internal Device Failure, Severity: 5
RTAS: event: 26, Type: Internal Device Failure, Severity: 5
RTAS: event: 27, Type: Internal Device Failure, Severity: 5
RTAS: event: 28, Type: Internal Device Failure, Severity: 5
RTAS: event: 29, Type: Internal Device Failure, Severity: 5
RTAS: event: 30, Type: Internal Device Failure, Severity: 5
RTAS: event: 31, Type: Internal Device Failure, Severity: 5
RTAS: event: 32, Type: Internal Device Failure, Severity: 5
RTAS: event: 33, Type: Internal Device Failure, Severity: 5
RTAS: event: 34, Type: Internal Device Failure, Severity: 5
RTAS: event: 35, Type: Internal Device Failure, Severity: 5
RTAS: event: 36, Type: Internal Device Failure, Severity: 5
RTAS: event: 37, Type: Internal Device Failure, Severity: 5
RTAS: event: 38, Type: Internal Device Failure, Severity: 5
RTAS: event: 39, Type: Internal Device Failure, Severity: 5
RTAS: event: 40, Type: Internal Device Failure, Severity: 5
RTAS: event: 41, Type: Internal Device Failure, Severity: 5
RTAS: event: 42, Type: Internal Device Failure, Severity: 5
RTAS: event: 43, Type: Internal Device Failure, Severity: 5
RTAS: event: 44, Type: Internal Device Failure, Severity: 5
RTAS: event: 45, Type: Internal Device Failure, Severity: 5
RTAS: event: 46, Type: Internal Device Failure, Severity: 5
RTAS: event: 47, Type: Internal Device Failure, Severity: 5
RTAS: event: 48, Type: Internal Device Failure, Severity: 5
RTAS: event: 49, Type: Internal Device Failure, Severity: 5
RTAS: event: 50, Type: Internal Device Failure, Severity: 5
RTAS: event: 51, Type: Internal Device Failure, Severity: 5
RTAS: event: 52, Type: Internal Device Failure, Severity: 5
RTAS: event: 53, Type: Internal Device Failure, Severity: 5
RTAS: event: 54, Type: Internal Device Failure, Severity: 5
RTAS: event: 55, Type: Internal Device Failure, Severity: 5
RTAS: event: 56, Type: Internal Device Failure, Severity: 5
RTAS: event: 57, Type: Internal Device Failure, Severity: 5
RTAS: event: 58, Type: Internal Device Failure, Severity: 5
RTAS: event: 59, Type: Internal Device Failure, Severity: 5
RTAS: event: 60, Type: Internal Device Failure, Severity: 5
RTAS: event: 61, Type: Internal Device Failure, Severity: 5
RTAS: event: 62, Type: Internal Device Failure, Severity: 5
RTAS: event: 63, Type: Internal Device Failure, Severity: 5
RTAS: event: 64, Type: Internal Device Failure, Severity: 5
RTAS: event: 65, Type: Internal Device Failure, Severity: 5
RTAS: event: 66, Type: Internal Device Failure, Severity: 5
RTAS: event: 67, Type: Internal Device Failure, Severity: 5
RTAS: event: 68, Type: Internal Device Failure, Severity: 5
RTAS: event: 69, Type: Internal Device Failure, Severity: 5
RTAS: event: 70, Type: Internal Device Failure, Severity: 5
RTAS: event: 71, Type: Internal Device Failure, Severity: 5
RTAS: event: 72, Type: Internal Device Failure, Severity: 5
RTAS: event: 73, Type: Internal Device Failure, Severity: 5
RTAS: event: 74, Type: Internal Device Failure, Severity: 5
RTAS: event: 75, Type: Internal Device Failure, Severity: 5
RTAS: event: 76, Type: Internal Device Failure, Severity: 5
RTAS: event: 77, Type: Internal Device Failure, Severity: 5
RTAS: event: 78, Type: Internal Device Failure, Severity: 5
RTAS: event: 79, Type: Internal Device Failure, Severity: 5
RTAS: event: 80, Type: Internal Device Failure, Severity: 5
RTAS: event: 81, Type: Internal Device Failure, Severity: 5
RTAS: event: 82, Type: Internal Device Failure, Severity: 5
RTAS: event: 83, Type: Internal Device Failure, Severity: 5
RTAS: event: 84, Type: Internal Device Failure, Severity: 5
RTAS: event: 85, Type: Internal Device Failure, Severity: 5
RTAS: event: 86, Type: Internal Device Failure, Severity: 5
RTAS: event: 87, Type: Internal Device Failure, Severity: 5
RTAS: event: 88, Type: Internal Device Failure, Severity: 5
RTAS: event: 89, Type: Internal Device Failure, Severity: 5
RTAS: event: 90, Type: Internal Device Failure, Severity: 5
RTAS: event: 91, Type: Internal Device Failure, Severity: 5
RTAS: event: 92, Type: Internal Device Failure, Severity: 5
RTAS: event: 93, Type: Internal Device Failure, Severity: 5
RTAS: event: 94, Type: Internal Device Failure, Severity: 5
RTAS: event: 95, Type: Internal Device Failure, Severity: 5
RTAS: event: 96, Type: Internal Device Failure, Severity: 5
RTAS: event: 97, Type: Internal Device Failure, Severity: 5
RTAS: event: 98, Type: Internal Device Failure, Severity: 5
RTAS: event: 99, Type: Internal Device Failure, Severity: 5
RTAS: event: 100, Type: Internal Device Failure, Severity: 5
RTAS: event: 101, Type: Internal Device Failure, Severity: 5
RTAS: event: 102, Type: Internal Device Failure, Severity: 5
RTAS: event: 103, Type: Internal Device Failure, Severity: 5
RTAS: event: 104, Type: Internal Device Failure, Severity: 5
RTAS: event: 105, Type: Internal Device Failure, Severity: 5
RTAS: event: 106, Type: Internal Device Failure, Severity: 5
RTAS: event: 107, Type: Internal Device Failure, Severity: 5
RTAS: event: 108, Type: Internal Device Failure, Severity: 5
RTAS: event: 109, Type: Internal Device Failure, Severity: 5
IOMMU table initialized, virtual merging disabled
ISA bridge at 0000:00:10.0
PCI: Probing PCI hardware done
get_random_bytes called before random driver initialization
TC classifier action (bugs to netdev@oss.sgi.com cc hadi@cyberus.ca)
probe_bus_pseries: processing c000000000868280
probe_bus_pseries: processing c000000000868448
probe_bus_pseries: processing c000000000868650
RTAS daemon started
audit: initializing netlink socket (disabled)
audit(1093353104.576:0): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
HVSI: registered 0 devices
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 123456K size 1024 blocksize
loop: loaded (max 8 devices)
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
mice: PS/2 mouse device common for all mice
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
oprofile: using ppc64/power4 performance monitoring.
NET: Registered protocol family 2
IP: routing cache hash table of 65536 buckets, 1024Kbytes
TCP: Hash tables configured (established 1048576 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
Freeing unused kernel memory: 192k freed
SCSI subsystem initialized
PCI: Enabling device: (0002:41:01.0), cmd 143
sym0: <1010-66> rev 0x1 at pci 0002:41:01.0 irq 69
sym0: No NVRAM, ID 7, Fast-80, LVD, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.1.18j
Using cfq io scheduler
sym0:8: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
Vendor: IBM Model: ST336753LC Rev: C517
Type: Direct-Access ANSI SCSI revision: 03
sym0:8:0: tagged command queuing enabled, command queue depth 16.
scsi(0:0:8:0): Beginning Domain Validation
sym0:8: asynchronous.
sym0:8: wide asynchronous.
sym0:8: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(0:0:8:0): Ending Domain Validation
SCSI device sda: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sda: drive cache: write through
sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 0, id 8, lun 0
sym0:10: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
Vendor: IBM Model: ST336753LC Rev: C517
Type: Direct-Access ANSI SCSI revision: 03
sym0:10:0: tagged command queuing enabled, command queue depth 16.
scsi(0:0:10:0): Beginning Domain Validation
sym0:10: asynchronous.
sym0:10: wide asynchronous.
sym0:10: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(0:0:10:0): Ending Domain Validation
SCSI device sdb: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sdb: drive cache: write through
sdb: sdb1 sdb2 sdb3
Attached scsi disk sdb at scsi0, channel 0, id 10, lun 0
Vendor: IBM Model: HSBPD4HD PU3SCSI Rev: 0016
Type: Enclosure ANSI SCSI revision: 02
scsi(0:0:15:0): Beginning Domain Validation
scsi(0:0:15:0): Ending Domain Validation
PCI: Enabling device: (0003:61:01.0), cmd 143
sym1: <875> rev 0x3 at pci 0003:61:01.0 irq 86
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: SCSI BUS has been reset.
scsi1 : sym-2.1.18j
sym1:5:0: ABORT operation started.
sym1:5:0: ABORT operation timed-out.
sym1:5:0: DEVICE RESET operation started.
sym1:5:0: DEVICE RESET operation complete.
sym1:5:control msgout: c.
sym1: TARGET 5 has been reset.
sym1:5:0: ABORT operation started.
sym1:5:0: ABORT operation complete.
sym1:5:0: BUS RESET operation started.
sym1:5:0: BUS RESET operation complete.
sym1: SCSI BUS reset detected.
sym1: SCSI BUS has been reset.
Vendor: IBM Model: DROM00203 Rev: 7R41
Type: CD-ROM ANSI SCSI revision: 02
scsi(1:0:5:0): Beginning Domain Validation
sym1:5: wide asynchronous.
sym1:5: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 14)
scsi(1:0:5:0): Domain Validation skipping write tests
scsi(1:0:5:0): Ending Domain Validation
sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
Attached scsi CD-ROM sr0 at scsi1, channel 0, id 5, lun 0
sym1:6: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 16)
Vendor: HP Model: IBM-C568303030!D Rev: C209
Type: Sequential-Access ANSI SCSI revision: 02
scsi(1:0:6:0): Beginning Domain Validation
sym1:6: FAST-20 SCSI 20.0 MB/s ST (50.0 ns, offset 16)
sym1:6: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 16)
scsi(1:0:6:0): Domain Validation skipping write tests
scsi(1:0:6:0): Ending Domain Validation
PCI: Enabling device: (0008:41:01.0), cmd 143
sym2: <1010-66> rev 0x1 at pci 0008:41:01.0 irq 91
sym2: No NVRAM, ID 7, Fast-80, LVD, parity checking
sym2: SCSI BUS has been reset.
scsi2 : sym-2.1.18j
sym2:8: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
Vendor: IBM Model: ST336753LC Rev: C517
Type: Direct-Access ANSI SCSI revision: 03
sym2:8:0: tagged command queuing enabled, command queue depth 16.
scsi(2:0:8:0): Beginning Domain Validation
sym2:8: asynchronous.
sym2:8: wide asynchronous.
sym2:8: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(2:0:8:0): Ending Domain Validation
SCSI device sdc: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sdc: drive cache: write through
sdc:
Attached scsi disk sdc at scsi2, channel 0, id 8, lun 0
sym2:10: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
Vendor: IBM Model: ST336753LC Rev: C517
Type: Direct-Access ANSI SCSI revision: 03
sym2:10:0: tagged command queuing enabled, command queue depth 16.
scsi(2:0:10:0): Beginning Domain Validation
sym2:10: asynchronous.
sym2:10: wide asynchronous.
sym2:10: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(2:0:10:0): Ending Domain Validation
SCSI device sdd: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sdd: drive cache: write through
sdd:
Attached scsi disk sdd at scsi2, channel 0, id 10, lun 0
Vendor: IBM Model: HSBPD4HD PU3SCSI Rev: 0016
Type: Enclosure ANSI SCSI revision: 02
scsi(2:0:15:0): Beginning Domain Validation
scsi(2:0:15:0): Ending Domain Validation
PCI: Enabling device: (0009:41:01.0), cmd 143
sym3: <1010-66> rev 0x1 at pci 0009:41:01.0 irq 107
sym3: No NVRAM, ID 7, Fast-80, LVD, parity checking
sym3: SCSI BUS has been reset.
scsi3 : sym-2.1.18j
sym3:8: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
Vendor: IBM Model: ST336753LC Rev: C517
Type: Direct-Access ANSI SCSI revision: 03
sym3:8:0: tagged command queuing enabled, command queue depth 16.
scsi(3:0:8:0): Beginning Domain Validation
sym3:8: asynchronous.
sym3:8: wide asynchronous.
sym3:8: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(3:0:8:0): Ending Domain Validation
SCSI device sde: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sde: drive cache: write through
sde: sde1
Attached scsi disk sde at scsi3, channel 0, id 8, lun 0
sym3:10: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
Vendor: IBM Model: ST336753LC Rev: C517
Type: Direct-Access ANSI SCSI revision: 03
sym3:10:0: tagged command queuing enabled, command queue depth 16.
scsi(3:0:10:0): Beginning Domain Validation
sym3:10: asynchronous.
sym3:10: wide asynchronous.
sym3:10: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(3:0:10:0): Ending Domain Validation
SCSI device sdf: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sdf: drive cache: write through
sdf: sdf1
Attached scsi disk sdf at scsi3, channel 0, id 10, lun 0
Vendor: IBM Model: HSBPD4HC PU3SCSI Rev: 0016
Type: Enclosure ANSI SCSI revision: 02
scsi(3:0:15:0): Beginning Domain Validation
scsi(3:0:15:0): Ending Domain Validation
PCI: Enabling device: (000b:41:01.0), cmd 143
sym4: <1010-66> rev 0x1 at pci 000b:41:01.0 irq 347
sym4: No NVRAM, ID 7, Fast-80, LVD, parity checking
sym4: SCSI BUS has been reset.
scsi4 : sym-2.1.18j
sym4:8: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
Vendor: IBM Model: ST336753LC Rev: C517
Type: Direct-Access ANSI SCSI revision: 03
sym4:8:0: tagged command queuing enabled, command queue depth 16.
scsi(4:0:8:0): Beginning Domain Validation
sym4:8: asynchronous.
sym4:8: wide asynchronous.
sym4:8: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(4:0:8:0): Ending Domain Validation
SCSI device sdg: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sdg: drive cache: write through
sdg: sdg1
Attached scsi disk sdg at scsi4, channel 0, id 8, lun 0
sym4:10: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
Vendor: IBM Model: ST336753LC Rev: C517
Type: Direct-Access ANSI SCSI revision: 03
sym4:10:0: tagged command queuing enabled, command queue depth 16.
scsi(4:0:10:0): Beginning Domain Validation
sym4:10: asynchronous.
sym4:10: wide asynchronous.
sym4:10: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(4:0:10:0): Ending Domain Validation
SCSI device sdh: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sdh: drive cache: write through
sdh: sdh1
Attached scsi disk sdh at scsi4, channel 0, id 10, lun 0
Vendor: IBM Model: HSBPD4HB PU3SCSI Rev: 0016
Type: Enclosure ANSI SCSI revision: 02
scsi(4:0:15:0): Beginning Domain Validation
scsi(4:0:15:0): Ending Domain Validation
PCI: Enabling device: (000c:41:01.0), cmd 143
sym5: <1010-66> rev 0x1 at pci 000c:41:01.0 irq 363
sym5: No NVRAM, ID 7, Fast-80, LVD, parity checking
sym5: SCSI BUS has been reset.
scsi5 : sym-2.1.18j
sym5:8: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
Vendor: IBM Model: ST336753LC Rev: C517
Type: Direct-Access ANSI SCSI revision: 03
sym5:8:0: tagged command queuing enabled, command queue depth 16.
scsi(5:0:8:0): Beginning Domain Validation
sym5:8: asynchronous.
sym5:8: wide asynchronous.
sym5:8: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(5:0:8:0): Ending Domain Validation
SCSI device sdi: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sdi: drive cache: write through
sdi: sdi1
Attached scsi disk sdi at scsi5, channel 0, id 8, lun 0
sym5:10: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
Vendor: IBM Model: ST336753LC Rev: C517
Type: Direct-Access ANSI SCSI revision: 03
sym5:10:0: tagged command queuing enabled, command queue depth 16.
scsi(5:0:10:0): Beginning Domain Validation
sym5:10: asynchronous.
sym5:10: wide asynchronous.
sym5:10: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 31)
scsi(5:0:10:0): Ending Domain Validation
SCSI device sdj: 71096640 512-byte hdwr sectors (36401 MB)
SCSI device sdj: drive cache: write through
sdj: sdj1
Attached scsi disk sdj at scsi5, channel 0, id 10, lun 0
Vendor: IBM Model: HSBPD4HA PU3SCSI Rev: 0016
Type: Enclosure ANSI SCSI revision: 02
scsi(5:0:15:0): Beginning Domain Validation
scsi(5:0:15:0): Ending Domain Validation
ReiserFS: sdb3: found reiserfs format "3.6" with standard journal
ReiserFS: sdb3: using ordered data mode
ReiserFS: sdb3: journal params: device sdb3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sdb3: checking transaction log (sdb3)
ReiserFS: sdb3: Using r5 hash to sort names
ioctl32(showconsole:1369): Unknown cmd fd(0) cmd(40045432){00} arg(ffffea88) on /dev/console
ioctl32(showconsole:1486): Unknown cmd fd(0) cmd(40045432){00} arg(ffffe9f8) on /dev/console
md: md0 stopped.
md: bind<sdg1>
md: bind<sdh1>
md: bind<sdi1>
md: bind<sdj1>
md: bind<sdf1>
md: raid0 personality registered as nr 2
md0: setting max_sectors to 128, segment boundary to 32767
raid0: looking at sdf1
raid0: comparing sdf1(35548032) with sdf1(35548032)
raid0: END
raid0: ==> UNIQUE
raid0: 1 zones
raid0: looking at sdj1
raid0: comparing sdj1(35548032) with sdf1(35548032)
raid0: EQUAL
raid0: looking at sdi1
raid0: comparing sdi1(35548032) with sdf1(35548032)
raid0: EQUAL
raid0: looking at sdh1
raid0: comparing sdh1(35548032) with sdf1(35548032)
raid0: EQUAL
raid0: looking at sdg1
raid0: comparing sdg1(35548032) with sdf1(35548032)
raid0: EQUAL
raid0: FINAL 1 zones
raid0: done.
raid0 : md_size is 177740160 blocks.
raid0 : conf->hash_spacing is 177740160 blocks.
raid0 : nb_zone is 1.
raid0 : Allocating 8 bytes for hash.
device-mapper: 4.1.0-ioctl (2003-12-10) initialised: dm@uk.sistina.com
ioctl32(showconsole:1574): Unknown cmd fd(0) cmd(40045432){00} arg(ffffea18) on /dev/console
ReiserFS: sde1: found reiserfs format "3.6" with standard journal
ReiserFS: sde1: using ordered data mode
ReiserFS: sde1: journal params: device sde1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: sde1: checking transaction log (sde1)
ReiserFS: sde1: Using r5 hash to sort names
ioctl32(showconsole:1649): Unknown cmd fd(0) cmd(40045432){00} arg(ffffea28) on /dev/console
ioctl32(showconsole:1855): Unknown cmd fd(0) cmd(40045432){00} arg(ffffea68) on /dev/console
e100: Intel(R) PRO/100 Network Driver, 3.0.27-k2-NAPI
e100: Copyright(c) 1999-2004 Intel Corporation
PCI: Enabling device: (0001:01:01.0), cmd 143
e100: eth0: e100_probe: addr 0x3fe00030000, irq 51, MAC addr 00:02:55:6F:6A:BD
PCI: Enabling device: (0001:21:01.0), cmd 143
e100: eth1: e100_probe: addr 0x3fe08030000, irq 52, MAC addr 00:02:55:6F:6A:CF
usbcore: registered new driver usbfs
usbcore: registered new driver hub
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
NET: Registered protocol family 10
Disabled Privacy Extensions on device c0000000004e13c0(lo)
IPv6 over IPv4 tunneling driver
Disabled Privacy Extensions on device c00000020bb97000(sit0)
sym1: SCSI parity error detected: SCR1=132 DBC=50000000 SBCL=0
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-24 13:29 ` Olaf Hering
@ 2004-08-24 20:39 ` Mike Anderson
2004-08-24 20:48 ` Vladimir G. Ivanovic
2004-08-24 20:51 ` Olaf Hering
0 siblings, 2 replies; 20+ messages in thread
From: Mike Anderson @ 2004-08-24 20:39 UTC (permalink / raw)
To: Olaf Hering; +Cc: James Bottomley, willy, SCSI Mailing List, Anton Blanchard
Olaf Hering [olh@suse.de] wrote:
> On Sat, Aug 21, James Bottomley wrote:
>
> > The problems with domain validation were just the tip of the iceberg in
> > the sym2 driver. Most of its problems seem to come from an overly
> > complex set of negotiating rules, which I've swept away with this patch.
>
> I see timeouts on the CDROM during boot with 2.6.8, they do not happen
> with our 2.6.5 based SLES9 kernel. This patch doesnt fix it, no idea if
> it was supposed to fix this sort of error.
>
> PCI: Enabling device: (0003:61:01.0), cmd 143
> sym1: <875> rev 0x3 at pci 0003:61:01.0 irq 86
> sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
> sym1: SCSI BUS has been reset.
> scsi1 : sym-2.1.18j
> sym1:5:0: ABORT operation started.
> sym1:5:0: ABORT operation timed-out.
> sym1:5:0: DEVICE RESET operation started.
> sym1:5:0: DEVICE RESET operation complete.
> sym1:5:control msgout: c.
> sym1: TARGET 5 has been reset.
> sym1:5:0: ABORT operation started.
> sym1:5:0: ABORT operation complete.
> sym1:5:0: BUS RESET operation started.
> sym1:5:0: BUS RESET operation complete.
> sym1: SCSI BUS reset detected.
> sym1: SCSI BUS has been reset.
> Vendor: IBM Model: DROM00203 Rev: 7R41
> Type: CD-ROM ANSI SCSI revision: 02
> scsi(1:0:5:0): Beginning Domain Validation
> sym1:5: wide asynchronous.
> sym1:5: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 14)
> scsi(1:0:5:0): Domain Validation skipping write tests
> scsi(1:0:5:0): Ending Domain Validation
> sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.20
> Attached scsi CD-ROM sr0 at scsi1, channel 0, id 5, lun 0
I would guess this cdrom is behind a ACARD. We have had issues in
the past with negotiation / interaction between the ACARD and the sym.
I currently do not have local access to a system with this config, but I
am asking around to see if I can get access to one.
-andmike
--
Michael Anderson
andmike@us.ibm.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-24 20:39 ` Mike Anderson
@ 2004-08-24 20:48 ` Vladimir G. Ivanovic
2004-08-24 20:50 ` Matthew Wilcox
2004-08-24 20:51 ` Olaf Hering
1 sibling, 1 reply; 20+ messages in thread
From: Vladimir G. Ivanovic @ 2004-08-24 20:48 UTC (permalink / raw)
To: Mike Anderson
Cc: Olaf Hering, James Bottomley, willy, SCSI Mailing List,
Anton Blanchard
I don't know what an ACARD is, but I have similar issues when I boot my
SMP system (ASUS CUV4X-DLS).
kernel: VFS: Mounted root (ext2 filesystem).
kernel: SCSI subsystem initialized
kernel: ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 19 (level, low) -> IRQ 177
kernel: sym0: <1010-33> rev 0x1 at pci 0000:00:08.0 irq 177
kernel: sym0: using 64 bit DMA addressing
kernel: sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking
kernel: sym0: open drain IRQ line driver, using on-chip SRAM
kernel: sym0: using LOAD/STORE-based firmware.
kernel: sym0: handling phase mismatch from SCRIPTS.
kernel: sym0: SCSI BUS has been reset.
kernel: scsi0 : sym-2.1.18j
kernel: Vendor: QUANTUM Model: ATLAS10K3_18_WLS Rev: 020K
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: sym0:6:0: tagged command queuing enabled, command queue depth 16.
kernel: scsi(0:0:6:0): Beginning Domain Validation
kernel: sym0:6: wide asynchronous.
kernel: sym0:6: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
kernel: scsi(0:0:6:0): Ending Domain Validation
kernel: SCSI device sda: 35916548 512-byte hdwr sectors (18389 MB)
kernel: SCSI device sda: drive cache: write back
kernel: sda: sda1 sda2 sda3 sda4
kernel: Attached scsi disk sda at scsi0, channel 0, id 6, lun 0
kernel: ACPI: PCI interrupt 0000:00:08.1[B] -> GSI 16 (level, low) -> IRQ 185
--
Vladimir G. Ivanovic http://leonora.org/~vladimir
Palo Alto, CA 94306 +1 650 678 8014
>>>>> "ma" == Mike Anderson <andmike@us.ibm.com> writes:
ma>
ma> Olaf Hering [olh@suse.de] wrote:
>> On Sat, Aug 21, James Bottomley wrote:
>>
>> > The problems with domain validation were just the tip of the iceberg in
>> > the sym2 driver. Most of its problems seem to come from an overly
>> > complex set of negotiating rules, which I've swept away with this patch.
>>
>> I see timeouts on the CDROM during boot with 2.6.8, they do not happen
>> with our 2.6.5 based SLES9 kernel. This patch doesnt fix it, no idea if
>> it was supposed to fix this sort of error.
>>
>> PCI: Enabling device: (0003:61:01.0), cmd 143
>> sym1: <875> rev 0x3 at pci 0003:61:01.0 irq 86
>> sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
>> sym1: SCSI BUS has been reset.
>> scsi1 : sym-2.1.18j
>> sym1:5:0: ABORT operation started.
>> sym1:5:0: ABORT operation timed-out.
>> sym1:5:0: DEVICE RESET operation started.
>> sym1:5:0: DEVICE RESET operation complete.
>> sym1:5:control msgout: c.
>> sym1: TARGET 5 has been reset.
>> sym1:5:0: ABORT operation started.
>> sym1:5:0: ABORT operation complete.
>> sym1:5:0: BUS RESET operation started.
>> sym1:5:0: BUS RESET operation complete.
>> sym1: SCSI BUS reset detected.
>> sym1: SCSI BUS has been reset.
>> Vendor: IBM Model: DROM00203 Rev: 7R41
>> Type: CD-ROM ANSI SCSI revision: 02
>> scsi(1:0:5:0): Beginning Domain Validation
>> sym1:5: wide asynchronous.
>> sym1:5: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 14)
>> scsi(1:0:5:0): Domain Validation skipping write tests
>> scsi(1:0:5:0): Ending Domain Validation
>> sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
>> Uniform CD-ROM driver Revision: 3.20
>> Attached scsi CD-ROM sr0 at scsi1, channel 0, id 5, lun 0
ma>
ma> I would guess this cdrom is behind a ACARD. We have had issues in
ma> the past with negotiation / interaction between the ACARD and the sym.
ma>
ma> I currently do not have local access to a system with this config, but I
ma> am asking around to see if I can get access to one.
ma>
ma> -andmike
ma> --
ma> Michael Anderson
ma> andmike@us.ibm.com
ma>
ma> -
ma> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
ma> the body of a message to majordomo@vger.kernel.org
ma> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-24 20:48 ` Vladimir G. Ivanovic
@ 2004-08-24 20:50 ` Matthew Wilcox
2004-08-24 21:39 ` Vladimir G. Ivanovic
0 siblings, 1 reply; 20+ messages in thread
From: Matthew Wilcox @ 2004-08-24 20:50 UTC (permalink / raw)
To: Vladimir G. Ivanovic
Cc: Mike Anderson, Olaf Hering, James Bottomley, willy,
SCSI Mailing List, Anton Blanchard
On Tue, Aug 24, 2004 at 01:48:55PM -0700, Vladimir G. Ivanovic wrote:
> I don't know what an ACARD is, but I have similar issues when I boot my
> SMP system (ASUS CUV4X-DLS).
>
> kernel: VFS: Mounted root (ext2 filesystem).
> kernel: SCSI subsystem initialized
> kernel: ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 19 (level, low) -> IRQ 177
> kernel: sym0: <1010-33> rev 0x1 at pci 0000:00:08.0 irq 177
> kernel: sym0: using 64 bit DMA addressing
> kernel: sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking
> kernel: sym0: open drain IRQ line driver, using on-chip SRAM
> kernel: sym0: using LOAD/STORE-based firmware.
> kernel: sym0: handling phase mismatch from SCRIPTS.
> kernel: sym0: SCSI BUS has been reset.
> kernel: scsi0 : sym-2.1.18j
> kernel: Vendor: QUANTUM Model: ATLAS10K3_18_WLS Rev: 020K
> kernel: Type: Direct-Access ANSI SCSI revision: 03
> kernel: sym0:6:0: tagged command queuing enabled, command queue depth 16.
> kernel: scsi(0:0:6:0): Beginning Domain Validation
> kernel: sym0:6: wide asynchronous.
> kernel: sym0:6: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
> kernel: scsi(0:0:6:0): Ending Domain Validation
> kernel: SCSI device sda: 35916548 512-byte hdwr sectors (18389 MB)
> kernel: SCSI device sda: drive cache: write back
> kernel: sda: sda1 sda2 sda3 sda4
> kernel: Attached scsi disk sda at scsi0, channel 0, id 6, lun 0
> kernel: ACPI: PCI interrupt 0000:00:08.1[B] -> GSI 16 (level, low) -> IRQ 185
Erm, I see no sign of any problem in this log. You negotiated to 160MB/s.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-24 20:39 ` Mike Anderson
2004-08-24 20:48 ` Vladimir G. Ivanovic
@ 2004-08-24 20:51 ` Olaf Hering
2004-08-25 6:57 ` Mike Anderson
1 sibling, 1 reply; 20+ messages in thread
From: Olaf Hering @ 2004-08-24 20:51 UTC (permalink / raw)
To: James Bottomley, willy, SCSI Mailing List, Anton Blanchard
On Tue, Aug 24, Mike Anderson wrote:
> I would guess this cdrom is behind a ACARD. We have had issues in
> the past with negotiation / interaction between the ACARD and the sym.
Oh, that would be possible. I will look through our patches and find the
one that adds an insane delay. Maybe it helps.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-24 20:50 ` Matthew Wilcox
@ 2004-08-24 21:39 ` Vladimir G. Ivanovic
2004-08-24 22:12 ` Matthew Wilcox
0 siblings, 1 reply; 20+ messages in thread
From: Vladimir G. Ivanovic @ 2004-08-24 21:39 UTC (permalink / raw)
To: Matthew Wilcox
Cc: Mike Anderson, Olaf Hering, James Bottomley, SCSI Mailing List,
Anton Blanchard
Sorry. The words "mismatch" and "reset" suggest (to me) that a problem
exists, and I'm extra sensitive to SCSI problems because of unresolved
problems like this (at boot):
smartd[1831]: Opened configuration file /etc/smartd.conf
smartd[1831]: Configuration file /etc/smartd.conf parsed.
smartd[1831]: Device: /dev/hdc, opened
smartd[1831]: Device: /dev/hdc, not found in smartd database.
smartd[1831]: Device: /dev/hdc, is SMART capable. Adding to "monitor" list.
smartd[1831]: Device: /dev/hdg, opened
smartd[1831]: Device: /dev/hdg, not found in smartd database.
smartd[1831]: Device: /dev/hdg, is SMART capable. Adding to "monitor" list.
smartd[1831]: Device: /dev/sda, opened
smartd[1831]: Device: /dev/sda, is SMART capable. Adding to "monitor" list.
kernel: sym0:6:0:ODD transfer in DATA IN phase.
kernel: sym0:6:0:COMMAND FAILED (87 0 10).
kernel: sym0:6:0:ODD transfer in DATA IN phase.
kernel: sym0:6:0:COMMAND FAILED (87 0 10).
kernel: sym0:6:0:ODD transfer in DATA IN phase.
kernel: sym0:6:0:COMMAND FAILED (87 0 10).
kernel: sym0:6:0:ODD transfer in DATA IN phase.
kernel: sym0:6:0:COMMAND FAILED (87 0 10).
kernel: sym0:6:0:ODD transfer in DATA IN phase.
kernel: sym0:6:0:COMMAND FAILED (87 0 10).
smartd[1831]: Monitoring 2 ATA and 1 SCSI devices
smartd[1831]: Device: /dev/sda, initial Temperature is 33 degrees
smartd[1833]: smartd has fork()ed into background mode. New PID=1833.
smartd: smartd startup succeeded
or this (at seemingly random times after booting):
kernel: sym0:6:0:ordered tag forced.
last message repeated 4 times
kernel: sym0:6:0:ordered tag forced.
last message repeated 3 times
last message repeated 29 times
last message repeated 5 times
or this (which causes my system to hang):
kernel: sym0:6: ERROR (81:0) (8-0-0) (3e/18/80) @ (scripta 38:f31c0004).
kernel: sym0: script cmd = e21c0004
kernel: sym0: regdump: da 00 00 18 47 3e 06 0f 04 08 86 00 80 00 0f 0a 72 cf 0c 00 02 00 00 00.
kernel: sym0: SCSI BUS reset detected.
kernel: sym0: enabling clock multiplier
kernel: sym0: Downloading SCSI SCRIPTS.
kernel: sym0: SCSI BUS has been reset.
kernel: sym0: command processing suspended for 3 seconds
kernel: sym0: command processing resumed
(Script cmd = e21c0004 triggers the same error also.)
--
Vladimir G. Ivanovic http://leonora.org/~vladimir
Palo Alto, CA 94306 +1 650 678 8014
>>>>> "mw" == Matthew Wilcox <willy@debian.org> writes:
mw>
mw> On Tue, Aug 24, 2004 at 01:48:55PM -0700, Vladimir G. Ivanovic wrote:
>> I don't know what an ACARD is, but I have similar issues when I boot my
>> SMP system (ASUS CUV4X-DLS).
>>
>> kernel: VFS: Mounted root (ext2 filesystem).
>> kernel: SCSI subsystem initialized
>> kernel: ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 19 (level, low) -> IRQ 177
>> kernel: sym0: <1010-33> rev 0x1 at pci 0000:00:08.0 irq 177
>> kernel: sym0: using 64 bit DMA addressing
>> kernel: sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking
>> kernel: sym0: open drain IRQ line driver, using on-chip SRAM
>> kernel: sym0: using LOAD/STORE-based firmware.
>> kernel: sym0: handling phase mismatch from SCRIPTS.
>> kernel: sym0: SCSI BUS has been reset.
>> kernel: scsi0 : sym-2.1.18j
>> kernel: Vendor: QUANTUM Model: ATLAS10K3_18_WLS Rev: 020K
>> kernel: Type: Direct-Access ANSI SCSI revision: 03
>> kernel: sym0:6:0: tagged command queuing enabled, command queue depth 16.
>> kernel: scsi(0:0:6:0): Beginning Domain Validation
>> kernel: sym0:6: wide asynchronous.
>> kernel: sym0:6: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 62)
>> kernel: scsi(0:0:6:0): Ending Domain Validation
>> kernel: SCSI device sda: 35916548 512-byte hdwr sectors (18389 MB)
>> kernel: SCSI device sda: drive cache: write back
>> kernel: sda: sda1 sda2 sda3 sda4
>> kernel: Attached scsi disk sda at scsi0, channel 0, id 6, lun 0
>> kernel: ACPI: PCI interrupt 0000:00:08.1[B] -> GSI 16 (level, low) -> IRQ 185
mw>
mw> Erm, I see no sign of any problem in this log. You negotiated to 160MB/s.
mw>
mw> --
mw> "Next the statesmen will invent cheap lies, putting the blame upon
mw> the nation that is attacked, and every man will be glad of those
mw> conscience-soothing falsities, and will diligently study them, and refuse
mw> to examine any refutations of them; and thus he will by and by convince
mw> himself that the war is just, and will thank God for the better sleep
mw> he enjoys after this process of grotesque self-deception." -- Mark Twain
mw> -
mw> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
mw> the body of a message to majordomo@vger.kernel.org
mw> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-24 21:39 ` Vladimir G. Ivanovic
@ 2004-08-24 22:12 ` Matthew Wilcox
2004-08-25 0:48 ` Vladimir G. Ivanovic
0 siblings, 1 reply; 20+ messages in thread
From: Matthew Wilcox @ 2004-08-24 22:12 UTC (permalink / raw)
To: Vladimir G. Ivanovic
Cc: Matthew Wilcox, Mike Anderson, Olaf Hering, James Bottomley,
SCSI Mailing List, Anton Blanchard
On Tue, Aug 24, 2004 at 02:39:01PM -0700, Vladimir G. Ivanovic wrote:
> Sorry. The words "mismatch" and "reset" suggest (to me) that a problem
> exists
sym2 has always displayed these messages at boot:
kernel: sym0: handling phase mismatch from SCRIPTS.
kernel: sym0: SCSI BUS has been reset.
The first one means "If there is a phase mismatch, we'll handle it in
the SCRIPTS rather than in the driver". The second one is a normal part
of bringup. Now, I'm all in favour of reducing driver verbosity at boot,
but I'm not sure I can delete either of those messages at this stage.
It's certainly something I want to look at doing.
> , and I'm extra sensitive to SCSI problems because of unresolved
> problems like this (at boot):
>
> smartd[1831]: Opened configuration file /etc/smartd.conf
> smartd[1831]: Configuration file /etc/smartd.conf parsed.
> smartd[1831]: Device: /dev/hdc, opened
> smartd[1831]: Device: /dev/hdc, not found in smartd database.
> smartd[1831]: Device: /dev/hdc, is SMART capable. Adding to "monitor" list.
> smartd[1831]: Device: /dev/hdg, opened
> smartd[1831]: Device: /dev/hdg, not found in smartd database.
> smartd[1831]: Device: /dev/hdg, is SMART capable. Adding to "monitor" list.
> smartd[1831]: Device: /dev/sda, opened
> smartd[1831]: Device: /dev/sda, is SMART capable. Adding to "monitor" list.
> kernel: sym0:6:0:ODD transfer in DATA IN phase.
> kernel: sym0:6:0:COMMAND FAILED (87 0 10).
> kernel: sym0:6:0:ODD transfer in DATA IN phase.
> kernel: sym0:6:0:COMMAND FAILED (87 0 10).
> kernel: sym0:6:0:ODD transfer in DATA IN phase.
> kernel: sym0:6:0:COMMAND FAILED (87 0 10).
> kernel: sym0:6:0:ODD transfer in DATA IN phase.
> kernel: sym0:6:0:COMMAND FAILED (87 0 10).
> kernel: sym0:6:0:ODD transfer in DATA IN phase.
> kernel: sym0:6:0:COMMAND FAILED (87 0 10).
> smartd[1831]: Monitoring 2 ATA and 1 SCSI devices
> smartd[1831]: Device: /dev/sda, initial Temperature is 33 degrees
> smartd[1833]: smartd has fork()ed into background mode. New PID=1833.
> smartd: smartd startup succeeded
>
> or this (at seemingly random times after booting):
>
> kernel: sym0:6:0:ordered tag forced.
> last message repeated 4 times
> kernel: sym0:6:0:ordered tag forced.
> last message repeated 3 times
> last message repeated 29 times
> last message repeated 5 times
>
> or this (which causes my system to hang):
>
> kernel: sym0:6: ERROR (81:0) (8-0-0) (3e/18/80) @ (scripta 38:f31c0004).
> kernel: sym0: script cmd = e21c0004
> kernel: sym0: regdump: da 00 00 18 47 3e 06 0f 04 08 86 00 80 00 0f 0a 72 cf 0c 00 02 00 00 00.
> kernel: sym0: SCSI BUS reset detected.
> kernel: sym0: enabling clock multiplier
> kernel: sym0: Downloading SCSI SCRIPTS.
> kernel: sym0: SCSI BUS has been reset.
> kernel: sym0: command processing suspended for 3 seconds
> kernel: sym0: command processing resumed
umm. The first and second ones don't seem too bad. The third one looks
like it needs some investigation though.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-24 22:12 ` Matthew Wilcox
@ 2004-08-25 0:48 ` Vladimir G. Ivanovic
0 siblings, 0 replies; 20+ messages in thread
From: Vladimir G. Ivanovic @ 2004-08-25 0:48 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: SCSI Mailing List
Wouldn't you know! Just as I was reading your email, my system frozen.
Then it froze twice again just after rebooting. Most unusal. "Normally" my
system hangs only at night, and it's never hung so many times in a row.
Maybe it's time for memtest...
>>>>> "mw" == Matthew Wilcox <willy@debian.org> writes:
mw> sym2 has always displayed these messages at boot:
mw>
mw> kernel: sym0: handling phase mismatch from SCRIPTS.
mw> kernel: sym0: SCSI BUS has been reset.
mw>
mw> The first one means "If there is a phase mismatch, we'll handle it in
mw> the SCRIPTS rather than in the driver". The second one is a normal part
mw> of bringup. Now, I'm all in favour of reducing driver verbosity at boot,
mw> but I'm not sure I can delete either of those messages at this stage.
mw> It's certainly something I want to look at doing.
OK. A possible rephrasing:
kernel: sym0: handling phase mismatches in SCRIPTS.
kernel: sym0: normal SCSI BUS reset.
>> kernel: sym0:6: ERROR (81:0) (8-0-0) (3e/18/80) @ (scripta 38:f31c0004).
>> kernel: sym0: script cmd = e21c0004
>> kernel: sym0: regdump: da 00 00 18 47 3e 06 0f 04 08 86 00 80 00 0f 0a 72 cf 0c 00 02 00 00 00.
>> kernel: sym0: SCSI BUS reset detected.
>> kernel: sym0: enabling clock multiplier
>> kernel: sym0: Downloading SCSI SCRIPTS.
>> kernel: sym0: SCSI BUS has been reset.
>> kernel: sym0: command processing suspended for 3 seconds
>> kernel: sym0: command processing resumed
mw> umm. The third one looks like it needs some investigation
mw> though.
(In my last email, I meant to say that "script cmd = 90080000" also
causes these errors.)
Is there any way I can help with an investigation? I'd *really* like to
solve these problems. It's been two years...
--
Vladimir G. Ivanovic http://leonora.org/~vladimir
Palo Alto, CA 94306 +1 650 678 8014
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-24 20:51 ` Olaf Hering
@ 2004-08-25 6:57 ` Mike Anderson
2004-08-25 9:25 ` Olaf Hering
0 siblings, 1 reply; 20+ messages in thread
From: Mike Anderson @ 2004-08-25 6:57 UTC (permalink / raw)
To: Olaf Hering; +Cc: James Bottomley, willy, SCSI Mailing List, Anton Blanchard
Olaf Hering [olh@suse.de] wrote:
> On Tue, Aug 24, Mike Anderson wrote:
>
> > I would guess this cdrom is behind a ACARD. We have had issues in
> > the past with negotiation / interaction between the ACARD and the sym.
>
> Oh, that would be possible. I will look through our patches and find the
> one that adds an insane delay. Maybe it helps.
>
Yes increasing scsi_inq_timeout to 27 seconds makes the messages go away
on my system. Prior to increasing the timeout I bk pulled scsi-misc-2.6
and received the same ABORT recovery sequence you did.
Output post increasing the timeout:
x0537p1:~ # modprobe sym53c8xx
sym0: <1010-66> rev 0x1 at pci 0000:58:01.0 irq 137
sym0: No NVRAM, ID 7, Fast-80, LVD, parity checking
sym0: SCSI BUS has been reset.
scsi3 : sym-2.1.18j
sym1: <1010-66> rev 0x1 at pci 0000:58:01.1 irq 138
sym1: No NVRAM, ID 7, Fast-80, LVD, parity checking
sym1: SCSI BUS has been reset.
scsi4 : sym-2.1.18j
Vendor: IBM Model: DROM0020311 Rev: 8R22
Type: CD-ROM ANSI SCSI revision: 02
scsi(4:0:1:0): Beginning Domain Validation
sym1:1: wide asynchronous.
sym1:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 14)
scsi(4:0:1:0): Domain Validation skipping write tests
scsi(4:0:1:0): Ending Domain Validation
sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
Attached scsi CD-ROM sr0 at scsi4, channel 0, id 1, lun 0
Attached scsi generic sg5 at scsi4, channel 0, id 1, lun 0, type 5
program scsi_id is using a deprecated SCSI ioctl, please convert it to
SG_IO
program scsi_id is using a deprecated SCSI ioctl, please convert it to
SG_IO
program hwscan is using a deprecated SCSI ioctl, please convert it to
SG_IO
program hwscan is using a deprecated SCSI ioctl, please convert it to
SG_IO
x0537p1:~ # sg_inq /dev/sg5
standard INQUIRY:
PQual=0 Device_type=5 RMB=1 [ANSI_version=2] version=0x02
[AERC=0] [TrmTsk=0] NormACA=0 HiSUP=0 Resp_data_format=2
SCCS=0 ACC=0 ALUA=0 3PC=0 Protect=0
BQue=0 EncServ=0 MultiP=0 MChngr=0 [ACKREQQ=0] Addr16=0
[RelAdr=0] WBus16=1 Sync=1 Linked=0 [TranDis=0] CmdQue=0
Clocking=0x0 QAS=0 IUS=0
length=148 (0x94) Peripheral device type: cd/dvd
Vendor identification: IBM
Product identification: DROM0020311
Product revision level: 8R22
-andmike
--
Michael Anderson
andmike@us.ibm.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-25 6:57 ` Mike Anderson
@ 2004-08-25 9:25 ` Olaf Hering
2004-08-25 11:58 ` Matthew Wilcox
0 siblings, 1 reply; 20+ messages in thread
From: Olaf Hering @ 2004-08-25 9:25 UTC (permalink / raw)
To: James Bottomley, willy, SCSI Mailing List, Anton Blanchard
On Tue, Aug 24, Mike Anderson wrote:
> Olaf Hering [olh@suse.de] wrote:
> > On Tue, Aug 24, Mike Anderson wrote:
> >
> > > I would guess this cdrom is behind a ACARD. We have had issues in
> > > the past with negotiation / interaction between the ACARD and the sym.
> >
> > Oh, that would be possible. I will look through our patches and find the
> > one that adds an insane delay. Maybe it helps.
> >
>
> Yes increasing scsi_inq_timeout to 27 seconds makes the messages go away
> on my system. Prior to increasing the timeout I bk pulled scsi-misc-2.6
> and received the same ABORT recovery sequence you did.
This patch fixed it. I'm sure this was already discussed on to dead, we
hit this bug initally one year ago with 2.4.21.
....
garloff@suse.de
Workaround
This broken chip seems to be so popular on PPC64 that the arch maintainers
want a PPC64 specific default. Oh well ...
diff -uNrp linux-2.6.5.inq_timeout/drivers/scsi/scsi_scan.c linux-2.6.5.inq_timeout.ppc64/drivers/scsi/scsi_scan.c
--- linux-2.6.5.inq_timeout/drivers/scsi/scsi_scan.c 2004-04-21 14:32:04.000000000 +0200
+++ linux-2.6.5.inq_timeout.ppc64/drivers/scsi/scsi_scan.c 2004-04-21 14:44:05.000000000 +0200
@@ -94,7 +94,17 @@ MODULE_PARM_DESC(max_report_luns,
"REPORT LUNS maximum number of LUNS received (should be"
" between 1 and 16384)");
+/* Some AChip ARC765 based DVD-ROM's take 15 or more seconds
+ * to reset. A scan will fail if made right after a reset.
+ * It's completely broken device behaviour: SCSI specification
+ * says devices need to be able to respond to INQUIRY always
+ * (after a selection timeout ... of 250ms).
+ */
+#ifdef __powerpc64__
+static unsigned int scsi_inq_timeout = SCSI_TIMEOUT/HZ+25;
+#else
static unsigned int scsi_inq_timeout = SCSI_TIMEOUT/HZ+3;
+#endif
module_param_named(inq_timeout, scsi_inq_timeout, int, S_IRUGO|S_IWUSR);
MODULE_PARM_DESC(inq_timeout,
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-25 9:25 ` Olaf Hering
@ 2004-08-25 11:58 ` Matthew Wilcox
2004-08-25 12:09 ` Olaf Hering
` (2 more replies)
0 siblings, 3 replies; 20+ messages in thread
From: Matthew Wilcox @ 2004-08-25 11:58 UTC (permalink / raw)
To: Olaf Hering; +Cc: James Bottomley, willy, SCSI Mailing List, Anton Blanchard
On Wed, Aug 25, 2004 at 11:25:41AM +0200, Olaf Hering wrote:
> This broken chip seems to be so popular on PPC64 that the arch maintainers
> want a PPC64 specific default. Oh well ...
>
> +/* Some AChip ARC765 based DVD-ROM's take 15 or more seconds
> + * to reset. A scan will fail if made right after a reset.
> + * It's completely broken device behaviour: SCSI specification
> + * says devices need to be able to respond to INQUIRY always
> + * (after a selection timeout ... of 250ms).
> + */
> +#ifdef __powerpc64__
> +static unsigned int scsi_inq_timeout = SCSI_TIMEOUT/HZ+25;
> +#else
> static unsigned int scsi_inq_timeout = SCSI_TIMEOUT/HZ+3;
> +#endif
>
> module_param_named(inq_timeout, scsi_inq_timeout, int, S_IRUGO|S_IWUSR);
> MODULE_PARM_DESC(inq_timeout,
How about hacking the ppc64 bootloader to always pass inq_timeout=30 instead?
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-25 11:58 ` Matthew Wilcox
@ 2004-08-25 12:09 ` Olaf Hering
2004-08-25 12:11 ` Anton Blanchard
2004-08-25 13:23 ` James Bottomley
2 siblings, 0 replies; 20+ messages in thread
From: Olaf Hering @ 2004-08-25 12:09 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: James Bottomley, SCSI Mailing List, Anton Blanchard
On Wed, Aug 25, Matthew Wilcox wrote:
> How about hacking the ppc64 bootloader to always pass inq_timeout=30 instead?
I did not know that value was tuneable (havent looked at the code using
it). That would be an option, sure.
--
USB is for mice, FireWire is for men!
sUse lINUX ag, nÜRNBERG
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-25 11:58 ` Matthew Wilcox
2004-08-25 12:09 ` Olaf Hering
@ 2004-08-25 12:11 ` Anton Blanchard
2004-08-25 13:43 ` Doug Maxey
2004-08-25 13:23 ` James Bottomley
2 siblings, 1 reply; 20+ messages in thread
From: Anton Blanchard @ 2004-08-25 12:11 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: Olaf Hering, James Bottomley, SCSI Mailing List
> > This broken chip seems to be so popular on PPC64 that the arch maintainers
> > want a PPC64 specific default. Oh well ...
> >
> > +/* Some AChip ARC765 based DVD-ROM's take 15 or more seconds
> > + * to reset. A scan will fail if made right after a reset.
> > + * It's completely broken device behaviour: SCSI specification
> > + * says devices need to be able to respond to INQUIRY always
> > + * (after a selection timeout ... of 250ms).
> > + */
> > +#ifdef __powerpc64__
> > +static unsigned int scsi_inq_timeout = SCSI_TIMEOUT/HZ+25;
> > +#else
> > static unsigned int scsi_inq_timeout = SCSI_TIMEOUT/HZ+3;
> > +#endif
> >
> > module_param_named(inq_timeout, scsi_inq_timeout, int, S_IRUGO|S_IWUSR);
> > MODULE_PARM_DESC(inq_timeout,
>
> How about hacking the ppc64 bootloader to always pass inq_timeout=30 instead?
Alternatively make scsi_inq_timeout non static and we can tweak this at
boot in ppc64 arch code. Assuming we no longer use these POS drives we
can avoid bumping the value on new machines.
Anton
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-25 11:58 ` Matthew Wilcox
2004-08-25 12:09 ` Olaf Hering
2004-08-25 12:11 ` Anton Blanchard
@ 2004-08-25 13:23 ` James Bottomley
2004-08-25 19:13 ` Mike Anderson
2 siblings, 1 reply; 20+ messages in thread
From: James Bottomley @ 2004-08-25 13:23 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: Olaf Hering, SCSI Mailing List, Anton Blanchard
On Wed, 2004-08-25 at 07:58, Matthew Wilcox wrote:
> How about hacking the ppc64 bootloader to always pass inq_timeout=30 instead?
This was indeed the solution I thought we agreed to last time.
James
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-25 12:11 ` Anton Blanchard
@ 2004-08-25 13:43 ` Doug Maxey
0 siblings, 0 replies; 20+ messages in thread
From: Doug Maxey @ 2004-08-25 13:43 UTC (permalink / raw)
To: Anton Blanchard
Cc: Matthew Wilcox, Olaf Hering, James Bottomley, SCSI Mailing List
On Wed, 25 Aug 2004 22:11:29 +1000, Anton Blanchard wrote:
>
>> > This broken chip seems to be so popular on PPC64 that the arch maintainers
>> > want a PPC64 specific default. Oh well ...
>> >
>> > +/* Some AChip ARC765 based DVD-ROM's take 15 or more seconds
>> > + * to reset. A scan will fail if made right after a reset.
>> > + * It's completely broken device behaviour: SCSI specification
>> > + * says devices need to be able to respond to INQUIRY always
>> > + * (after a selection timeout ... of 250ms).
>> > + */
>> > +#ifdef __powerpc64__
>> > +static unsigned int scsi_inq_timeout = SCSI_TIMEOUT/HZ+25;
>> > +#else
>> > static unsigned int scsi_inq_timeout = SCSI_TIMEOUT/HZ+3;
>> > +#endif
>> >
>> > module_param_named(inq_timeout, scsi_inq_timeout, int, S_IRUGO|S_IWUSR);
>> > MODULE_PARM_DESC(inq_timeout,
>>
>> How about hacking the ppc64 bootloader to always pass inq_timeout=30 instead?
>
>Alternatively make scsi_inq_timeout non static and we can tweak this at
>boot in ppc64 arch code. Assuming we no longer use these POS drives we
>can avoid bumping the value on new machines.
>
These ACARDs are on all iseries with optical drives, and it is a
limitation of ATAPI devices. You should actually wait 31 sec to
be sure.
++doug
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-25 13:23 ` James Bottomley
@ 2004-08-25 19:13 ` Mike Anderson
0 siblings, 0 replies; 20+ messages in thread
From: Mike Anderson @ 2004-08-25 19:13 UTC (permalink / raw)
To: James Bottomley
Cc: Matthew Wilcox, Olaf Hering, SCSI Mailing List, Anton Blanchard
James or Matthew,
Was the SYM_VERSION number going to be advanced post this
change? I guess I can use the checksum now that the driver is
using MODULE_VERSION, but it would be nice if the version
advanced beyond 2.1.18j.
-andmike
--
Michael Anderson
andmike@us.ibm.com
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: [PATCH] fix sym2 negotiation
2004-08-21 18:37 [PATCH] fix sym2 negotiation James Bottomley
2004-08-22 17:32 ` Matthias Andree
2004-08-24 13:29 ` Olaf Hering
@ 2004-08-27 16:54 ` Kai Makisara
2 siblings, 0 replies; 20+ messages in thread
From: Kai Makisara @ 2004-08-27 16:54 UTC (permalink / raw)
To: James Bottomley; +Cc: willy, SCSI Mailing List
On Sat, 21 Aug 2004, James Bottomley wrote:
> The problems with domain validation were just the tip of the iceberg in
> the sym2 driver. Most of its problems seem to come from an overly
> complex set of negotiating rules, which I've swept away with this patch.
>
...
This is a success report.
A couple of days ago I noticed that my HP 5713A tape drive failed domain
validation. The logs showed that this has happened for a long time. I
inserted some printks into spi_dv_device_compare_inquiry in
spi_transport_spi.c. The printks indicated that the drive returned sense
data at first inquiry in the function. The sense code was ILLEGAL REQUEST
and ASC/ASCQ showed "Invalid message error".
After installing the small sym2 patch for old Quantum Atlas drives, the
problem did not disappear. After installing additionally this patch the
domain validation now succeeds.
--
Kai
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2004-08-27 16:54 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-21 18:37 [PATCH] fix sym2 negotiation James Bottomley
2004-08-22 17:32 ` Matthias Andree
2004-08-22 18:03 ` James Bottomley
2004-08-24 13:29 ` Olaf Hering
2004-08-24 20:39 ` Mike Anderson
2004-08-24 20:48 ` Vladimir G. Ivanovic
2004-08-24 20:50 ` Matthew Wilcox
2004-08-24 21:39 ` Vladimir G. Ivanovic
2004-08-24 22:12 ` Matthew Wilcox
2004-08-25 0:48 ` Vladimir G. Ivanovic
2004-08-24 20:51 ` Olaf Hering
2004-08-25 6:57 ` Mike Anderson
2004-08-25 9:25 ` Olaf Hering
2004-08-25 11:58 ` Matthew Wilcox
2004-08-25 12:09 ` Olaf Hering
2004-08-25 12:11 ` Anton Blanchard
2004-08-25 13:43 ` Doug Maxey
2004-08-25 13:23 ` James Bottomley
2004-08-25 19:13 ` Mike Anderson
2004-08-27 16:54 ` Kai Makisara
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox