linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Ewan D.Milne" <emilne@redhat.com>,
	Tomas Henzl <thenzl@redhat.com>,
	Andrea Gelmini <andrea.gelmini@gelma.net>,
	lkp@01.org
Subject: Re: [LKP] [lkp] [ses] 3417c1b5cb: WARNING: CPU: 2 PID: 2013 at fs/xfs/xfs_file.c:772 xfs_file_dio_aio_write+0x2a2/0x320()
Date: Mon, 28 Dec 2015 18:11:42 -0800	[thread overview]
Message-ID: <1451355102.2331.11.camel@HansenPartnership.com> (raw)
In-Reply-To: <87bn9b0zjh.fsf@yhuang-dev.intel.com>

On Mon, 2015-12-28 at 16:04 +0800, Huang, Ying wrote:
> James Bottomley <James.Bottomley@HansenPartnership.com> writes:
> 
> > [cc to linux-scsi added]
> > On Mon, 2015-12-28 at 09:43 +0800, kernel test robot wrote:
> > > FYI, we noticed the below changes on
> > > 
> > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.gi
> > > t ma
> > > ster
> > > commit 3417c1b5cb1fdc10261dbed42b05cc93166a78fd ("ses: Fix
> > > problems
> > > with simple enclosures")
> > > 
> > > This may be the intended behavior, we found after your commit,
> > > the
> > > following new message appears in kernel log:
> > > 
> > > [   40.804515] scsi 8:0:12:0: Wrong diagnostic page; asked for 7
> > > got
> > > 0
> > > 
> > > To reproduce:
> > > 
> > >         git clone
> > > git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
> > >         cd lkp-tests
> > >         bin/lkp install job.yaml  # job file is attached in this
> > > email
> > >         bin/lkp run     job.yaml
> > 
> > OK, so what is the enclosure device at host 8?  And what happens
> > when
> > you use sg_ses to ask for page 7?
> 
> We run xfstests on the test machine.  You can check the dmesg
> (kmsg.xz)
> attached in the original reporting email for information about scsi
> host
> 8.

It's not a test failure, it's a problem with your hardware, which looks
to be a Promise SAS expander with enclosure services. 

can you run sg_ses <dev> on it followed by sg_ses --page=7 --hex <dev>?
 To get the sg device run sg_map -i and it should tell you what the
mappings are.

Thanks,

James
 


      parent reply	other threads:[~2015-12-29  2:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87ziwv2vrp.fsf@yhuang-dev.intel.com>
2015-12-28  5:19 ` [lkp] [ses] 3417c1b5cb: WARNING: CPU: 2 PID: 2013 at fs/xfs/xfs_file.c:772 xfs_file_dio_aio_write+0x2a2/0x320() James Bottomley
     [not found]   ` <87bn9b0zjh.fsf@yhuang-dev.intel.com>
2015-12-29  2:11     ` James Bottomley [this message]

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=1451355102.2331.11.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=andrea.gelmini@gelma.net \
    --cc=emilne@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=thenzl@redhat.com \
    --cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).