From: Doug Ledford <dledford@redhat.com>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: Tigran Aivazian <tigran@veritas.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [bug] aic7xxx panic Re: Linux 2.4.1-ac5
Date: Wed, 07 Feb 2001 19:02:56 -0500 [thread overview]
Message-ID: <3A81E230.E0482280@redhat.com> (raw)
In-Reply-To: <E14QbMw-0001JD-00@the-village.bc.nu> <Pine.LNX.4.21.0102072113080.1699-100000@penguin.homenet> <20010208002950.A1254@werewolf.able.es>
"J . A . Magallon" wrote:
>
> On 02.07 Tigran Aivazian wrote:
> > Alan, Doug,
> >
> > If this is a known problem -- ignore. Otherwise, I will gladly assist as
> > much as you need.
> >
> > Just tried ac5 kernel and, behold (btw, why does serial console not work
> > anymore, I had to copy these by hand):
> >
> > (scsi0) BRKADRINT error(0x44):
> > Illegal Opcode in sequencer program
> > PCI Error detected
> > (scsi0) SEQADDR=0x58
> > Kernel panic: aic7xxx: unrecoverable BRKADRINT
> >
> > The Linux 2.4.2-pre1 works fine. Next thing I was thinking was to try ac4
> > and also to try on a different machine which has a different revision of
> > the same type of aic7xxx HBA.
> >
>
> I am running ac5 on a AHA-2940U2/W, no problem.
>
> I patched the kernel with a patch from Doug Ledford posted in the list.
Problems with disks and CD-ROMs connected to non-Ultra2 controllers is
confirmed and I think my fix is just about done (currently testing a minor
sequencer change to solve the problem, I cleared SG_COUNT when I shouldn't
have, which meant disconnects in the middle of a transfer spelled death for
the transfer, resulting in a data overrun on reconnect, and this problem only
shows up on non-Ultra2 controllers under real transfers scenarios, which my
testing missed because I was using all Ultra2 controllers, so I built another
test machine with non-Ultra2 controllers to check my fix)
--
Doug Ledford <dledford@redhat.com> http://people.redhat.com/dledford
Please check my web site for aic7xxx updates/answers before
e-mailing me about problems
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-08 0:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 20:10 Linux 2.4.1-ac5 Alan Cox
2001-02-07 20:30 ` Christoph Hellwig
2001-02-07 20:39 ` Alan Cox
2001-02-07 20:54 ` Matthias Schniedermeyer
2001-02-07 21:03 ` Adrian Bunk
2001-02-07 22:13 ` [bug] aic7xxx panic " Tigran Aivazian
2001-02-07 23:29 ` J . A . Magallon
2001-02-08 0:02 ` Doug Ledford [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=3A81E230.E0482280@redhat.com \
--to=dledford@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
/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.