From: Jens Axboe <axboe@suse.de>
To: merlin hughes <merlin@merlin.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at drivers/scsi/scsi_lib.c:819 with 2.5.44-ac5
Date: Wed, 30 Oct 2002 15:35:02 +0100 [thread overview]
Message-ID: <20021030143502.GK3416@suse.de> (raw)
In-Reply-To: <20021030141812.BF07786921@primary.mx.nitric.com>
On Wed, Oct 30 2002, merlin hughes wrote:
> Hi,
>
> Tyan Tiger S2466-4M, 2xAthlon MP, Adaptec 29160, Adaptec 2940u2w,
> software RAID 5, gcc 2.95.4. The core drives are on the 29160. Works
> fine under 2.4.19.
>
> 2.5.44 panics during boot with SCSI problems; I didn't catch what the
> error was.
>
> 2.5.44-ac5 boots but bugs after a few seconds.
>
> Attached: config, syslog, lspci (under 2.4.19)
>
> Oct 28 12:36:09 badb kernel: Incorrect number of segments after building list
> Oct 28 12:36:09 badb kernel: counted 2, received 1
> Oct 28 12:36:09 badb kernel: req nr_sec 8, cur_nr_sec 8
Please try 2.5.44-BK and see if that works, James fixed this one.
--
Jens Axboe
next prev parent reply other threads:[~2002-10-30 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 14:18 kernel BUG at drivers/scsi/scsi_lib.c:819 with 2.5.44-ac5 merlin hughes
2002-10-30 14:35 ` Jens Axboe [this message]
2002-10-30 15:43 ` merlin
2002-10-30 18:15 ` Patrick Mansfield
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=20021030143502.GK3416@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=merlin@merlin.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