From: Doug Ledford <dledford@redhat.com>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: 2.5.43 oops in adaptec driver
Date: Wed, 16 Oct 2002 21:49:34 -0400 [thread overview]
Message-ID: <20021017014934.GM8159@redhat.com> (raw)
In-Reply-To: <20021016210914.P15163@parcelfarce.linux.theplanet.co.uk>
On Wed, Oct 16, 2002 at 09:09:14PM +0100, Matthew Wilcox wrote:
> On Wed, Oct 16, 2002 at 01:57:54PM -0400, Doug Ledford wrote:
> > Duh, forgot to add INIT_LIST_HEAD(&p->aic_devs); to aic7xxx_register() so
> > the list_add() is oopsing. Patch attached. Let me know if this *doesn't*
> > solve the problem (I'm not at work where I can test this yet).
>
> well, it partially solves the problem. it doesn't oops any more, but
> it still offlines all the devices.
>
> here's the boot log:
>
> SCSI subsystem driver Revision: 1.00
> (scsi0) <Adaptec AIC-7899 Ultra 160/m SCSI host adapter> found at PCI 2/1/0
> (scsi0) Wide Channel A, SCSI ID=7, 32/255 SCBs
> (scsi0) Downloading sequencer code... 396 instructions downloaded
> (scsi1) <Adaptec AIC-7899 Ultra 160/m SCSI host adapter> found at PCI 2/1/1
> (scsi1) Wide Channel B, SCSI ID=7, 32/255 SCBs
> (scsi1) Downloading sequencer code... 396 instructions downloaded
> scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.5/5.2.0
> <Adaptec AIC-7899 Ultra 160/m SCSI host adapter>
> scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.2.5/5.2.0
> <Adaptec AIC-7899 Ultra 160/m SCSI host adapter>
> Vendor: Model: Rev:
> Type: Direct-Access ANSI SCSI revision: 00
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after error recovery: host 0 channel 0 id 0 lun 0
> scsi_eh_offline_sdevs: Device offlined - not ready or command retry failed after error recovery: host 0 channel 0 id 1 lun 0
> Vendor: Model: Rev:
> Type: Direct-Access ANSI SCSI revision: 00
Hmmm...this is classic interrupt routing problem type symptoms. Can you
try booting with noapic or with a up kernel and see what happens? Also,
try Justin's driver. Interestingly enough, here mine works with no more
changes than just the one I already sent to you and Justin's doesn't :-/
Going to start debugging Justin's driver for now until I hear back from
you.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
prev parent reply other threads:[~2002-10-17 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 17:41 2.5.43 oops in adaptec driver Matthew Wilcox
2002-10-16 17:57 ` Doug Ledford
2002-10-16 20:09 ` Matthew Wilcox
2002-10-17 1:49 ` 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=20021017014934.GM8159@redhat.com \
--to=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=willy@debian.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.