From: "René Rebe" <rene.rebe@gmx.net> To: James Simmons <jsimmons@transvirtual.com> Cc: linux-kernel@vger.kernel.org, ademar@conectiva.com.br, rolf@sir-wum.de, linux-fbdev-devel@lists.sourceforge.net Subject: Re: sis630 - help needed debugging in the kernel Date: Wed, 13 Jun 2001 23:25:02 +0200 [thread overview] Message-ID: <20010613232502.34fd0237.rene.rebe@gmx.net> (raw) In-Reply-To: <Pine.LNX.4.10.10106130952590.16375-100000@transvirtual.com> In-Reply-To: <20010613172320.306d5208.rene.rebe@gmx.net> <Pine.LNX.4.10.10106130952590.16375-100000@transvirtual.com> [-- Attachment #1: Type: text/plain, Size: 746 bytes --] Thanks for the quick reply! On Wed, 13 Jun 2001 09:54:21 -0700 (PDT) James Simmons <jsimmons@transvirtual.com> wrote: > > > I currently try to debug why the sisfb driver crashes my machine. (SIS 630 > > based laptop - linux-2.4.5-ac13). > > You can do one of two things. Post both System.map and the complete oops > or you can run ksymoops on the oops. I can find the problem then. Thanks. ksymoops' output is attached. [...] k33p h4ck1n6 René -- René Rebe (Registered Linux user: #127875) http://www.rene.rebe.myokay.net/ -Germany- Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms. [-- Attachment #2: ksymoops.txt --] [-- Type: application/octet-stream, Size: 2452 bytes --] ksymoops 2.3.7 on i686 2.4.4-ac5. Options used -V (specified) -K (specified) -L (specified) -O (specified) -m /mnt/net/portable/usr/src/linux/System.map (specified) Unable to handle kernel paging request at virtual address cc800180 c01b8f61 *pde = 0af2d067 Oops: 0002 CPU: 0 EIP: 0010:[<c01b8f61>] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010206 eax: 0f0f0f0f ebx: c026e51c ecx: 00000003 edx: 00000000 esi: cc800180 edi: c026f460 ebp: 0f0f0f0f esp: c12fde50 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 1, stackpage=c12fd000) Stack: c02c23e0 c02dc4c0 00000593 00000000 cc7fdc08 ffffffff 00000000 00000320 cc7fdc00 c01ac77c c12ee000 c02dc4c0 c12fe342 00000001 0000051e 00000000 c12fe340 c12fe342 00000001 00000593 c018150c c12ee000 c12fe340 00000001 Call Trace: [<cc7fdc08>] [<cc7fdc00>] [<c01ac77c>] [<c018150c>] [<c0181584>] [<c01adede>] [<c0181f04>] [<c01856f9>] [<c01aaeb9>] [<c0105013>] [<c010542c>] Code: 89 06 8a 03 24 0f 0f b6 d0 8b 44 24 18 23 04 97 31 e8 89 46 >>EIP; c01b8f61 <fbcon_cfb8_putcs+1ad/2c8> <===== Trace; cc7fdc08 <END_OF_CODE+c51ad78/????> Trace; cc7fdc00 <END_OF_CODE+c51ad70/????> Trace; c01ac77c <fbcon_putcs+b8/d0> Trace; c018150c <do_update_region+118/164> Trace; c0181584 <update_region+2c/38> Trace; c01adede <fbcon_switch+1aa/1bc> Trace; c0181f04 <redraw_screen+e0/160> Trace; c01856f9 <take_over_console+ed/188> Trace; c01aaeb9 <register_framebuffer+f9/140> Trace; c0105013 <init+7/114> Trace; c010542c <kernel_thread+28/38> Code; c01b8f61 <fbcon_cfb8_putcs+1ad/2c8> 00000000 <_EIP>: Code; c01b8f61 <fbcon_cfb8_putcs+1ad/2c8> <===== 0: 89 06 mov %eax,(%esi) <===== Code; c01b8f63 <fbcon_cfb8_putcs+1af/2c8> 2: 8a 03 mov (%ebx),%al Code; c01b8f65 <fbcon_cfb8_putcs+1b1/2c8> 4: 24 0f and $0xf,%al Code; c01b8f67 <fbcon_cfb8_putcs+1b3/2c8> 6: 0f b6 d0 movzbl %al,%edx Code; c01b8f6a <fbcon_cfb8_putcs+1b6/2c8> 9: 8b 44 24 18 mov 0x18(%esp,1),%eax Code; c01b8f6e <fbcon_cfb8_putcs+1ba/2c8> d: 23 04 97 and (%edi,%edx,4),%eax Code; c01b8f71 <fbcon_cfb8_putcs+1bd/2c8> 10: 31 e8 xor %ebp,%eax Code; c01b8f73 <fbcon_cfb8_putcs+1bf/2c8> 12: 89 46 00 mov %eax,0x0(%esi) <0>Kernel panic: Attempted to kill init!
prev parent reply other threads:[~2001-06-13 21:25 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-13 15:23 René Rebe 2001-06-13 16:54 ` James Simmons 2001-06-16 21:27 ` René Rebe 2001-06-17 14:03 ` James Simmons 2001-06-18 18:32 ` René Rebe 2001-06-18 19:28 ` Paul Mundt 2001-06-18 21:58 ` James Simmons 2001-06-18 22:02 ` Paul Mundt 2001-06-18 21:01 ` René Rebe 2001-06-13 21:25 ` René Rebe [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=20010613232502.34fd0237.rene.rebe@gmx.net \ --to=rene.rebe@gmx.net \ --cc=ademar@conectiva.com.br \ --cc=jsimmons@transvirtual.com \ --cc=linux-fbdev-devel@lists.sourceforge.net \ --cc=linux-kernel@vger.kernel.org \ --cc=rolf@sir-wum.de \ --subject='Re: sis630 - help needed debugging in the kernel' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).