public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "James Stevenson" <james@stev.org>
To: "Jens Axboe" <axboe@suse.de>
Cc: "Stephan von Krawczynski" <skraw@ithnet.com>,
	"linux-kernel" <linux-kernel@vger.kernel.org>,
	"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	"Marcelo Tosatti" <marcelo@conectiva.com.br>
Subject: Re: OOPS in 2.4.21-pre5, ide-scsi
Date: Thu, 13 Mar 2003 16:50:46 -0000	[thread overview]
Message-ID: <016c01c2e980$b2d4ee60$0cfea8c0@ezdsp.com> (raw)
In-Reply-To: 20030313163707.GH836@suse.de

> > strange looks alot like the ones i have seen though the whole 2.4.x
tree.
> >
> > this was discussed before somebody said they would send a patch myself
> > and sombody else were going to test it but the patch never happens.
> > >From what i can work out an error occurs on the cd drive and the
request
> > queue is then empty and the ide-scsi driver then attempts to access the
> > reuest queue that doesnt exist i never did manage to find out
> > where the request get removed from the queue though.
>
> Your explanation doesn't quite make sense, but I can take a look at the
> problem :-)
>
> What kernel is the below oops from? What compiler?

i can trigger this on any 2.4.x series kernel.
-> Insert dmaged / lightly scratched cd into drive
   dd /dev/scd0 bs=8192k of=file
   wait for opps.
   opps also cd tries to re read several times
   short hang then the following output

gcc versions.
Whatever shits with redhat 7.1 + 7.2 + 7.3 and the
updates between them in each of the redhat versions.
but normally
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)

or
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113)

> > *pde = 00000000
> > Oops: 0000
> > CPU:    0
> > EIP:    0010:[<c01e5783>]    Not tainted
> > Using defaults from ksymoops -t elf32-i386 -a i386
> > EFLAGS: 00010202
> > eax: 00000000   ebx: c7a71000   ecx: c0327104   edx: 00000000
> > esi: 00000001   edi: c13a4fc0   ebp: cb23df58   esp: cb23df44
> > ds: 0018   es: 0018   ss: 0018
> > Process klogd (pid: 381, stackpage=cb23d000)
> > Stack: 00000000 c0327294 c13de260 c0327294 00000202 cb23df78 c01cdd11
> > c0327294
> >        c01e5700 c0327104 c121db00 04000001 0000000f cb23df98 c010a0bd
> > 0000000f
> >        c13de260 cb23dfc4 cb23dfc4 0000000f c02f8ae0 cb23dfbc c010a24d
> > 0000000f
> > Call Trace: [<c01cdd11>] [<c01e5700>] [<c010a0bd>] [<c010a24d>]
[<c010c358>]
> > Code: 8b 72 18 46 89 72 18 8b 55 f0 8b 82 f0 00 00 00 8b 58 04 53
> >
> > >>EIP; c01e5783 <idescsi_pc_intr+83/290>   <=====
> > Trace; c01cdd11 <ide_intr+c1/120>
> > Trace; c01e5700 <idescsi_pc_intr+0/290>
> > Trace; c010a0bd <handle_IRQ_event+3d/70>
> > Trace; c010a24d <do_IRQ+7d/c0>
> > Trace; c010c358 <call_do_IRQ+5/d>
> > Code;  c01e5783 <idescsi_pc_intr+83/290>
> > 00000000 <_EIP>:
> > Code;  c01e5783 <idescsi_pc_intr+83/290>   <=====
> >    0:   8b 72 18                  mov    0x18(%edx),%esi   <=====
> > Code;  c01e5786 <idescsi_pc_intr+86/290>
> >    3:   46                        inc    %esi
> > Code;  c01e5787 <idescsi_pc_intr+87/290>
> >    4:   89 72 18                  mov    %esi,0x18(%edx)
> > Code;  c01e578a <idescsi_pc_intr+8a/290>
> >    7:   8b 55 f0                  mov    0xfffffff0(%ebp),%edx
> > Code;  c01e578d <idescsi_pc_intr+8d/290>
> >    a:   8b 82 f0 00 00 00         mov    0xf0(%edx),%eax
> > Code;  c01e5793 <idescsi_pc_intr+93/290>
> >   10:   8b 58 04                  mov    0x4(%eax),%ebx
> > Code;  c01e5796 <idescsi_pc_intr+96/290>
> >   13:   53                        push   %ebx
> >
> > <0>Kernel panic: Aiee, killing interrupt handler!
> >
> > 1 warning issued.  Results may not be reliable.
>
> --
> Jens Axboe



  parent reply	other threads:[~2003-03-13 16:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27 21:10 OOPS in 2.4.21-pre5, ide-scsi Stephan von Krawczynski
2003-02-28 15:28 ` 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
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 [this message]
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='016c01c2e980$b2d4ee60$0cfea8c0@ezdsp.com' \
    --to=james@stev.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=skraw@ithnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox