[Bug 197875] Processes hang on attempted access of WDC WD30-EZRX 3TB HDD on HP Z420 Workstation

2019-10-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=197875 Theodore Tso (ty...@mit.edu) changed: What|Removed |Added Comment #23 is|0 |1 private|

[Bug 197875] Processes hang on attempted access of WDC WD30-EZRX 3TB HDD on HP Z420 Workstation

2019-10-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=197875 Jerry Smith (jerrysmith3...@gmail.com) changed: What|Removed |Added CC||jerrysmith3...@gm

[Bug 197875] Processes hang on attempted access of WDC WD30-EZRX 3TB HDD on HP Z420 Workstation

2019-10-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=197875 Gabriel Carter (jigneshsharm...@gmail.com) changed: What|Removed |Added CC||jigneshsharm.

[Bug 204815] qla2xxx: firmware is not responding to mailbox commands

2019-09-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204815 --- Comment #3 from Roman Bolshakov (r.bolsha...@yadro.com) --- Hi Martin, I can't tell for sure, because f8f97b0c5b7f7 introduces a regression fixed in 1710ac17547ac8b ("scsi: qla2xxx: Fix read offset in qla24xx_load_risc_flash()"). Here's the

[Bug 204815] qla2xxx: firmware is not responding to mailbox commands

2019-09-13 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204815 Martin Wilck (mwi...@suse.com) changed: What|Removed |Added CC||mwi...@suse.com --- Comm

[Bug 204815] qla2xxx: firmware is not responding to mailbox commands

2019-09-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204815 Roman Bolshakov (r.bolsha...@yadro.com) changed: What|Removed |Added Regression|No |Yes -- You are

[Bug 204815] qla2xxx: firmware is not responding to mailbox commands

2019-09-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204815 --- Comment #1 from Roman Bolshakov (r.bolsha...@yadro.com) --- Created attachment 284927 --> https://bugzilla.kernel.org/attachment.cgi?id=284927&action=edit firmware behaves properly -- You are receiving this mail because: You are watching t

[Bug 204815] New: qla2xxx: firmware is not responding to mailbox commands

2019-09-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204815 Bug ID: 204815 Summary: qla2xxx: firmware is not responding to mailbox commands Product: SCSI Drivers Version: 2.5 Kernel Version: 5.2-rc1 up to 5.3-rc8 Hardware: PPC-6

[Bug 204769] SCSI devices missing for disks attached to controller

2019-09-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204769 --- Comment #2 from Johannes Jordan (li...@lanrules.de) --- > The enclosure looks like its on another port correct ? > 0:1:x:x Funny enough, the enclosure is 0:3:0:0, and is properly exposed by both kernel versions. Btw., it seems like this is a

[Bug 204769] SCSI devices missing for disks attached to controller

2019-09-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204769 --- Comment #1 from lober...@redhat.com --- On Wed, 2019-09-04 at 15:18 +, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=204769 > > Bug ID: 204769 >Summary: SCSI devices missi

[Bug 204769] New: SCSI devices missing for disks attached to controller

2019-09-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204769 Bug ID: 204769 Summary: SCSI devices missing for disks attached to controller Product: SCSI Drivers Version: 2.5 Kernel Version: 5.12.11 Hardware: Intel OS: Linux

[Bug 204685] New: Sometimes Lenovo Yoga C630 WOS boot is delayed due to UFS initialization error

2019-08-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204685 Bug ID: 204685 Summary: Sometimes Lenovo Yoga C630 WOS boot is delayed due to UFS initialization error Product: SCSI Drivers Version: 2.5 Kernel Version: 5.2 Hardware:

[Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data

2019-08-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 --- Comment #11 from Yill Din (justinc...@yopmail.com) --- Thx for answer. I tried to patch my distribution-kernel with your bugfix. It works brilliant. I can use all my usb-devices again. -- You are receiving this mail because: You are the a

[Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data

2019-08-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 --- Comment #10 from Bart Van Assche (bvanass...@acm.org) --- This patch has been accepted in Martin's tree as commit dccc96abfb21 ("scsi: core: Reduce memory required for SCSI logging") and is on its way to kernel v5.4. If you need that patch in

[Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data

2019-08-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 Yill Din (justinc...@yopmail.com) changed: What|Removed |Added CC||justinc...@yopmail.com

[Bug 188061] On quad port QLE2564 can't add in target only 2 ports

2019-08-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=188061 Stefan Leitner (stefan.leit...@gmail.com) changed: What|Removed |Added CC||stefan.leit...

[Bug 204243] WARNING: possible circular locking dependency detected [sr_mod]

2019-07-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204243 --- Comment #3 from Thomas Schmitt (scdbac...@gmx.net) --- Sorry, i wrote "sr_block_open()" where i meant "sr_block_ioctl()". -- You are receiving this mail because: You are the assignee for the bug.

[Bug 204243] WARNING: possible circular locking dependency detected [sr_mod]

2019-07-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204243 Thomas Schmitt (scdbac...@gmx.net) changed: What|Removed |Added CC||scdbac...@gmx.net --

[Bug 204243] WARNING: possible circular locking dependency detected [sr_mod]

2019-07-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204243 --- Comment #1 from Erhard F. (erhar...@mailbox.org) --- Created attachment 283869 --> https://bugzilla.kernel.org/attachment.cgi?id=283869&action=edit kernel .config (5.2.1) -- You are receiving this mail because: You are the assignee for the

[Bug 204243] New: WARNING: possible circular locking dependency detected [sr_mod]

2019-07-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204243 Bug ID: 204243 Summary: WARNING: possible circular locking dependency detected [sr_mod] Product: IO/Storage Version: 2.5 Kernel Version: 5.2.1 Hardware: All

[Bug 204173] New: HDDs not detected as generic scsi through AACRAID

2019-07-14 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204173 Bug ID: 204173 Summary: HDDs not detected as generic scsi through AACRAID Product: SCSI Drivers Version: 2.5 Kernel Version: 5.2.0 Hardware: All OS: Linux Tre

[Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data

2019-07-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 --- Comment #8 from Bart Van Assche (bvanass...@acm.org) --- Thanks for testing! I will submit a more elaborate patch after the merge window has closed. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data

2019-07-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 --- Comment #7 from Jan Palus (jpa...@fastmail.com) --- The patch seems to fix the issue -- 5 successful boots in a row and no trace of failed percpu allocation. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data

2019-07-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 --- Comment #6 from Bart Van Assche (bvanass...@acm.org) --- The "size=4104" in the error message probably refers to the SCSI log buffer. >From drivers/scsi/scsi_logging.c: #define SCSI_LOG_SPOOLSIZE 4096 struct scsi_log_buf { char buffer

[Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data

2019-07-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 --- Comment #5 from Jan Palus (jpa...@fastmail.com) --- Created attachment 283597 --> https://bugzilla.kernel.org/attachment.cgi?id=283597&action=edit kernel config 5.2 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data

2019-07-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 --- Comment #4 from Bart Van Assche (bvanass...@acm.org) --- Can you share your kernel config? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data

2019-07-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 --- Comment #3 from Jan Palus (jpa...@fastmail.com) --- Not sure if that's relevant but reported percpu values differ between those versions 5.1: percpu: Embedded 46 pages/cpu s151552 r8192 d28672 u524288 5.2: percpu: Embedded 54 pages/cpu s18

[Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data

2019-07-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 --- Comment #2 from Jan Palus (jpa...@fastmail.com) --- >From 5.1.15 where it works reliably well. Now I've noticed that this error seems somewhat random -- in most cases insert fails but every 10 boots or so it succeeds. Note that attempt to loa

[Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data

2019-07-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 Bart Van Assche (bvanass...@acm.org) changed: What|Removed |Added CC||bvanass...@acm.org

[Bug 204119] New: scsi_mod: Could not allocate 4104 bytes percpu data

2019-07-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=204119 Bug ID: 204119 Summary: scsi_mod: Could not allocate 4104 bytes percpu data Product: IO/Storage Version: 2.5 Kernel Version: 5.2 Hardware: All OS: Linux Tree:

[Bug 197877] arcmsr fails to initialize Areca ARC-1110/ARC-1120 on some systems

2019-07-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=197877 k...@sognnes.no changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 71981] Writing session to CD does not update some important cached information

2019-06-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=71981 Roger (rogerx@gmail.com) changed: What|Removed |Added CC||rogerx@gmail.com --- Co

[Bug 199435] HPSA + P420i resetting logical Direct-Access never complete

2019-05-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199435 --- Comment #34 from Don (don.br...@microsemi.com) --- (In reply to Anthony Hausman from comment #33) > Hi Don, > > Did you send it to kernel.org? > Any idea when the patch will be available in the kernel? > > Is the patch compatible with the la

[Bug 199435] HPSA + P420i resetting logical Direct-Access never complete

2019-05-07 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199435 --- Comment #33 from Anthony Hausman (anthonyhaussm...@gmail.com) --- Hi Don, Did you send it to kernel.org? Any idea when the patch will be available in the kernel? Is the patch compatible with the last kernel longterm release 4.19? Thanks in

[Bug 199887] Fibre login failure on older adapters

2019-04-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199887 Matthew Whitehead (whitehe...@acm.org) changed: What|Removed |Added CC||whitehe...@acm.or

[Bug 199435] HPSA + P420i resetting logical Direct-Access never complete

2019-04-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199435 --- Comment #32 from Don (don.br...@microsemi.com) --- Created attachment 282479 --> https://bugzilla.kernel.org/attachment.cgi?id=282479&action=edit Patch to correct resets hpsa: correct device resets - Correct a race condition that o

[Bug 107371] I/O error when accessing disk in standby

2019-04-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=107371 j...@jki.io changed: What|Removed |Added CC||j...@jki.io --- Comment #2 from j...@jki.io

[Bug 107371] I/O error when accessing disk in standby

2019-04-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=107371 --- Comment #1 from flyse...@gmx.de --- still present in 4.19.29 -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 202859] Corruption when reading from disk with 32-core processor (megaraid_sas)

2019-04-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 Antti Tönkyrä (daeda...@pingtimeout.net) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 201313] pm80xx mpi_ssp_completion 1883:SAS Address of IO Failure Drive:

2019-03-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201313 --- Comment #7 from MasterCATZ (masterc...@hotmail.com) --- I am using a LSI / Avago 9302-16e 12Gb/s PCIe 3.0 SAS HBA Raid Controller 03-25688-00 with out any issues if you want anything tested I can put the PM8003 PMC-Sierra back in -- Y

[Bug 201313] pm80xx mpi_ssp_completion 1883:SAS Address of IO Failure Drive:

2019-03-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201313 Deepak Ukey (ukeydeepa...@gmail.com) changed: What|Removed |Added CC||ukeydeepa...@gmail.

[Bug 199435] HPSA + P420i resetting logical Direct-Access never complete

2019-03-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199435 --- Comment #31 from Anthony Hausman (anthonyhaussm...@gmail.com) --- (In reply to Don from comment #30) > I have been re-writing the eh_reset path recently. > > I found a race condition between the completion handler and the reset > handler. >

[Bug 201313] pm80xx mpi_ssp_completion 1883:SAS Address of IO Failure Drive:

2019-03-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201313 Marius Schiffer (marius.schif...@gmail.com) changed: What|Removed |Added CC||marius.schif

[Bug 199435] HPSA + P420i resetting logical Direct-Access never complete

2019-03-22 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199435 --- Comment #30 from Don (don.br...@microsemi.com) --- I have been re-writing the eh_reset path recently. I found a race condition between the completion handler and the reset handler. I have an update that I have been aggressively testing that

[Bug 202859] Corruption when reading from disk with 32-core processor (megaraid_sas)

2019-03-12 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 --- Comment #10 from Antti Tönkyrä (daeda...@pingtimeout.net) --- Created attachment 281751 --> https://bugzilla.kernel.org/attachment.cgi?id=281751&action=edit lscpu and debug-block-sdb output Both outputs in this attachment. -- You are rece

[Bug 202859] Corruption when reading from disk with 32-core processor (megaraid_sas)

2019-03-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 --- Comment #9 from Lei Ming (tom.leim...@gmail.com) --- >From the debugfs log, the blk-mq mapping is just one simple 1:N, all online 64 CPUs(128 all possible CPUs) are mapped to hw queue 0. I don't understand why this issue doesn't happen after

[Bug 202859] Corruption when reading from disk with 32-core processor (megaraid_sas)

2019-03-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 --- Comment #8 from Antti Tönkyrä (daeda...@pingtimeout.net) --- With single disk I was able to reproduce the problem with smp_affinity_enable=0 too. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 202859] Corruption when reading from disk with 32-core processor (megaraid_sas)

2019-03-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 --- Comment #7 from Antti Tönkyrä (daeda...@pingtimeout.net) --- Update, I did another run with slightly lighter load on single disk and reproduced the problem successfully. So can be reproduced when reading/writing on single disk. (SSD in this ca

[Bug 202859] Corruption when reading from disk with 32-core processor (megaraid_sas)

2019-03-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 --- Comment #6 from Antti Tönkyrä (daeda...@pingtimeout.net) --- After doing a 6 hour long run, I was unable to trigger the issue on a single disk. I'll go for another run now but I have attached the information requested above. Output of the comm

[Bug 202859] Corruption when reading from disk with 32-core processor (megaraid_sas)

2019-03-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 --- Comment #5 from Antti Tönkyrä (daeda...@pingtimeout.net) --- Created attachment 281717 --> https://bugzilla.kernel.org/attachment.cgi?id=281717&action=edit output of (cd /sys/kernel/debug/block/sdb && find . -type f -exec grep -aH . {} \;)

[Bug 202859] Corruption when reading from disk with 32-core processor (megaraid_sas)

2019-03-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 --- Comment #4 from Antti Tönkyrä (daeda...@pingtimeout.net) --- Created attachment 281715 --> https://bugzilla.kernel.org/attachment.cgi?id=281715&action=edit output of (cd /sys/kernel/debug/block/sdb && find . -type f -exec grep -aH . {} \;)

[Bug 202859] Corruption when reading from disk with 32-core processor (megaraid_sas)

2019-03-11 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 --- Comment #3 from Antti Tönkyrä (daeda...@pingtimeout.net) --- Created attachment 281713 --> https://bugzilla.kernel.org/attachment.cgi?id=281713&action=edit lscpu -- You are receiving this mail because: You are watching the assignee of the

[Bug 202859] Corruption when reading from disk with 32-core processor (megaraid_sas)

2019-03-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 Lei Ming (tom.leim...@gmail.com) changed: What|Removed |Added CC||tom.leim...@gmail.com

[Bug 202859] Corruption when reading from disk with 32-core processor (megaraid_sas)

2019-03-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 Antti Tönkyrä (daeda...@pingtimeout.net) changed: What|Removed |Added Summary|Corruption when reading |Corruption when

[Bug 202859] Corruption when reading from disk with 32-core processor

2019-03-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 --- Comment #1 from Antti Tönkyrä (daeda...@pingtimeout.net) --- Oh, and the script assumes that folders /mnt/{b,c,d,e,f,g} exist. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 202859] New: Corruption when reading from disk with 32-core processor

2019-03-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202859 Bug ID: 202859 Summary: Corruption when reading from disk with 32-core processor Product: SCSI Drivers Version: 2.5 Kernel Version: 4.14.x, 4.15.x, 4.19.x Hardware: x86

[Bug 199703] HPSA blocking boot on HP smart Array P400

2019-02-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199703 --- Comment #32 from Roberto M. (roby_program...@fastwebnet.it) --- (In reply to Loic S. from comment #31) > Hi > > I had the same issue. HP Smart Array P400 controller in a HP DL385 migrating > from Ubuntu 16.04 to 18.04, so a kernel going from

[Bug 199703] HPSA blocking boot on HP smart Array P400

2019-02-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199703 Loic S. (llze...@gmail.com) changed: What|Removed |Added CC||llze...@gmail.com --- Comme

[Bug 202425] 3w-9xxx: 3ware 9650SE-2LP RAID controller not working on AMD Ryzen system

2019-02-01 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202425 Bjorn Helgaas (bhelg...@google.com) changed: What|Removed |Added CC||bhelg...@google.com

[Bug 202425] 3w-9xxx: 3ware 9650SE-2LP RAID controller not working on AMD Ryzen system

2019-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202425 --- Comment #3 from Bart Van Assche (bvanass...@acm.org) --- On 1/30/19 7:42 PM, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=202425 > > --- Comment #2 from robert.smit...@protonmail.com --- > (In reply

[Bug 202425] 3w-9xxx: 3ware 9650SE-2LP RAID controller not working on AMD Ryzen system

2019-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202425 --- Comment #2 from robert.smit...@protonmail.com --- (In reply to Bart Van Assche from comment #1) > Can you bisect this issue to identify the commit that introduced this > regression? I found it. The commit is: 60db3a4d8cc9073cf56264785197ba75e

[Bug 201609] sysfs duplicate filename on driver loading Adaptec AIC-9410W

2019-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 --- Comment #10 from Emil Velikov (emil.l.veli...@gmail.com) --- (In reply to James.Bottomley from comment #9) > On Wed, 2019-01-30 at 11:43 +, bugzilla-dae...@bugzilla.kernel.org > wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=201609

[Bug 201609] sysfs duplicate filename on driver loading Adaptec AIC-9410W

2019-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 --- Comment #9 from james.bottom...@hansenpartnership.com --- On Wed, 2019-01-30 at 11:43 +, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=201609 > > Emil Velikov (emil.l.veli...@gmail.com) changed:

[Bug 201609] sysfs duplicate filename on driver loading Adaptec AIC-9410W

2019-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 --- Comment #8 from james.bottom...@hansenpartnership.com --- On Wed, 2019-01-30 at 14:21 +, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=201609 > > Bjorn Helgaas (bhelg...@google.com) changed: > >

[Bug 201609] sysfs duplicate filename on driver loading Adaptec AIC-9410W

2019-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 Bjorn Helgaas (bhelg...@google.com) changed: What|Removed |Added CC||bhelg...@google.com

[Bug 201609] sysfs duplicate filename on driver loading Adaptec AIC-9410W

2019-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 --- Comment #6 from Emil Velikov (emil.l.veli...@gmail.com) --- I stand corrected: The aic94xx revision file exposes a string (which look like hexadecimal number) based on the revision number. Regardless, the ideas proposed earlier are still appl

[Bug 201609] sysfs duplicate filename on driver loading Adaptec AIC-9410W

2019-01-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 Emil Velikov (emil.l.veli...@gmail.com) changed: What|Removed |Added CC||emil.l.veli...@g

[Bug 202425] 3w-9xxx: 3ware 9650SE-2LP RAID controller not working on AMD Ryzen system

2019-01-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202425 Bart Van Assche (bvanass...@acm.org) changed: What|Removed |Added CC||bvanass...@acm.org

[Bug 202425] New: 3w-9xxx: 3ware 9650SE-2LP RAID controller not working on AMD Ryzen system

2019-01-27 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=202425 Bug ID: 202425 Summary: 3w-9xxx: 3ware 9650SE-2LP RAID controller not working on AMD Ryzen system Product: SCSI Drivers Version: 2.5 Kernel Version: >= 3.11 Hardware: x

[Bug 201609] sysfs duplicate filename on driver loading Adaptec AIC-9410W

2019-01-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 --- Comment #4 from james.bottom...@hansenpartnership.com --- On Sat, 2019-01-26 at 03:13 +, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=201609 > > Pablo Ruiz García (pablo.r...@gmail.com) changed:

[Bug 201609] sysfs duplicate filename on driver loading Adaptec AIC-9410W

2019-01-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 Bart Van Assche (bvanass...@acm.org) changed: What|Removed |Added CC||bvanass...@acm.org

[Bug 201609] sysfs duplicate filename on driver loading Adaptec AIC-9410W

2019-01-25 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 Pablo Ruiz García (pablo.r...@gmail.com) changed: What|Removed |Added CC||pablo.r...@gmai

[Bug 199435] HPSA + P420i resetting logical Direct-Access never complete

2019-01-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199435 --- Comment #29 from Gaetan Trellu (gaetan.tre...@incloudus.com) --- The issue came back too... The only way so for to avoid the crashes has been to switch the card from RAID to HBA but at performances cost. -- You are receiving this mail becau

[Bug 199435] HPSA + P420i resetting logical Direct-Access never complete

2019-01-23 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199435 --- Comment #28 from Anthony Hausman (anthonyhaussm...@gmail.com) --- I have actually compiled the hpsa driver 3.4.20.141 into the kernel 4.19.13. I still have the same behavior, a heavy load (3000) and all disk of the controller unavailable. Bu

[Bug 201935] Writing data to tape broken

2018-12-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201935 --- Comment #4 from Todd Aiken (tai...@mvtech.ca) --- Just installed 4.19.11, and the fix works. Many thanks to everyone who helped squash this bug. :-) -- You are receiving this mail because: You are the assignee for the bug.

[Bug 201935] Writing data to tape broken

2018-12-18 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201935 --- Comment #3 from Bart Van Assche (bvanass...@acm.org) --- A fix has been queued for the 4.19 stable series and should be included in a 4.19.x stable kernel soon. See also https://lore.kernel.org/lkml/20181218163929.193192...@linuxfoundation.org

[Bug 201953] New: System freeze/hang during shutdown/restart (at " sd 0:0:0:0: [sda] Stopping disk")

2018-12-10 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201953 Bug ID: 201953 Summary: System freeze/hang during shutdown/restart (at " sd 0:0:0:0: [sda] Stopping disk") Product: SCSI Drivers Version: 2.5 Kernel Version: 4.* ish (i checked

[Bug 201935] Writing data to tape broken

2018-12-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201935 --- Comment #2 from Todd Aiken (tai...@mvtech.ca) --- I can confirm that reverting commit f3587d76da05f68098ddb1cb3c98cc6a9e8a402c does indeed solve the problem. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 201935] Writing data to tape broken

2018-12-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201935 Bart Van Assche (bvanass...@acm.org) changed: What|Removed |Added CC||bvanass...@acm.org

[Bug 201941] Errors with SanDisk and Samsung 64GB micro SD cards on ThinkPad E485

2018-12-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201941 --- Comment #1 from alexander.reim...@pm.me --- Created attachment 279911 --> https://bugzilla.kernel.org/attachment.cgi?id=279911&action=edit lspci -vvs 03:00.0 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 201941] New: Errors with SanDisk and Samsung 64GB micro SD cards on ThinkPad E485

2018-12-09 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201941 Bug ID: 201941 Summary: Errors with SanDisk and Samsung 64GB micro SD cards on ThinkPad E485 Product: IO/Storage Version: 2.5 Kernel Version: 4.19.4 Hardware: x86-64

[Bug 201935] New: Writing data to tape broken

2018-12-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201935 Bug ID: 201935 Summary: Writing data to tape broken Product: IO/Storage Version: 2.5 Kernel Version: 4.19.5 Hardware: Intel OS: Linux Tree: Mainline

[Bug 199435] HPSA + P420i resetting logical Direct-Access never complete

2018-12-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199435 --- Comment #27 from Gaetan Trellu (gaetan.tre...@incloudus.com) --- By compiling the hpsa kernel module from SourceForge on Ubuntu 16.04 with kernel 4.4 solved the issue for us. Steps: # apt-get install dkms build-essential # tar xjvf hpsa-3.4.2

[Bug 201609] sysfs duplicate filename on driver loading Adaptec AIC-9410W

2018-11-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 Vitaly Vlasov (vnig...@gmail.com) changed: What|Removed |Added See Also||https://bugzilla.redha

[Bug 201609] sysfs duplicate filename on driver loading Adaptec AIC-9410W

2018-11-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 --- Comment #1 from Vitaly Vlasov (vnig...@gmail.com) --- I found same error on Redhat bugtracker: https://bugzilla.redhat.com/show_bug.cgi?id=1443678 Some people says that kernel 4.9.x is not affected -- You are receiving this mail because: Yo

[Bug 201609] New: sysfs duplicate filename on driver loading Adaptec AIC-9410W

2018-11-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201609 Bug ID: 201609 Summary: sysfs duplicate filename on driver loading Adaptec AIC-9410W Product: SCSI Drivers Version: 2.5 Kernel Version: 4.18.16 Hardware: x86-64

[Bug 201583] New: 4.19.0 mpt3sas generates I/O Error while spinning up drives

2018-10-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201583 Bug ID: 201583 Summary: 4.19.0 mpt3sas generates I/O Error while spinning up drives Product: SCSI Drivers Version: 2.5 Kernel Version: 4.19.0 Hardware: All

[Bug 201199] hpsa blocking boot on HP smart Array P410

2018-10-26 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201199 --- Comment #8 from Seb Lu (se...@seblu.net) --- Hello, Any idea? Any test I can do to find what's wrong? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 199435] HPSA + P420i resetting logical Direct-Access never complete

2018-10-15 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=199435 --- Comment #26 from Gaetan Trellu (gaetan.tre...@incloudus.com) --- Moved from Ubuntu 16.04.5 to CentOS 7.5 with hpsa kernel module (kmod-hpsa-3.4.20-141.rhel7u5.x86_64.rpm) from HPE website. Running without kernel panic since more than a week.

[Bug 201313] pm80xx mpi_ssp_completion 1883:SAS Address of IO Failure Drive:

2018-10-04 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201313 --- Comment #4 from MasterCATZ (masterc...@hotmail.com) --- however it might also have something to do with serial number being read wrong? the drive is an SEAGATE ST33000650NS SM (NA01) Serial # 500605ba00b9be18 but the logs show [11125.2

[Bug 201313] pm80xx mpi_ssp_completion 1883:SAS Address of IO Failure Drive:

2018-10-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201313 --- Comment #3 from MasterCATZ (masterc...@hotmail.com) --- it might actually be part of this bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740701 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 201313] pm80xx mpi_ssp_completion 1883:SAS Address of IO Failure Drive:

2018-10-03 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201313 --- Comment #2 from MasterCATZ (masterc...@hotmail.com) --- it might be also related to the SEAGATE ST33000650NS as my other drives are HITACHI HUA723030ALA64SA and I used a spare and it formatted with fewer kernel errors, but still did have some

[Bug 201313] pm80xx mpi_ssp_completion 1883:SAS Address of IO Failure Drive:

2018-10-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201313 --- Comment #1 from MasterCATZ (masterc...@hotmail.com) --- pm80xx mpi_ssp_completion 1874:sas IO status 0x24 [ 708.424035] pm80xx mpi_ssp_completion 1883:SAS Address of IO Failure Drive:500605ba00b9cca2 [ 708.424241] sd 1:0:8:0: Power-on or dev

[Bug 201313] New: pm80xx mpi_ssp_completion 1883:SAS Address of IO Failure Drive:

2018-10-02 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201313 Bug ID: 201313 Summary: pm80xx mpi_ssp_completion 1883:SAS Address of IO Failure Drive: Product: IO/Storage Version: 2.5 Kernel Version: 4.18.11-041811-generic Hardware

[Bug 198975] Highpoint 840A RocketRAID Controller and drives are NOT detected by SCSI_HPTIOP kernel module

2018-09-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=198975 --- Comment #6 from Matthias Lippert (mae.lipp...@gmail.com) --- highpoint has ABSOLUTLY no interest to integrate in-kernel drivers for the rocketraid 800er series. also the raid controller CANNOT boot from RAID 6, RAID 5 yes but no bootable RAI

[Bug 201221] New: USB drive shows up with write protection enabled

2018-09-24 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201221 Bug ID: 201221 Summary: USB drive shows up with write protection enabled Product: IO/Storage Version: 2.5 Kernel Version: 4.14.44-4.19 Hardware: All OS: Linux

[Bug 201199] hpsa blocking boot on HP smart Array P410

2018-09-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201199 --- Comment #6 from Seb Lu (se...@seblu.net) --- Created attachment 278709 --> https://bugzilla.kernel.org/attachment.cgi?id=278709&action=edit controller version -- You are receiving this mail because: You are the assignee for the bug.

[Bug 201199] hpsa blocking boot on HP smart Array P410

2018-09-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201199 --- Comment #7 from Seb Lu (se...@seblu.net) --- Created attachment 278711 --> https://bugzilla.kernel.org/attachment.cgi?id=278711&action=edit lspci -- You are receiving this mail because: You are the assignee for the bug.

[Bug 201199] hpsa blocking boot on HP smart Array P410

2018-09-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201199 --- Comment #5 from Seb Lu (se...@seblu.net) --- Created attachment 278707 --> https://bugzilla.kernel.org/attachment.cgi?id=278707&action=edit bios version -- You are receiving this mail because: You are the assignee for the bug.

[Bug 201199] hpsa blocking boot on HP smart Array P410

2018-09-21 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=201199 --- Comment #4 from Seb Lu (se...@seblu.net) --- Created attachment 278705 --> https://bugzilla.kernel.org/attachment.cgi?id=278705&action=edit config for 4.15.0-22 (working ubuntu) -- You are receiving this mail because: You are the assignee

  1   2   3   4   5   6   7   8   9   10   >