This patch set include some bug fixes for pm80xx driver.
Changes from V1:
For "Fixed kernel panic during error recovery for SATA drive" patch,
-Acquired the spin lock after aborting all the requests.
Deepak Ukey (3):
pm80xx : Fixed kernel panic during error recovery for
Added the logic for collecting IOP log respective to event log size.
Signed-off-by: Deepak Ukey
Signed-off-by: Viswas G
Reviewed-by: Jack Wang
---
drivers/scsi/pm8001/pm8001_ctl.c | 33 +
1 file changed, 17 insertions(+), 16 deletions(-)
diff --git a/drivers/sc
Disabling the SATA drive interface cause kernel panic. When the drive
Interface is disabled, device should be deregistered after aborting
all pending IO's. Also changed the port recovery timeout to 1 ms
for PM8006 controller.
V2:
-Acquired spin lock after aborting all r
Added support to read event log size from MPI configuration table
and export through sysfs.
Signed-off-by: Deepak Ukey
Signed-off-by: Viswas G
Reviewed-by: Jack Wang
---
drivers/scsi/pm8001/pm8001_ctl.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/scsi/pm800
On Tue, 2019-07-02 at 13:27 +0200, Maurizio Lombardi wrote:
> With a possibly faulty disk the following messages may appear in the logs:
>
> kernel: sd 0:0:9:0: timing out command, waited 180s
> kernel: sd 0:0:9:0: timing out command, waited 20s
> kernel: sd 0:0:9:0: timing out command, waited 20s
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:
https://bugzilla.kernel.org/show_bug.cgi?id=204119
Bart Van Assche (bvanass...@acm.org) changed:
What|Removed |Added
CC||bvanass...@acm.org
On 08/07/19 09:01:35, Ming Lei wrote:
> > > > > > > >
> > > > > > > > commit f664a3cc17b7d0a2bc3b3ab96181e1029b0ec0e6
> > > > > > > >
> > > > > > > > [...]
>
> 1) run the bcc biosnoop trace in one terminal after mounting the fs on the
> USB dirve
>
> 2) start the write test in another tem
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
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
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.
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.
On Tue, Jul 09, 2019 at 11:18:38PM +0200, Andrea Vai wrote:
> On 08/07/19 09:01:35, Ming Lei wrote:
> > > > > > > > >
> > > > > > > > > commit f664a3cc17b7d0a2bc3b3ab96181e1029b0ec0e6
> > > > > > > > >
> > > > > > > > > [...]
> >
> > 1) run the bcc biosnoop trace in one terminal after mount
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
Provide more information of fatal errros and auto-hibern8 errors
to improve debugging by extending extend existed UFS error history
framework.
Signed-off-by: Stanley Chu
Reviewed-by: Avri Altman
---
drivers/scsi/ufs/ufshcd.c | 11 ++-
drivers/scsi/ufs/ufshcd.h | 10 +-
2 files c
Remove "uic" term in below error history functions and structures
for more general usages,
struct ufs_uic_err_reg_hist;
void ufshcd_update_uic_reg_hist(struct ufs_uic_err_reg_hist *reg_hist,
u32 reg);
void ufshcd_print_uic_err_hist(struct ufs_hba *hba,
struct ufs_uic)err_reg_hist *
Currently only "interrupt-based" errors have their own history,
however there are "non-interrupt-based" errors which may be
fatal also needing history to improve debugging or help know
the health status of UFS devices.
For example,
- Link startup fail
- Suspend fail
- Resume fail
- Task or request
This patchset provides more information of fatal errros and auto-hibern8 errors
to improve debugging by keeping their error history as completed as possible.
Thanks Avri so much for prompt reviewing patchset v1.
I would like to post v2 to add one more patch "scsi: ufs: Add history of fatal
event
Currently UFS error history will be reset and lost during host reset
flow by ufschd_probe_hba().
We shall not reset it and then error history can be kept as completed
as possible to improve debugging.
In addition, fix a minor display error in ufshcd_print_err_hist().
Signed-off-by: Stanley Chu
19 matches
Mail list logo
