From: Bryce Harrington <bryce@osdl.org>
To: "Moore, Eric" <Eric.Moore@lsil.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [OOPS] -git8,9: NULL pointer dereference in mptspi_dv_renegotiate_work
Date: Fri, 29 Sep 2006 17:27:55 -0700 [thread overview]
Message-ID: <20060930002755.GI12968@osdl.org> (raw)
In-Reply-To: <664A4EBB07F29743873A87CF62C26D70350500@NAMAIL4.ad.lsil.com>
On Fri, Sep 29, 2006 at 06:10:42PM -0600, Moore, Eric wrote:
> On Friday, September 29, 2006 3:41 PM, Bryce Harrington wrote:
> > > Can you enable debug messages in the driver Makefile, for
> > > the line called MPT_DEBUG_CONFIG; that way we can find out which
> > > config page failed.
> >
> > Sure; not sure what the interesting part is, but here's the full log
> > from this:
> >
> > http://crucible.osdl.org/runs/2265/sysinfo/amd01.2.console
> >
>
>
> Thanks. It appears you enabled MPT_DEBUG instead of MPT_DEBUG_CONFIG.
> All the "WaitForDoorbell" debugs are from that. Can you recheck your
> Makefile.
Does this look better?
http://crucible.osdl.org/runs/2265/sysinfo/amd01.3.console
Bryce
next prev parent reply other threads:[~2006-09-30 0:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 0:10 [OOPS] -git8,9: NULL pointer dereference in mptspi_dv_renegotiate_work Moore, Eric
2006-09-30 0:10 ` Moore, Eric
2006-09-30 0:27 ` Bryce Harrington [this message]
[not found] ` <664A4EBB07F29743873A87CF62C26D702A994F@NAMAIL4.ad.lsil.com>
2006-09-30 21:55 ` Bryce Harrington
-- strict thread matches above, loose matches on Subject: below --
2006-09-29 18:29 Moore, Eric
2006-09-29 18:29 ` Moore, Eric
2006-09-29 21:41 ` Bryce Harrington
2006-09-28 20:25 Bryce Harrington
2006-09-28 21:51 ` Andrew Morton
2006-09-28 22:54 ` Bryce Harrington
2006-09-29 0:26 ` Andrew Morton
2006-09-29 17:17 ` Bryce Harrington
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=20060930002755.GI12968@osdl.org \
--to=bryce@osdl.org \
--cc=Eric.Moore@lsil.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.