memtest86+ hangs during test nr.2 every time
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
While looking for the source of error messages by the kernel I tried to test the system's RAM with memtest86+ from the grub menu and memtest86+ starts fine but hangs within seconds during test nr. 2.
This happens not with the current version of memtest86+ from upstream (via a bootable cd image).
A fixed/updated memtest86+ would be great.
---
ProblemType: Bug
ApportVersion: 2.20.11-
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CasperMD5CheckR
CurrentDesktop: KDE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-01-26 (139 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 20HES0FW00
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.187.12
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: focal
Uname: Linux 5.4.0-74-generic x86_64
UnreportableReason: In diesem Bericht geht es um ein Paket, welches nicht installiert ist.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: False
dmi.bios.date: 10/19/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N1QET90W (1.65 )
dmi.board.
dmi.board.name: 20HES0FW00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad T470
dmi.product.name: 20HES0FW00
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1931846
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.