From: Jens Axboe <axboe@suse.de>
To: James Stevenson <james@stev.org>
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 17:46:17 +0100 [thread overview]
Message-ID: <20030313164617.GI836@suse.de> (raw)
In-Reply-To: <016c01c2e980$b2d4ee60$0cfea8c0@ezdsp.com>
On Thu, Mar 13 2003, James Stevenson wrote:
> > > 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)
weee ok not my choice for compilers, but probably alright. do me a favor
then:
# cd /to/kernel/source
# rm drivers/scsi/ide-scsi.o
# EXTRA_CFLAGS=-g make drivers/scsi/ide-scsi.o
# objdump -S drivers/scsi/ide-scsi.o > /tmp/some_file
and then mail me some_file (privately), thanks.
--
Jens Axboe
next prev parent reply other threads:[~2003-03-13 16:35 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
2003-03-13 16:46 ` Jens Axboe [this message]
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=20030313164617.GI836@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=james@stev.org \
--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