From: Jens Axboe <axboe@suse.de>
To: Peter Osterlund <petero2@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel BUG at scsi_merge.c:83
Date: Wed, 2 Jan 2002 08:32:23 +0100 [thread overview]
Message-ID: <20020102083223.J16092@suse.de> (raw)
In-Reply-To: <m2zo3xr0qu.fsf@pengo.localdomain>
In-Reply-To: <m2zo3xr0qu.fsf@pengo.localdomain>
On Wed, Jan 02 2002, Peter Osterlund wrote:
> Hi!
>
> While doing some stress testing on the 2.5.2-pre5 kernel, I am hitting
> a kernel BUG at scsi_merge.c:83, followed by a kernel panic. The
> problem is that scsi_alloc_sgtable fails because the request contains
> too many physical segments. I think this patch is the correct fix:
Correct, ll_rw_blk default is ok now. I missed this when killing
scsi_malloc/scsi_dma, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2002-01-02 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 1:38 [PATCH] kernel BUG at scsi_merge.c:83 Peter Osterlund
2002-01-02 7:32 ` Jens Axboe [this message]
2002-01-02 11:23 ` Peter Osterlund
-- strict thread matches above, loose matches on Subject: below --
2002-01-03 4:28 Douglas Gilbert
2002-01-03 8:18 ` Jens Axboe
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=20020102083223.J16092@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
/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