From: root <root@trgras.timpanogas.org>
To: linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Oops in 2.2.18 with pppd dial in server
Date: Thu, 30 Nov 2000 18:59:26 -0700 [thread overview]
Message-ID: <20001130185926.A884@trgras.timpanogas.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 194 bytes --]
Alan,
I was able to reproduce this oops with a somewhat more reliable ksymoops (I was ready for this nasty bug this time). Looks like the problem is in the sockets
code.
See attached.
Jeff
[-- Attachment #2: oops.txt --]
[-- Type: text/plain, Size: 602 bytes --]
ksymoops 0.7c on i686 2.2.18pre21. Options used
EIP: 0010: [<c013365d>]
Using defaults from ksymoops -t elf32-i386 -a i386
Call Trace: [<c014c43d>] [<c014cb15>] [<c012d79a>] [<c012dda8>] [<c014cb82>] [<c014d7cb>] [<c010a038>]
Warning (Oops_read): Code line not seen, dumping what data is available
>>EIP; c013365d <get_empty_inode+15/98> <=====
Trace; c014c43d <get_fd+91/9c>
Trace; c014cb15 <sock_create+85/d8>
Trace; c012d79a <permission+1a/2c>
Trace; c012dda8 <open_namei+1dc/34c>
Trace; c014cb82 <sys_socket+1a/7c>
Trace; c014d7cb <sys_socketcall+5f/1a8>
Trace; c010a038 <system_call+34/38>
next reply other threads:[~2000-12-01 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 1:59 root [this message]
2000-12-01 12:46 ` Alan Cox
2000-12-01 18:17 ` Jeff V. Merkey
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=20001130185926.A884@trgras.timpanogas.org \
--to=root@trgras.timpanogas.org \
--cc=jmerkey@timpanogas.org \
--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
all inboxes | Powered by JetHome®