https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
Kubilay Kocak changed:
What|Removed |Added
Keywords|patch-ready |
--- Comment #42 from Kubilay Koca
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
Scott Aitken changed:
What|Removed |Added
CC||freebsd-bugzilla@thismonkey
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #40 from Eitan Adle
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
Jan Beich changed:
What|Removed |Added
Attachment #166854|text/x-log |text/plain
mime type|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #39 from Graham Allan ---
Created attachment 166854
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=166854&action=edit
kern.log with dev.mps.0.debug_level=4, drive removed and reinserted but no
detect
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
Graham Allan changed:
What|Removed |Added
CC||g...@umn.edu
--- Comment #38 from G
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #37 from kungfujesu...@gmail.com ---
OK disregard my previous comment. For one my issue probably isn't even the
same, my drives aren't disappearing. For two, the issue I had, which emitted
similar / the same write command timeo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
kungfujesu...@gmail.com changed:
What|Removed |Added
CC||kungfujesu...@gmail.com
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #35 from karli.sjob...@slu.se ---
Created attachment 162037
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162037&action=edit
kernel-critical log
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #34 from karli.sjob...@slu.se ---
I did it! I don´t think I can provide you with much better data than this!
Today we installed a new SC837E26-RJBOD1 around 13:20 in the log and inserted
and pulled the external SAS cable a coupl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #33 from karli.sjob...@slu.se ---
> --- Comment #32 from Stephen McConnell ---
> OK. I might be able to set something up and run some I/O to see what happens.
> In the meantime, can you run a test where you set the debug_level
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #32 from Stephen McConnell ---
OK. I might be able to set something up and run some I/O to see what happens.
In the meantime, can you run a test where you set the debug_level to 0x1F and
then send me the complete log? I don't
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #31 from karli.sjob...@slu.se ---
(In reply to Stephen McConnell from comment #30)
OK, yeah we´re on the same page. The drive doesn´t show up but therein ends the
similarities.
OK, driver timeout is more appropriate but lies at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #30 from Stephen McConnell ---
> --- Comment #29 from karli.sjob...@slu.se --- Look, if you rather want me to
> open up a new bug report, I can do that, but the end result is the same as in
> this report; a disk gets kicked for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #29 from karli.sjob...@slu.se ---
Look, if you rather want me to open up a new bug report, I can do that, but the
end result is the same as in this report; a disk gets kicked for whatever
reason, you reinsert a new drive, but it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #28 from Stephen McConnell ---
Hi Karli, I don't see anything in the logs that makes me think this is the same
issue as the original issue. Can you explain why you think so? The original
problem was a spinup delay that the dri
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #27 from karli.sjob...@slu.se ---
Set "sysctl dev.mps.0.debug_level=0x1F".
Reinserted SATA drive, captured in file "reinsert_sata.out". No disk was
recognized.
Then reinserted SAS drive, captured in file "reinsert_sas.out". It
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #26 from karli.sjob...@slu.se ---
Created attachment 161820
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161820&action=edit
debug logs 0x1F
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #25 from Stephen McConnell ---
The last few entries in the bug log looks like a different issue to me than the
SATA spinup issue. But, in response to that latest problem:
The log entries show that the AttachedDevHandle for Phy
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #24 from karli.sjob...@slu.se ---
Attaching an event of trying to reseat a drive in a currently "blocked" port.
Set "sysctl dev.mps.0.debug_level=4", called "mps_debug.log"
/K
--
You are receiving this mail because:
You are th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #23 from karli.sjob...@slu.se ---
Created attachment 161521
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161521&action=edit
mps_debug.log
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #22 from karli.sjob...@slu.se ---
No it can´t, it´s not really fixed.
We have upgraded several of our systems to have this driver and also flashed
the firmware of our HBA's to P19. Tried to flash with firmware 20.00.04.00 to
mat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #21 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #20 from commit-h...@freebsd.org ---
A commit references this bug:
Author: slm
Date: Thu Jun 4 16:27:24 UTC 2015
New revision: 283990
URL: https://svnweb.freebsd.org/changeset/base/283990
Log:
MFC: r283661
- Updated all fi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #19 from commit-h...@freebsd.org ---
A commit references this bug:
Author: slm
Date: Thu May 28 18:24:28 UTC 2015
New revision: 283661
URL: https://svnweb.freebsd.org/changeset/base/283661
Log:
The wrong commit message was gi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #18 from Stephen McConnell ---
Done for stable/10. Sorry it took so long.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #17 from karli.sjob...@slu.se ---
Hi!
Any chance to see this MFC'd soon?
From the svnweb link it says to MFC after two weeks and it´s been six weeks
(2015-04-08) already so...
Best Regards
Karli Sjöberg
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #16 from commit-h...@freebsd.org ---
A commit references this bug:
Author: slm
Date: Tue Feb 24 22:07:48 UTC 2015
New revision: 279253
URL: https://svnweb.freebsd.org/changeset/base/279253
Log:
- Updated all files with 2015 A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #15 from Stephen McConnell ---
I have sent the changes to my mentors for review and hope to get this committed
next week.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #14 from karli.sjob...@slu.se ---
Chipping in a 'me too' here:
mpssas_get_sata_identify: error reading SATA PASSTHRU; iocstatus = 0x47
mpssas_get_sata_identify: error reading SATA PASSTHRU; iocstatus = 0x804b
mpssas_get_sata_ide
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #13 from Stephen McConnell ---
Royce, I got a question from you about this bug in my email, but I don't see it
in this report for some reason. The question was:
"Will this patch be applied for 10.2-RELEASE? I do not yet see i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
Royce Williams changed:
What|Removed |Added
CC||ro...@tycho.org
--- Comment #12 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #11 from Michał Margula ---
Hello,
I really appreciate and thank you for your effort. Today I applied patch to
10.0-RELEASE-p9. It still works flawlessly - I can remove disk and reinsert
them freely, but few things:
- to apply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
Stephen McConnell changed:
What|Removed |Added
Status|Needs Triage|Patch Ready
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #10 from Stephen McConnell ---
Created attachment 148149
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=148149&action=edit
Spinup wait sysctl change
Michal, sorry about the delay in getting back to you on this. I ha
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #9 from Michał Margula ---
I can confirm that this patch fixes issue. Will it be incorporated into driver
in some way?
Thank you once more!
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #8 from Michał Margula ---
Hello,
First of all - thank you for your help and time spent on that issue. Also I am
sorry that it took so long for me to respond, but I had upgrade that box to
FreeBSD 10.0 (it was 9.2 because of th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #7 from Stephen McConnell ---
Can you apply the attached msleep patch (in a tar file)? This will cause the
driver to sleep for 3 seconds if there is an IOC Status in the
get_sata_identify function. You will probably need to re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #6 from Stephen McConnell ---
Created attachment 145541
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=145541&action=edit
msleep patch to mps_sas_lsi.c (FreeBSD 10.0)
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #5 from Michał Margula ---
Hello,
Thank you for your reply and time. It is possible that chassis causes trouble
because it has 36 disk bays (it came completly assembled from Supermicro).
I would love to try with extended timeo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
Stephen McConnell changed:
What|Removed |Added
CC||s...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #3 from Michał Margula ---
Unfortunately same issue is in FreeBSD 9.3-RELEASE:
# uname -a
FreeBSD 9.3-RELEASE FreeBSD 9.3-RELEASE #0 r260512: Thu Jul 10 23:44:39 UTC
2004 r...@snap.freebsd.org:/usr/obj/usr/srcv/sys/GENERI
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #2 from Michał Margula ---
Created attachment 144142
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144142&action=edit
Debug log after reinsterting same drive in same bay
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
--- Comment #1 from Michał Margula ---
Created attachment 144141
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144141&action=edit
Debug log after removing drive
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348
Mark Linimon changed:
What|Removed |Added
Summary|LSI2308 and WD3000FYYZ |[mps] LSI2308 with
45 matches
Mail list logo
