Backport upstream commit to Ubuntu 15.10 (Wily) SRU stream
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Canonical Kernel Team | ||
Wily |
Fix Released
|
Undecided
|
Tim Gardner | ||
Xenial |
Fix Released
|
Medium
|
Canonical Kernel Team |
Bug Description
== Comment: #0 - UMA KRISHNAN <email address hidden> - 2015-11-18 16:27:06 ==
---Problem Description---
When FC login times out, cxlflash resets the link. As part of reset, when the link comes back up, cxlflash driver calls scsi_scan_host() and in case previous scan is still running we get the message and stack dump on console/logs.
scsi host2: scsi_prep_
CPU: 16 PID: 55 Comm: kworker/16:1 Not tainted 4.2.0-439-f9a408a+ #1
Workqueue: events cxlflash_
Call Trace:
[c00000078bea7ae0] [c000000000a6e720] dump_stack+
[c00000078bea7b10] [c0000000006f539c] scsi_scan_
[c00000078bea7bb0] [d000000004085344] cxlflash_
[c00000078bea7c50] [c0000000000d8b64] process_
[c00000078bea7ce0] [c0000000000d9014] worker_
[c00000078bea7d80] [c0000000000e1630] kthread+0x110/0x130
[c00000078bea7e30] [c000000000009530] ret_from_
cxlflash 0009:00:00.0: cxlflash_
This message is alarming to customers. Community has already fixed this. We would like to see the upstreamed commit a4cf30e15ccea82
---uname output---
Linux tul83p1 4.2.0-444-5b49ef1+ #1 SMP Wed Nov 18 12:44:21 CST 2015 ppc64le ppc64le ppc64le GNU/Linux
Machine Type = 8286-42A
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Simply disconnecting the adapter and plugging it back in, triggers this scenario.
Contact Information = <email address hidden>
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
*Additional Instructions for <email address hidden>:
-Attach sysctl -a output output to the bug.
tags: | added: architecture-ppc64le bugnameltc-133324 severity-medium targetmilestone-inin--- |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Canonical Kernel Team (canonical-kernel-team) |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux (Ubuntu Xenial): | |
status: | Triaged → Fix Released |
Changed in linux (Ubuntu Wily): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
status: | New → In Progress |
Changed in linux (Ubuntu Wily): | |
status: | In Progress → Fix Committed |
tags: | removed: verification-needed-wily |
tags: |
added: verification-done-wily removed: architecture-ppc64le bugnameltc-133324 severity-medium targetmilestone-inin--- |
tags: |
added: architecture-ppc64le bugnameltc-133324 severity-medium targetmilestone-inin--- removed: verification-done-wily |
tags: | added: verification-done-wily |
tags: |
added: targetmilestone-inin1510 removed: targetmilestone-inin--- |
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- wily' to 'verification- done-wily' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!