All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Giacomo Mulas <gmulas@ca.astro.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel 2.4.4: BUG in ll_rw_blk.c?
Date: Wed, 9 May 2001 16:51:25 +0200	[thread overview]
Message-ID: <20010509165125.C521@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0105091634370.29725-100000@capitanata.ca.astro.it>
In-Reply-To: <Pine.LNX.4.21.0105091634370.29725-100000@capitanata.ca.astro.it>; from gmulas@ca.astro.it on Wed, May 09, 2001 at 04:45:15PM +0200

On Wed, May 09 2001, Giacomo Mulas wrote:
> 	I am running a 2.4.4 kernel compiled from the sources in the
> debian kernel-source package (it only includes a couple of small patches
> taken from pre and ac, as far as I can tell) and run in the following
> oopses, always while compiling the kernel itself. Here I included three
> different oopses, and the computer had been rebooted between them (for
> different reasons). Is this a known bug? Any fix available for it?
> The computer is a 500MHz PIII, with a 440BX chipset on the motherboard,
> more data available if required (just ask) running debian potato. The only
> "nonstandard" system component is a 2.1.3 libc6 compiled with the 2.4.4
> kernel headers, to be able to use large files. Here come the
> (decoded) oopses:
> 
> May  7 14:57:11 stampace kernel: elevator returned crap (-1072325408)
> May  7 14:57:11 stampace kernel: kernel BUG at ll_rw_blk.c:778!
> May  7 14:57:11 stampace kernel: invalid operand: 0000

If this happens, either your kernel or hardware is seriously screwed --
this is a _never happens_ case. So I suggest that you try a pristine
kernel, most likely this one has been mangled.

-- 
Jens Axboe


      reply	other threads:[~2001-05-09 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-09 14:45 kernel 2.4.4: BUG in ll_rw_blk.c? Giacomo Mulas
2001-05-09 14:51 ` Jens Axboe [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=20010509165125.C521@suse.de \
    --to=axboe@suse.de \
    --cc=gmulas@ca.astro.it \
    --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 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.