public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/2  scsi-rc-fixes-2.6] FC Remote Port patch
Date: Wed, 9 Feb 2005 10:32:46 -0800	[thread overview]
Message-ID: <20050209183246.GE7116@plap.qlogic.org> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C12EB47@xbl3.ma.emulex.com>

On Tue, 08 Feb 2005, James.Smart@Emulex.Com wrote:

>   This patch also moves the dev_loss attribute from the target-level
>   fc_transport device to the remote port device. It also deletes the
>   link_down attribute. The fc_target_block and fc_target_unblock 
>   routines have been replaced by fc_remote_port_block and
>   fc_remote_port_unblock. The fc_host_block/unblock functions have
>   been removed (unused).
> 

still trying to track down the following oops:

	Unable to handle kernel paging request at virtual address 6b6b6be7
	 printing eip:
	c028ef0f
	*pde = 00000000
	Oops: 0000 [#1]
	SMP
	Modules linked in: qla2322 qla2xxx
	CPU:    0
	EIP:    0060:[<c028ef0f>]    Not tainted VLI
	EFLAGS: 00010082   (2.6.11-rport)
	EIP is at scsi_device_get+0x2f/0x70
	eax: 6b6b6b6b   ebx: c156aac4   ecx: d9bd1b90   edx: fffffffa
	esi: c156ac58   edi: c156aac4   ebp: d9bd1b74   esp: dcc3fe08
	ds: 007b   es: 007b   ss: 0068
	Process qla2322_3_dpc (pid: 12662, threadinfo=dcc3e000 task=dfebca40)
	Stack: d9bd1b7c d5318000 c028efda 00000286 d9bd1b74 d7487ccc d5318000
	c029af10
	       c028f07d 00000000 db507c74 d7487ccc 00000023 db507d70 c029afbf
	d68d07fc
	       00000000 d53181fc d5319338 e08633d3 c01020b5 c04221ec 00000282
	0000002c
	Call Trace:
	 [<c028efda>] __scsi_iterate_devices+0x3a/0x70
	 [<c029af10>] fc_device_block+0x0/0x10
	 [<c028f07d>] starget_for_each_device+0x6d/0x80
	 [<c029afbf>] fc_remote_port_block+0x3f/0x70
	 [<e08633d3>] qla2x00_mark_device_lost+0x53/0xe0 [qla2xxx]
	 [<c01020b5>] __down_trylock+0x65/0x80
	 [<c03097ab>] __down_failed_trylock+0x7/0xc
	 [<c011be61>] vprintk+0x141/0x160
	 [<e0867508>] qla2x00_device_resync+0x238/0x2d0 [qla2xxx]
	 [<e08682d0>] qla2x00_mbx_sem_timeout+0x0/0x10 [qla2xxx]
	 [<e08668bc>] qla2x00_configure_fabric+0x7c/0x3e0 [qla2xxx]
	 [<c01f3d54>] vsnprintf+0x394/0x510
	 [<c01176fd>] __wake_up_locked+0x1d/0x20
	 [<c01020b5>] __down_trylock+0x65/0x80
	 [<c03097ab>] __down_failed_trylock+0x7/0xc
	 [<c011be61>] vprintk+0x141/0x160
	 [<e086629a>] qla2x00_configure_loop+0x1aa/0x200 [qla2xxx]
	 [<e086793c>] qla2x00_loop_resync+0x8c/0xd0 [qla2xxx]
	 [<e0864115>] qla2x00_do_dpc+0x3a5/0x470 [qla2xxx]
	 [<c010310a>] work_resched+0x5/0x16
	 [<e0863d70>] qla2x00_do_dpc+0x0/0x470 [qla2xxx]
	 [<c0101345>] kernel_thread_helper+0x5/0x10
	Code: ff ff 53 89 c3 8b 80 a8 02 00 00 83 e8 03 83 f8 01 76 3e 8d b3
	94 01 00 00 89 f0 e8 6c cc fb ff 85 c0 ba fa ff ff ff 74 28 8b 03 <8b>
	40 7c 8b 10 85 d2 74 1b b8 00 e0 ff ff 21 e0 83 3a 02 8b 40

seems like sdev->shost is bogus when fc_remote_port_block() is
called...

On a side note:

	+/*
	+ * fc_rport_terminate - this routine tears down and deallocates a remote port.
	+ * @rport:     The remote port to be terminated
	+ *
	+ * Notes:
	+ *     This routine assumes no locks are held on entry.
	+ */
	+extern int lpfc_ext_debug;
	+static void
	+fc_rport_terminate(struct fc_rport  *rport)
	+{

lpfc_ext_debug -- residuals from some test code?

--
AV

  parent reply	other threads:[~2005-02-09 18:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09  4:18 [PATCH 2/2 scsi-rc-fixes-2.6] FC Remote Port patch James.Smart
2005-02-09  8:15 ` Mike Christie
2005-02-09 18:09 ` Christoph Hellwig
2005-02-09 18:32 ` Andrew Vasquez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-09 18:07 James.Smart
2005-02-09 19:24 James.Smart
2005-02-09 23:03 ` Andrew Vasquez
2005-02-10 18:56   ` Andrew Vasquez

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=20050209183246.GE7116@plap.qlogic.org \
    --to=andrew.vasquez@qlogic.com \
    --cc=James.Smart@Emulex.Com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox