mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Kasprzak <kas@informatics.muni.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AIC7xxx kernel driver; ATTN Mr. Justin T. Gibbs
Date: Fri, 29 Jun 2001 11:34:07 +0200	[thread overview]
Message-ID: <20010629113407.C1100@informatics.muni.cz> (raw)
In-Reply-To: <3B38C4D2.EB2A8944@mycompany.com> <E15Ewis-0003ul-00@the-village.bc.nu>
In-Reply-To: <E15Ewis-0003ul-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, Jun 26, 2001 at 06:33:58PM +0100

Alan Cox wrote:
: Except for an obscure bug under very high memory load I'm not aware of any 
: outstanding bugs in the AIC7xxx driver, certainly not like you describe. There
: is however always a first time for any bug 8)

	Well, AIC7xxx crashes on me with stock 2.4.5 kernel
(Athlon TB 850, ASUS A7V). I run 2.4.3 + zerocopy patches, and when I tried
to upgrade to 2.4.5, it crashes during boot while initializing the AIC7xxx
driver. I have written down the Oops numbers by hand, but I had to
reboot the server back to 2.4.3+zerocopy.

	Here are relevant parts of dmesg on 2.4.3 (just to identify the
hardware):

SCSI subsystem driver Revision: 1.00
request_module[scsi_hostadapter]: Root fs not mounted
PCI: Found IRQ 12 for device 00:0a.0
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.1.5
        <Adaptec 2940 Ultra SCSI adapter>
        aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs

  Vendor: SEAGATE   Model: ST118273W         Rev: 5698
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
(scsi0:A:0): 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
scsi0:0:0:0: Tagged Queuing enabled.  Depth 8
SCSI device sda: 35566480 512-byte hdwr sectors (18210 MB)
 sda: sda1 sda2

Now the Oops tracing:

EIP was ahc_match_scb + 0x19

Call trace:

ahc_search_qinfifo + 0x187
ahc_abort_scbs + 0x6a
__udelay + 0x27
ahc_reset_current_channel + 0x27c
ahc_pci_config + 0x4e2
pci_read_config_byte + 0x1c
...

-Yenya

-- 
\ Jan "Yenya" Kasprzak <kas at fi.muni.cz>       http://www.fi.muni.cz/~kas/
\\ PGP: finger kas at aisa.fi.muni.cz   0D99A7FB206605D7 8B35FCDE05B18A5E //
\\\             Czech Linux Homepage:  http://www.linux.cz/              ///
It is a very bad idea to feed negative numbers to memcpy.         --Alan Cox

  reply	other threads:[~2001-06-29  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 17:22 myemail
2001-06-26 17:33 ` Alan Cox
2001-06-29  9:34   ` Jan Kasprzak [this message]
2001-06-26 19:46 ` Brian Gerst
2001-06-29 17:40 ` Justin T. Gibbs

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=20010629113407.C1100@informatics.muni.cz \
    --to=kas@informatics.muni.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®