From: Cliff Albert <cliff@oisec.net>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda
Date: Sat, 28 Apr 2001 20:31:43 +0200 [thread overview]
Message-ID: <20010428203143.A27784@oisec.net> (raw)
In-Reply-To: <20010428202225.D11994@emma1.emma.line.org>
In-Reply-To: <20010428202225.D11994@emma1.emma.line.org>; from matthias.andree@stud.uni-dortmund.de on Sat, Apr 28, 2001 at 08:22:25PM +0200
On Sat, Apr 28, 2001 at 08:22:25PM +0200, Matthias Andree wrote:
> These have further devices (CD writer, CD-ROM drive), and these machines
> are 100% in 2.2.19. With 2.4.3 and 2.4.4-pre8, I get this problem
> (pencil & paper copy for Machine #2, DO NOT "grep"):
>
> AIC 7XXX EISA/VLB/PCI SCSI HBA DRIVER 6.1.5
> aic7880: wide Channel A, SCSI ID=7, 16/255 SCBs
> scsi0: SCSI host adapter emulation for IDE devices
> PCI: found IRQ 5 for dev 00:09.0
> scsi1:0:0:0: Attempting to queue an abort message.
> Command found on device queue
> aic7xxx_abort returns 8194
Getting the same errors here, but only a few seconds after my adaptec gets initialized and all disks/cdrs/zips get attached + mounted. On 2.4.3-ac14 it only gives these errors and happily runs afterwards. But on 2.4.4 it panics after $random time.
My setup is a P2B-S motherboard with a Quantum Fireball ST 6.4 GB HDD
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.1.11
<Adaptec aic7890/91 Ultra2 SCSI adapter>
aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs
Vendor: QUANTUM Model: FIREBALL ST6.4S Rev: 0F0C
Type: Direct-Access ANSI SCSI revision: 02
(scsi0:A:0): 20.000MB/s transfers (20.000MHz, offset 15)
And the specific errors are
scsi0:0:0:0: Attempting to queue a TARGET RESET message
scsi0:0:0:0: Command not found
aic7xxx_dev_reset returns 8194
Device not ready. Make sure there is a disc in the drive.
> Then, the Kernel detects the SECOND SCSI disk and attaches it as sda
> (Linux 2.2 would mount that as sdb), the first disk is "gone" (Linux 2.2
> would mount that as sda). Regretfully, my root partition is on the
> FIRST SCSI disk, so the kernel panicks since it cannot mount /.
>
> That's all I copied in a hurry, maybe it's sufficient to debug, if not,
> I can try to grab a null modem cable and catch the full sequence; I'd be
> glad if someone could mention the "canonical" aic7xxx LILO append
> parameters for a full debug trace in that case.
--
Cliff Albert | IRCNet: #linux.nl, #ne2000, #linux, #freebsd.nl
cliff@oisec.net | #openbsd, #ipv6, #cu2.nl
-[ICQ: 18461740]--------| 6BONE: CA2-6BONE RIPE: CA3348-RIPE
next prev parent reply other threads:[~2001-04-28 18:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 18:22 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda Matthias Andree
2001-04-28 18:31 ` Cliff Albert [this message]
2001-04-28 18:47 ` poptix
2001-04-29 11:21 ` Matthias Andree
2001-04-29 9:36 ` Steve 'Denali' McKnelly
2001-04-29 10:25 ` J . A . Magallon
2001-04-29 16:17 ` Steve 'Denali' McKnelly
2001-04-29 18:09 ` J . A . Magallon
2001-04-29 22:47 ` Matthias Andree
2001-04-29 16:32 ` David Relson
2001-04-29 23:36 ` Steve 'Denali' McKnelly
2001-04-29 23:39 ` Matthias Andree
2001-04-30 13:40 ` Todd M. Roy
[not found] ` <20010430163045.A13230@emma1.emma.line.org>
2001-04-30 14:36 ` Todd M. Roy
2001-04-30 14:45 ` Cliff Albert
2001-05-03 22:40 ` Matthias Andree
2001-05-02 4:34 ` Justin T. Gibbs
2001-05-02 4:31 ` Justin T. Gibbs
2001-05-03 15:04 ` Success, aic7xxx 6.1.13 fixes boot problems in 2.4.3 2.4.4pre8 2.4.4 (was: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda) Matthias Andree
2001-05-03 19:03 ` Justin T. Gibbs
-- strict thread matches above, loose matches on Subject: below --
2001-04-29 5:20 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda Royans Tharakan
2001-04-29 11:23 ` Matthias Andree
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=20010428203143.A27784@oisec.net \
--to=cliff@oisec.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@stud.uni-dortmund.de \
/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.