public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Hammers <ch@westend.com>
To: linux-kernel@vger.kernel.org
Subject: Re: BUG() in asm/pci.h:142 with 2.4.13 (cause found!)
Date: Tue, 30 Oct 2001 15:25:49 +0100	[thread overview]
Message-ID: <20011030152549.A18935@westend.com> (raw)
In-Reply-To: <20011025120701.C6557@westend.com>
In-Reply-To: <20011025120701.C6557@westend.com>; from ch@westend.com on Thu, Oct 25, 2001 at 12:07:01PM +0200

Hello

The cause for my problems with crashing kernels when accessing the tape
drive were differences between the original external RAID that belongs
to the machine and a temporarily, nearly equal, RAID that we attached while
the original was send away for repair. 
The temp. RAID was Ultra3 160 and /proc/scsi/aic7xxx/0 showed me a cur.
speed of 160 while the "old" and working one only did Ultra2 with 80Mbit/s.

I don't know if it's a hardware incompatibility or if the Linux kernel 
drivers cannot handle this specific case.

The problem exists in 2.4.11-pre6, 2.4.13, 2.4.12-ac6 and 2.4.13 with
patched from axboa(?) and D. Miller.
 
bye,

 -christian-


On Thu, Oct 25, 2001 at 12:07:01PM +0200, Christian Hammers wrote:
...
> 2.4.13 was the easiest one to reproduce: when starting the tape backup
> to a HP DDS3/DAT Streamer (C1537A) via a Adaptec SCSI Controller 
> (Adaptec 7892A in /proc/pci) on a Gigabyte GA-6VTXD Dual Motherboard with
> two PIII and 2GB of RAM it crashed immediately with the error attached
> below. The machine was under "stresstest-simulation" load at this time.
...
> kernel: kernel BUG at /usr/local/src/kernel/linux-2.4.13/include/asm/pci.h:142!
...
> kernel: scsi0:0:0:0: Attempting to queue an ABORT message
> kernel: (scsi0:A:0:0): Queuing a recovery SCB
> kernel: scsi0:0:0:0: Device is disconnected, re-queuing SCB  
...

-- 
Christian Hammers    WESTEND GmbH - Aachen und Dueren     Tel 0241/701333-0
ch@westend.com     Internet & Security for Professionals    Fax 0241/911879
           WESTEND ist CISCO Systems Partner - Premium Certified


      parent reply	other threads:[~2001-10-30 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 10:07 BUG() in asm/pci.h:142 with 2.4.13 Christian Hammers
2001-10-25 10:18 ` Jens Axboe
2001-10-25 11:11 ` Jens Axboe
2001-10-25 17:23   ` Christian Hammers
2001-10-25 17:32     ` Jens Axboe
2001-10-25 17:47       ` Christian Hammers
2001-10-26  0:25       ` SCSI tape crashes (was Re: BUG() in asm/pci.h:142 with 2.4.13) David S. Miller
2001-10-26  2:26         ` Jeff V. Merkey
2001-10-26  1:32           ` SCSI tape crashes David S. Miller
2001-10-26  3:56             ` Jeff V. Merkey
2001-10-26  1:33           ` SCSI tape crashes (was Re: BUG() in asm/pci.h:142 with 2.4.13) Christian Hammers
2001-10-28  1:34         ` Pete Harlan
2001-10-25 20:10 ` BUG() in asm/pci.h:142 with 2.4.13 Christian Hammers
2001-10-30 14:25 ` Christian Hammers [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=20011030152549.A18935@westend.com \
    --to=ch@westend.com \
    --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