Some dmesg outputs from same machine running 20.04 and 22.04 :
########## 20.04 ##########
django@ASGARD:~$ dmesg | grep -Ei "ata4|sector|mtd"
[ 0.668757] ata4: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a280
irq 29
[ 0.985537] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 0.986510] ata4.00: ATA-8: Hitachi HDS721010CLA332, JP4OA3MA, max UDMA/133
[ 0.986812] ata4.00: ATA Identify Device Log not supported
[ 0.986815] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[ 0.990241] ata4.00: ATA Identify Device Log not supported
[ 0.990245] ata4.00: configured for UDMA/133
[ 0.990254] ata3.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 32), AA
django@ASGARD:~$ dmesg | grep -Ei "erro|warn|fail"
[ 0.461495] RAS: Correctable Errors collector initialized.
[ 0.637675] ACPI Warning: SystemIO range
0x0000000000001828-0x000000000000182F conflicts with OpRegion
0x0000000000001800-0x000000000000187F (\PMIO) (20210730/utaddress-204)
[ 0.637701] ACPI Warning: SystemIO range
0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion
0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
[ 0.637717] ACPI Warning: SystemIO range
0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion
0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210730/utaddress-204)
[ 0.637723] ACPI Warning: SystemIO range
0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion
0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
[ 0.637741] ACPI Warning: SystemIO range
0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion
0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210730/utaddress-204)
[ 0.637746] ACPI Warning: SystemIO range
0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion
0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
[ 0.987186] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330)
[ 0.988437] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to
previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 0.991691] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330)
[ 0.994698] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to
previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 5.955272] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro. Quota mode:
none.
########## 22.04 ##########
django@ASGARD:~$ sudo dmesg | grep -Ei "ata4|sector|mtd"
[sudo] Mot de passe de django :
[ 0.749555] ata4: SATA max UDMA/133 abar m2048@0xf7d1a000 port 0xf7d1a280
irq 29
[ 1.063160] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.064160] ata4.00: ATA-8: Hitachi HDS721010CLA332, JP4OA3MA, max UDMA/133
[ 1.064490] ata4.00: ATA Identify Device Log not supported
[ 1.064502] ata4.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[ 1.065584] ata3.00: 234441648 sectors, multi 1: LBA48 NCQ (depth
32), AA
[ 1.065959] ata4.00: ATA Identify Device Log not supported
[ 1.065962] ata4.00: configured for UDMA/133
[ 5.500484] systemd[1]: Starting Load Kernel Module mtdpstore...
[ 5.509953] mtd device must be supplied (device name is empty)
[ 6.096722] mtd device must be supplied (device name is empty)
[ 35.920387] ata4.00: exception Emask 0x10 SAct 0x4000 SErr 0x4890000 action
0xe frozen
[ 35.920394] ata4.00: irq_stat 0x0c400040, interface fatal error, connection
status changed
[ 35.920395] ata4: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
[ 35.920398] ata4.00: failed command: READ FPDMA QUEUED
[ 35.920399] ata4.00: cmd 60/b8:70:00:a2:df/00:00:5b:00:00/40 tag 14 ncq dma
94208 in
[ 35.920415] ata4.00: status: { DRDY }
[ 35.920418] ata4: hard resetting link
[ 39.236175] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 39.237909] ata4.00: ATA Identify Device Log not supported
[ 39.239613] ata4.00: ATA Identify Device Log not supported
[ 39.239625] ata4.00: configured for UDMA/133
[ 39.239679] blk_update_request: I/O error, dev sdb, sector
1541382656 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
[ 39.239721] ata4: EH complete
django@ASGARD:~$ sudo dmesg | grep -Ei "erro|warn|fail"
[ 0.539349] RAS: Correctable Errors collector initialized.
[ 0.718130] ACPI Warning: SystemIO range
0x0000000000001828-0x000000000000182F conflicts with OpRegion
0x0000000000001800-0x000000000000187F (\PMIO) (20210730/utaddress-204)
[ 0.718821] ACPI Warning: SystemIO range
0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion
0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
[ 0.718830] ACPI Warning: SystemIO range
0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion
0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210730/utaddress-204)
[ 0.718835] ACPI Warning: SystemIO range
0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion
0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
[ 0.718840] ACPI Warning: SystemIO range
0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion
0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210730/utaddress-204)
[ 0.718844] ACPI Warning: SystemIO range
0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion
0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
[ 1.064777] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330)
[ 1.064839] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to
previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 1.066762] ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330)
[ 1.066822] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to
previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 5.515808] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro. Quota mode:
none.
[ 35.920394] ata4.00: irq_stat 0x0c400040, interface fatal error,
connection status changed
[ 35.920395] ata4: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
[ 35.920398] ata4.00: failed command: READ FPDMA QUEUED
res 50/00:b8:00:a2:df/00:00:5b:00:00/40 Emask 0x10 (ATA
bus error)
[ 39.239655] sd 3:0:0:0: [sdb] tag#14 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_OK cmd_age=3s
[ 39.239679] blk_update_request: I/O error, dev sdb, sector
1541382656 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
########## END ##########
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Committed
Status in systemd source package in Focal:
Confirmed
Status in systemd source package in Jammy:
Confirmed
Bug description:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd
device must be supplied (device name is empty)" message is not the
cause of failed boots. This work around is only for those who are
annoyed by the error message, but are otherwise not experiencing any
issues.
If you are not able to boot your system, but you see this error
message, please open a separate bug with your journalctl and dmesg
logs.
# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i 's/modprobe@mtdpstore.service //'
/etc/systemd/system/systemd-pstore.service
# systemctl daemon-reload
[Impact]
Due to mtdpstore not being properly configured as a pstore backend,
when systemd-pstore.service tries to load the module, users get the
following error in dmesg:
[ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
[ 18.462685] mtd device must be supplied (device name is empty)
This is a distracting error for users trying to diagnose other system
issues, especially if their system does not boot after a kernel crash
and this is the only message displayed on the console.
[Test Plan]
* Force a kernel crash to populate /sys/fs/pstore, thus causing
systemd-pstore.service to start on the subsequent boot:
# echo 1 > /proc/sys/kernel/sysrq
# echo 1 > /proc/sys/kernel/panic
# echo c > /proc/sysrq-trigger
* When the system reboots, observe the error in dmesg:
# dmesg | grep mtd
[Where problems could occur]
If a system was relying on this pstore backend, and mtdpstore is built
as a module, it is possible for systemd-pstore.service to trigger
before mtdpstore is loaded, causing systemd-pstore to not copy the
contents of /sys/fs/pstore. Note however that before the patched
introduced as a result of bug 1978079, systemd-pstore.service would
not attempt to load *any* kernel modules.
[Original Description]
After updating my 22.04 system (possibly caused by Systemd update).
And now booting, dmesg has two errors:
'mtd device must be supplied (device name is empty)'.
See line 8 and 134 in the included logfile.
The system are booting as it should though, and the system are working
like it should no errors at all.
Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?
I have an EFI mounted at boot but it isn't used because I have
installed my system in legacy BIOS mode.
Is this maybe the culprit?
I could ignore the message but it isn't nice though.
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
