All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: OOPS in 2.4.21-pre5, ide-scsi
Date: Thu, 27 Feb 2003 22:10:17 +0100	[thread overview]
Message-ID: <20030227221017.4291c1f6.skraw@ithnet.com> (raw)

Hello all,

I just installed pre5 and did my current favourite test: mounting a cdrom with ide-scsi. Maybe you remember my problem: I enter the mount, cdrom spins up, around 20-30 seconds, then freeze.

But this time it oops'ed, and here it is:
(I had to write it down by hand, and "filled" it in another oops "form", so just forget the date/time. All the values should be correct, I checked twice.)

# ksymoops < oops 
ksymoops 2.4.5 on i686 2.4.21-pre5.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.21-pre5/ (default)
     -m /boot/System.map-2.4.21-pre5 (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Nov  5 19:48:49 linux kernel: Oops: 0002
Nov  5 19:48:49 linux kernel: CPU:    0
Nov  5 19:48:49 linux kernel: EIP:    0010:[<c0213ab3>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Nov  5 19:48:49 linux kernel: EFLAGS: 00010202
Nov  5 19:48:49 linux kernel: eax: 00000000   ebx: 00000001   ecx: c1613d84   edx: 3e076fe3
Nov  5 19:48:49 linux kernel: esi: d93ca000   edi: c0363d80   ebp: c165cd80   esp: d98d3f2c
Nov  5 19:48:49 linux kernel: ds: 0018   es: 0018   ss: 0018
Nov  5 19:48:49 linux kernel: Process setiathome (pid: 1371, stackpage=d98d3000)
Nov  5 19:48:49 linux kernel: Stack: 00000177 51eb851f d98d2000 00100000 c01299e5 bffffa60 d98d3f50 3e076fe3
Nov  5 19:48:49 linux kernel:        c1613d60 c0363d80 00000286 c0363cd0 c01dcbd6 c0363d80 00000000 c0213a50
Nov  5 19:48:49 linux kernel:        c1634c80 04000001 00000000 d98d3fc4 c0109129 0000000f c1613d60 d98d3fc4
Nov  5 19:48:49 linux kernel: Call Trace:    [<c01299e5>] [<c01dcbd6>] [<c0213a50>] [<c0109129>] [<c0109348>] [<c010bec8>]
Nov  5 19:48:49 linux kernel: Code: ff 42 18 89 3c 24 c7 44 24 04 01 00 00 00 e8 ae fc ff ff 31


>>EIP; c0213ab3 <idescsi_pc_intr+63/360>   <=====

>>ecx; c1613d84 <_end+12a072c/20557a08>
>>edx; 3e076fe3 Before first symbol
>>esi; d93ca000 <_end+190569a8/20557a08>
>>edi; c0363d80 <ide_hwifs+520/2c60>
>>ebp; c165cd80 <_end+12e9728/20557a08>
>>esp; d98d3f2c <_end+195608d4/20557a08>

Trace; c01299e5 <getrusage+d5/230>
Trace; c01dcbd6 <ide_intr+e6/180>
Trace; c0213a50 <idescsi_pc_intr+0/360>
Trace; c0109129 <handle_IRQ_event+69/a0>
Trace; c0109348 <do_IRQ+98/f0>
Trace; c010bec8 <call_do_IRQ+5/d>

Code;  c0213ab3 <idescsi_pc_intr+63/360>
00000000 <_EIP>:
Code;  c0213ab3 <idescsi_pc_intr+63/360>   <=====
   0:   ff 42 18                  incl   0x18(%edx)   <=====
Code;  c0213ab6 <idescsi_pc_intr+66/360>
   3:   89 3c 24                  mov    %edi,(%esp,1)
Code;  c0213ab9 <idescsi_pc_intr+69/360>
   6:   c7 44 24 04 01 00 00      movl   $0x1,0x4(%esp,1)
Code;  c0213ac0 <idescsi_pc_intr+70/360>
   d:   00 
Code;  c0213ac1 <idescsi_pc_intr+71/360>
   e:   e8 ae fc ff ff            call   fffffcc1 <_EIP+0xfffffcc1> c0213774 <idescsi_do_end_request+a4/e0>
Code;  c0213ac6 <idescsi_pc_intr+76/360>
  13:   31 00                     xor    %eax,(%eax)

Nov  5 19:48:49 linux kernel:  <0>Kernel panic: Aiee, killing interrupt handler!

1 warning issued.  Results may not be reliable.


Hope this helps

Regards,
Stephan

             reply	other threads:[~2003-02-27 21:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 21:10 Stephan von Krawczynski [this message]
2003-02-28 15:28 ` OOPS in 2.4.21-pre5, ide-scsi Stephan von Krawczynski
2003-03-11 17:24   ` Stephan von Krawczynski
2003-03-13  9:47 ` Herbert Xu
2002-12-31 11:14   ` Willy Gardiol
2002-12-31 11:14     ` Willy Gardiol
2003-03-13 15:23   ` Stephan von Krawczynski
2003-03-13 15:50 ` James Stevenson
2003-03-13 16:37   ` Jens Axboe
2003-03-13 16:39     ` Willy Gardiol
2003-03-13 16:47       ` Jens Axboe
2003-03-13 18:50       ` Andre Hedrick
2003-03-13 20:28         ` Alan Cox
2003-03-13 16:50     ` James Stevenson
2003-03-13 16:46       ` Jens Axboe
2003-03-13 17:11         ` James Stevenson
2003-03-13 17:14           ` Jens Axboe
2003-03-13 17:31             ` Stephan von Krawczynski
2003-03-13 17:37               ` Jens Axboe
2003-03-13 17:41                 ` Stephan von Krawczynski
2003-03-13 17:52                   ` Jens Axboe
2003-03-13 18:28             ` Alan Cox

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=20030227221017.4291c1f6.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.