RE: Oops in 2.1.104p1 + Trace

Jordan Mendelson (jordy@wserv.com)
Fri, 29 May 1998 10:44:47 -0400


Just a followup on this, I forgot to mention that I did follow 'make
mrpropper' to turn off SMP... that did *NOT* fix it.

The machine contains the following:

NE2000 clone ISA
Motorola VoiceSurfer 56k ISA
Adaptec 2930 PCI
Matrox Millenium 2 PCI
Creative Labs Voodoo2 PCI
Ensoniq AudioPCI PCI
SCSI JVC CDR
IDE Toshiba CD-ROM
Intel 82371SB PIIX3 Chipset (USB, the works)
2 IDE HD's (conner and quantum)
96 megs EDO RAM
Pentium-2 266

> -----Original Message-----
> From: owner-linux-kernel@vger.rutgers.edu
> [mailto:owner-linux-kernel@vger.rutgers.edu]On Behalf Of Jordan
> Mendelson
> Sent: Friday, May 29, 1998 1:16 AM
> To: linux-kernel@vger.rutgers.edu
> Subject: Oops in 2.1.104p1 + Trace
>
>
>
> Ok, I get this during boot directly after my scsi cdrom detection...
>
> Oops: 0000
> CPU: 0
> EIP: 0010:[<c010aa07>]
> EFLAGS: 00010046
> eax: 00000010 ebx: 0009e000 ecx: 00000000 edx: 00000010
> esi: 00000000 edi: c038e000 ebp: c038ddcc esp: c038dd54
> ds: 0018 es: 0018 ss: 0018
> Process swapper: (pid: 1, process nr: 1, stackpage = c038d000)
> Stack: c01e002b c038ddcc 00000000 c038ddcc c038de20 06000000
> c7000000 c6800000
> 0018a497 c010aa81 c038ddcc c01e07e3 c01e1600 00000000
> 00000000 c010f95c
> c01e1600 c038ddcc 00000000 c038c000 00000000 0000002f
> c038de20 00000000
> CallTrace: [<c01e002b>] [<c7000000>] [<c6800000>] [<c010aa81>]
> [<c01e07e3>] [<c01e1600>] [<c010f95c>]
> [<c01e1600>] [<c01c9328>] [<c010a6f4>] [<c01120c5>]
> [<c0118365>] [<c010b61d>] [<c010a67c>] [<c01dddcd>]
> [<c01dde2a>] [<c01c273a>] [<c0202ad3>] [<c01c9d6e>]
> [<c01c9cb0>] [<c01c9759>] [<c01c2d0c>] [<c01c37cf>]
> [<c01c9b8c>] [<c012ef44>] [<c010a5bc>] [<c0120bb4>]
> [<c01e0018>] [<c01080d7>] [<c0107fdc>] [<c0108088>]
> Code: 64 8a 04 0e 0f a1 88 c2 31 c0 88 d0 89 44 24 10 50 68 db07
> Aiee, killing interrupt handler
>
>
> Using `/System.map' to map addresses to symbols.
>
> >>EIP: c010aa07 <show_registers+203/23c>
> Trace: c01e002b <stext_lock+bb3/1f01>
> Trace: c7000000
> Trace: c6800000
> Trace: c010aa81 <die_if_kernel+41/50>
> Trace: c01e07e3 <stext_lock+136b/1f01>
> Trace: c01e1600 <bad_pmd_string+287/2ff>
> Trace: c010f95c <do_page_fault+30c/31c>
> Trace: c01e1600 <bad_pmd_string+287/2ff>
> Trace: c01c9328 <sr_detect>
> Trace: c010a6f4 <error_code+30/38>
> Trace: c01120c5 <timer_bh+32d/37c>
> Trace: c0118365 <do_bottom_half+45/64>
> Trace: c010b61d <do_IRQ+3d/44>
> Trace: c010a67c <ret_from_intr>
> Trace: c01dddcd <__delay+5/8>
> Trace: c01dde2a <__const_udelay+12/18>
> Trace: c01c273a <scsi_do_cmd+32a/3f0>
> Trace: c0202ad3 <RCSid+6abd/6b0e>
> Trace: c01c9d6e <sr_do_ioctl+9a/210>
> Trace: c01c9cb0 <sr_ioctl_done>
> Trace: c01c9759 <get_capabilities+5d/1c8>
> Trace: c01c2d0c <scsi_init_malloc+34/6c>
> Trace: c01c37cf <resize_dma_pool+2f7/3d0>
> Trace: c01c9b8c <sr_finish+e0/16c>
> Trace: c012ef44 <sys_setup+40/44>
> Trace: c010a5bc <system_call+38/3c>
> Trace: c0120bb4 <kswapd>
> Trace: c01e0018 <stext_lock+ba0/1f01>
> Trace: c01080d7 <init+4f/1a8>
> Trace: c0107fdc <this_must_match_init_task+1fdc/2000>
> Trace: c01080d7 <init+4f/1a8>
> Code: c010aa07 <show_registers+203/23c>
> Code: c010aa07 <show_registers+203/23c> 64 8a 04 0e
> movb %fs:(%esi,%ecx,1),%al
> Code: c010aa0b <show_registers+207/23c> 0f a1 popl %fs
> Code: c010aa0d <show_registers+209/23c> 88 c2
> movb %al,%dl
> Code: c010aa0f <show_registers+20b/23c> 31 c0
> xorl %eax,%eax
> Code: c010aa17 <show_registers+213/23c> 88 d0
> movb %dl,%al
> Code: c010aa19 <show_registers+215/23c> 89 44 24 10
> movl %eax,0x10(%esp,1)
> Code: c010aa1d <show_registers+219/23c> 50 pushl %eax
> Code: c010aa1e <show_registers+21a/23c> 68 07 00 00 90
> pushl $0x90000007
> Code: c010aa29 <show_registers+225/23c> 90 nop
> Code: c010aa2a <show_registers+226/23c> 90 nop
>
> Intel Pentium 2 266
> Intel 82371SB PIIX3 Chipset
> gcc version egcs-2.90.25 980302 (egcs-1.0.2 prerelease)
> Linux 2.1.104p1 w/ SMP = 1 & commented out
>
> It took me about an hour to write down this Oops message, and I'm sure I
> still didn't get it right. You'd think someone would put an option in the
> kernel to automatically attempt to do a call trace in something I can
> actually read. Also, damn Oops messages wrap on my 80 char wide display,
> plus the first line of the Call Trace contains 7 calls and not 8 making it
> uneven causing me undo stress when quadrupal checking :)
>
>
> Jordan
>
> --
> Jordan Mendelson : http://jordy.wserv.com
> Web Services, Inc. : http://www.wserv.com
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
>

--
Jordan Mendelson     : http://jordy.wserv.com
Web Services, Inc.   : http://www.wserv.com

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu