All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Nick Orlov <bugfixer@list.ru>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Fw: 2.6.12-mm2: 3ware SATA RAID inaccessible
Date: Mon, 27 Jun 2005 09:22:22 -0500	[thread overview]
Message-ID: <1119882142.5175.11.camel@mulgrave> (raw)
In-Reply-To: <20050627044647.GA4104@nikolas.hn.org>

On Mon, 2005-06-27 at 00:46 -0400, Nick Orlov wrote:
> c0267437 tw_interrupt+0x317/0x480
> c013ac9d handle_IRQ_event+0x3d/0x70
> c013adb0 __do_IRQ+0xe0/0x170
> c0104fc3 do_IRQ+0x23/0x40
> c01031ce common_interrupt+0x1a/0x20
> c0100ca6 default_idle+0x26/0x30
> c0110bbc apm_cpu_idle+0xce/0x160
> c0100d24 cpu_idle+0x34/0x50
> c03947e5 start_kernel+0x165/0x180
> c0394360 unknown_bootoption+0x0/0x1e0

tw_interrupt wasn't actually modified.  However, it should have executed
another call, probably where it's doing a null ptr deref, probably in
one of the completion routines, which should be identified by the EIP;
could you tell me what this is?

Thanks,

James



  reply	other threads:[~2005-06-27 14:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-26 22:39 Fw: 2.6.12-mm2: 3ware SATA RAID inaccessible Andrew Morton
2005-06-26 23:37 ` James Bottomley
2005-06-27  4:46   ` Nick Orlov
2005-06-27 14:22     ` James Bottomley [this message]
2005-06-28  2:08       ` Nick Orlov
2005-06-28  4:05         ` James Bottomley
2005-06-28 11:02           ` Nick Orlov
2005-06-28 12:09             ` Jens Axboe
2005-06-28 14:18               ` James Bottomley
2005-06-28 14:23                 ` Jens Axboe
2005-06-29  1:58                   ` Nick Orlov
2005-06-27  7:52   ` Jens Axboe
2005-06-27 14:22     ` James Bottomley
2005-06-27 14:27       ` Jens Axboe
2005-06-28  8:25   ` Jens Axboe

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=1119882142.5175.11.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=bugfixer@list.ru \
    --cc=linux-scsi@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 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.