kernel 5.15.221 does not recognize mbr partitions and therefore does not boot
https://bugzilla.kernel.org/show_bug.cgi?id=222016
Artem S. Tashkinov ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Bisected commit-id| |694e1b6aabe4cd359b42c44b54c
| |409c3147b6020
Component|Kernel |SCSI
Version|unspecified |2.5
Assignee|[email protected] |[email protected]
|rnel.org |
Product|Linux |IO/StorageSignature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=222016
Artem S. Tashkinov ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |CODE_FIX--- Comment #14 from Artem S. Tashkinov ([email protected]) --- Queued for 5.15.222:
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=222016
Richard Narron ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|CODE_FIX |------ Comment #15 from Richard Narron ([email protected]) --- Where is the new version of 5.15.x with the bugfix? I see nothing on kernel.org...
Programming manager John Moline used to have programmers who reported bug fixes as "done" before the code was installed into production.
He made sure that the fix was "done done" before closing it out.
I'm marking this bug as open until it is "done done".
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=222016
Bastiaan Welmers ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #16 from Bastiaan Welmers ([email protected]) ---
I can confirm this issue of not booting because sata devices are missing, after building with Ubuntu 22.04 kernel patches. (Every 5.15 build until 5.15.220 succeeded thus far and ran succesfully)
I unfortunately also can confirm that a build of the git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git branch queue/5.15 commit 731937a9e48136b71ba06095c68204a4f545efed is failing with "Error 2"
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=222016
--- Comment #17 from The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) --- (In reply to Bastiaan Welmers from comment #16)
Quoted 4 lines
I unfortunately also can confirm that a build of the git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git branch queue/5.15 commit
731937a9e48136b71ba06095c68204a4f545efedis failing with "Error 2"
What's the error? Is it related to the revert?
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=222016
--- Comment #18 from Bastiaan Welmers ([email protected]) ---
Update: good news, my build now succeeds and runs without problems on a Thinkpad T450s when using 38803ff4fab8 from git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git branch queue/5.15
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=222016
--- Comment #19 from Bastiaan Welmers ([email protected]) --- (In reply to The Linux kernel's regression tracker (Thorsten Leemhuis) from comment #17)
Quoted 8 lines
(In reply to Bastiaan Welmers from comment #16)
Quoted 4 lines
I unfortunately also can confirm that a build of the git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git branch queue/5.15 commit
731937a9e48136b71ba06095c68204a4f545efedis failing with "Error 2"What's the error? Is it related to the revert?
The error on 731937a9e481 seems to be:
[01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/drivers/mmc/core/host.c:[m[K In function '[01m[Kmmc_free_host[m[K':
[01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/drivers/mmc/core/host.c:664:26:[m[K [01;31m[Kerror: [m[Kpassing argument 1 of '[01m[Kcancel_work_sync[m[K'
from incompatible pointer type [[01;31m[K-Werror=incompatible-pointer-types[m[K]
664 | cancel_work_sync([01;31m[K&host->sdio_irq_work[m[K);
| [01;31m[K^~~~~~~~~~~~~~~~~~~~[m[K
| [01;31m[K|[m[K
| [01;31m[Kstruct delayed_work *[m[KIn file included from [01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/include/linux/rhashtable-types.h:15[m[K,
from
[01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/include/linux/ipc.h:7[m[K,
from
[01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/include/uapi/linux/sem.h:5[m[K,
from
[01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/include/linux/sem.h:5[m[K,
from
[01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/include/linux/sched.h:15[m[K,
from
[01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/include/linux/ratelimit.h:6[m[K,
from
[01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/include/linux/dev_printk.h:16[m[K,
from
[01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/include/linux/device.h:15[m[K,
from
[01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/drivers/mmc/core/host.c:12[m[K:
[01m[K/mnt/WDGREEN_1TB/bastiaan2/build/ubuntu-linux-5.15/include/linux/workqueue.h:466:50:[m[K [01;36m[Knote: [m[Kexpected '[01m[Kstruct work_struct *[m[K' but
argument is of type '[01m[Kstruct delayed_work *[m[K'
466 | extern bool cancel_work_sync([01;36m[Kstruct work_struct
*work[m[K);
| [01;36m[K~~~~~~~~~~~~~~~~~~~~^~~~[m[KFull screen log can be found on
https://users.welmers.net/bastiaan/731937a9e481-screenlog.0.txt
However, on the newer 38803ff4fab8 this error is gone.
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=222016
--- Comment #20 from Richard Narron ([email protected]) ---
I "fixed" the error in 5.15.221 by replacing the full drivers/scsi/ directory with the old directory from 5.15.220.
So I know that the bug is in the drivers/scsi directory...
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=222016
--- Comment #21 from Richard Narron ([email protected]) --- Where is this 38803ff4fab8 patch? What is it?
Can you give me a url for the patch?
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=222016
--- Comment #22 from Richard Narron ([email protected]) --- Kernel 5.15.222-rc1 works fine on Intel x86-64 and x86 systems
and on AMD AMD64 systems
When 5.15.222 is released and I test well, then I will close this bug
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=222016
--- Comment #23 from Marco ([email protected]) ---
Can also confirm that 5.15.222-rc1 looks good to me now (tested on Intel x86-64 and x86).
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=222016
Richard Narron ([email protected]) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |CODE_FIX--- Comment #24 from Richard Narron ([email protected]) --- I am closing this ticket.
Kernel 5.15.222 works fine on Intel x86-64 and x86 systems
and on AMD amd64 and x86 systems
Signature · 4 lines
You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.