mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fernando Jimenez <fjimenez@roundcorners.com>
To: linux-kernel@vger.kernel.org
Subject: Re: newbie Q: kernel BUG at vmalloc.c??
Date: Mon, 4 Mar 2002 13:31:13 +0000	[thread overview]
Message-ID: <20020304132620Z292359-889+117147@vger.kernel.org> (raw)
In-Reply-To: <20020304131308Z292338-889+117136@vger.kernel.org>
In-Reply-To: <20020304131308Z292338-889+117136@vger.kernel.org>

OK, please ignore this. I was making a rather stupid mistake. I clearly am in need of another caffeine fix. ;)

Thanks anyway

FJ

On Monday 04 March 2002 13:17, Fernando Jimenez wrote:
> Hi all
>
> I am coding a relatively simple (although it's proving quite hard) module
> for the linux kernel, and I have bumped into this!!
>
> Mar  4 13:09:55 localhost kernel: kernel BUG at vmalloc.c:235!
> Mar  4 13:09:55 localhost kernel: invalid operand: 0000
> Mar  4 13:09:55 localhost kernel: CPU:    0
> Mar  4 13:09:55 localhost kernel: EIP:    0010:[<c01320a6>]    Not tainted
> Mar  4 13:09:55 localhost kernel: EFLAGS: 00000282
> Mar  4 13:09:55 localhost kernel: eax: 0000001d   ebx: 0804b000   ecx:
> 00000001   edx: 000021ba Mar  4 13:09:55 localhost kernel: esi: 0804aa20  
> edi: 00000000   ebp: c616ff98   esp: c616ff14 Mar  4 13:09:55 localhost
> kernel: ds: 0018   es: 0018   ss: 0018
> Mar  4 13:09:55 localhost kernel: Process ioctl (pid: 1121,
> stackpage=c616f000) Mar  4 13:09:55 localhost kernel: Stack: c028bf79
> 000000eb 00000002 00000001 00000282 00000001 c0350a64 00000246 Mar  4
> 13:09:55 localhost kernel:        00000024 c616ff98 0804aa20 0804aa20
> 00000000 c616ff98 c8829e08 0804aa20 Mar  4 13:09:55 localhost kernel:      
>  000001f2 00000163 c013faed c585537c c5feb23c c68cdc94 c7d1a000 c13b396c
> Mar  4 13:09:55 localhost kernel: Call Trace: [<c8829e08>] [<c013faed>]
> [<c0114906>] [<c0150706>] [<c01075bb>] Mar  4 13:09:55 localhost kernel:
> Mar  4 13:09:55 localhost kernel: Code: 0f 0b 5b 5e 31 c0 e9 a4 02 00 00 6a
> 02 53 e8 d7 fd ff ff 5a
>
> I'm sure I must be doing something wrong somewhere, but the line "kernel
> BUG at vmalloc" does look worrying, and I don't quite know where it's
> comming from. I'm using kernel 2.4.17 on a RH7.2 box, and the ofending part
> of code is:
>
> mdp_blks_use = vmalloc(mdp_blk_use_size * sizeof(char));
>
> where mdp_blk_use_size is an integer, and I'm sure it's been set to
> something, and mdp_blks_use is a char pointer. I have used vmalloc in other
> parts of the code and it works fine. This is very confusing
>
> Sorry if I'm doing something glaringly stupid here, still quite a newbie at
> kernel hacking. :) Thanks for your help -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

      reply	other threads:[~2002-03-04 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-04 13:17 Fernando Jimenez
2002-03-04 13:31 ` Fernando Jimenez [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=20020304132620Z292359-889+117147@vger.kernel.org \
    --to=fjimenez@roundcorners.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

all inboxes | Powered by JetHome®