From: KFPieper@t-online.de (Klaus Pieper)
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: ISDN Router Oopses
Date: Wed, 28 Feb 2001 20:04:46 +0100 [thread overview]
Message-ID: <3A9D4BCE.5E92C965@t-online.de> (raw)
Hello,
I use an older pc as ISDN router (Debian potato, kernel 2.2.17pre stock
from the distro, isdnutils 3.0-20, ssh-nonfree 1.2.27-6.1, wwwoffle).
The thing has never worked properly. I suspected hardware problems and
swapped the ram modules, but still have oopses.
I checked the memory with memtest86, was Ok. Had a kernel compilation
loop for one hour, also ok.
How can I make shure if the hardware is Ok?
What could be wrong with the software?
Here are some recent examples of the crashes.
TIA
Klaus
------------------------
Feb 26 19:25:16 groucho kernel: Oops: 0000
Feb 26 19:25:16 groucho kernel: CPU: 0
Feb 26 19:25:16 groucho kernel: EIP: 0010:[kfree+110/396]
Feb 26 19:25:16 groucho kernel: EFLAGS: 00010086
Feb 26 19:25:16 groucho kernel: eax: 00000210 ebx: c1fff080 ecx:
24548a53 edx: c123cbac
Feb 26 19:25:16 groucho kernel: esi: c123cb80 edi: 00000202 ebp:
000003cc esp: c04cbe7c
Feb 26 19:25:16 groucho kernel: ds: 0018 es: 0018 ss: 0018
Feb 26 19:25:16 groucho kernel: Process find (pid: 1026, process nr: 27,
stackpage=c04cb000)
Feb 26 19:25:16 groucho kernel: Stack: c1cb0770 000003cc c08d7b80
c0131a57 c123cb80 00000000 c03231c8 00000403
Feb 26 19:25:16 groucho kernel: c04cbecc 00000001 00000403
c01329ff ffffffc9 00000403 00000000 c03231c8
Feb 26 19:25:16 groucho kernel: c02b7604 c03231c8 c08d0db0
c0848330 c04cbecc c04cbecc c0132a65 00000403
Feb 26 19:25:16 groucho kernel: Call Trace: [prune_dcache+203/280]
[try_to_free_inodes+183/248] [grow_inodes+29/416]
[get_new_inode+177/292] [get_new_inode+193/292] [iget+88/96]
[ext2_lookup+82/124]
Feb 26 19:25:16 groucho kernel: [real_lookup+79/156]
[lookup_dentry+292/476] [__namei+38/88] [sys_newlstat+13/96]
[system_call+52/56]
Feb 26 19:25:16 groucho kernel: Code: 8b 41 08 3d 2b 2f c3 a5 0f 85 c4
00 00 00 8b 41 0c 85 c0 74
-------------
Feb 27 19:13:14 groucho kernel: Oops: 0000
Feb 27 19:13:14 groucho kernel: CPU: 0
Feb 27 19:13:14 groucho kernel: EIP: 0010:[sock_poll+24/36]
Feb 27 19:13:14 groucho kernel: EFLAGS: 00010282
Feb 27 19:13:14 groucho kernel: eax: c180e5ec ebx: 00000000 ecx:
ffffffff edx: c0a89ec0
Feb 27 19:13:14 groucho kernel: esi: 00000000 edi: 00000020 ebp:
00000005 esp: c0951f34
Feb 27 19:13:14 groucho kernel: ds: 0018 es: 0018 ss: 0018
Feb 27 19:13:14 groucho kernel: Process sshd (pid: 813, process nr: 23,
stackpage=c0951000)
Feb 27 19:13:14 groucho kernel: Stack: 00000000 c012f85f c0a89ec0
00000000 00000001 00000004 c1882a78 00000000
Feb 27 19:13:14 groucho kernel: c0950000 c0950000 7fffffff
00000000 c19f9000 00000007 c012fd27 00000007
Feb 27 19:13:14 groucho kernel: c0951fa8 c0951fa4 c0950000
00000000 00000000 bffff27c c1714be4 00000000
Feb 27 19:13:14 groucho kernel: Call Trace: [do_select+283/516]
[sys_select+991/1280] [system_call+52/56]
Feb 27 19:13:14 groucho kernel: Code: 8b 41 20 ff d0 83 c4 0c c3 8d 76
00 53 8b 5c 24 08 85 db 75
reply other threads:[~2001-02-28 19:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3A9D4BCE.5E92C965@t-online.de \
--to=kfpieper@t-online.de \
--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®