From: "Ivan G." <ivangurdiev@linuxfreemail.com>
To: James Simmons <jsimmons@transvirtual.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
LFB <linux-fbdev-devel@lists.sourceforge.net>
Subject: 2.5.11 framebuffer kernel panic
Date: Mon, 29 Apr 2002 14:38:25 -0600 [thread overview]
Message-ID: <02042914382500.00843@cobra.linux> (raw)
In-Reply-To: <Pine.LNX.4.10.10204291056490.15166-100000@www.transvirtual.com>
Well, here's the result of my first 2.5 compiled kernel :
Codes were hand-copied. Inaccuracy is possible but unlikely.
I checked several times.
----------------------------------------------------------------
ksymoops 2.4.0 on i686 2.4.19-pre3. Options used
-v /usr/src/linux-2.5.11/vmlinux (specified)
-K (specified)
-L (specified)
-o /lib/modules/2.5.11 (specified)
-m /boot/System.map-2.5.11 (specified)
No modules in ksyms, skipping objects
Unable to handle kernel NULL pointer dereference at virtual address 000001b4
*pde = 00000000
oops: 0000
CPU: 0
EIP: 0010: [<c02055f6>] Not tainted.
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010283
eax: c0336570 ebx: 00007f80 ecx: 00000000
esi: 00000000 edi: 00000180 ebp: 00000000 esp: d3eefce8
ds: 0018 es: 0018 ss: 0018
Stack: 00007f80 c0336680 c1313800 00000000 c0203a70 c0336570 00000002 00000000
00000180 00000003 c02b48f4 c02b4a60 00000206 00000003 00000246 c012f69f
c02b48f4 c02b4a5c 000001f0 00000000 c12d79c0 000001f0 c1308000 c012d39e
Call Trace: [<c0203a70>] [<c012f69f>] [<c012d39f>] [<c01ff424>] [<c0200990>]
[<c01ba4a9>] [<c01fef53>] [<c01fe603>] [<c01ba5de>] [<c01be0ed>]
[<c01fd91a>] [<c0105000>] [<c0105070>] [<c0105000>] [<c0105646>]
[<c0105050>]
Code: 8b 9d b4 01 00 00 85 db 0f 84 ac 00 00 00 0f b7 82 02 01 00
>>EIP; c02055f6 <atyfb_cursor+16/e0> <=====
Trace; c0203a70 <atyfbcon_switch+70/e0>
Trace; c012f69f <__alloc_pages+3f/180>
Trace; c012d39f <kmem_cache_grow+ef/270>
Trace; c01ff424 <fbcon_cursor+b4/1e0>
Trace; c0200990 <fbcon_switch+140/1c0>
Trace; c01ba4a9 <redraw_screen+c9/140>
Trace; c01fef53 <fbcon_setup+843/940>
Trace; c01fe603 <fbcon_init+b3/e0>
Trace; c01ba5de <visual_init+9e/100>
Trace; c01be0ed <take_over_console+ad/180>
Trace; c01fd91a <register_framebuffer+fa/130>
Trace; c0105000 <_stext+0/0>
Trace; c0105070 <init+20/180>
Trace; c0105000 <_stext+0/0>
Trace; c0105646 <kernel_thread+26/30>
Trace; c0105050 <init+0/180>
Code; c02055f6 <atyfb_cursor+16/e0>
00000000 <_EIP>:
Code; c02055f6 <atyfb_cursor+16/e0> <=====
0: 8b 9d b4 01 00 00 mov 0x1b4(%ebp),%ebx <=====
Code; c02055fc <atyfb_cursor+1c/e0>
6: 85 db test %ebx,%ebx
Code; c02055fe <atyfb_cursor+1e/e0>
8: 0f 84 ac 00 00 00 je ba <_EIP+0xba> c02056b0
<atyfb_cursor+d0/e0>
Code; c0205604 <atyfb_cursor+24/e0>
e: 0f b7 82 02 01 00 00 movzwl 0x102(%edx),%eax
<0> Kernel panic: Attempted to kill Init!
next prev parent reply other threads:[~2002-04-29 20:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 5:53 2.5.11 framebuffer compilation error Ivan G.
2002-04-29 9:26 ` Miles Lane
2002-04-29 18:01 ` James Simmons
2002-04-29 19:38 ` Ivan G.
2002-04-29 20:38 ` Ivan G. [this message]
2002-04-29 22:52 ` 2.5.11 framebuffer kernel panic James Simmons
2002-04-30 1:54 ` 2.5.11 framebuffer kernel panic [Resolved] Ivan G.
2002-04-30 16:53 ` James Simmons
2002-05-02 12:28 ` 2.5.11 framebuffer compilation error Paul Mackerras
2002-05-02 22:20 ` James Simmons
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=02042914382500.00843@cobra.linux \
--to=ivangurdiev@linuxfreemail.com \
--cc=jsimmons@transvirtual.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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