public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: alan@lxorguk.ukuu.org.uk, marcelo@conectiva.com.br
Subject: Re: OOPS in 2.4.21-pre5, ide-scsi
Date: Fri, 28 Feb 2003 16:28:41 +0100	[thread overview]
Message-ID: <20030228162841.17ac0092.skraw@ithnet.com> (raw)
In-Reply-To: <20030227221017.4291c1f6.skraw@ithnet.com>

On Thu, 27 Feb 2003 22:10:17 +0100
Stephan von Krawczynski <skraw@ithnet.com> wrote:

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

Additional comment:

This oops is reproducable at my system. I tried today again, and again it
happened on the same EIP. If I got that right it is this code:


                if (status.b.check)
                        rq->errors++;
                idescsi_end_request(drive, 1);
                return ide_stopped;
        }

Obviously rq is somehow damaged. I tried to retrieve further info by adding:

/* $$$ */
                local_irq_enable();
                printk("scsi: %08lx, pc: %08lx, rq: %08lx\n",scsi,pc,rq);
                if (status.b.check)
                        rq->errors++;
                idescsi_end_request(drive, 1);
                return ide_stopped;
        }

Interestingly there are about 10 lines in syslog with this output, then it
stops for around 10-20 seconds, and _then_ it oops'es. I got the feeling that
this "late" rq is indeed long gone, when the code is entered.
I tried to patch a bit around this problem, but no success at this time...

-- 
Regards,
Stephan

  reply	other threads:[~2003-02-28 15:19 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 [this message]
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
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=20030228162841.17ac0092.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox