mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.11
Date: Thu, 3 Mar 2005 01:54:37 +0100	[thread overview]
Message-ID: <20050303005436.GA11516@mail.13thfloor.at> (raw)
In-Reply-To: <4225C86C.8000502@tls.msk.ru>

On Wed, Mar 02, 2005 at 05:06:36PM +0300, Michael Tokarev wrote:
> Herbert Poetzl wrote:
> []
> >BUG_ON() and friends are still broken (at least on x86)
> []
> >Freeing unused kernel memory: 244k freed
> >------------[ cut here ]------------
> >kernel BUG at <bad filename>:9377!
> >	      ~~~~~~~~~~~~~~~~~~~
> 
> Have you tried compiling with CONFIG_DEBUG_INFO=y ?
> (Looks like CONFIG_DEBUG_BUGVERBOSE should either
> depend on CONFIG_DEBUG_INFO or turn it on).

egrep 'CONFIG_DEBUG_(INFO|BUGVERBOSE)' .config
# CONFIG_DEBUG_BUGVERBOSE is not set
CONFIG_DEBUG_INFO=y

good point, just it seems to be the other way round ..

with CONFIG_DEBUG_BUGVERBOSE set I get the correct
file and line, but no stack information ...

Freeing unused kernel memory: 104k freed
------------[ cut here ]------------
kernel BUG at init/main.c:692!
invalid operand: 0000 [#1]
PREEMPT 
CPU:    0
EIP:    0060:[<c0100330>]    Not tainted VLI
EFLAGS: 00000246   (2.6.11-rc1) 
eax: 00000000   ebx: c01002b0   ecx: 00000000   edx: 00000000
esi: 00000000   edi: 00000000   ebp: 00000000   esp: c10bdff0
ds: 007b   es: 007b   ss: 0068
Process swapper (pid: 1, threadinfo=c10bc000 task=c10b3aa0)
Stack: c0100635 00000000 00000000 00000000 
Call Trace:
 [<c0100635>]
Code: 29 c0 01 00 00 00 6a 00 6a 02 68 97 0a 24 c0 e8 47 07 06 00 83 c4 0c 85 c0 78 60 6a 00 e8 a9 80 07 00 6a 00 e8 a2 80 07 00 58 5a <0f> 0b b4 02 13 0a 24 c0 a1 24 21 29 c0 85 c0 75 32 68 a4 0a 24 

maybe there is another option which sneaked in,
will investigate ...

thanks,
Herbert

PS: was it ever considered to hard code the explicit BUG_*
files and lines via a macro instead of that (probably very
fancy and efficient but nevertheless) strange address stuff?

I mean, are bug reports with missing/wrong file/line info
really what the kernel developers want to see in the future?

> /mjt

  reply	other threads:[~2005-03-03  1:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02  8:02 Linus Torvalds
2005-02-28 18:44 ` key bounce problem with 2.6.11-rc5 Jan Niehusmann
2005-03-02 20:06   ` bouncing keys and skipping sound with 2.6.11 Jan Niehusmann
2005-03-06 18:55     ` Jan Niehusmann
2005-03-07  7:26       ` Stefan Seyfried
2005-03-12 11:13         ` Jan Niehusmann
2005-03-02 10:31 ` Linux 2.6.11 Matthias Andree
2005-03-02 11:01   ` Jesper Juhl
2005-03-02 15:46   ` Linus Torvalds
2005-03-02 16:47     ` Matthias Andree
2005-03-02 17:35       ` Linus Torvalds
2005-03-03  5:20     ` Ryan Anderson
2005-03-03 12:21       ` Matthias Andree
2005-03-02 12:47 ` Herbert Poetzl
2005-03-02 14:06   ` Michael Tokarev
2005-03-03  0:54     ` Herbert Poetzl [this message]
2005-03-02 16:18 ` John Cherry
2005-03-02 23:24 ` Jan Dittmer
2005-03-06  0:19 ` J.A. Magallon
2005-03-06  5:48   ` Trond Myklebust
2005-03-06  6:03     ` Neil Brown

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=20050303005436.GA11516@mail.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    /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®