linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: linux-scsi@vger.kernel.org
Subject: Re: qla1280: failing mbox check
Date: Fri, 12 May 2006 09:07:22 -0400	[thread overview]
Message-ID: <4464888A.1000807@gentoo.org> (raw)
In-Reply-To: <yq04pzvr9dz.fsf@jaguar.mkp.net>

Jes Sorensen wrote:
> 'git bisect' is your friend here.
> 
> Cheers,
> Jes

That was the answer I was afraid of....  Already tried using git bisect to track 
down a bootmem allocation bug in SGI O2 systems (2.6.17 just broke everything it 
seems...), but the bisection point happened to be around the time when all the 
bitops changes were occuring (moving duplicate functions from asm-mips -> 
asm-generic), resulting in a tree that wouldn't even compile.

Having to patch up a broken tree so it even builds to determine if the bisection 
is good or bad might obscure the bug, but well, guess that's something to try on 
the weekend.

Offhand, though, is there anything I should keep an eye out for that can do 
things like setting mb[] to 0x0 (i.e., things you guys might've seen happen in 
the past?).  And what do those numbers for 'mailbox0', 'ictrl', and 'istatus' 
mean (I'm guessing not much, because they're probably qla1040-specific error 
codes that require chip docs to understand).


--Kumba

-- 
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees

"Such is oft the course of deeds that move the wheels of the world: small hands 
do them because they must, while the eyes of the great are elsewhere."  --Elrond

  reply	other threads:[~2006-05-12 13:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12  4:06 qla1280: failing mbox check Kumba
2006-05-12  7:26 ` Jes Sorensen
2006-05-12 13:07   ` Kumba [this message]
2006-05-15  9:13     ` Jes Sorensen
2006-05-16  4:36       ` Kumba

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4464888A.1000807@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).