Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]

Bug #1742630 reported by Saverio Proto
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Unknown
linux (Ubuntu)
Triaged
High
Unassigned
Artful
Triaged
High
Unassigned

Bug Description

I cannot boot from 4.13.0-21-generic

Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]

This Kernel bug was already fixed in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882414

Relevant discussion:
https://marc.info/?l=linux-scsi&m=151523964725984&w=2

Ubuntu needs to fix this, because otherwise _many_ people will complain about crashes when they upgrade from 4.9 (or 4.4) to 4.13, which Ubuntu defined as their new “HWE” kernel.

Saverio Proto (zioproto)
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1742630

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Saverio Proto (zioproto) wrote : Re: Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]

The Kernel does not boot at all, so it is not possible to collect the data with apport-collect

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Saverio Proto (zioproto) wrote :

I have tested this version linux-image-generic-hwe-16.04 4.13.0.26.46
It does not work for me

summary: - Booting from 4.13.0-21-generic leads to Oops: NULL pointer dereference -
- RIP: isci_task_abort_task+0x30/0x3e0 [isci]
+ PTI Kernels: Booting from 4.13.0-21-generic leads to Oops: NULL pointer
+ dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]
summary: - PTI Kernels: Booting from 4.13.0-21-generic leads to Oops: NULL pointer
- dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]
+ PTI Kernels: Booting from 4.13 leads to Oops: NULL pointer dereference -
+ RIP: isci_task_abort_task+0x30/0x3e0 [isci]
tags: added: artful kernel-da-key
Changed in linux (Ubuntu):
importance: Undecided → High
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Changed in linux (Ubuntu Artful):
status: New → Triaged
importance: Undecided → High
tags: added: pti
Changed in linux:
status: Unknown → Fix Released
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: PTI Kernels: Booting from 4.13 leads to Oops: NULL pointer dereference - RIP: isci_task_abort_task+0x30/0x3e0 [isci]

If this bug is happening with 4.13.0-21, it's probably not PTI related.

I'll build a test kernel with the commit you posted in the description and post it shortly.

tags: removed: pti
summary: - PTI Kernels: Booting from 4.13 leads to Oops: NULL pointer dereference -
- RIP: isci_task_abort_task+0x30/0x3e0 [isci]
+ Booting from 4.13 leads to Oops: NULL pointer dereference - RIP:
+ isci_task_abort_task+0x30/0x3e0 [isci]
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I built a test kernel with the patch posted here:
https://marc.info/?l=linux-scsi&m=151557324907914

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1742630

Can you test this kernel and see if it resolves this bug?

Revision history for this message
Saverio Proto (zioproto) wrote :

I have the kernel running and I confirm that it resolved the bug

Linux s0008 4.13.0-25-generic #29~lp1742630 SMP Thu Jan 11 18:42:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

thank you

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This bug and bug 1726519 are probably duplicates.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.