public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wenzhuo Zhang <wenzhuo@zhmail.com>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: Re: [OOPS] 2.4.13-ac5 default_idle [even more info]
Date: Thu, 22 Nov 2001 21:33:47 +0800	[thread overview]
Message-ID: <20011122213346.A2634@zhmail.com> (raw)
In-Reply-To: <20011120234928.B714@zhmail.com> <20011121180453.A4734@zhmail.com>
In-Reply-To: <20011121180453.A4734@zhmail.com>


RedHat kernel-2.4.9-13.i586.rpm locks up the pentium box too. 8(

[wenzhuo@daisy wenzhuo]$ ksymoops -m /boot/System.map-2.4.9-13 panda.oops-rh2.4.
9-13 
ksymoops 2.4.1 on i686 2.4.9-13.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.9-13/ (default)
     -m /boot/System.map-2.4.9-13 (specified)

Error (expand_objects): cannot stat(/lib/ext3.o) for ext3
ksymoops: No such file or directory
Error (expand_objects): cannot stat(/lib/jbd.o) for jbd
ksymoops: No such file or directory
Warning (compare_maps): mismatch on symbol partition_name  , ksyms_base
says c01
b5c80, System.map says c0156ea0.  Ignoring ksyms_base entry
Warning (compare_maps): mismatch on symbol usb_devfs_handle  , usbcore
says d086
da00, /lib/modules/2.4.9-13/kernel/drivers/usb/usbcore.o says d086d520.
Ignorin
g /lib/modules/2.4.9-13/kernel/drivers/usb/usbcore.o entry
Warning (map_ksym_to_module): cannot match loaded module ext3 to a
unique module
 object.  Trace may not be reliable.
CPU:  0
EIP:  0010:[<c01053a4>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00000246
eax: 00000000  ebx: c02c4000  ecx: 00000000  edx: 00000019
esi: c0105380  edi: c02c4000  ebp: 0008e000  esp: c02c5fe0
ds: 0018  es: 0018  ss: 0018
Stack: c0105412 00003000 000a0600 c0105000 c02c68ae c0300460 00000000
c0100197
Call Trace: [<c0105412>]  cpu_idle [kernel] 0x42
[<c0105000>] stext [kernel] 0x0
Code: c3 fb c3 89 f6 8d bc 27 00 00 00 00 fb 83 c8 ff ba 00 e0 ff

>>EIP; c01053a4 <default_idle+14/30>   <=====
Trace; c0105412 <cpu_idle+32/70>
Trace; c0105000 <_stext+0/0>
Code;  c01053a4 <default_idle+14/30>
00000000 <_EIP>:
Code;  c01053a4 <default_idle+14/30>   <=====
   0:   c3                        ret       <=====
Code;  c01053a5 <default_idle+15/30>
   1:   fb                        sti    
Code;  c01053a6 <default_idle+16/30>
   2:   c3                        ret    
Code;  c01053a7 <default_idle+17/30>
   3:   89 f6                     mov    %esi,%esi
Code;  c01053a9 <default_idle+19/30>
   5:   8d bc 27 00 00 00 00      lea    0x0(%edi,1),%edi
Code;  c01053b0 <default_idle+20/30>
   c:   fb                        sti    
Code;  c01053b1 <default_idle+21/30>
   d:   83 c8 ff                  or     $0xffffffff,%eax
Code;  c01053b4 <default_idle+24/30>
  10:   ba 00 e0 ff 00            mov    $0xffe000,%edx

  <0> Kernel panic: Attempted to kill the idle task!

3 warnings and 2 errors issued.  Results may not be reliable.


On Wed, Nov 21, 2001 at 06:04:53PM +0800, Wenzhuo Zhang wrote:
> 
> More info:
> It's a slackware-8.0 box.
> # gcc --version
> 2.95.3
> # ld -v
> GNU ld version 2.11.90.0.19 (with BFD 2.11.90.0.19)
> 
> The motherboard is a Asus P/I-P55TP4N. And the CPU is Petium(classic)
> 100MHz.
> # cat cpuinfo 
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 5
> model           : 2
> model name      : Pentium 75 - 200
> stepping        : 6
> cpu MHz         : 99.475
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : yes
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu vme de pse tsc msr mce cx8
> bogomips        : 198.24
> 
> 
> I don't know whether it's a kernel issue or a hardware issue. Pls shed
> light over it. Thanks
> 
> (The box crashed again when I was writing this message.)
> 
> On Tue, Nov 20, 2001 at 11:49:28PM +0800, Wenzhuo Zhang wrote:
> > 
> > Hello,
> > 
> > I noticed frequent crashings of my old Pentium desktop, after I kept it
> > running 24x7 as a gateway/filewall. Tonight, I caught sight of a oops
> > and hand-copied it down.
> > 
> > ksymoops 2.3.4 on i686 2.4.13-ac5.  Options used
> > 		  ^^ Since I cannot compile ksymoops in the slackware-8.0
> >   box, I copied the kernel/modules to another box, and ran ksymoops there.
> >      -V (default)
> >      -k /proc/ksyms (default)
> >      -l /proc/modules (default)
> >      -o /lib/modules/2.4.13-ac5/ (default)
> >      -m /boot/System.map-2.4.13-ac5 (specified)
> > 
> > CPU: 0
> > EIP: 0010:[<c0105173>] Not tainted
> > Using defaults from ksymoops -t elf32-i386 -a i386
> > EFLAGS: 00000246
> > eax: 00000000 ebx: c0210000 ecx: c11e2260 edx: c11e2260
> > esi: c0105150 edi: ffffe000 ebp: 0008e000 esp: c0211fdc
> > ds: 0018 es: 0018 ss:0018
> > Process swapper (pid: 0, stackpage=c0211000)
> > Stack: c01051d7 00003000 000a0600 c0105000 c0105027 c02127f3 00000000 c0246060
> >        c0100197
> > Call Trace: [<c01051d7>] [<c0105000>] [<c0105027>]
> > Code: c3 fb c3 89 f6 fb ba 00 e0 ff ff 21 e2 b8 ff ff ff ff 87 42
> > 
> > >>EIP; c0105173 <default_idle+23/28>   <=====
> > Trace; c01051d7 <cpu_idle+3f/54>
> > Trace; c0105000 <_stext+0/0>
> > Trace; c0105027 <rest_init+27/28>
> > Code;  c0105173 <default_idle+23/28>
> > 00000000 <_EIP>:
> > Code;  c0105173 <default_idle+23/28>   <=====
> >    0:   c3                        ret       <=====
> > Code;  c0105174 <default_idle+24/28>
> >    1:   fb                        sti    
> > Code;  c0105175 <default_idle+25/28>
> >    2:   c3                        ret    
> > Code;  c0105176 <default_idle+26/28>
> >    3:   89 f6                     mov    %esi,%esi
> > Code;  c0105178 <poll_idle+0/20>
> >    5:   fb                        sti    
> > Code;  c0105179 <poll_idle+1/20>
> >    6:   ba 00 e0 ff ff            mov    $0xffffe000,%edx
> > Code;  c010517e <poll_idle+6/20>
> >    b:   21 e2                     and    %esp,%edx
> > Code;  c0105180 <poll_idle+8/20>
> >    d:   b8 ff ff ff ff            mov    $0xffffffff,%eax
> > Code;  c0105185 <poll_idle+d/20>
> >   12:   87 42 00                  xchg   %eax,0x0(%edx)
> > 
> >   <0> Kernel panic: Attempted to kill the idle task!
> > 
> > 
> > Thanks,
> > 
> > -- 
> > Wenzhuo
> >   GnuPG Key ID 0xBA586A68
> >   Key fingerprint = 89C7 C6DE D956 F978 3F12  A8AF 5847 F840 BA58 6A68
> > -
> > 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/
> 
> -- 
> Wenzhuo
>   GnuPG Key ID 0xBA586A68
>   Key fingerprint = 89C7 C6DE D956 F978 3F12  A8AF 5847 F840 BA58 6A68
> -
> 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/

-- 
Wenzhuo
  GnuPG Key ID 0xBA586A68
  Key fingerprint = 89C7 C6DE D956 F978 3F12  A8AF 5847 F840 BA58 6A68

      reply	other threads:[~2001-11-22 13:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20 15:49 [OOPS] 2.4.13-ac5 default_idle Wenzhuo Zhang
2001-11-21 10:04 ` [OOPS] 2.4.13-ac5 default_idle [more info] Wenzhuo Zhang
2001-11-22 13:33   ` Wenzhuo Zhang [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=20011122213346.A2634@zhmail.com \
    --to=wenzhuo@zhmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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