Dave wrote:

> Thanks, Jason. Looks like disabling intrd didn't help
> at all, though. :(

Do you get an "excessive interrupt processing.  Disabling port"
message from the nv_sata driver before that WARNING, perhaps?

See bug 6642154:

  http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6642154


I'm now running opensolaris with an nv_sata driver changed like this,
and so far, there have been no more "excessive interrupt processing"
hangs:

diff -r a183e54573d2 usr/src/uts/common/sys/sata/adapters/nv_sata/nv_sata.h
--- a/usr/src/uts/common/sys/sata/adapters/nv_sata/nv_sata.h    Thu Feb 07 
06:05:33 2008 -0800
+++ b/usr/src/uts/common/sys/sata/adapters/nv_sata/nv_sata.h    Thu Dec 13 
10:23:15 2007 +0100
@@ -625,7 +625,7 @@ typedef struct prde {
  * processing loop, declare the interrupt wedged and
  * disable.
  */
-#define        NV_MAX_INTR_LOOP 10
+#define        NV_MAX_INTR_LOOP 32
 
 /*
  * flag values for nv_copy_regs_out

> I wonder, can I force Solaris to use the legacy ata
> driver for the MCP55 chip in SXCE b81?

Should work by removing the relevant "nv_sata" 
driver binding entry from the /etc/driver_aliases file.

Note that if your root filesystem is on "nv_sata"
this will break booting from that drive, until you
manually fix the bootpath in /boot/solaris/bootenv.rc,
and update /etc/vfstab with the new disk device
names.

> --
> Dave
> 
> On 02/06/2008 03:21 PM, Jason J. W. Williams wrote:
> > Hi Dave,
> > 
> > This might help:
> http://docs.sun.com/app/docs/doc/820-0724/gawod?a=view
> > 
> > -J
> > 
> > On Feb 6, 2008 3:03 PM, David Anderson
> <[EMAIL PROTECTED]> wrote:
> >> I see someone submitted this same bug about 3 days
> ago:
> >>
> >>
> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bu
> g_id=6658565
> >>
> >> Can anyone comment on whether disabling intrd is a
> safe workaround until
> >> the bug is fixed in future SXCE releases? What
> else might disabling
> >> intrd adversely affect?
> >>
> >> I'm dead in the water until I can either
> workaround or have a fix.
> >> Please advise.
> >>
> >> --
> >> Dave
> >>
> >> On 02/06/2008 02:15 PM, Dave wrote:
> >>
> >>> I've got a number of machines running nv_b81 and
> I'm getting messages
> >>> like this:
> >>>
> >>> WARNING: /[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/[EMAIL 
> >>> PROTECTED],0 (sd0):
> >>>          Error for Command: read(10)
>                Error Level: Retryable
> quested Block: 10089026                  Error Block:
> 10089026
> >>>          Vendor: ATA
>                                Serial Number:
> Additional_Sense
> >>>          ASC: 0x0 (no additional sense info),
> ASCQ: 0x0, FRU: 0x0
> >>> NOTICE: /[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]:
> >>>   port 0: device reset
> >>>
> >>> I'm unable to use the machines after I get the
> warning - they must be
> >>> hard rebooted. I've tried disabling NCQ in
> /etc/system without success.
> >>> This has happened in prior versions of Nevada as
> well. I usually get the
> >>> message when first booting, but not always.
> >>>
> >>> All machines are running Dual Proc Opteron 2214,
> Tyan 2927G2NR
> >>> motherboard, WD 500GB SATA drives.
> >>>
> >>> I'm at my wits end trying to find the solution.
> Any help is appreciated.
> >>>
> >>> Thanks
> >>> --
> >>> Dave
> >>> _______________________________________________
> >>> storage-discuss mailing list
> >>> [email protected]
> >>>
> http://mail.opensolaris.org/mailman/listinfo/storage-d
> iscuss
> >> _______________________________________________
> >> storage-discuss mailing list
> >> [email protected]
> >>
> http://mail.opensolaris.org/mailman/listinfo/storage-d
> iscuss
> >>
> _______________________________________________
> storage-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/storage-d
> iscuss
 
 
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to