From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 15001] megaraid_sas fills dmesg with megasas: Failed to copy out to user sense data
Date: Fri, 5 Feb 2010 07:34:58 GMT [thread overview]
Message-ID: <201002050734.o157YwZh031806@demeter.kernel.org> (raw)
In-Reply-To: <bug-15001-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15001
--- Comment #10 from Alex <mailatgoogl@gmail.com> 2010-02-05 07:34:50 ---
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > (In reply to comment #6)
> > > > thank you for the patch , it handles the issue , tested on 2.6.32.7 .
> > >
> > > That means that you no more see the
> > > "megasas: Failed to copy out to user sense data"
> > Yes , that means that I don't see this message any more ,
> > and what does it mean "Failed to copy out to user sense data" ?
> That means that the function copy_to_user in the driver failed and the ioctl
> returned EFAULT. Usually programs can cope with that, but it could mean that
> they are not able to collect informations from that device.
>
> > > or have you also verified that the management software works as expected?
> > And I still can retrieve information with MegaCli utility , should I check
> > something special ?
> I'm not sure with MegaCli, what I meant here is the Dell management sw 'Open
> Manage', so if you can check if this sw can collect info from megaraid driver.
I guess it is ok ,
OMSA is 6.0.1-8 . For example
omreport storage vdisk
omreport storage pdisk controller=0
works as expected .
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-02-05 7:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 12:42 [Bug 15001] New: megaraid_sas fills dmesg with megasas: Failed to copy out to user sense data bugzilla-daemon
2010-01-08 16:21 ` [Bug 15001] " bugzilla-daemon
2010-01-11 11:04 ` bugzilla-daemon
2010-01-11 11:12 ` bugzilla-daemon
2010-01-15 12:09 ` bugzilla-daemon
2010-02-03 13:41 ` bugzilla-daemon
2010-02-04 11:00 ` bugzilla-daemon
2010-02-04 13:22 ` bugzilla-daemon
2010-02-04 14:29 ` bugzilla-daemon
2010-02-04 15:36 ` bugzilla-daemon
2010-02-05 7:34 ` bugzilla-daemon [this message]
2010-02-05 14:16 ` bugzilla-daemon
2010-02-05 14:51 ` bugzilla-daemon
2010-02-11 13:31 ` bugzilla-daemon
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=201002050734.o157YwZh031806@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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