"spi-nor spi0.1:Software reset failed:-524" in shutdown screen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
New
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
AceLan Kao | ||
Jammy |
Won't Fix
|
Undecided
|
AceLan Kao | ||
Mantic |
Won't Fix
|
Undecided
|
AceLan Kao | ||
Noble |
Fix Released
|
Undecided
|
AceLan Kao | ||
linux-oem-6.5 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
AceLan Kao | ||
Mantic |
Invalid
|
Undecided
|
Unassigned | ||
Noble |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
There is a spi error message on the screen when shutting down the machine.
It won't hurt anything and all device work well in the next boot up.
Intel SPI controller doesn't support reset command, but our customer feel bad about this message.
[Fix]
Distinguish the error code -EOPNOTSUPP from -ENOTSUPP, and not showing the warnning when it's op not supported.
https:/
[Test case]
1. boot up the system with intel SPI controller on it
2. power off the system and check if there are spi software reset failed errors on the screen.
[Where problems could occur]
There is a minor risk of breaking user-space applications
that rely on specific return codes for unsupported operations. However,
this risk is considered low, as such use-cases are unlikely to be common
or critical.
Changed in linux (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in linux (Ubuntu Mantic): | |
status: | New → In Progress |
Changed in linux (Ubuntu Noble): | |
status: | New → In Progress |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in linux-oem-6.5 (Ubuntu Mantic): | |
status: | New → Invalid |
Changed in linux-oem-6.5 (Ubuntu Noble): | |
status: | New → Invalid |
Changed in linux (Ubuntu Jammy): | |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux (Ubuntu Mantic): | |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux (Ubuntu Noble): | |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
assignee: | nobody → AceLan Kao (acelankao) |
tags: | added: oem-priority originate-from-2036480 somerville |
Changed in linux-oem-6.5 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-jammy-linux-oem-6.5 removed: verification-needed-jammy-linux-oem-6.5 |
This bug is awaiting verification that the linux-oem- 6.5/6.5. 0-1010. 11 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- jammy-linux- oem-6.5' to 'verification- done-jammy- linux-oem- 6.5'. If the problem still exists, change the tag 'verification- needed- jammy-linux- oem-6.5' to 'verification- failed- jammy-linux- oem-6.5' .
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!