All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathias Klein <ma_klein@gmx.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: oops in kernel 2.6.15-rc7
Date: Mon, 2 Jan 2006 13:57:53 +0100	[thread overview]
Message-ID: <20060102125750.GB21933@sidney> (raw)
In-Reply-To: <43B5B37F.4040508@liberouter.org>


[-- Attachment #1.1: Type: text/plain, Size: 2486 bytes --]

On Fri, Dec 30, 2005 at 11:23:59PM +0100, Jiri Slaby wrote:
> Mathias Klein napsal(a):
> > Hello,
> > 
> > i recently got another oops. As suggested by Pekka Enberg I've enabled
> > CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC.
> > 
> > If you need more informations please let me know.
> > 
> > ------------------------------------------------------------------------
> > 
> > Dec 30 20:12:11 sidney kernel: [31895.552562] Unable to handle kernel NULL pointer dereference at virtual address 00000020
> > Dec 30 20:12:11 sidney kernel: [31895.552699]  printing eip:
> > Dec 30 20:12:11 sidney kernel: [31895.552914] c0136b90
> > Dec 30 20:12:11 sidney kernel: [31895.552933] *pde = 00000000
> > Dec 30 20:12:11 sidney kernel: [31895.553014] Oops: 0000 [#1]
> > Dec 30 20:12:11 sidney kernel: [31895.553065] PREEMPT 
> > Dec 30 20:12:11 sidney kernel: [31895.553147] Modules linked in: sd_mod usb_storage scsi_mod md5 ipv6 lp capi kernelcapi capifs nls_iso8859_15 nls_cp437 vfat fat parport_pc parport joydev evdev nvidiafb 8139too mii rivafb crc32 tuner tvaudio msp3400 bttv video_buf firmware_class snd_ens1370 gameport i2c_algo_bit snd_rawmidi snd_seq_device snd_bt87x v4l2_common btcx_risc tveeprom videodev snd_pcm snd_ak4531_codec snd_timer snd_page_alloc snd soundcore i2c_viapro i2c_core uhci_hcd usbcore ide_cd cdrom
> > Dec 30 20:12:11 sidney kernel: [31895.554927] CPU:    0
> > Dec 30 20:12:11 sidney kernel: [31895.554933] EIP:    0060:[mempool_free+4/104]    Not tainted VLI
> > Dec 30 20:12:11 sidney kernel: [31895.554942] EFLAGS: 00010282   (2.6.15-rc7.sidney.11) 
> [snip]
> > Dec 30 20:12:11 sidney kernel: [31895.559540]  [pdflush+31/33] pdflush+0x1f/0x21
> > Dec 30 20:12:11 sidney kernel: [31895.559665]  [kthread+110/156] kthread+0x6e/0x9c
> > Dec 30 20:12:11 sidney kernel: [31895.559797]  [kernel_thread_helper+5/11] kernel_thread_helper+0x5/0xb
> > Dec 30 20:12:11 sidney kernel: [31895.559922] Code: 7e 14 00 75 05 e8 46 d2 16 00 89 d8 89 fa e8 8b 32 ff ff 8b 45 dc e9 6f ff ff ff 31 db 8d 65 f4 89 d8 5b 5e 5f c9 c3 55 89 e5 57 <56> 8b 7d 08 53 8b 5d 0c 8b 43 10 39 43 14 7d 43 89 d8 e8 89 da 
> mm, strange, could you post .config, gcc version and one more question, what is
> .sidney.11?

sidney.xx is only an alias for the maschine I build that kernel for and a
number indicating a .config. No patches are included in the kernel.

Please see attached the .config
gcc version is 4.0.2-2 (Debian package version)

Mathias

[-- Attachment #1.2: config-2.6.15-rc7.sidney.11.gz --]
[-- Type: application/octet-stream, Size: 5504 bytes --]

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-01-02 13:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-30 19:44 oops in kernel 2.6.15-rc7 Mathias Klein
2005-12-30 22:23 ` Jiri Slaby
2006-01-02 12:57   ` Mathias Klein [this message]
2005-12-31  1:40 ` Jiri Slaby
2006-01-02 13:00   ` Mathias Klein

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=20060102125750.GB21933@sidney \
    --to=ma_klein@gmx.de \
    --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.