mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srihari Vijayaraghavan <harisri@bigpond.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Jens Axboe <axboe@suse.de>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>,
	Arjan van de Ven <arjanv@redhat.com>
Subject: Re: 2.5.49: kernel BUG at drivers/block/ll_rw_blk.c:1950!
Date: Wed, 27 Nov 2002 19:12:05 +1100	[thread overview]
Message-ID: <200211271912.05131.harisri@bigpond.com> (raw)
In-Reply-To: <15843.54741.609413.371274@notabene.cse.unsw.edu.au>

Hello Neil,

On Wednesday 27 November 2002 07:13, Neil Brown wrote:
> Srihari, could you possibly try with the following patch please to see
> if it gives more useful information.

No worries. That did the trick.

The following message appears just before the first oops:
Nov 27 18:56:32 localhost kernel: bio_add_page: want to add 4096 at 17658 but 
only allowed 3072 - prepare to oops...

second oops:
Nov 27 18:56:36 localhost kernel:  <3>bio_add_page: want to add 4096 at 426874 
but only allowed 3072 - prepare to oops...

And the third:
Nov 27 18:56:39 localhost kernel:  <3>bio_add_page: want to add 4096 at 427002 
but only allowed 3072 - prepare to oops...

Hope that helps. I can give the oops report(s) if you need (but they are once 
again the same "kernel BUG at drivers/block/ll_rw_blk.c:1950!").

Thanks.
-- 
Hari
harisri@bigpond.com


  reply	other threads:[~2002-11-27  7:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26 11:03 Srihari Vijayaraghavan
2002-11-26 19:56 ` Andrew Morton
2002-11-26 20:13   ` Neil Brown
2002-11-27  8:12     ` Srihari Vijayaraghavan [this message]
2002-11-27  8:29       ` Jens Axboe
2002-11-27  8:37         ` Andrew Morton
2002-12-01 23:49         ` Neil Brown
2002-12-02  8:24           ` Jens Axboe
2002-11-26 20:22   ` Arjan van de Ven

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=200211271912.05131.harisri@bigpond.com \
    --to=harisri@bigpond.com \
    --cc=akpm@digeo.com \
    --cc=arjanv@redhat.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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®