[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: Crash



I interpret the crash like this...

1. Someone went to check their mail
2. The pop server had to spawn a process (authentication/delivery/or
whatever)
3. It called mmap to allocate memory for the spawned process
4. Crash!

Could be bad code in pop server.  Could be bad memory.  I would recompile
kernel and pop server just to make sure that it doesn't happen again.  Also
if you are changing $CC / $CFLAGS options, use the defaults.



> -----Original Message-----
> From: Bryan Opfer [mailto:redhat balor tldinc net]
> Sent: Saturday, February 27, 1999 1:02 PM
> To: Statux
> Cc: redhat-list redhat com
> Subject: Re: Crash
>
>
>
>
> On Fri, 26 Feb 1999, Statux wrote:
>
> > Bryan Opfer wrote:
> >
> > > My server crashed last night and when I rebooted it, I
> had a bunch of
> > > errors like the following in the messages log.
> > >
> > > ---------------------------------
> > >
> > > Feb 26 08:49:47 www kernel: general protection: 0000
> > > Feb 26 08:49:47 www kernel: CPU:    0
> > > Feb 26 08:49:47 www kernel: EIP:    0010:[shrink_mmap+120/524]
> > > Feb 26 08:49:47 www kernel: EFLAGS: 00010286
> > > Feb 26 08:49:47 www kernel: eax: 80000000   ebx: 0038c548
>   ecx: 00000006
> > > edx: 80000000
> > > Feb 26 08:49:47 www kernel: esi: 000003ff   edi: 00001fff
>   ebp: 00008000
> > > esp: 03ec5ec0
> > > Feb 26 08:49:47 www kernel: ds: 0018   es: 0018   fs:
> 002b   gs: 002b
> > > ss: 0018
> > > Feb 26 08:49:47 www kernel: Process ipop3d (pid: 1106,
> process nr: 44,
> > > stackpage=03ec5000)
> > > Feb 26 08:49:47 www kernel: Stack: 00000006 00000001
> 00000000 00000000
> > > 04999700 80000000 0011fd00 00000006
> > > Feb 26 08:49:47 www kernel:        00000000 00000001
> 00000003 00000118
> > > 00000000 04999700 0012073d 00000003
> > > Feb 26 08:49:47 www kernel:        00000000 00000001
> 00013000 00017000
> > > 00000000 04999700 0027c2b0 00016000
> > > Feb 26 08:49:47 www kernel: Call Trace: [try_to_free_page+80/180]
> > > [__get_free_pages+421/444] [try_to_read_ahead+40/296]
> > > [generic_file_read+686/1536] [sys_read+190/228] [system_call+85/
> > > 124]
> > > Feb 26 08:49:47 esus kernel: Code: f6 42 14 10 74 0e 0f
> ba 72 14 04 19 c0
> > > 0f ba 6b 18 02 19 c0
> > >
> > > ----------------------------------
> > >
> > > Does anyone know what would cause those messages?  Bad memory or
> > > something?  or do I need to upgrade the kernel.  The
> machine is running
> > > Redhat 4.2 and kernel 2.0.32
> > >
> > > Thanks,
> > > Bryan Opfer
> > >
> > > --
> > >   PLEASE read the Red Hat FAQ, Tips, Errata and the
> MAILING LIST ARCHIVES!
> > >                 http://www.redhat.com http://archive.redhat.com
> > >          To unsubscribe: mail redhat-list-request redhat com with
> > >                        "unsubscribe" as the Subject.
> >
> > Perhaps.. sorta looks like a plain kernel crash.. then
> again you could have
> > some hardware stories floating around... What processor
> (company/version) do
> > you have in that machine?
>
> The processor is a Pentium 200Mhz (non MMX).
>
> -Bryan Opfer
>
>
> --
>   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING
> LIST ARCHIVES!
> 		http://www.redhat.com http://archive.redhat.com
>          To unsubscribe: mail redhat-list-request redhat com with
>                        "unsubscribe" as the Subject.
>



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]