All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick <patrick@spacesurfer.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel oops in tcp_ipv4.c
Date: Sat, 13 Jan 2001 13:36:46 +0000	[thread overview]
Message-ID: <3A6059EE.CC565072@spacesurfer.com> (raw)

Mike Galbraith wrote:
> 
> On Fri, 12 Jan 2001, Patrick wrote:
> 
> > I am running a medium-high traffic web server on an SMP machine. I have
> > always had problems with linux hanging (No syslog messages and no
> > console response). I have tried kernel versions 2.2.12, 2.2.14 and
> > 2.2.16
> > Recently I tried 2.2.17, this kernel was up for about a month, before
> > there was a kernel oops. The syslog messages are:
> >
> > Jan 11 21:10:06 ws2 kernel: tcp_v4_hash: bug, socket state is 1
> > Jan 11 21:10:06 ws2 kernel: Unable to handle kernel NULL pointer
> > dereference at virtual address 00000000
> > Jan 11 21:10:06 ws2 kernel: current->tss.cr3 = 0ca7c000, %cr3 = 0ca7c000
> > Jan 11 21:10:06 ws2 kernel: *pde = 00000000
> > Jan 11 21:10:06 ws2 kernel: Oops: 0002
> > Jan 11 21:10:06 ws2 kernel: CPU:    0
> >
> > The code that outputs the first message is in tcp_ipv4.c, and was added
> > in version 2.2.17. The code deliberately causes a kernel oops when it
> > encounters this bug, presumably because the IP stack is unusable at this
> > point.
> >
> > If this code was deliberately added then presumably someone knows what
> > might cause the problem. Is there a patch somewhere that fixes this
> > problem?
> 
> Hi,
> 
> You should post the full processed oops.. what the trap is there for ;-)
> 
>         -Mike

Hello Mike,

How do I process the oops? Are kernel core dumps generated when there is
an oops and if so where is the core file?

regards,
Patrick
-- 
Patrick Mackinlay                                patrick@spacesurfer.com
ICQ: 59277981                                        tel: +44 7050699851
                                                     fax: +44 7050699852
SpaceSurfer Limited                          http://www.spacesurfer.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-13 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-13 13:36 Patrick [this message]
     [not found] <200101132029.f0DKTla156931@saturn.cs.uml.edu>
2001-01-14 13:23 ` Kernel oops in tcp_ipv4.c Patrick
  -- strict thread matches above, loose matches on Subject: below --
2001-01-12 19:06 Patrick
2001-01-14 19:46 ` kuznet
2001-01-14 20:05   ` Patrick

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=3A6059EE.CC565072@spacesurfer.com \
    --to=patrick@spacesurfer.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pim@uknet.spacesurfer.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.