mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jacek Kawa <jfk@zeus.polsl.gliwice.pl>
To: vl@kki.org, vandrove@vc.cvut.cz, ollie@sis.com.tw
Cc: linux-kernel@vger.kernel.org
Subject: OOPS, 2.4.20, preemption, ptrace, ext3 patches; (sis900?/ncpfs?)
Date: Mon, 28 Apr 2003 22:50:42 +0200	[thread overview]
Message-ID: <20030428205042.GA11571@finwe.eu.org> (raw)

Hello!

I got something like this today (more details below):

<OOPS>
ksymoops 2.4.8 on i686 2.4.20-i.  Options used
     -V (default)
     -k ./ksyms (specified)
     -l /proc/modules (default)
     -o /lib/modules/2.4.20-i/ (default)
     -m ./System.map-2.4.20-i (specified)

OOPS: 0000
CPU: 0  
EIP: 0010: [<c0114f10>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010017
eax: c2034000 ebx: 00000000 ecx: 00000001 edx: 00000001
esi: c21234ec edi: 00000001 ebp: c2035f54 esp: c2035f40
ds: 0018 es: 0018 ss: 0018
Process nwsfind (pid: 764, stackpage=c2035000)
Stack: 00000001 00000282 c2aad3e0 c3e9e9e0 fffffffd 00000046 c01c7d4f c2aad3e0
       c01c71f7 c2aad3e0 c3e9e9e0 c01c846a c3e9e9e0 00000000 c01cc9b4 c3e9e9e0
       00000001 c028db68 fffffffd 00000046 c011cfd4 c028db68 c2034000 00000002
Call Trace: [<c01c7d4f>] [<c01c71f7>] [<c01c846a>] [<c01cc9b4>] [<c011cfd4>] [<c0108706>] [[<c010adf3>] 
Code: 8b 53 fc 8b 02 85 c7 75 2f 8b 1b 39 f3 75 f1 b8 00 e0 ff ff


>>EIP; c0114f10 <__wake_up+30/90>   <=====

>>eax; c2034000 <_end+1d7e9c8/455ca28>
>>esi; c21234ec <_end+1e6deb4/455ca28>
>>ebp; c2035f54 <_end+1d8091c/455ca28>
>>esp; c2035f40 <_end+1d80908/455ca28>

Trace; c01c7d4f <sock_def_write_space+8f/a0>
Trace; c01c71f7 <sock_wfree+37/40>
Trace; c01c846a <__kfree_skb+4a/150>
Trace; c01cc9b4 <net_tx_action+34/c0>
Trace; c011cfd4 <do_softirq+d4/e0>
Trace; c0108706 <do_IRQ+f6/130>
Trace; c010adf3 <call_do_IRQ+5/12>

Code;  c0114f10 <__wake_up+30/90>
00000000 <_EIP>:
Code;  c0114f10 <__wake_up+30/90>   <=====
   0:   8b 53 fc                  mov    0xfffffffc(%ebx),%edx   <=====
Code;  c0114f13 <__wake_up+33/90>
   3:   8b 02                     mov    (%edx),%eax
Code;  c0114f15 <__wake_up+35/90>
   5:   85 c7                     test   %eax,%edi
Code;  c0114f17 <__wake_up+37/90>
   7:   75 2f                     jne    38 <_EIP+0x38>
Code;  c0114f19 <__wake_up+39/90>
   9:   8b 1b                     mov    (%ebx),%ebx
Code;  c0114f1b <__wake_up+3b/90>
   b:   39 f3                     cmp    %esi,%ebx
Code;  c0114f1d <__wake_up+3d/90>
   d:   75 f1                     jne    0 <_EIP>
Code;  c0114f1f <__wake_up+3f/90>
   f:   b8 00 e0 ff ff            mov    $0xffffe000,%eax

Aiee, killing interrupt handler. In interrupt handler: not syncing.

</OOPS>

This station has to have access to ncpfs volumes and for last few days
has also been print server. Everything worked fine until motherboard upgrade
(new CPU, network card is now onboard,...). Now kernel oopses every time I reboot,
after umounting local filesystems. 

I believe it may be ncp or sis900 (or both) related (please forgive me if 
I misunderstood this oops :)

I didn't test neither 2.4.21-rc1, nor 2.4.20 without preemption enabled, nor
other NIC, but I will try to do it as soon as possible. 


Linux:
-----
Linux indis 2.4.20-i #1 pon mar 17 21:32:14 CET 2003 i686 unknown unknown GNU/Linux
 (with ptrace, preempt-2.4.20-1, all 2.4.20 ext3 patches)

Utils:
-----
modutils: 2.4.21
gcc: version 3.2.3 20030309 (Debian prerelease
ncpfs: 2.2.3 (without NDS), as in Debian SID
mount: mount-2.11z
binutils: 2.13.90.0.18

NIC:
---
Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 82)

- More -
--------

Config:
http://zeus.polsl.gliwice.pl/~jfk/kernel/2.4.20-i/oops1/config-2.4.20-i

Dmesg:
http://zeus.polsl.gliwice.pl/~jfk/kernel/2.4.20-i/oops1/dmesg

cpuinfo:
http://zeus.polsl.gliwice.pl/~jfk/kernel/2.4.20-i/oops1/cpuinfo.txt

lspci:
http://zeus.polsl.gliwice.pl/~jfk/kernel/2.4.20-i/oops1/lspci.txt
http://zeus.polsl.gliwice.pl/~jfk/kernel/2.4.20-i/oops1/lspci_-v.txt
http://zeus.polsl.gliwice.pl/~jfk/kernel/2.4.20-i/oops1/lspci_-v_-v.txt

modules (before reboot):
http://zeus.polsl.gliwice.pl/~jfk/kernel/2.4.20-i/oops1/modules.txt

oops (one more time)
http://zeus.polsl.gliwice.pl/~jfk/kernel/2.4.20-i/oops1/oops_decoded.txt


JK

-- 
Jacek Kawa, jfk[at]zeus.polsl.gliwice.pl

             reply	other threads:[~2003-04-28 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-28 20:50 Jacek Kawa [this message]
2003-05-02 21:26 ` oops 2.4.21-rc1, sis900 [was: OOPS, 2.4.20 ...] Jacek Kawa

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=20030428205042.GA11571@finwe.eu.org \
    --to=jfk@zeus.polsl.gliwice.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ollie@sis.com.tw \
    --cc=vandrove@vc.cvut.cz \
    --cc=vl@kki.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®