From: Paul Blazejowski <paulb@blazebox.homeip.net>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Linux [2.6.0-test3/mm1] aic7xxx problems.
Date: Tue, 12 Aug 2003 14:56:16 -0400 [thread overview]
Message-ID: <1060714576.849.3.camel@blaze.homeip.net> (raw)
In-Reply-To: <2425882704.1060622541@aslan.btc.adaptec.com>
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
On Mon, 2003-08-11 at 13:22, Justin T. Gibbs wrote:
>
> I don't think that any of the changes between 6.2.35 and 6.2.36 will
> make a difference for you, but you could try upgrading. The source
> files are here:
>
> http://people.FreeBSD.org/~gibbs/linux/SRC/
>
> The console output you've provided makes me think that interrupts are
> not working correctly in your system.
>
> --
> Justin
>
>
Justin,
I have a nice oops from the
http://people.freebsd.org/~gibbs/linux/SRC/aic79xx-linux-2.5-20030603-tar.gz driver on 2.6.0-test3.
I took few snaps which show the scsi controller scan process and the
oops from kernel, they are at:
http://www.blazebox.homeip.net:81/diffie/images/linux-2.6.0-test2/2.6.36/
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-08-12 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1060543928.887.19.camel@blaze.homeip.net>
2003-08-11 17:22 ` Linux [2.6.0-test3/mm1] aic7xxx problems Justin T. Gibbs
2003-08-11 17:39 ` Paul Blazejowski
2003-08-11 19:42 ` Rahul Karnik
2003-08-12 1:10 ` Paul Blazejowski
[not found] ` <3F384819.4070108@genebrew.com>
2003-08-12 18:09 ` Paul Blazejowski
2003-08-13 18:38 ` Justin T. Gibbs
2003-08-25 0:16 ` Paul Blazejowski
2003-08-12 18:56 ` Paul Blazejowski [this message]
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=1060714576.849.3.camel@blaze.homeip.net \
--to=paulb@blazebox.homeip.net \
--cc=gibbs@scsiguy.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox