public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: Jens Axboe <axboe@suse.de>, Andre Hedrick <andre@linux-ide.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 34-mm2 ide problems - unexpected interrupt
Date: Fri, 13 Sep 2002 21:42:23 -0400	[thread overview]
Message-ID: <200209132142.23964.tomlins@cam.org> (raw)
In-Reply-To: <20020913060647.GH1847@suse.de>

Hi,

To check if the problem I am seeing is with the port to 2.5 I tried
2.4.20-pre5-ac4 and 2.4.20-pre5-ac6.  Both booted correctly.

Now to try 2.5.34+bk without Andrew's mm patch.  If that fails what 
debugging info would help solve the unexpected interrupt problem?

TIA,

Ed Tomlinson

  parent reply	other threads:[~2002-09-14  1:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12 12:38 34-mm2 ide problems - unexpected interrupt Ed Tomlinson
2002-09-12 12:42 ` Jens Axboe
2002-09-12 22:30   ` Ed Tomlinson
2002-09-13  6:06     ` Jens Axboe
2002-09-13 11:36       ` Ed Tomlinson
2002-09-14  1:42       ` Ed Tomlinson [this message]
2002-09-14  2:58         ` 34-bk current " Ed Tomlinson
2002-09-14 13:36           ` Jens Axboe
2002-09-14 19:39             ` 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=200209132142.23964.tomlins@cam.org \
    --to=tomlins@cam.org \
    --cc=andre@linux-ide.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.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