https://bugzilla.kernel.org/show_bug.cgi?id=85101
Robert Elliott changed:
What|Removed |Added
CC||elli...@hp.com
--- Comment #1 from Rober
https://bugzilla.kernel.org/show_bug.cgi?id=85101
--- Comment #2 from linux-...@crashplan.pro ---
In this case the hardware seems broken.
The P410 controller is only used for upgrading the HP SAS expander firmware.
This time we started with upgrading the controller firmware:
===
./ccissflash
https://bugzilla.kernel.org/show_bug.cgi?id=85101
--- Comment #3 from Robert Elliott ---
Controller lockup means the firmware crashed (e.g. an ASSERT statement
triggered). That can be due to hardware problems or firmware bugs. You might
see if it boots with nothing attached; then with one expan
https://bugzilla.kernel.org/show_bug.cgi?id=85101
--- Comment #4 from linux-...@crashplan.pro ---
@Robert Elliott
Thanks for all your help.
The issue turns out not to be the HP P410 controller.
Using another mainboard the same HP P410 controller is ok.
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=85101
linux-...@crashplan.pro changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=85101
linux-...@crashplan.pro changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|UNRE
https://bugzilla.kernel.org/show_bug.cgi?id=85151
Bug ID: 85151
Summary: pm80xx + 7805H + HP SAS port expander =
mpi_smp_completion 2604:smp IO status 0x2 and sas:
expander ... discovery failed(0xffa6)
Product: SCSI Driv
https://bugzilla.kernel.org/show_bug.cgi?id=85151
Jack Wang changed:
What|Removed |Added
CC||xjtu...@gmail.com
--- Comment #1 from Jack Wa
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #2 from linux-...@crashplan.pro ---
Sorry, I haven't got a SAS analyzer available.
As far as I know these HP SAS expander are based on PMC Sierra PM 8005 IC
a.k.a. PM8005 SXP 36x6GSec.
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #3 from linux-...@crashplan.pro ---
Regression #2: firmware upgrade for Adaptec PMC-Sierra PM8018 SAS HBA [Series
7H] [9005:8088]:
old:
Number of controllers = 1
CONTROLLER_ADDRESS | VENDOR_ID | DEVICE_ID | FIRMWARE_REVISION | BIOS_VER
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #4 from Jack Wang ---
Could you check if the expander has new firmware?
you can also check smp support through smp_utils
http://sg.danny.cz/sg/smp_utils.html
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #5 from linux-...@crashplan.pro ---
Yes, the expander has new firmware (v. 2.10 available since early September).
Although my guess is that a firmware upgrade will not be possible as long as
the SAS HBA has an address (a.k.a. initiator
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #6 from Jack Wang ---
Ah, I forgot no bsg node if expander discover failed:(
HBA SAS address is 0, does not matter.
>From my point, this bug clear SMP protocol related, you could report to PMC, I
think they will offer help.
--
You a
https://bugzilla.kernel.org/show_bug.cgi?id=85101
--- Comment #6 from linux-...@crashplan.pro ---
The HP Smart Array P410 still has its issues: sometimes the diagnostics LED
turns amber, other times it works ok.
As a fall back a Marvell controller detects the HP SAS expander card fine:
# lsscsi -
https://bugzilla.kernel.org/show_bug.cgi?id=85101
--- Comment #7 from Robert Elliott ---
You need to specify a download microcode mode. Using deferred activation, the
most modern approach:
1. sg_write_buffer --mode=dmc_offs_defer --bpw=4096 --in=xxx.bin /dev/sgXX
2. sg_write_buffer --mode=activ
https://bugzilla.kernel.org/show_bug.cgi?id=85101
--- Comment #8 from linux-...@crashplan.pro ---
Confirmation of successful firmware download/update/flash to the HP SAS
expander card using the commands:
# sg_write_buffer --mode=dmc_offs_defer --bpw=4096 --in=PUF21000.bin /dev/sg1
# sg_write_buffe
https://bugzilla.kernel.org/show_bug.cgi?id=81861
Leon Woestenberg changed:
What|Removed |Added
CC||sidebranch.li...@gmail.com
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #7 from Jack Wang ---
Cc pmchba maillist.
2014-09-25 18:20 GMT+02:00 :
> https://bugzilla.kernel.org/show_bug.cgi?id=85151
>
> --- Comment #6 from Jack Wang ---
> Ah, I forgot no bsg node if expander discover failed:(
> HBA SAS addr
https://bugzilla.kernel.org/show_bug.cgi?id=85151
Suresh Thiagarajan changed:
What|Removed |Added
CC||sures...@gmail.com
--- Comment #8 fr
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #9 from linux-...@crashplan.pro ---
Even with latest HP SAS expander firmware version 2.10 (CP022989, Sep 9th 2014,
PUF21000.bin e898facebe75c180c0a9e7d521d0285a), no drives attached, only the
7805H with one cable SFF-8643 to SFF-8088 (
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #10 from linux-...@crashplan.pro ---
After splitting module loading and connecting the expander, and enabling
verbose pm80xx logging in between:
1. disconnect cable
2. modprobe pm80xx
3. # echo 0xfff > $(find /sys -iname logging_level)
https://bugzilla.kernel.org/show_bug.cgi?id=85101
linux-...@crashplan.pro changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=85751
Bug ID: 85751
Summary: iSCSI initiator lockup during login
Product: IO/Storage
Version: 2.5
Kernel Version: 3.16.4
Hardware: All
OS: Linux
Tree: Mainline
https://bugzilla.kernel.org/show_bug.cgi?id=85751
Sagi Grimberg changed:
What|Removed |Added
CC||sa...@dev.mellanox.co.il
--- Comment #1 f
https://bugzilla.kernel.org/show_bug.cgi?id=85751
Bart Van Assche changed:
What|Removed |Added
Summary|iSCSI initiator lockup |iSCSI initiator lockup
https://bugzilla.kernel.org/show_bug.cgi?id=85751
--- Comment #2 from Bart Van Assche ---
This is not easy to reproduce and happened while testing a modification of
iSCSI target software. The following commands were issued at the initiator
side:
* iscsiadm -m discovery -p 192.168.1.124 -t st
* is
https://bugzilla.kernel.org/show_bug.cgi?id=85751
Bart Van Assche changed:
What|Removed |Added
Attachment #152781|Output generated by echo w |Output generated by echo w
descr
https://bugzilla.kernel.org/show_bug.cgi?id=85751
--- Comment #3 from Bart Van Assche ---
On 10/07/14 19:03, Mike Christie wrote:
> On 10/07/2014 11:42 AM, bugzilla-dae...@bugzilla.kernel.org wrote:
>> * iscsiadm -m discovery -p 192.168.1.124 -t st
>> * iscsiadm -m node -p 192.168.1.124 -l
>> (so
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #11 from linux-...@crashplan.pro ---
Created attachment 153151
--> https://bugzilla.kernel.org/attachment.cgi?id=153151&action=edit
pm80xx dmesg even more verbose output after patching pm80xx.ko
This is the applied patch:
===
diff --
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #12 from linux-...@crashplan.pro ---
Note the changed behavior with kernel "Linux ubuntu14 3.17.0-031700rc7-generic
#201409281835 SMP Sun Sep 28 22:36:30 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux"
&& patched pm80xx, despite the SAS discov
https://bugzilla.kernel.org/show_bug.cgi?id=85151
--- Comment #13 from linux-...@crashplan.pro ---
Note: having 2 pieces of the HP SAS expander connected at the same time, one to
each port of the Adaptec 7805H, results in a kernel oops:
35.475138] sas: DONE DISCOVERY on port 7, pid:137, result
https://bugzilla.kernel.org/show_bug.cgi?id=111341
--- Comment #5 from walter59 ---
hello,
bug is still alive on most boards --- changes has has no resolved problems.
regards
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: se
https://bugzilla.kernel.org/show_bug.cgi?id=106841
Tom Yan changed:
What|Removed |Added
Kernel Version|4.2.4 |4.4.1
--
You are receiving this mail because:
https://bugzilla.kernel.org/show_bug.cgi?id=106841
Tom Yan changed:
What|Removed |Added
Summary|do not output error for |ses: do not output error
|si
https://bugzilla.kernel.org/show_bug.cgi?id=106841
--- Comment #2 from Tom Yan ---
This commit did NOT fix anything:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/ses.c?id=3417c1b5cb1fdc10261dbed42b05cc93166a78fd
Only the error changes from:
scsi 7:0:0:1: F
https://bugzilla.kernel.org/show_bug.cgi?id=111441
--- Comment #19 from nab ---
Hey Hannes,
On Tue, 2016-02-16 at 20:08 +0100, Hannes Reinecke wrote:
> On 02/08/2016 09:01 AM, Nicholas A. Bellinger wrote:
> > On Tue, 2016-02-02 at 14:56 -0800, Nicholas A. Bellinger wrote:
> >> On Mon, 2016-02-01
https://bugzilla.kernel.org/show_bug.cgi?id=112241
--- Comment #1 from Anthony ---
Created attachment 206351
--> https://bugzilla.kernel.org/attachment.cgi?id=206351&action=edit
Screenshot with call trace for kernel 4.5.0
--
You are receiving this mail because:
You are watching the assignee o
https://bugzilla.kernel.org/show_bug.cgi?id=112241
Anthony changed:
What|Removed |Added
Kernel Version|4.3.3 |4.5.0
--- Comment #2 from Anthony ---
With ke
https://bugzilla.kernel.org/show_bug.cgi?id=112241
--- Comment #3 from nab ---
Hi Anthony,
On Mon, 2016-02-29 at 02:26 +, bugzilla-dae...@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=112241
>
> Anthony changed:
>
>What|Removed
https://bugzilla.kernel.org/show_bug.cgi?id=114401
Bug ID: 114401
Summary: crash dump aic94xx
Product: SCSI Drivers
Version: 2.5
Kernel Version: 4.4.3-gentoo #1 SMP Mon Feb 29 16:03:39 MSK 2016
x86_64
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=111341
--- Comment #6 from walter59 ---
hi,
fine bug is resolved in version 4.5_rc7.
thanks
ticket closed
regards
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "u
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #16 from Orion ---
ok thanks. the best would be to check if another guys can test it also
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-sc
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #3 from Orion ---
Seems to work now thank you very much.
do you think your patch will be included on 4.x kernels?
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the li
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #12 from Orion ---
how can I mark tested on your patch?
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to ma
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #15 from nickkra...@sympatico.ca ---
And if you do get around to it try testing on mainline. Personally I wrote the
patch on mail line so if it applies clearly to your kernel it possibly works
fine on main line but just doubt check if y
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #14 from Orion ---
Tested-by: Orion ad...@e-blokos.com
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to maj
https://bugzilla.kernel.org/show_bug.cgi?id=91711
nickkra...@sympatico.ca changed:
What|Removed |Added
CC||nickkra...@sympatico.ca
--- Comm
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #10 from nickkra...@sympatico.ca ---
That's OK :). If you can however add tested by on my patch I would really
appreciate it.
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list:
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #5 from nickkra...@sympatico.ca ---
If you are willing to test the patch against main line kernel just o make sure
it's just fine. I also rewrote the patch with a commit log now just add your
tested by below it.
--
You are receiving t
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #18 from nickkra...@sympatico.ca ---
Those patches may fix it but I am pretty sure those patches are in the 3.18.3
kernel release back port. Maybe I am work but let Orion test those patches too
to see if those should be back ported or a
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #13 from nickkra...@sympatico.ca ---
Just type the line:
Tested-by: Your Full Name email address
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe li
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #8 from nickkra...@sympatico.ca ---
Sorry do you mean the bug log or the kernel bugzilla log?
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #2 from nickkra...@sympatico.ca ---
The patch I just attached about this may fix your issue.
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #4 from nickkra...@sympatico.ca ---
Created attachment 209781
--> https://bugzilla.kernel.org/attachment.cgi?id=209781&action=edit
Test Patch
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscrib
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #6 from Orion ---
sorry I can't have access to the log anymore...
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a mes
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #19 from Orion ---
Unfortunately for now my DC blocked all ssh access and I'm afraid it's for a
long time...
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "u
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #11 from Orion ---
I just had time yesterday to check the log and see that the errors disappear.
today no ssh access at all. anyhow it's months now they are creating troubles
against me so I just give up and ask my money back next week
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #9 from Orion ---
just today my data center blocked my server where the card is
because of invoice contentious... a kind of conspiracy against my project
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://bugzilla.kernel.org/show_bug.cgi?id=91711
Adam Radford changed:
What|Removed |Added
CC||aradf...@gmail.com
--- Comment #17 from Ad
https://bugzilla.kernel.org/show_bug.cgi?id=91711
--- Comment #7 from nickkra...@sympatico.ca ---
The kernel log or the bug log.
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a mes
https://bugzilla.kernel.org/show_bug.cgi?id=115351
Bug ID: 115351
Summary: redundant pointless messages
Product: IO/Storage
Version: 2.5
Kernel Version: All
Hardware: All
OS: Linux
Tree: Mainline
S
https://bugzilla.kernel.org/show_bug.cgi?id=115351
--- Comment #1 from d gilbert ---
On 16-03-27 03:48 PM, bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=115351
>
> Bug ID: 115351
> Summary: redundant pointless messages
>
https://bugzilla.kernel.org/show_bug.cgi?id=115351
--- Comment #2 from Jonathan ---
clearly if 16 is enough for 2^64 then just get rid of the error message all
together, and call it done.
I don't know why sd_try_rc16_first() returns zero.
I don't even know how to find out.
This is all the dmesg
https://bugzilla.kernel.org/show_bug.cgi?id=115351
--- Comment #3 from Jonathan ---
scsi 4:3:0:0: Wrong diagnostic page; asked for 7 got 0
I get bunches of these
--
You are receiving this mail because:
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscri
https://bugzilla.kernel.org/show_bug.cgi?id=98171
amal...@yahoo.com changed:
What|Removed |Added
CC||amal...@yahoo.com
--- Comment #8 from
https://bugzilla.kernel.org/show_bug.cgi?id=60644
rlung...@yahoo.com changed:
What|Removed |Added
CC||rlung...@yahoo.com
--- Comment #49 fr
https://bugzilla.kernel.org/show_bug.cgi?id=111381
Gabriel A. Devenyi changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=114401
bastienphilb...@gmail.com changed:
What|Removed |Added
CC||bastienphilb...@gmail.com
---
https://bugzilla.kernel.org/show_bug.cgi?id=114401
Bulanov Maxim changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=114401
--- Comment #3 from bastienphilb...@gmail.com ---
That seems to be due to a WARN_ON that only triggers once. Does this work OK
now besides the warning.
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsub
https://bugzilla.kernel.org/show_bug.cgi?id=116751
Bug ID: 116751
Summary: Double-Fetch bug in
Linux-4.5/drivers/scsi/aacraid/commctrl.c
Product: SCSI Drivers
Version: 2.5
Kernel Version: 4.5
Hardware: All
https://bugzilla.kernel.org/show_bug.cgi?id=116771
Bug ID: 116771
Summary: NULL pointer dereference when 'cat
/sys/class/fc_host/host1/fabric_name'
Product: SCSI Drivers
Version: 2.5
Kernel Version: 4.6-rc1 to 4.6-rc4
H
https://bugzilla.kernel.org/show_bug.cgi?id=116751
--- Comment #1 from Pengfei Wang ---
Created attachment 214111
--> https://bugzilla.kernel.org/attachment.cgi?id=214111&action=edit
source file
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscrib
https://bugzilla.kernel.org/show_bug.cgi?id=118081
Bug ID: 118081
Summary: open-iscsi Ping timeout erro
Product: SCSI Drivers
Version: 2.5
Kernel Version: 4.4.7
Hardware: All
OS: Linux
Tree: Mainline
https://bugzilla.kernel.org/show_bug.cgi?id=118071
Bug ID: 118071
Summary: open-iscsi Ping timeout erro
Product: IO/Storage
Version: 2.5
Kernel Version: 4.4.7
Hardware: All
OS: Linux
Tree: Mainline
https://bugzilla.kernel.org/show_bug.cgi?id=118081
--- Comment #1 from Mike Christie ---
On 05/11/2016 10:34 PM, bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=118081
>
> Bug ID: 118081
>Summary: open-iscsi Ping timeout erro
>
https://bugzilla.kernel.org/show_bug.cgi?id=118281
Bug ID: 118281
Summary: SCSI disk driver (sd) bug (wrong max_sectors value)
Product: SCSI Drivers
Version: 2.5
Kernel Version: 4.6
Hardware: All
OS: Linux
Tre
https://bugzilla.kernel.org/show_bug.cgi?id=118081
--- Comment #2 from Liu zhengyuan ---
Thanks for your replay. Yes, I am using LIO and I had make a XFS file system
on the LUN at the Initiator side . As you said, the sync_cache command was
issued by XFS log infrastructure actually. When I repl
https://bugzilla.kernel.org/show_bug.cgi?id=118621
Bug ID: 118621
Summary: After upgrading from ubuntu 15.10 to 16.04 CD-R's
won't mount, others mount just fine
Product: IO/Storage
Version: 2.5
Kernel Version: 4.4.0-22-generic
https://bugzilla.kernel.org/show_bug.cgi?id=118081
--- Comment #3 from nab ---
Hey Mike & Co,
Apologies for missing this bug-report. Comments below.
(Adding target-devel CC')
On Fri, 2016-05-13 at 11:19 -0500, Mike Christie wrote:
> On 05/11/2016 10:34 PM, bugzilla-dae...@bugzilla.kernel.org
https://bugzilla.kernel.org/show_bug.cgi?id=118081
--- Comment #4 from Liu zhengyuan ---
Hi, nab:
Did you mean doing iozone test on a local disk LUN not a iscsi LUN from the
word "are you seeing something different wrt iozone on a Linux host..?"? If
so, I didn`t found any different between this
https://bugzilla.kernel.org/show_bug.cgi?id=118621
albapom...@gmail.com changed:
What|Removed |Added
CC||albapom...@gmail.com
--- Comment #
https://bugzilla.kernel.org/show_bug.cgi?id=118621
--- Comment #2 from albapom...@gmail.com ---
After looking for more information, I found this comment on a forum.
Hi,
this must be a new bug with Linux kernel or udev.
A significant difference between CD TAO and CD SAO at read
https://bugzilla.kernel.org/show_bug.cgi?id=59301
Summary: mpt2sas0 fails after short time of work
Product: SCSI Drivers
Version: 2.5
Kernel Version: 3.5.0-32-generic ubuntu
Platform: All
OS/Version: Linux
Tree: Mainline
https://bugzilla.kernel.org/show_bug.cgi?id=59301
Anton Pomozov changed:
What|Removed |Added
Platform|All |x86-64
Severity|blocking
https://bugzilla.kernel.org/show_bug.cgi?id=59301
Anton Pomozov changed:
What|Removed |Added
Kernel Version|3.5.0-32-generic ubuntu |3.5.0
--- Comment #1 from Anton Pomoz
https://bugzilla.kernel.org/show_bug.cgi?id=59601
Summary: commit 97dec564fd4948e0e560869c80b76e166ca2a83e breaks
communication with XYRATEX disk shelves
Product: SCSI Drivers
Version: 2.5
Platform: All
OS/Version: Linux
https://bugzilla.kernel.org/show_bug.cgi?id=59601
--- Comment #1 from Saurav Kashyap 2013-06-11
18:23:45 ---
HI Jack,
Please provide the driver logs for both good and bad case with
ql2xextended_error_logging=1. The commit you have mentioned don't effect 2G
cards.
Have you tried reverting t
https://bugzilla.kernel.org/show_bug.cgi?id=59601
--- Comment #3 from Jack Hill 2013-06-17 14:05:31 ---
Created an attachment (id=104981)
--> (https://bugzilla.kernel.org/attachment.cgi?id=104981)
dmest output for bad kernel with extended error reporting
--
Configure bugmail: https://bugz
https://bugzilla.kernel.org/show_bug.cgi?id=59601
--- Comment #2 from Jack Hill 2013-06-17 14:04:52 ---
Created an attachment (id=104971)
--> (https://bugzilla.kernel.org/attachment.cgi?id=104971)
dmesg output for good kernel with extended error reporting
--
Configure bugmail: https://bug
https://bugzilla.kernel.org/show_bug.cgi?id=59601
--- Comment #4 from Jack Hill 2013-06-17 14:14:03 ---
Hi,
I have attached dmesg output from good ad bad kernels with extended error
logging.
Reverting the commit solved the problem. I was not able to revert the commit on
3.10-rc4 because it
https://bugzilla.kernel.org/show_bug.cgi?id=59601
--- Comment #5 from Saurav Kashyap 2013-06-19
18:29:46 ---
Hi Jack,
I am seeing "FCP I/O protocol failure (0x8/0x2)" messages in the failed logs.
We need more data on what is coming back to the driver. I am attaching a patch
that will dump t
https://bugzilla.kernel.org/show_bug.cgi?id=59601
--- Comment #6 from Saurav Kashyap 2013-06-19
18:31:38 ---
Created an attachment (id=105401)
--> (https://bugzilla.kernel.org/attachment.cgi?id=105401)
Patch for dumping the incoming packet to the driver.
Apply this patch, enable ql2xexten
https://bugzilla.kernel.org/show_bug.cgi?id=60191
Summary: Bad flush cache
Product: IO/Storage
Version: 2.5
Kernel Version: 3.8.13
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
https://bugzilla.kernel.org/show_bug.cgi?id=59601
--- Comment #7 from Jack Hill 2013-07-02 22:13:28 ---
Created an attachment (id=106661)
--> (https://bugzilla.kernel.org/attachment.cgi?id=106661)
dmesg output with packet dumps
I have attached the dmesg output after applying the patch you
https://bugzilla.kernel.org/show_bug.cgi?id=59601
--- Comment #8 from Jack Hill 2013-07-02 22:15:42 ---
Also, I think the commit that I claimed introduced the problem after my bisect
run was the wrong one, it appears to be the last good commit. I think the one
that introduces the bug is ff2f
https://bugzilla.kernel.org/show_bug.cgi?id=59301
Marian Marinov changed:
What|Removed |Added
CC||m...@yuhu.biz
--- Comment #2 from Ma
https://bugzilla.kernel.org/show_bug.cgi?id=59301
--- Comment #3 from Marian Marinov 2013-07-03 00:36:39 ---
[root@BlackPearl ~]# uname -a
Linux BlackPearl.yuhu.biz 2.6.32-358.11.1.el6.i686 #1 SMP Wed Jun 12 01:01:27
UTC 2013 i686 i686 i386 GNU/Linux
[root@BlackPearl ~]# cat /etc/redhat-rele
https://bugzilla.kernel.org/show_bug.cgi?id=59601
--- Comment #9 from Saurav Kashyap ---
Created attachment 106870
--> https://bugzilla.kernel.org/attachment.cgi?id=106870&action=edit
Properly-set-the-tagging-for-commands
Hi Jack,
Try this patch and see if this resolves this issue.
thanks,
~S
https://bugzilla.kernel.org/show_bug.cgi?id=59601
Jack Hill changed:
What|Removed |Added
Kernel Version||>2.6.38-rc2
--- Comment #10 from Jack Hill -
201 - 300 of 1266 matches
Mail list logo
